Direct Brand US A2P 10DLC Overview
- Access to AT&T and T-Mobile (including Sprint) A2P 10DLC routes requires registration of your business ("Brand") and use cases ("Campaigns"). This registration is available through the Trust Hub (in the Twilio Console) and, for ISV-type customers, via API.
- Please see Limitations of A2P 10DLC pilot access for some information about the current state of A2P 10DLC.
- To see a list of the information required, see our support article How do I register to use A2P 10DLC Messaging.
US A2P 10DLC Overview
This “direct brand” guide is for companies who want to register their own business for A2P 10DLC messaging capabilities.
If you are an independent software vendor (ISV) undergoing this process for a client, please read our ISV US A2P 10DLC Onboarding Guide.
US Application-to-Person 10-Digit Long Code (A2P 10DLC) messaging is the latest offering from US carriers to help support the growing ecosystem of businesses texting their customers while protecting end-users from unwanted messages. 10-digit long codes have traditionally been designed for Person-to-Person (P2P) traffic only, causing businesses to be constrained by limited throughput and heightened filtering.
The launch and support of A2P 10DLC across all carriers in the United States provides good actors with increased deliverability and throughput, but also requires additional registration to build trust with carriers. There are associated fees with this registration process and also per-message carrier fees.
Please see our support article for associated fees.
It’s best to think of US A2P 10DLC in two main categories: routes, and registration. First, carriers prepare their routes ready for traffic on 10-digit long codes, after which they pass through additional fees per outbound message segment. Second, the carriers require that a message originator register their US A2P brand and messaging campaign use cases. Registered traffic immediately benefits from reduced filtering. Twilio has created a centralized process allowing customers to add and manage all necessary information via the Trust Hub.
Standard Brand vs. Starter Brand
Updates are coming to Twilio’s Starter Brand registration based on changes from The Campaign Registry (TCR) and mobile carriers. We will provide updates on how this change may impact US A2P 10DLC registration as soon as they are available. Brands with EINs will no longer be able to use Twilio's Starter Brand registration going forward.
In the meantime, if you are registering on behalf of an organization with an EIN/Tax ID, please complete a Standard registration.
Twilio offers three options for registering your business for US A2P 10DLC messaging: Starter Brand, Low Volume Standard Brand, and Standard Brand registration. To determine which of these is best for you, you should primarily consider your current and expected messaging traffic volume.
Note that if your business has a Tax identification number (such as an EIN), you are not eligible for a Starter Brand.
| Starter Brand | Low-Volume Standard Brand |
Standard Brand |
|
| Phone number limits | Up to five 10-digit long codes | 400 |
400 |
| Daily message volume |
1,000 SMS segments and MMS per day to T-Mobile (approximately 3,000 SMS segments and MMS per day across US carriers) |
Up to 6,000 segments per day |
2,000 up to unlimited SMS segments and MMS per day to T-Mobile, depending on your Trust Score |
Your business would be better suited for the Low Volume Standard Brand if you send fewer than 6,000 messages per day to the US and do not require high message throughput. To register for a Low Volume Standard Brand, you should follow the same steps, but skip secondary vetting.
Registration Guides
What’s next?
To learn more about US A2P 10DLC, please read the following resources:
Get help with A2P 10DLC
Need help building or registering your A2P 10DLC application? Learn more about Twilio Professional Services for A2P 10DLC.
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.
