Limitations of A2P 10DLC pilot access

Twilio is partnering with carriers on a phased onboarding approach to register customers for A2P 10DLC in the United States. We are sending invitations to customers in stages to participate in registration. As of April 27, 2021, we are in a pilot stage for A2P 10DLC onboarding.

If you have been granted access to onboarding via a targeted email notification from Twilio, please be aware that there are limitations during the A2P 10DLC pilot stage. These limitations will be removed over time, and will not be present at the full launch of A2P 10DLC.

Most importantly, please note that completing US A2P registration during the pilot 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 who use our pilot A2P registration APIs to register their clients. Those are listed separately below. Read on for details.

Article contents:

Carrier limitations in A2P 10DLC pilot stage

Once you complete registration and are ready to enable A2P 10DLC toward AT&T, our team can enable your Twilio Account SID to use AT&T’s A2P route for long code. In the initial pilot stage, this will not be done automatically, to give you the opportunity to review your Trust Score and the messaging throughput (MPS) you will receive (see “Throughput limitations” below).

If you complete registration and do choose to enable A2P 10DLC toward AT&T, this will give you the benefit of higher deliverability with lower filtering risk toward AT&T. You will pay the same fees as you would otherwise, and enjoy reduced fees once AT&T increases the cost of unregistered traffic (date TBD).

Registered clients in the initial pilot stage will NOT have any message traffic moved to T-Mobile’s A2P connection until further notice. We will provide an update once this becomes available.

Throughput limitations in A2P 10DLC pilot stage

In the initial pilot stage, the TCR Trust Score you receive will dictate the maximum throughput of your long code numbers toward AT&T, however, your throughput will still be dependent on how many numbers you have. The final implementation of message sending throughput as outlined in Message throughput and Trust Scores is still underway.

In the initial pilot stage, you will continue to receive 1 MPS per Twilio +1 phone number, but your maximum throughput toward AT&T only will be dictated by your TCR Trust Score. If you have more MPS on Twilio than you receive in throughput to AT&T based on your Trust Score, Twilio will queue those messages toward AT&T. 

This means if you have fewer Twilio long code numbers than the throughput you receive toward AT&T, you will send at a lower throughput than you have been allocated. 

If you have more Twilio +1 long code numbers than the throughput you receive toward AT&T, you may be limited by the assigned AT&T throughput.

Messages toward Verizon and T-Mobile will continue to be handled as usual during the initial pilot stage, with a sending rate of 1 MPS per Twilio long code phone number

Limitations with sharing A2P Brand registration across multiple Twilio Account SIDs

If your business has multiple use cases spread out across multiple Twilio Account SIDS (multiple primary accounts, or primary and subaccounts), we recommend onboarding only your main Twilio account at this time. There is currently a limitation that prevents customers with multiple Twilio Account SIDs to share the same US A2P Brand registration.

Therefore, our recommendation is to prioritize registration of your main Twilio account (i.e. the one that is most important to your operations). Once it is possible to share your US A2P Brand registration across your remaining Twilio accounts, we will provide a means to do so.

Limitations specific to ISV-type customers using the ISV registration API

You must use the API to register your clients

Twilio is currently working on support for registering Secondary A2P Brand profiles via the Twilio Console. Until this is complete, you must use the API provided to register your clients.

Getting the TCR Trust Score for your registered clients

After you complete Brand registration for your clients (Secondary Brand Registration) via API, a TCR 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 TCR Trust Score, contact Twilio’s A2P 10DLC Onboarding Operations team via 10dlc-onboarding@twilio.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 TCR Trust Score after you have completed the A2P Brand registration step for that client, as that is when the score is generated.

Considerations when using >50 long codes for one use case

If you have more than 50 Twilio US/Canada long code numbers in a single Messaging Service, you can complete A2P registration, but in order to move your messaging to T-Mobile later, you will need to either reduce your phone number count below 50 or complete a T-Mobile Special Business Review to continue operating with >50 phone numbers in a single campaign use case (the fee for a T-Mobile Special Business Review is $5000, but this fee has been waived until further notice).

For this reason, we recommend that customers in prioritize onboarding campaign use cases with fewer than 50 Twilio phone numbers. In order to prepare to move your messaging traffic to T-Mobile’s A2P connection when it becomes available, do not move numbers between Messaging Services with registered A2P campaign use cases, or add more numbers to the Messaging Service after completing registration.

Other considerations

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 during the initial pilot (see above).

Have more questions? Submit a request
Powered by Zendesk