- 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.
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.
In this guide, you will find a detailed explanation of how to register:
- A Twilio Business Profile.
- Access to the US A2P 10DLC ecosystem.
- SMS campaign use cases within the ecosystem.
Prefer to watch a walkthrough? Check out our video of the onboarding process:
US A2P 10DLC registration will be available starting in phases through the Twilio Console and via API. To see a list of the information required, see our support article How do I register to use A2P 10DLC Messaging.
Onboarding your US A2P brand and campaign use cases typically requires a single day of work, involving form fills and click-throughs. After you complete this process, you will benefit from lower filtering. When increased rate limits launch, you will automatically inherit those capabilities.
Actions required (see below for step-by-step instructions):
- Within the Trust Hub in the Twilio Console, create a Twilio Primary Business Profile.
- Register a “US A2P brand” for US A2P10DLC capabilities.
- Register new campaign use case and link to a Messaging Service.
Before you begin the registration process for A2P10DLC, collect the following information to ensure a smooth onboarding flow:
Please note: If you have a US entity or an International Tax ID, use your EIN to register your business profile and to avoid brand registration failures. DUNS numbers are not accepted. US Social Security Numbers are also not accepted for sole proprietorships; in order to complete Standard registration you need to have an EIN or (for non-US entities) another form of business ID.
|Point(s) of Contact||
One authorized representative with the following info:
Providing a second authorized representative is optional.
Within the Trust Hub in the Twilio Console, create your Twilio Business Profile. This step validates your business identity, and you will only need to do this once.
If you are opted into the new Twilio Console Beta experience, you can find the Trust Hub under Account > Trust Hub > Customer profiles.
If you are on the legacy version of the Twilio Console, locate Trust Hub in the left-hand navigation, under the Home icon.
The submission of your Business Profile may take up to 72 hours for approval.
You will need to include:
- Under Business Details: the Business name.
- Under Business Address: the Business Address and other metadata.
- Under Business Information: the Business’ identity within the ecosystem, the Business type, ID, industry, website URL, and region information.
While registering your business information, you will also provide:
- Under Authorized Representatives: information about Authorized Representative(s) associated with your Business Profile.
- Under Notification Settings: an email address for notifications about the status of your Business Profile.
Make sure to review your business profile information under Review and Submit before submitting.
Prior to brand registration, Government entities will still create a Business Profile as normal. We recommend that Government customers should choose Non-profit corporation from the Business Type dropdown, and Government from the Business Industry dropdown, as shown below:
Prior to brand registration, non-profit organizations will still create a Business Profile as normal. We recommend that non-profit customers should choose Non-profit corporation from the Business Type dropdown, and Not for Profit from the Business Industry dropdown:
Business Profile or Customer Profile?
As of April 2021, Twilio Trust Hub only supports Customer Profiles for business customers, so you will only find the option to create a primary Business Profile within the Customer Profile section of the Trust Hub. Down the road, Trust Hub will also support profiles specific to Government agencies and non-profit organizations. For now, when you create a profile, you will create a profile called a “Business Profile”. There is no practical distinction between this and the Customer Profile at present.
Next, register your newly created Business Profile for A2P 10DLC capabilities by creating a US A2P brand. This step will register your business for US A2P10DLC capabilities, as well as calculate your Trust Score. For more information on Trust Scores, see below.
You will need to include:
- Your registered Business Profile (from Step 1).
- Your Company type and stock information (if public).
Once you hit the Register button, Twilio will submit your application for approval. Approval typically occurs within a few minutes of submitting.
As of July 22, 2021. Government agencies are now able to register for US A2P Messaging.
Government agencies are eligible for increased messaging throughput on the T-Mobile network, regardless of their campaign use case. Verified Government brands will receive unlimited daily message caps on T-Mobile*. Throughput on AT&T will be determined based on the campaign use case.
*Standard Twilio platform messaging rate limits still apply.
To successfully register and unlock increased throughput, it is critically important that public sector customers select Government as their Company Type during registration:
Providing accurate information about your agency and selecting Government as the company type during brand registration will trigger automatic vetting of your organization. If confirmed by TCR as a Government entity, the above increased throughput will be applied.
Government agencies can begin to register with all Standard Campaign use cases, and will also be eligible for the Emergency Special Use Case. If you will be sending alerts that meet the definition of the Emergency use case, please see our support article on Special Use Cases for more information.
To successfully register and unlock increased throughput, it is important that non-profit organizations select Non-Profit as their Company Type during registration:
Registering as a non-profit will ensure that you are able to qualify for special use cases that are reserved for non-profit entities. These special use cases offer additional pricing and/or throughput benefits.
When registering your brand with the Non-Profit company type, TCR will automatically perform vetting to confirm the specific non-profit tax status of your organization: for example, 501(c)(3), 501(c)(4). The specific 501c status will have an impact on which campaign use cases your non-profit will qualify for.
Examples of this are:
- 501(c)(3) non-profits will qualify for the Charity/501(c)(3) special use case, which will provide substantial discounts on A2P carrier fees.
- 501(c)(4), 501(c)(5), and 501(c)(6) non-profits will qualify for the Political special use case, which will provide increased messaging throughput for advocacy-related messaging.
Once you’ve registered your brand as a non-profit, you can move on to registering campaign use cases for non-profits.
When you register your A2P Brand, you will receive a Trust Score that determines your long code messaging throughput to US networks as well as daily message limits with T-Mobile. To help ensure that you receive the highest possible throughput, Twilio provides an additional vetting process.
As a direct brand registering with a primary Business Profile, Twilio offers Automated Secondary Vetting and will automatically submit your brand for secondary vetting at no cost to you as part of the brand registration process. Secondary vetting is an automated additional review process which can lead to increased throughput and messaging limits. With Automated secondary vetting, you don’t have to take any additional action to benefit from this additional review process upon completing your US A2P brand registration.
For more information, please see our support article on Secondary Vetting for A2P 10DLC.
Please note: If you have a US entity or an International Tax ID, use EIN to register your business profile and to avoid brand registration failures. Do not use a DUNS number.
Note: As a Sole Proprietorship, use your EIN number to register your business profile. DUNS and SSN are not accepted values.
In order to obtain the best possible Trust Score, you should provide accurate, up-to-date information. This includes:
All companies creating a Business Profile must provide their Tax ID. For non-US companies, a Tax ID from your respective country is preferred.
For private and public companies, the provided EIN and Legal Company Name has to match registration sources. The most common errors are:
- The incorrect name is added, including the name of the messaging provider, or a trade or fictitious name of the company instead of the official legally registered name.
- The number entered in the EIN field is not a valid EIN or home country company ID number.
- The DUNS number has been added into the EIN field.
The following information will help you prepare accurate US EIN and Tax ID information for review:
- For companies with presence in the US, a US EIN is required.
- For non-US companies, the number provided in the EIN/Tax ID field has to match any of the fully automated sources available.
- A Dun & Bradstreet DUNS number is accepted only if no tax number is available, or if you do not wish to register for US A2P messaging and only want to register for Shaken/Stir.
- For non-profit and political organizations, the EIN has to match the Legal Company Name available in the list of Tax-Exempt Organizations or Registered Political Organizations.
For all entity types, a mismatch in one of the following may result in a lower Trust Score:
- Address/Street line
- Postal Code/Zip Code
Submitting the address of a local branch or any address that is different from the official registered company address may produce a mismatch that lowers your Trust Score.
Public companies’ stock ticker symbol and their designated stock exchange must match available sources. Available stock ticker values are:
The following factors will impact the Trust Score, but cannot be influenced by data submitted:
- Company size — For all companies, points are earned for the detected size of the company based on independent sources of employee count and revenue.
- Years in operation — All companies earn points for their years in operation and domain age.
Once you have created and registered your Business Profile and US A2P brand, it’s time to register a campaign use case for sending messages over A2P 10DLC routes.
Examples of campaign use cases are marketing messages and order confirmations. A specific US A2P brand — like the one you created in Step 2 — may have one or more campaign use cases associated with it, such as one for marketing notifications and another for order confirmations. However, the registration process is the same for each campaign use case that you create. For more information on campaign use cases, please see our Support FAQ on A2P 10DLC.
Campaign use case registration may take several minutes to complete. After that, any phone number within the connected Messaging Service will be identified as A2P 10DLC with the associated campaign use case; you should see lower filtering.
For more information on how to add a phone number to your Messaging Service, please read our PhoneNumber Resource API reference page.
You’ll need the following information for the campaign use case creation process:
- The Messaging Service to be associated with the campaign.
- The A2P use case type — you can view the full list in this List of Campaign Types.
- The use case description.
- Two sample messages, each up to 1024 characters long.
- At least one Twilio Phone Number to add to the Messaging Service’s Sender Pool.
You can purchase a Twilio Phone Number ahead of time by either visiting the Phone Numbers section of the Twilio Console or from the command line with the Twilio CLI:
twilio phone-numbers:buy:local --country-code US --sms-enabled
When you’re ready to register a campaign use case, decide whether you want to Create a new Messaging Service or Use an existing Messaging Service, then click Continue:
To register a campaign use case, you must link it to a Messaging Service. If you selected Create a Messaging Service on the last page, you wil need to create a Messaging Service by providing a memorable name, and select what you will be using the Messaging Service for:
Remember: each Messaging Service should map to a single campaign use case.
When you’ve finished editing your campaign use case, don’t forget to hit the Save and continue button.
If you currently do not use Messaging Services, you do not need to make any changes to your code. You can continue to pass a phone number in the
From field when sending a message. Your phone numbers will need to be in a Messaging Service associated with your campaign use case, but it is not necessary to send your Messaging Service SID in your API requests. However, you will need to add those phone numbers to a Messaging Service for SMS campaign use case registration purposes. Using a Messaging Service also allows you to group phone numbers together for similar campaign use cases, making the registration process more straightforward.
In the Add Senders section, select the phone numbers to add to your Messaging Service Sender Pool. If you already have available numbers — those not attached to other Messaging Services — you can select them under Numbers available for association.
If you do not have any available numbers, click the Buy a new number link, which will take you to the Phone Numbers section of the Twilio Console to purchase one. Once you have purchased an SMS-capable number, you can return to the Trust Hub and reload the page.
In the Set Up Integration section, you will configure how your Messaging Service will integrate with your application and handle inbound messages. There are four options:
- Defer to sender’s webhook will use the HTTP webhook as defined for the given Phone Number (“sender”). This is default option.
- Drop the message will ignore incoming messages.
- Send a webhook will send an HTTP webhook request for incoming messages.
- Autocreate a Conversation will create new Conversations — please see Twilio Conversations Autocreation documentation for more details.
You also use this section to set up delivery status callbacks and set the validity period for unsent messages.
After hitting Save and continue, you’ll go to the Register Campaign Use Case screen. Here, you will need to enter:
- The A2P campaign use case.
- A description of the campaign use case.
- Two sample messages for the campaign use case.
- Select whether your messages will include embedded links and/or phone numbers.
- Agree to the terms and conditions, as well as the monthly carrier fees associated with your campaign use case.
Don’t forget to hit the Register campaign use case button at the end.
Once your campaign use case registration is approved, you will see an on-screen message indicating that your registration flow is complete:
At this point, you can register additional campaign use cases and view all of your registered US A2P brands.
Congratulations, you have successfully registered for US A2P Messaging capabilities by creating a Business Profile, submitting a US A2P brand, and registering a campaign use case associated with a Twilio Messaging Service!
A2P 10DLC brand and campaign registration for all 501(c) Non-profit Organizations is now available as part of Twilio’s A2P 10DLC Console onboarding experience.
527 Political Organizations should wait until further notice to register their campaign use cases. Support for this use case is coming soon, and you will be notified once it is available.
501(c)(3) brands vetted by TCR will be able to register for the following 10DLC use cases:
- Charity/501(c)(3) — Communications from a registered 501(c)(3) aimed at providing help and raising money for those in need.
- Emergency — Notification services designed to support public safety/health during natural disasters, armed conflicts, pandemics, and other national or regional emergencies.
A majority of 501(c)(3)s should register using the Charity/501(c)(3) special use case, unless your messaging meets the definition of Emergency above. Charity/501(c)(3) is a dedicated campaign type for 501(c)(3)s that provides significant carrier fee discounts to support social impact messaging.
All standard use cases will be disabled for 501(c)(3)s and will not appear in the Available A2P campaign use cases dropdown in the Console during campaign registration. This is to ensure that 501(c)(3)s can take advantage of carrier fee discounts associated with the Charity special use case.
501(c)(4), 501(c)(5), and 501(c)(6) organizations will be able to register for the following 10DLC use cases:
- Political — Part of an organized effort to influence decision making of a specific group.
- Standard — For all other messaging that doesn’t meet the definition of Political or Emergency.
- Emergency — Notification services designed to support public safety/health during natural disasters, armed conflicts, pandemics, and other national or regional emergencies.
Any advocacy-related messaging should be registered using the Political special use case. Political campaigns will receive increased messaging throughput. 501(c)(4)s, 501(c)(5)s, and 501(c)(6)s will not be required to provide a Campaign Verify token to register with the Political special use case.
All non-political messaging should be registered with either standard use cases or the Emergency special use case.
Please see our support article for detailed information on fees and throughput for special use case types.
Other 501(c) Non-profit Designations
All other non-profit designations should register their campaigns using standard use cases.
527 political campaigns, parties, or action committees will be required to register their organization with Campaign Verify (CV) and provide a CV token during A2P registration to register campaign use cases. Support for this registration is coming soon.
We recommend that 527s take two actions now:
- Register with Campaign Verify now to receive your CV token as a verified political sender.
- Register your A2P brand with Twilio now, and return to register your campaigns when support for 527s registering with the Political use case is launched. We will notify you via email when this happens.
Please Note: Emergency use case registration requires additional carrier approval.
There are 5 Special Campaign Use Cases which require additional carrier review (post-approval) of all attempted registrations immediately following registration:
- Agents, franchise, local branches: brands that have multiple agents, franchises or offices in the same brand vertical, but require individual localized numbers per agent/location/office.
- Proxy (formerly Conversational): peer-to-peer app-based group messaging with proxy/pooled numbers.
- Emergency: notification services designed to support public safety/health during natural disasters, armed conflicts, pandemics, and other national or regional emergencies.
- Social: communication between public figures/influencers and their communities.
- Sweepstakes: all gambling and sweepstakes messaging.
Post-approval for these special use cases is required before the phone numbers on the campaign are registered for A2P 10DLC and before unlocking associated pricing or throughput benefits available. Carrier review for post-approval campaigns takes an average of 7 days.
Campaigns requiring post-approval can either be approved or rejected by carriers. If approved, all SMS messages sent or received from the phone numbers in the Messaging Service you used to register the campaign will be routed as registered A2P messaging traffic. If rejected, you will not be able to send or receive A2P-registered SMS messages from the phone numbers in the Messaging Service until you re-register your campaign with an automatic approval use case.
During the "Register Campaign Use Case" section of the registration process, click the Available A2P campaign use cases dropdown menu. The campaign use cases types that require post-approval are categorized as Requires Carrier Review:
Select your A2P campaign use case and continue with the setup process for your Messaging Service.
After registering a campaign requiring post-approval, your campaign will be updated with a status of "In Progress" while the carriers review it. Your traffic will not be moved to registered A2P routes until approved by carriers. If you are already sending messages using the associated Messaging Service on unregistered SMS routes, this will continue to function as normal in this state.
You will receive an email from Twilio with the results of the carrier review after it is completed. Carrier review takes an average of 7 days.
You will either be approved or rejected by the carriers.
If approved, your messaging traffic will be successfully registered on A2P routes in accordance with the pricing and throughput of the selected campaign type. Your campaign will be marked as "Verified" in the Console.
If rejected, you will have the opportunity to resubmit your campaign with a different use case that will be automatically approved by the carriers. Your campaign status will be marked as "Failed" in the Console.
To learn more about US A2P 10DLC, please read the following resources: