SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Belgium Porting

The following topics are discussed in this guide:

- Belgium porting requirements

- Belgium porting restrictions

- Belgium porting process 

- Belgium porting timelines

- Belgium common rejections

- Belgium additional information

 

In Belgium we offer porting for the following number types:

 

Number type Number type prefix Capabilities
Local +32-1 to +32-9* Voice
Toll-Free +32-800 Voice
National +32-78 Voice

*you find BE Local Numbers prefixes with corresponding localities here

Belgium porting requirements

*per number type

ALL NUMBER TYPES

Requirements

Description
 

LOA

Put the name of your current provider as per invoice. This must be verified with operator name information available on public domain here.
 

Billing document

 Not older than 3 months.
 

Account SID

 ☑️
 

BE phone number regulations

To upload your documents please select
“Phone Numbers” > “Regulatory Compliance“ > “Bundles”
in your console menu or just follow the link: https://www.twilio.com/console/phone-numbers/regulatory-compliance/bundles.

Choose the country, phone number type and follow the instructions. Processing of the compliance documents may take up to several business days.

Once your documents have been accepted, please share the associated links that start with "BU" and "AD" along with the porting request.

 

Belgium porting restrictions

There are no known porting restrictions. 

Belgium porting process 

  1. Submit your porting request with all the requirements in place via this submission form. 
  2. Twilio validates the port request. If everything in Step 1 is correct, you can expect Twilio to approve your port request within 24 business hours.
  3. Twilio submits the number to the Carrier Partner. This can take up to 24 business hours.
  4. Twilio’s Carrier Partner reaches out to the current provider. Your request is submitted to your soon-to-be former service provider as a port request. During this time, do not close your account with your service provider and keep your numbers active. This can take around one week to complete.
  5. Response from the carrier. At this point, your request is either approved or rejected:
    • Approved: If approved, Twilio will notify you about a porting date. 
    • Rejected: Rejections can occur due to various reasons. For example, invalid VAT Number or invalid/incomplete range of numbers. Read more about common reasons for port request rejections below. Rejections may add an undetermined amount of time to your porting request.
  6. Twilio reaches out to you with a porting date. Twilio emails you with a porting date and time slot if known. Your number is on your Account and can be visible in the Twilio Console.
  7. Configure your number. It is critical to configure your number prior to the porting date. This will minimise the service downtime. You can configure the numbers from the Twilio Console.
  8. Your phone number is with Twilio. Once your number is routed to Twilio and everything works as expected, you can remove the number from your former provider.

Belgium porting timelines

Depending on complexity of the port, we can complete your port request within the approximate time frames listed below:

Local +32-1 to +32-9 2-4 weeks
Toll-Free +32-800
National +32-78

 

In case you wish to expedite your request please reach out to your current provider to confirm you are porting your number away from their service and to Twilio.

If the current provider rejects your port during the porting process, an additional time may be added from the time that the rejection is resolved.  

Belgium porting rejections

There are a number of factors that can delay port orders. Below is a list of the most common rejection reasons and how to address them. In each case, we would need to resolve the rejection to be able to proceed with the port.

 

Rejection Explanation How to solve the rejection
Unauthorised signatory LOA (Letter of Authorisation) is signed by an unauthorised individual
  1. LOA must be signed by the authorised user and/or owner of the number. 
    1. Update the signature and send the document to Twilio to resume your porting request
Incorrect Site Address Site address on the LOA (Letter of Authorisation) is not matching current provider’s records
  1. Ask your current provider what site address they have on records
    1. Update porting request with the correct address
    2. If site address was changed, update it with your current provider and let Twilio know to resume your porting request
Invalid/incomplete range of numbers Number you wish to port is part of a bigger numbering range
  1. Ask your current provider if there are any associated numbers to the one you wish to port / if number is part of a bigger range
    1. Include all associated numbers / range to the porting request
    2. If your current provider allows to break down the range, you can request them to do that and port a single number
      1. Once your provider breaks down the range, let Twilio know to resume your porting request

 

 
Inactive number Numbers are not currently in service with your current provider and/or you have outstanding charges on the account
  1. Contact your current provider to reinstate the number
    1. Once this is done, let Twilio know to resume your porting request

Unfortunately, we cannot contact your current service provider on your behalf. For security reasons, your current service provider will naturally refuse to provide us with your private and confidential information. 

For a more summarised view of porting requirements, please visit our guidelines page here. 

Belgium porting definitions

Belgian Institute for Postal services and Telecommunications (BIPT): federal regulatory body responsible for regulating the electronic communications market in Belgium.

 

Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk