A2P 10DLC

How to Register A2P 10DLC in GoHighLevel

Written from doing this repeatedly on client accounts, including the fields that quietly decide whether you are approved.

Howard KanCo-founder and COO, Agency Logics

Spent 8 years running operations for a startup studio that launched more than a dozen companies. Leads CRM, automation, AI assistants, websites, and delivery infrastructure at Agency Logics.

Published

The registration, step by step

  1. Open Trust Center

    In HighLevel, A2P 10DLC is managed in Trust Center, which holds the Business Profile, Brand, Campaigns, and consent information in one place. Start here rather than in phone number settings.

  2. Complete the Business Profile exactly as it appears on public record

    Legal business name, EIN or business registration number, business type, registered address, and website. These must match what the IRS and your state registration show, character for character. A DBA in this field when the EIN is under a different legal name is the single most common cause of brand vetting failure.

  3. Submit the Brand and wait for approval

    Brand registration usually returns in minutes to a few hours. Do not start the campaign until the brand is approved or you are continuing directly from the brand flow.

  4. Add opt-in language to your website before submitting the campaign

    Every form that collects a phone number needs visible consent language, for example: By providing your phone number, you agree to receive text messages from [Business]. Message and data rates may apply. Message frequency varies. Reply STOP to opt out. If this is not publicly visible on the page you cite, the campaign is rejected.

  5. Choose one specific use case, not a general one

    Pick the use case that matches what you will actually send. Generic descriptions such as notifications or customer updates are rejected. Describe who receives the messages, why, and what triggers them.

  6. Write sample messages that match the declared use case

    If you register for appointment reminders, your samples cannot read like promotions. Include your business name in the samples, and put opt-out language such as Reply STOP to opt out in at least one of them.

  7. Provide a publicly reachable opt-in form URL

    The reviewer will open it. It must load without a login, and the consent language from step four must be visible on that exact page. A URL behind a funnel step, a password, or a cookie wall fails.

  8. Submit the campaign and plan around the review window

    The campaign goes to The Campaign Registry and then to each carrier. HighLevel documents 1 to 5 business days. Do not schedule a send or promise a client launch date against the fast end of that range.

The four fields that decide the outcome

Most of the form is administrative. Four fields carry essentially all of the rejection risk, and they are judged against each other rather than individually.

1. Legal business name and EIN

These are checked against public records. Use the registered legal entity, not the trading name, not the brand you market under, and not an abbreviation. If your EIN is registered to "Smith Holdings LLC" and you trade as "Smith Comfort Air," the brand goes in as Smith Holdings LLC.

2. Campaign use case and description

Generic wording is rejected on sight. "Customer notifications" tells a reviewer nothing. Say who is receiving the message, why they are on your list, and what triggers a send. A description that reads like an internal ticket beats one that reads like marketing copy.

3. Sample messages

These must look like the use case you declared. Registering appointment reminders and then submitting promotional samples is an instant flag. Include the business name in the message, and carry opt-out language in at least one sample.

4. Opt-in method and opt-in form URL

The reviewer opens the URL you provide. The consent language has to be visible on that page, publicly, without a login. This is the one that catches agencies out most often, because the form lives inside a funnel step that is not directly reachable.

Where this sits in a build

Registration is a dependency, not a task. On partner accounts we start brand registration before anything else in the messaging build, because the campaign review window is the only part of the timeline nobody controls. Everything else, list cleaning, sequence writing, calendar routing, can happen in parallel while the campaign sits with the carriers.

Note also that registration only settles whether your message is delivered. Whether you were allowed to send it to that particular contact is a separate question governed by the TCPA, and the published guidance on that is currently wrong almost everywhere. See the corrected TCPA rules.

Common questions

Where is A2P 10DLC registration in GoHighLevel?
In Trust Center, which provides a guided workflow for the Business Profile, Brand, Campaigns, consent information, and submissions in one place. Registration is not done from the phone number settings, which is where most people look first.
Does the agency register on behalf of the client, or does the client register?
The brand belongs to the client's legal entity and must be registered with their legal business name and EIN. An agency can drive the process and complete the submission, but it cannot register a client's messaging under the agency's own entity. Each business that sends needs its own approved brand and campaign.
My brand was approved but my campaign was rejected. What now?
That is normal and it is almost always one of three things: opt-in language missing from the website, sample messages that do not match the declared use case, or a campaign description that is too generic. Resubmission no longer carries the $15 fee, so the cost of a rejection is the review cycle, not the money. Fix the mismatch and resubmit.
Can I send texts while registration is pending?
No. Unregistered 10DLC traffic has been blocked outright by the major US carriers since 1 February 2025. Messages sent before approval do not queue up and deliver later, they are simply dropped.
Do I need a separate campaign for each client sub-account?
Each sending business needs its own brand and campaign tied to its own legal entity. If you run multiple client sub-accounts in HighLevel, plan for a registration per client, each with its own timeline, rather than one registration covering the agency.

Sources

  1. 1.HighLevel: registering your A2P brand Trust Center brand flow and required business details.
  2. 2.HighLevel: A2P campaign registration step-by-step guide and FAQs Campaign fields, opt-in method options, and the review window.
  3. 3.HighLevel: A2P 10DLC campaign approval best practices Opt-in language requirements and sample message guidance.
  4. 4.HighLevel: A2P campaign rejections, required fixes and vetting errors Rejection categories and remediation.

Stuck in a rejection loop?

Most repeat rejections come down to a mismatch between what the campaign declares and what the website shows. That is a 30-minute fix once you can see which of the four fields is out of step, and it is the first thing we sort out on any partner account that sends SMS.

Apply For a Growth Partnership