A2P 10DLC in 2026: The Agency Guide (and the Legal Way to Skip It)
What A2P 10DLC registration actually requires in 2026, why campaigns get rejected, what it costs per message, and when agencies can legitimately skip it.
June 11, 2026 · 9 min read · GoGHL Team
Around 1,300 people search "A2P 10DLC news today" every month. Not "what is A2P" - news, today. That tells you everything about how this system feels from the inside: carriers keep changing the rules, and the people responsible for client texting keep refreshing the page.
This guide covers what A2P 10DLC actually is, what registration involves in 2026, what it costs, why campaigns get rejected, and the one route that legitimately does not require any of it - texting from a number you actually own.
What A2P 10DLC actually is
A2P stands for application-to-person. 10DLC is "10-digit long code" - a standard local phone number used by software to send texts. When Twilio, SignalWire, or any CPaaS provider sends SMS on your behalf over a US carrier route, that traffic is classified as A2P, and US carriers require it to be registered.
Registration happens through The Campaign Registry (TCR), the industry body that sits between messaging providers and carriers. You register twice: once as a brand (the legal entity sending messages) and once per campaign (the specific use case, like appointment reminders or marketing).
What registration involves in 2026
For an agency, the unpleasant part is doing this per client. Each client is its own brand with its own EIN, and each use case is its own campaign. The process looks like this:
- Brand registration: legal name, EIN, address, website - vetted against business registries. Mismatched details fail silently or get a low trust score.
- Campaign registration: declared use case, sample messages, opt-in flow description, and proof of consent collection. Reviewed by both TCR and downstream carriers.
- Fees: one-time brand fees, recurring per-campaign monthly fees, plus per-message carrier surcharges layered on top of your provider's per-segment rate.
- Wait time: days when everything is clean, weeks when anything needs manual review or resubmission.
- Throughput assignment: your daily sending limit is tied to your brand's trust score - low-score brands get throttled hard.
The hidden cost isn't the fees - it's the two to six weeks a new client sits unable to text their own leads while paperwork clears.
Why campaigns get rejected
Carriers reject or flag campaigns for reasons that feel arbitrary but follow a pattern. Generic sample messages that don't match the declared use case. Opt-in language that doesn't explicitly mention SMS. Websites that don't display a privacy policy or terms. URL shorteners like bit.ly in sample content. Industries carriers consider high-risk - debt, insurance leads, affiliate marketing - face extra scrutiny regardless of how clean the submission is.
Rejection isn't a dead end, but every resubmission resets the review clock. Agencies running dozens of sub-accounts in GoHighLevel feel this most: one client's rejected campaign becomes a support ticket, a refund conversation, and a churn risk.
The route that doesn't require A2P at all
A2P 10DLC governs application-sent traffic on rented application numbers. It does not govern the texts you send from your own phone. When a real person's number - a SIM you own, your business line - sends a message, that traffic is person-to-person from the carrier's perspective. No brand registration, no campaign vetting, no per-message surcharge.
That's the model GoGHL uses for SMS in GoHighLevel: you connect the number you already own, and texts send from it - while every message still logs into GHL Conversations, fires workflows, and gets answered from the same inbox as WhatsApp and iMessage. Setup is minutes because there is no registry to wait on.
Two honest caveats. First, consent rules still apply - TCPA and local regulations govern what you send and to whom, regardless of how the message travels. Second, your own number sends at human scale, not call-center scale; pacing tools like drip mode exist specifically to keep volume natural. For most agency use cases - lead follow-up, reminders, reviews, reactivation - that's exactly the volume profile you want anyway.
Rule of thumb: if your use case is conversations with people who know your client, own-number SMS fits. If it's 100,000 identical blasts to a cold list, you need registered A2P - and a different business model.
When you should still register A2P
Skipping A2P isn't always the answer. Register if you genuinely need five-digit daily volumes per client, dedicated short codes, or you're in a vertical where compliance teams demand registered routes. Plenty of agencies run both: registered A2P through LC Phone for high-volume blasts (compare the alternatives), own-number SMS through GoGHL for the two-way conversations that actually close deals.
A2P 10DLC solved a real spam problem by making application traffic accountable. But it was never meant to stand between a local business and a lead who asked to be texted back. For that kind of texting, the number your client already owns - connected to the CRM they already use - remains the fastest, cheapest, most human route available.
Try it inside your own GHL account
One install adds WhatsApp, iMessage, and SMS to every sub-account. Free for 7 days, no credit card.