SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site,, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to, 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.

What should I do to ensure a seamless transition of service during the porting process?

We never expect a loss of service when you port your numbers to Twilio. To ensure this seamless experience, there are two things that you should do:

  1. Continue your current service with your carrier, PBX, app, etc. for at least 10 days past the scheduled port date. For instance, you should continue to pay for existing phone service with your current carrier until you’ve verified that calls are routing to Twilio as expected. This way, if the scheduled porting time is delayed for any reason, you can ensure that your current coverage will continue.
  2. Make sure to fully test and configure your Twilio app at least 48-hours before your scheduled port date. Since port times occasionally vary, it’s imperative that you have your app up and running when the number re-routes to Twilio. If your app is not running and properly configured, your phone service won’t work as expected after the port occurs, even though traffic has been re-routed to Twilio.

As soon as your porting request has been submitted to Twilio, you can configure your phone numbers to receive and respond to incoming Twilio voice calls or text messages. This allows you to configure the webhooks for the phone numbers or associate them with an Elastic SIP Trunk, Messaging Service, Proxy Number Pool, etc., prior to traffic going live on the number.

Have more questions? Submit a request
Powered by Zendesk