How should I configure my short code messaging application during a live migration to Twilio?
Because carriers don’t all switch traffic at the same time, you’ll need to modify your application to ensure that inbound messages reach your application and outbound messages reach your end user during the migration from one provider to another. We recommend the following process when modifying your application for a migration:
- Your receiving system—the application that processes inbound messages from Twilio and the previous short code provider—must be configured to receive messages from both short code providers for the period of the migration.
- Configure your application to send via Twilio by default. Using message delivery information, you can determine whether or not a message has been sent successfully. If a message fails to send, attempt to send the message again via the old provider.
Once all carriers have migrated their traffic to Twilio, the Twilio Short Code Operations Team will notify you, at which point you may discontinue service with your existing provider and completely migrate all short code traffic to Twilio.
If your short code migration configuration does not or cannot be set up in this way, please contact us at email@example.com or your Account Manager to discuss how your short code should be configured.
For details on how to migrate your short code to Twilio, please see here.
If you would like Twilio to manage your short code lease with Neustar/CSCA, please review our short code lease transfer instructions here.
Please email us at firstname.lastname@example.org with any questions!