Twilio registration for A2P 10DLC is now available for all customers. Please be aware as you register that there are still limitations as Twilio rolls out A2P 10DLC. These limitations are being removed over time, and this article is being updated accordingly as the situation changes.
Most importantly, please note that completing US A2P registration during the current stage does not instantly transition your message traffic to A2P 10DLC connections. Once you complete registration, Twilio will validate that your registration setup is correct before migrating your traffic to the new A2P 10DLC connections.
There are also some limitations that uniquely affect ISV-type customers. Those are listed separately below. Read on for details.
- Registration limitations
- Carrier limitations
- Throughput limitations
- MMS Limitations
- Special Use Cases not fully supported
- Limitations with sharing A2P Brand registration across multiple Twilio Account SIDs
- Limitations specific to ISV-type customers
- Other considerations
Registration limitations in A2P 10DLC
Subaccounts: It is not currently possible to create a Primary Business Profile on a subaccount. However, if you are a Direct customer and you complete registration of your Primary Business Profile and A2P Brand on your Twilio parent account, you can share it to your subaccounts. You can reach out to Support if you don't want this parent-to-subaccount profile sharing to take place. See Limitations with sharing A2P Brand registration across multiple Twilio Account SIDs below.
Carrier limitations in A2P 10DLC
Migration of T-Mobile traffic is currently paused, so for new registrations only AT&T traffic is being currently being migrated. Once T-Mobile enablement resumes, customers who have successfully registered their traffic for A2P will have it migrated automatically.
Throughput limitations in A2P 10DLC
As of July 12, the Trust Score you receive will dictate the throughput of your long code numbers toward AT&T. The final implementation of message sending throughput for all carriers, as outlined in Message throughput and Trust Scores, is still underway.
Messages toward Verizon and T-Mobile users continue to be handled as usual, with a sending rate of 1 MPS per Twilio +1 phone number. However, once your traffic is registered and moved to AT&T's A2P 10DLC route, your throughput toward AT&T mobile users will be dictated by your Trust Score.
MMS Limitations in A2P 10DLC
Twilio MMS traffic is not currently sent over A2P 10DLC. Customers registered for A2P 10DLC will continue to have their MMS traffic to T-Mobile and AT&T sent using our standard long code routes. We are working with carriers to fully support MMS over A2P 10DLC at a later stage.
Special Use Cases for A2P 10DLC not fully supported
When registering your A2P 10DLC Campaigns, some additional "Special" campaign use cases have been announced by AT&T, but support by other participating carriers has not yet been confirmed. Twilio has removed these use case options from our Console and API temporarily until they are confirmed to be supported by all carriers. For more information please see Special Use Cases for A2P 10DLC.
Limitations with sharing A2P Brand registration across multiple Twilio Account SIDs
Sharing from a primary Twilio Account SID to another primary account's subaccounts
If your business has multiple use cases spread out across multiple primary Twilio Account SIDs ("projects"), you can now request Twilio share your A2P Brand registration to another primary Twilio account. However, if the second primary Twilio account has subaccounts, you will not be able to share the (already-shared) Brand from that parent Account SID to those subaccounts.
This is an uncommon scenario, but if this applies to you, Twilio is working toward a solution, however there is no ETA. As of now, you can solve this by registering your A2P Brand again on any additional Primary Accounts that have subaccounts, and then share the Brand to those subaccounts.
Limitations specific to ISV-type customers
Getting the Trust Score for your registered clients
After you complete Brand registration for your clients (Secondary Brand Registration) via API, a Trust Score will be generated for the client; however, this score is not currently exposed by the API or Console.
In order to see your registered client's Trust Score, contact Twilio’s A2P 10DLC Onboarding Operations team via email@example.com and include:
- The Account SID corresponding to the client’s A2P registration
- The exact legal name of the client as submitted in their Business Profile
Please note, the Twilio A2P 10DLC Onboarding team can only retrieve a business’s Trust Score after you have completed the A2P Brand registration step for that client, as that is when the score is generated.
No phone number registration status for externally-registered Campaigns.
Twilio does not currently have the ability to retrieve number registration status for externally-registered Campaigns. If you are am ISV who registers Campaigns directly with TCR and associate those with Twilio numbers, we cannot currently confirm which of your Twilio numbers have been fully migrated to your A2P registration.
Short code numbers or Toll-Free numbers in your Messaging Service will not be affected by A2P 10DLC registration.
For customers who use Messaging Service number selection (passing a Messaging Service SID in your API requests instead of specific From numbers), any short code or Toll-Free numbers in your Messaging Service will continue to be prioritized over long code numbers. This is because of their higher MPS throughput – long code numbers continue to receive 1 MPS (see above).