A2P 10DLC Registration:
Get Approved on the First Try

What Is A2P 10DLC?

A2P 10DLC is a mandatory U.S. carrier registration system for businesses sending text messages. It verifies who is sending SMS (brand registration) and what they're sending (campaign registration). Every business texting U.S. phone numbers — including GoHighLevel agencies — must complete A2P registration or their messages will be blocked by carriers.

A2P stands for Application-to-Person. 10DLC stands for 10-Digit Long Code — the standard local-looking phone numbers businesses use for SMS. The registration system was built by U.S. carriers to verify who is sending and what is being sent before allowing traffic through their networks.

The process has two layers:

Most rejections don't happen at Brand Registration. They happen at Campaign Registration — because opt-in forms, privacy policies, and terms of service don't match what carriers require. The rest of this guide covers exactly what they're looking for.

Note for GoHighLevel users: Hot Prospector enforces TCPA compliance at the session level inside GHL — color-coding calling hours by timezone and building compliance gates into campaign workflows. Once your A2P registration is approved, your SMS follow-up sequences run automatically. This guide gets you to that point.

What Does a Compliant A2P Opt-In Form Require?

A compliant A2P opt-in form requires two separate, unchecked consent checkboxes — one for marketing messages, one for non-marketing — both with specific carrier-required language. Consent must remain optional even when the phone field is required. Privacy Policy and Terms & Conditions links must appear in the footer.

Your opt-in form is the most scrutinized part of your submission. Carriers want proof that your contacts explicitly agreed to receive messages — and that the form itself gives them a real, unconstrained choice.

Two Separate Checkboxes: Marketing vs. Non-Marketing

You must have two distinct, independent consent checkboxes — one for marketing messages and one for non-marketing messages. Contacts must be able to opt into one, both, or neither. A single combined checkbox will get you rejected.

Marketing checkbox — exact language required:

Non-marketing checkbox — exact language required:

No Pre-Selected Checkboxes

Consent checkboxes must arrive unchecked. The person filling out your form must manually check the box — that's what "affirmative action" means in carrier compliance language. Pre-checking a consent box is an automatic rejection trigger and may result in your numbers being flagged entirely.

Consent Is Always Optional — Even When Phone Is Required

If your form has a required phone field, that's fine. But the consent checkbox must still be optional. A person must be able to submit the form with their phone number without agreeing to receive texts. You cannot block form submission based on whether someone checked the SMS consent box.

After submission, you can only contact them through channels they actually consented to. Phone number captured but no SMS consent checked? Call them. Don't text them.

Does Your Campaign Description Need to Match Your Opt-In Form?

Yes. Your A2P campaign description and opt-in checkbox language must align exactly. If your campaign says "appointment reminders," your non-marketing checkbox must say "appointment reminders" — not just "non-marketing messages." Mismatched language is one of the most common campaign rejection reasons during Twilio review.

Your Campaign Registration includes a description of the types of messages you'll send. Carriers will compare that description against your consent checkboxes word for word.

What Links Must Appear in Your A2P Form Footer?

Every form collecting phone numbers must include two visible, clickable links in the footer: a Privacy Policy link and a Terms & Conditions link. Both must be accessible before the form is submitted. Links hidden behind popups, overlays, or a logged-in view will result in A2P rejection.

This applies to all forms — landing pages, GHL funnels, booking pages, website contact forms, everything.

What Must Your Privacy Policy Include for A2P Approval?

Your Privacy Policy must include a non-sharing clause stating that no mobile information will be shared with third parties for marketing purposes. It must never mention buying, selling, or affiliating with lead data. All contact information in the policy must exactly match your Brand Registration.

Your Privacy Policy must do more than exist — it must say the right things. Carriers and Twilio reviewers read it. These are the non-negotiable requirements:

No Mention of Selling, Buying, or Sharing Leads

If your Privacy Policy mentions lead affiliation, lead sharing, or buying/selling lead data in any context — even to say you don't do it poorly — it will get flagged. Keep lead-commerce language out of it entirely.

Required Non-Sharing Clause

This exact language, or language to this effect, must appear in your Privacy Policy:

What Clauses Must Your Terms of Service Include for A2P?

A2P-compliant Terms of Service must include five clauses: a business identity statement, opt-out and support instructions (STOP/HELP keywords), a carrier liability disclaimer, a message frequency disclosure, and a cross-link to your Privacy Policy. Missing any one of these is a common rejection trigger.

Not paraphrases. Not vague references. The actual substance of each clause, in plain language — verified against carrier requirements.

1. Business Identity Clause

State your business name and give a brief description of the types of messages subscribers will receive. This tells users who they're hearing from and why.

2. Opt-Out & Support Mechanism

Users must be told exactly how to stop messages and how to get support. Here is the required substance:

3. Carrier Liability Clause

This one is short but required word-for-word:

4. Message Frequency Clause

5. Privacy Policy Cross-Link

Your Terms of Service must link back to your Privacy Policy:

How Does A2P Registration Work for DBA Businesses?

If you operate under a brand name different from your legal EIN name, declare the DBA relationship explicitly in your campaign description, on your website header or footer, and throughout your Privacy Policy and Terms. Use the format: [Legal Name] DBA [Brand Name] — consistently, everywhere.

If your registered EIN is under one legal name but you operate under a different brand name, that's a DBA (Doing Business As) situation. Carriers need to see that relationship clearly documented — not buried or implied.

Can You Use a Subdomain for A2P Registration?

Yes, subdomains are allowed for A2P registration — but carriers must clearly see how the subdomain connects to your main brand and how users discover it. If the subdomain appears to exist only as a compliance front with no organic path to it, it will be rejected.

Subdomains like form.youragency.com are fine, but carriers need to understand two things before they'll approve them.

Subdomain Readiness Checklist

Why Do A2P Campaigns Get Rejected?

A2P campaigns are most commonly rejected for: opt-in forms that aren't publicly accessible, a single combined consent checkbox instead of two separate ones, pre-selected checkboxes, missing footer links, campaign descriptions that don't match checkbox language, and Privacy Policies that mention lead sharing. Most rejections are avoidable.

A2P Pre-Submission Checklist: What to Verify Before You Submit

Before submitting A2P registration, verify: your opt-in form is publicly accessible with two separate unchecked consent checkboxes, your form footer includes clickable Privacy Policy and Terms links, your campaign description matches your checkbox language exactly, and your Privacy Policy contains the required non-sharing clause.