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.

Why was my friendly name not included in the Verify SMS?

Due to mobile carrier regulations, Verify might need to remove the friendly name from the message body. 

This is due to compliance, and our best-effort to ensure delivery of your OTP in this restricted destinations. 


For Singapore, we use different Alphanumeric Sender IDs and message template combinations, depending on several customer-specific criteria and the time period. To learn more about the different options, please take a look at Singapore Sender ID Handling.


If keeping the friendly name is essential for your business case, you can configure your own phone number to send the Verify SMS. However, you won't benefit from one of the advantages of Verify which is that we directly manage a global pool of short and long codes, therefore, customers don't need to buy or manage their own numbers.

Additionally, please be aware of the limitations a short / long code might have, you will only be able to use it for the country it is supported in and on the provider it has been provisioned for. Also, Verify reporting tools may not show messages sent through your own dedicated long/short codes that you bought and manage.

If you still prefer to use this workaround, please escalate to our Twilio Support Team.

Have more questions? Submit a request
Powered by Zendesk