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.

Number is “rejected” during the porting process

Sometimes, a request to port a phone number into Twilio can result in an initial rejection by the current carrier of that number.  These rejections occur for a variety of reasons, such as an incorrect PIN for an account, an address or zip code that doesn’t match the current carrier’s record, or a port request made by an unauthorized user on the account. You can read more about common reasons for port request rejections here. In nearly all cases, these rejections can be remedied by the rightful user of the phone number such that the port request will be able to proceed. However, rejections will inevitably delay the process of porting your number into Twilio. The surest way to reduce the likelihood of a port rejection is to obtain a Customer Service Record (CSR) from your current carrier. You can read more about obtaining a CSR here.


Have more questions? Submit a request
Powered by Zendesk