A2P 10DLC Registration Guide

A2P 10DLC registration helps businesses send application-to-person (A2P) SMS and MMS messages over U.S. local 10-digit phone numbers.

Mobile carriers use this registration framework to identify legitimate business messaging, improve trust in the messaging ecosystem, and reduce unwanted or non-compliant traffic.

If your business uses DialNext to send messages to customers in the United States from local 10-digit numbers, you may need to register your Brand and Campaign before sending A2P messaging traffic.

This guide explains what information you should prepare, how the registration process works, and how to reduce the risk of delays or campaign rejection.

What is A2P 10DLC?

A2P stands for Application-to-Person, while 10DLC stands for 10-Digit Long Code.

A2P 10DLC allows businesses to send application-generated SMS and MMS messages using standard U.S. local phone numbers.

Common examples include:

Businesses must register their messaging use case so carriers can understand who is sending messages, what type of content they send, and how recipients provide consent.

How A2P 10DLC Registration Works

A2P 10DLC registration generally involves three main components:

1. Business or Brand Registration

First, provide accurate information about the business sending the messages.

Depending on the business and registration type, this information may include:

Make sure the information you provide matches official business records wherever applicable.

Your website, email domain, business identity, and submitted Brand information should also clearly correspond to the same organization. Inconsistent information can cause delays or rejection.

2. Campaign Registration

After registering the Brand, provide information about how the business plans to use SMS or MMS.

A Campaign represents a specific messaging use case.

You may need to provide:

Your Campaign description should clearly explain what messages you send, who receives them, and why they receive them.

Avoid vague descriptions such as simply writing “marketing” or “notifications.” 

3. Campaign Review

The Campaign then goes through a vetting process.

Reviewers check whether your registration information, consent process, messaging examples, policies, and declared use case meet applicable requirements.

Do not begin sending A2P traffic through the registered route until the Campaign has received the required approval.

Review times can vary depending on submission volumes and whether reviewers require additional information. Therefore, submit registrations well before you plan to launch a messaging campaign.

Choose the Correct Messaging Use Case

Choose the Campaign use case that most accurately represents the messages you plan to send.

Examples may include:

Your Campaign description, sample messages, and actual messaging traffic should remain consistent with the selected use case.

For example, if you register a Campaign for customer support, do not use it to send unrelated promotional messages unless your registered use case and recipient consent appropriately cover that messaging.

Describe Your Opt-In Process Clearly

Consent is one of the most important parts of A2P 10DLC registration.

Your registration should clearly explain how recipients agree to receive your messages.

Depending on the Campaign, users may opt in through methods such as:

If you use multiple opt-in methods for the same Campaign, describe all of them.

For website or application opt-ins, SMS consent should be clear and voluntary. Do not preselect consent checkboxes or make SMS consent mandatory for an unrelated action such as creating an account or completing a purchase.

Messaging consent should also remain separate from general Terms of Service acceptance. 

Example Website Opt-In

A compliant opt-in may clearly tell users:

By checking this box, you agree to receive text messages from [Brand Name]. Message frequency may vary. Message and data rates may apply. Reply STOP to opt out and HELP for help. View our Terms and Privacy Policy.

The exact disclosures you need can depend on the Campaign and applicable requirements, so businesses should ensure their consent workflow matches their actual messaging practices.

Privacy Policy and Terms and Conditions

Your messaging registration should include accessible and appropriate Privacy Policy and Terms and Conditionsinformation.

Your Privacy Policy should explain how you collect and use customer information.

Importantly, it should clearly address mobile information and messaging consent. Current A2P vetting guidance requires appropriate disclosure that mobile opt-in information and consent will not be shared with third parties or affiliates for marketing or promotional purposes. 

Your messaging Terms should appropriately describe the program and may need to include information such as:

Make sure the URLs submitted during registration are publicly accessible and functional.

Provide Accurate Sample Messages

Your sample messages should accurately represent the messages you intend to send after approval.

Good sample messages should:

For example:

[Brand Name]: Hi [First Name], your appointment is scheduled for [Date] at [Time]. Reply STOP to opt out.

For a promotional Campaign:

[Brand Name]: Save 20% on your next order through [Date]. Visit [Website] for details. Reply STOP to opt out.

Do not include real customer personally identifiable information in registration examples. Use placeholders such as [First Name], [Date], or [Order Number] instead. 

Configure Opt-Out and HELP Handling

Recipients must have a clear way to stop receiving messages and obtain assistance.

Common opt-out keywords include:

STOP, UNSUBSCRIBE, END, QUIT

When a recipient opts out, your messaging workflow should acknowledge the request and stop sending further messages as required.

Similarly, users who send HELP should receive useful support information, such as a support email address, website, or phone number.

If your messaging configuration manages these responses directly rather than relying on a provider’s default handling, make sure the corresponding keywords and response messages are correctly configured.

Recurring Messaging Confirmation

For recurring messaging Campaigns, users should receive an appropriate confirmation after opting in.

The confirmation should clearly identify the program and provide relevant information such as:

This helps recipients understand what they subscribed to and how to manage their messaging preferences. 

Common Reasons A2P 10DLC Registrations Are Rejected

Campaign registrations may be rejected when submitted information is incomplete, inconsistent, or does not sufficiently demonstrate compliant messaging practices.

Common issues include:

Review your entire submission before sending it for approval. Small inconsistencies can delay registration.

A2P 10DLC Registration Checklist

Before submitting your registration, confirm that:

Completing these checks before submission can reduce avoidable delays and rejection risk.

What Happens After Registration?

After you submit your Brand and Campaign, the registration enters the applicable verification and vetting process.

Once the Campaign receives approval, you can associate eligible U.S. 10DLC phone numbers with the approved messaging setup and begin sending messages according to the registered use case and consent practices.

Approval does not remove your ongoing compliance responsibilities. Continue following your declared Campaign purpose, recipient consent requirements, opt-out requests, and applicable messaging policies.

Frequently Asked Questions

Is A2P 10DLC registration required for business texting?

Businesses that send application-to-person messaging traffic over U.S. local 10-digit numbers generally need to use the applicable A2P 10DLC registration framework.

How long does A2P 10DLC registration take?

Approval time varies based on submission volume and whether the Campaign requires additional review. Because review times can change, submit your Campaign in advance rather than relying on a fixed approval timeframe.

Why was my A2P 10DLC Campaign rejected?

Common reasons include incomplete business information, an unclear opt-in process, insufficient Privacy Policy disclosures, inconsistent sample messages, or a Campaign description that does not adequately explain the use case.

Do customers need to opt in before receiving messages?

You should obtain the appropriate level of consent before sending messages. The required consent method depends on the type of messaging you send and applicable requirements.

Can I use the same Campaign for every type of SMS?

Not necessarily. Your actual messages should match the use case and purpose declared during Campaign registration. Different messaging purposes may require different Campaigns or consent flows.

Can I send marketing messages after a customer opts in for transactional updates?

Do not assume consent for one Campaign automatically applies to another. Consent is tied to the messaging purpose, and promotional messaging may require separate appropriate consent. 

Need Help?

If you need assistance with A2P 10DLC registration or Campaign setup in DialNext, contact help@dialnext.io.

Related Articles