A2P 10DLC Campaign Vetting Delays: Twilio cannot approve 10DLC Campaigns ourselves, and must rely on third parties who control our connections to carriers to sign off. These external processes are creating several week delays for our customers. We continue to escalate these issues and are working to reduce delays wherever possible. Further details will be shared in the Campaign Vetting Changes article as they become available.

What does it mean when my current carrier “releases” my number?

When a carrier releases a number from their RespOrg (Responsible Organization) over to Twilio, this means that this losing carrier has made the number available for us to port. Releasing a number from a carrier’s RespOrg does not mean that the number has finished porting. Once a number’s RespOrg is released to Twilio, we must work with carriers to reconfigure the number for the new network routing before completing the final porting process. It’s standard industry practice for a losing carrier to continue service on a number for 10 days after that number has been released to a different carrier’s RespOrg. This overlapping coverage is designed to ensure that a number will not have a lapse in coverage during the porting process.

After you submit your port request, we’ll monitor your number’s RespOrg throughout the early stages of the porting process to ensure that we know when the number is released to Twilio’s RespOrg. It’s important to note that we can’t start the process of re-routing your number to Twilio until it has been released to us by your current carrier.

When your number has finished configuring, we’ll provide you with a completion date for your port request. You’ll want to make sure to have your Voice and/or Messaging URLs configured well in advance of the final port date so you can ensure the number will be working when the porting process completes.

Have more questions? Submit a request
Powered by Zendesk