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 these restricted destinations. 

Singapore

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.

Canada

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.

Turkey

For Turkey, you'll need to register your own Sender ID to send your friendly name in the verification messages. If you don't have a preregistered Sender ID, we'll send your traffic using the TWVerify sender, appending the signature Sent via TWVerify.

To ensure compliance with local regulations, the Custom Templates feature will not be available in Turkey.