How to get your phone number A2P approved in 2026

Modified on: Wed, 7 Jan, 2026 at 4:01 PM

A2P 10DLC registration is a process used by U.S. cellular carriers (e.g. Verizon, AT&T, T-Mobile, etc) to verify who is sending SMS (text messages) and what is being sent to their customers. This helps ensure your contacts are receiving message they actually want to receive. Follow these guidelines to avoid A2P rejections, save time and easily stay compliant!



TABLE OF CONTENTS


Overview of A2P Registration


A2P 10DLC registration is a mandatory carrier requirement for businesses sending application-to-person (A2P) SMS traffic in the United States. Registration is enforced by U.S. cellular carriers to verify sender legitimacy, consent integrity, and message transparency. Follow the guidelines in this article to get approved and stay approved.


Scenario 1: Mandatory Phone Number Collection


When a phone number field is mandatory (marked as required) in form, survey, quiz, web chat widget or calendar booking, users cannot be forced to agree to SMS messaging in order to submit. The phone field and consent choices are separate decisions.


When a phone number field is mandatory, apply the rules below:



Strict Seperation


Consent checkboxes must be distinct for Marketing messages vs. Non-Marketing messages so subscribers can opt into one, both, or neither. Make sure you have two checkboxes with the following exact messages:


  1. "I consent to receive marketing text messages from [Business Name] at the phone number provided. Frequency may vary. Message & data rates may apply. Text HELP for assistance, reply STOP to opt out."

  2. I consent to receive non-marketing text messages from [BUSINESS NAME] about [USE_CASE_FROM_CAMPAIGN_DESCRIPTION] Message & data rates may apply. Text HELP for assistance, reply STOP to opt out.


[BUSINESS NAME] should match what’s on the CP 575/147C Document. 


Note for DBAs: If you have an EIN for your company but you want to use a different brand name for your messages, you can add this sentence "We are doing DBA as [Business_Name]" in the Campaign Use Case Description.

Make sure the rest of the submission, including the website, Privacy Policy, T &C, and the business name shown in opt-in form checkboxes, matches the declared [Legal Business Name] DBA [DBA Name].

DBAs and other relationships must be VERY clear on the websites, typically in T&Cs. If it's unclear or cannot be found, it can be rejected.




No Pre-Selection of Checkboxes


Consent checkboxes cannot be pre-selected by default. The users must manually select the consent checkboxes that they would like to agree to. 


Important: Never default a checkbox to "Checked". The user must take affirmative action.




Even if the phone number is required, checking the consent box must remain optional for submission. Submitting a form (even with a phone number) cannot be conditional on marketing consent.


After submission, you must execute the communication channels based on their consent checkbox selections only.




Privacy Policy and Terms and Conditions (TnC) are mandatory requirements within the footer of all forms. 


For more information, see Terms of Service Clauses and Privacy Policy Essentials.



Scenario 2: Optional Phone Number Collection


When a phone number field is optional (NOT marked as required) in form, survey, quiz or calendar booking, users still cannot be forced to agree to SMS messaging. The phone field and consent choices are separate decisions.


When a phone number field is optional in a form, survey, quiz, or calendar booking, apply the rules below:



Strict Seperation


Consent checkboxes must be distinct for Marketing messages vs. Non-Marketing messages. Make sure you have two checkboxes with the following exact messages:


  1. I consent to receive marketing text messages from [Business Name] at the phone number provided. Frequency may vary. Message & data rates may apply. Text HELP for assistance, reply STOP to opt out."

  2. I consent to receive non-marketing text messages from [BUSINESS NAME] about [USE_CASE_FROM_CAMPAIGN_DESCRIPTION] Message & data rates may apply. Text HELP for assistance, reply STOP to opt out.


[BUSINESS NAME] should match what’s on the CP 575/147C Document. 


Note for DBAs: If you have an EIN for your company but you want to use a different brand name for your messages, you can add this sentence "We are doing DBA as [Business_Name]" in the Campaign Use Case Description.

Make sure the rest of the submission, including the website, Privacy Policy, T &C, and the business name shown in opt-in form checkboxes, matches the declared [Legal Business Name] DBA [DBA Name].

DBAs and other relationships must be VERY clear on the websites, typically in T&Cs. If it's unclear or cannot be found, it can be rejected.




No Pre-Selection of Checkboxes


Consent checkboxes cannot be pre-selected by default. The users must manually select the consent checkboxes that they would like to agree to. 


Important: Never default a checkbox to "Checked". The user must take affirmative action.




Users should never be required to check a consent box just to submit the form. Submitting a form (even with a phone number) cannot be conditional on marketing consent.


After submission, you must execute the communication channels based on their consent checkbox selections.




Privacy Policy and Terms and Conditions (TnC) are mandatory requirements within the footer of all forms. 


For more information, see Terms of Service Clauses and Privacy Policy Essentials.




The footers of all forms must include all of the following elements in order to for a A2P submission to be successful:



Privacy Policy


A clear, direct link must be added at the footer of every form. Click here for details on what must be included.



Terms & Conditions (TnC)


A visible link to Terms & Conditions(TnC) must be in the footer. Click here for details on what must be included.



Accessibility


Ensure legal links are not obscured by other design elements or pop-ups. These links must be clear and visible.



Transparency


Users must be able to review how their data will be handled before form submission. Ensure your Privacy Policy and TnC are accessible without extra steps.


Privacy Policy Essentials


Privacy Policy and Terms and Conditions must be added at the footer of the form, and it should never talk about affiliation, selling or buying of leads.



Strict Prohibition


The policy should never mention affiliation, selling, or buying of leads.



Non-Sharing Clause


Your policy must include this exact language regarding third-party sharing. 


"No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. Information sharing to subcontractors in support services, such as customer service, is permitted. All other use case categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.”


Terms of Service Clauses


Your Terms of Service must identify the sender, provide opt‑out and support instructions, disclose frequency, and reference your Privacy Policy. Ensure the following clauses are included:



TnC: Business Identity Clause


Clearly insert your business name and a brief description of the messages users can expect. This clause gives users an idea of who you are and what you do.



TnC: Opt-Out & Support Mechanisms


This must cover how users can opt out of messaging and explain how they can get support.


“You can cancel the SMS service at any time. Just text "STOP" to the [Phone Number]. After you send the SMS message "STOP" to us, we will send you an SMS message to confirm that you have been unsubscribed. After this, you will no longer receive SMS messages from us. If you want to join again, just sign up as you did the first time and we will start sending SMS messages to you again. If you are experiencing issues with the messaging program you can reply with the keyword HELP for more assistance, or you can get help directly at [support email address or toll-free number].”



 TnC: Carrier Liability Clause


"Carriers are not liable for delayed or undelivered messages."



TnC: Message Frequency Clause


This clause must cover the frequency in which you receive messages as a user.


 “As always, message and data rates may apply for any messages sent to you from us and to us from you. You will receive [message frequency]. If you have any questions about your text plan or data plan, it is best to contact your wireless provider.”




You must have a cross-link to your privacy policy within the Terms of Service.


“If you have any questions regarding privacy, please read our privacy policy: [link to privacy policy]”


How to Get Support


If you need help or have questions about A2P registration, click on the help button and ask for A2P help. Our team is on standby to review all of your submissions! 


To reach support, click the Help (?) button in the upper right corner of the screen then use the Start Chat dropdown to select Agent Chat.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article