[ GoHighLevel ]
A2P 10DLC Registration Checklist for GoHighLevel (Free and Printable)
Texts not delivering, or your A2P campaign rejected again? Work through this checklist before you submit, and most rejections never happen.
We build the funnels, stores and CRMs we write about — this isn't outsourced content.

This A2P 10DLC registration checklist is the one we work through before submitting a brand or campaign in GoHighLevel. Most rejections we see are not about the business at all. They come from small mismatches: a business name that differs between the website and the form, a sample message without the company name, or a sign-up form that never actually asks for consent to receive texts.
Go through each section below before you click submit. It will not guarantee approval, because the mobile carriers and their registry make the final decision, but a complete and consistent application gives you the best chance of getting it right the first time.
What A2P 10DLC registration is, in one minute
A2P 10DLC is the registration that US mobile carriers expect from businesses sending texts from ordinary 10-digit numbers through software such as GoHighLevel. You register two things: your brand (the business sending the messages) and your campaign (who you text, why, and how they agreed to it). Texts from numbers that are not registered are likely to be filtered or blocked, which is why so many new GoHighLevel accounts see messages fail.
In GoHighLevel, registration lives in Settings → Phone System → Trust Center. The brand has to be approved before the campaign can be submitted, and HighLevel’s own step-by-step campaign registration guide shows the current screens.
Checklist part 1: Your brand details
- ☐ Legal business name typed exactly as it appears on your tax registration, including words like LLC or Inc.
- ☐ Tax ID (EIN) matches that legal name. If you do not have one, you will only see the single-number (sole proprietor style) option, which has lower limits.
- ☐ Business address and phone match your official records.
- ☐ Trading name: if customers know you by a different name, say so clearly. HighLevel suggests adding a line such as “We are doing business as [Brand Name]” to the campaign description.
- ☐ Volume tier: choose the low or high volume standard brand based on how many texts you really expect to send.
Checklist part 2: Your website
Reviewers visit your website to check that the business is real and that it matches what you registered. This is where many rejections start.
- ☐ The website is live and public, not a “coming soon” page or behind a login.
- ☐ The business name on the website matches the brand registration.
- ☐ Contact details (email, phone or address) are easy to find.
- ☐ A privacy policy page is public and linked from the site.
- ☐ The privacy policy says that mobile numbers and SMS consent are not shared or sold to third parties for their marketing.
- ☐ A terms and conditions page is public, and covers your SMS program: what you send, how often, that message and data rates may apply, and how to get help or opt out.
- ☐ The same business name appears on the website, privacy policy, terms and the opt-in form.
Checklist part 3: Opt-in and consent
Carriers want to see exactly how people agree to receive your texts. If the reviewer cannot see a clear opt-in, the campaign will not be approved.
- ☐ Every form that collects a phone number has an SMS consent checkbox or clear consent wording next to it.
- ☐ The checkbox is not pre-ticked, and texting consent is optional. People must be able to submit the form, book or buy without agreeing to texts.
- ☐ Consent is shown on the form itself, not hidden only inside the terms or privacy policy.
- ☐ If you send both marketing and non-marketing texts, consider separate consent for each.
- ☐ The opt-in page is publicly visible. If it is not (for example a paper form or an in-store sign-up), have a public link or image that shows it.
- ☐ You can describe every way people opt in: website form, chat widget, booking form, paper form, QR code or verbally.
Checklist part 4: Campaign description and use case
- ☐ Use case matches what you actually send: marketing, informational (such as appointment reminders and customer care) or mixed.
- ☐ The description answers four questions in plain English: who is sending, who receives the texts, what the texts are about, and how people opt in.
- ☐ The description mentions every opt-in method you listed.
- ☐ Everything is written in English.
Checklist part 5: Sample messages
- ☐ Samples look like real messages you will send, not placeholders.
- ☐ Each sample includes your business name.
- ☐ At least one sample shows how to opt out (for example “Reply STOP to opt out”).
- ☐ Samples match the use case and description. A campaign registered for appointment reminders should not have promotional samples.
- ☐ No public link shorteners. Use your own domain for links.
- ☐ No custom fields or merge tags left in the text, such as {{contact.first_name}}.
Two simple examples of the style that works well:
- “Hi, this is [Business Name]. Your consultation is confirmed for tomorrow at 3 pm. Reply C to confirm or call us to reschedule. Reply STOP to opt out.”
- “[Business Name]: thanks for your enquiry about a new website. When is a good time for a quick call? Reply STOP to opt out.”
Checklist part 6: Opt-in, HELP and STOP messages
- ☐ Opt-in confirmation names your business, says how often you text, mentions that message and data rates may apply, and explains HELP and STOP.
- ☐ HELP reply includes your business name and a way to contact you (email, phone or website).
- ☐ STOP reply confirms the person is unsubscribed and will receive no more texts.
- ☐ STOP actually works in your account: test it with your own number before going live.
Common reasons A2P 10DLC campaigns get rejected
If your campaign has been rejected, check these first. Each one is usually fixable and the campaign can be resubmitted.
- Names do not match between the brand, website, privacy policy and opt-in form.
- Consent is unclear: the checkbox is pre-ticked, texts are required to submit the form, or consent only appears inside the terms.
- Privacy policy allows sharing of mobile numbers or consent with partners or affiliates.
- Website problems: not live, unfinished, behind a login, or missing a privacy policy or terms page.
- Description is vague or does not match the use case.
- Sample messages are missing the business name, missing opt-out wording, use link shorteners or do not match the description.
- HELP message does not include the business name or a support contact.
Some types of content and use cases cannot be registered at all, whatever the wording. If you are unsure whether your business is allowed, check HighLevel’s and the carriers’ current rules before you submit.
After approval: two final checks
- ☐ Each sending number is linked to the approved campaign and shows as A2P verified under Settings → Phone System → Phone Numbers.
- ☐ Your live forms, chat widget and messages still match what you registered. If you change what you send, update the registration too.
Fast replies to new enquiries depend on texts actually being delivered, so registration is worth getting right before you build follow-up like missed-call text-back or appointment reminders.
Want someone to handle your A2P 10DLC registration?
If your campaign keeps getting rejected, or you would rather not spend an afternoon on compliance wording, our team prepares and submits A2P 10DLC registrations in GoHighLevel, fixes rejected campaigns and sets up the opt-in wording on your forms and website. See our A2P 10DLC registration help, or our wider GoHighLevel services. Fast delivery, reasonable pricing, and a free audit to start.
Frequently asked questions
Your legal business name and tax ID, a live website with a public privacy policy and terms, an opt-in form with clear SMS consent, a plain description of who you text and why, and realistic sample messages that include your business name and opt-out wording.
The most common reasons are mismatched business names, unclear or pre-ticked consent, a privacy policy that allows sharing mobile numbers, a missing or unfinished website, and sample messages without the business name or opt-out wording.
In GoHighLevel, accounts without a tax ID can usually only use the single-number registration option, which has lower sending limits. Businesses with an EIN can register a standard brand.
No. HighLevel’s checks help you catch problems, but the carriers and their registry make the final decision. A complete, consistent application gives you the best chance.
Yes. A GoHighLevel specialist can prepare your brand and campaign details, set up compliant opt-in wording and submit or fix the registration in your account. Tocal IT Works offers this as part of its GoHighLevel services.
[ Tags ]
- GoHighLevel
- A2P 10DLC
- SMS
- Compliance
- Checklist
[ Need a hand? ]
Let Us Build It For You.
30 minutes, no pressure — we’ll look at your setup and tell you honestly what to fix first.
[ Keep reading ]

[ GoHighLevel ]
What Does a GoHighLevel Virtual Assistant (GHL VA) Do — and When Should You Hire One?
GoHighLevel can run a lot of your sales and marketing — if someone keeps it running. Here’s what a GHL VA actually does, when it makes sense to hire one, and how to choose well.

[ GoHighLevel ]
How to Build Workflows in GoHighLevel: A Step-by-Step Guide
Workflows are the engine of GoHighLevel. Here’s how to plan, build, test and publish one properly — and how to keep your automations easy to manage as they grow.
