A2P 10DLC Registration in 2026: Costs, Timelines and What Changed

A2P 10DLC registration is mandatory for sending SMS to United States and Canadian numbers from a 10-digit long code. Without it, carriers filter your messages. They do not bounce with a useful error, they simply do not arrive, which is why so many GoHighLevel launches stall on a workflow that looks like it is running perfectly.

Registration has two parts. Brand registration verifies who your business is, once. Campaign registration covers what you intend to send, and you can hold several campaigns under one brand. Every phone number attaches to exactly one campaign at a time.

What A2P 10DLC is

A2P means application-to-person: messages sent by software rather than typed by a human. 10DLC is the standard 10-digit phone number most businesses use, as opposed to a short code or a toll-free number.

US carriers introduced the framework to make automated messaging traceable to a verified business. In exchange for registering, you get higher throughput and much better deliverability than unregistered traffic, which is increasingly filtered to nothing.

What changed in 2026

Two things matter if you last registered a while ago.

Privacy policy and terms URLs are now enforced. Effective 30 June 2026, Twilio rejects new A2P 10DLC campaign submissions through its API that do not include a working privacy policy URL and a terms and conditions URL. These links were already a vetting expectation, but they were inconsistently enforced. Now they are checked, and other providers are moving the same way.

The practical consequence: the URLs must be live, publicly reachable and actually about your business before you submit. A privacy policy behind a login, a page that 404s, or a placeholder generated for another company are all grounds for rejection.

Campaign review times have lengthened. Through mid-2026, campaign vetting has been running around 10 to 15 days because of submission volume. Brand approval remains quick at one to three business days. If you are used to quoting clients a one-week turnaround on SMS going live, that number is out of date.

What it costs

The fees come from three separate places, which is why nobody can quote a single number.

The Campaign Registry raised brand registration from $4.00 to $4.50 and standard vetting from $40.00 to $41.50 with effect from August 2025, and those are the figures in force through 2026. The recurring monthly campaign fee varies meaningfully by use case, so check the current rate card in your own account rather than budgeting from a blog figure.

How long approval takes

Plan for a rejection. First-time submissions are rejected often enough that assuming approval on the first pass is optimistic, and each resubmission restarts the review clock.

How to register

1. Get your business details exactly right. Legal business name, EIN, and registered address as they appear on your official registration. Not your trading name, not your mailing address. A single mismatch fails brand vetting.
2. Publish a privacy policy and terms page. Live, public, on the domain you are registering, and genuinely about your business. Since June 2026 this is checked rather than assumed.
3. Put visible opt-in on the page you cite. The form you point to must show consent language: what messages the person will receive, that message and data rates apply, and how to stop. A pre-ticked box is not consent.
4. Submit brand registration. In GoHighLevel this lives in the sub-account trust centre. Wait for approval before submitting the campaign.
5. Submit the campaign. Pick the use case that genuinely describes your traffic. Provide two or three sample messages that look like what you will really send.
6. Attach numbers. Once approved, attach each phone number to the campaign. A number with no campaign sends unregistered traffic.

Why campaigns get rejected

Agencies with many sub-accounts

Each client business registers its own brand, using its own legal entity and EIN. You cannot register once as the agency and cover every client, because the framework is designed to tie messages to the business actually sending them.

Practical implications:

• Collect the details up front. Legal name, EIN and registered address should be part of onboarding, not a scramble during the build.
• Make the privacy policy part of the deliverable. Every client site needs one before registration, so build it into the site rather than treating it as an afterthought.
• Start on day one. Two to three weeks of registration runs in parallel with your build, which costs nothing. Started after the build, it becomes a two-week delay the client watches.
• Track status per client. A pipeline with stages for submitted, brand approved, campaign approved and numbers attached prevents the situation where nobody knows which accounts can actually send.

Our snapshots are built with this sequence in mind: SMS workflows ship paused, so a client account can be fully configured and tested while registration is still pending, then switched on the day approval lands.