What is A2P 10DLC?
10DLC stands for 10-digit Long Code. 10DLC messaging lets businesses send sanctioned Application-to-Person (A2P) messaging traffic over local phone numbers, also known as “long codes”.
Why do I need to submit so much information?
This is an industry-wide practice with the goal of reducing spam, fraud, unwanted messaging, and protect SMS as a trusted communications channel in the U.S. Every messaging provider who services A2P Campaigns is required to follow this process.
Best Practices
Ensure data accuracy and consistency
Make sure you submit Campaign registrations with accurate and consistent data:
Gather Campaign details
You will need to provide a detailed description of your SMS campaign, including the purpose, sender, recipient, and message flow. It is also recommended to provide sample messages and opt-in methods to demonstrate your compliance with regulations.
| Parameter | Description/Requirements |
| Campaign description
(description) required |
Provide a detailed description of what purpose this campaign serves. The description should explain who the sender and the recipient are and why messages are sent to the intended recipient.
Ensure the description aligns with the campaign use case you will specify below. It should also be descriptive enough to be able to pass manual reviews. Example: “This Campaign will send weekly marketing messages about offers and sales from Your Company to end customers who have opted in.” Note: If you are a financial institution engaged in direct, first-party lending to end customers, please specify “Direct Lending” in the Campaign description so that our review team can set this attribute properly before submitting the registration request to TCR. Please indicate this even if your particular Campaign use case is not directly related to your lending services offer (e.g., OTP). |
| Opt-in message flow
required (40 – 2048 characters) |
Describe in detail how a consumer opts into your campaign, therefore consenting to receive your messages. If there are multiple opt-in methods that can be used for the same campaign, please list them all.
Note: If a website is used for opting in, include a link to the website. The website must have a privacy policy and terms of service. Privacy policies also should include a statement of non-sharing for mobile phone numbers, message frequency, and “message and data rates may apply” disclosure. Please include a link to the policy. If the described opt-in mechanism and other required information are not publicly accessible via the company website URL you provided, please provide a URL where screenshots of the relevant pages are hosted. Understanding the opt-in mechanism is crucial for the Campaign to be accepted by TCR. Example: “End users opt-in by visiting www.yourcompany.com and adding their phone number. They then check a box agreeing to receive text messages from Your Company. Additionally, end users can also opt in by texting START to (323) 555-1212 www.yourcompany.com. Privacy Policy at www.yourcompany.com/privacy” |
| Sample message #1
required (20-1024 characters) |
These should be specific examples of messages you will send in this Campaign.
Sample messages must be aligned with the Campaign description provided above and the use case below. In each message, make sure to identify your brand by name and/or website. Also, use brackets [] to indicate any content that will be conditionalized. Example “This is a message from the Your Company. Your order for [ item] will be delivered by [time] on [date]. If you have questions or would like to change your order schedule, please call 323-555-1212 . If you would like to opt out of future notifications like this, text STOP in reply to this message.” |
| Sample message #2
required (20-1024 characters) |
See above. |
| Campaign use case type | Specify the use case type of your campaign. You can select the type from the list of use case types.
Example: MARKETING. Ensure the use case aligns with your Campaign description and sample messages above. |
| Are there embedded links? | Enter Yes or No to indicate whether this SMS campaign will send messages containing URL links.
Best practice: Include any such links in your sample messages so that they can be verified. |
| Are there embedded phone numbers? | Enter Yes or No to indicate whether this SMS campaign will send messages containing phone numbers.
Best practice: Include any such phone numbers in your sample messages so that they can be verified. |
| Opt-in auto-response message
optional (20-320 characters) |
If end users can send a text with a keyword to start receiving recurring messages from this campaign, provide the auto-response messages that will be sent to the end users.
The opt-in auto-response should include the brand name, confirmation of opt-in enrollment to a campaign with recurring messages, how to get help, and a clear description of how to opt out. Note: This field is required if end users can send a text with a keyword to start receiving messages from this campaign. |
| Opt-out auto-response message
optional (20-320 characters) |
Provide the text for an auto-generated response that will be sent if the opt-out keywords are received from your end users. In the response, you must acknowledge the opt-out request and confirm no further messages will be sent. It is also recommended that the opt-out messages include your brand name.
Note: This field is required if you manage the opt-out keywords by yourself. |
| Help keywords auto-response message
optional (20-320 characters) |
Provide the text for an auto-generated response that will be sent if help keywords are received from your end users. The response may include the brand name and additional support contact information.
Note: This field is required if you manage the help keywords and opt-outs yourself. |
| Opt-in keywords
optional (not more than 255 characters) |
Provide one or several keywords that end users can text in to start receiving messages from this campaign. If there is more than one keyword, provide them in a comma-delimited list.
Note: This field is required if end users can send a text with a keyword to start receiving messages from this campaign. |
| Opt-out keywords
optional (not more than 255 characters) |
Provide one or several keywords that end users can text in to stop receiving messages from this campaign. If there is more than one keyword, provide them in a comma-delimited list.
Values must be alphanumeric. Note: This field is required if you manage the opt-out keywords yourself |
| Keywords used to request help
optional (not more than 255 characters) |
Provide one or several keywords that end users can text in to receive help.
Values must be alphanumeric.
|
List of campaign use case types for A2P 10DLC registration
The tables below show campaign use case types that will be available for registration under United States A2P 10DLC. Please note, the current maximum Campaigns per Use Case limits are as follows:
- 100 for Nonprofit and Government Brands
- 200 for Private and Public Profit Brands
Standard Campaign Use Cases
The following table contains the list of standard campaign use cases that will be available within US A2P when registration launches.
Table 1: List of standard campaign use cases
| Campaign use case (registered on your Messaging Service) |
Description |
| 2FA | Any authentication or account verification such as OTP |
| Account Notifications | Notifications about the status of an account or related to being a part of an account |
| Customer Care | Support, account management, and other avenues of customer interaction |
| Delivery Notifications | Information about the status of a delivery |
| Fraud Alert Messaging | Messaging about potentially fraudulent activity such as spending alerts |
| Higher Education | Message campaigns from colleges, universities, and other education institutions |
| Marketing | Promotional content such as sales and limited time offers |
| Mixed | A campaign that covers multiple use cases such as Customer Care and Delivery Notifications. Note – mixed campaigns are likely to have lower throughput and a higher cost per message. NOTE: Low-Volume Brands are eligible for the Low-Volume Mixed use case detailed below. |
| Polling and voting | For conducting polling and voting, such as customer surveys. Not for political use. |
| Public Service Announcement | PSAs to raise audience awareness about a given topic |
| Security Alert | Notification of a compromised system (software or hardware related) |
Special Campaign Use Cases
There are some use cases that carriers consider “Special,” with additional requirements and (in some cases) different fees. These include Charity / 501(c)(3) Nonprofit, Emergency Services, and Political use cases, among others.
Low-Volume Use Cases
In addition to the standard “Mixed/Marketing” use case, there is a separate Campaign use case designated as “Low Volume Mixed”– this option supports the same multiple use cases but has a lower monthly fee than a standard Campaign and is fixed at the lowest throughput tier below, regardless of your Trust Score.
Sole Proprietor Use Cases
No longer supported
Version 01.08142024