How to Set Up A2P 10DLC in GoHighLevel (2026 Guide)

Why A2P 10DLC Compliance is Mandatory in 2026

US mobile carriers require all businesses sending text messages to register their traffic through the Application-to-Person 10-Digit Long Code system. If you skip this registration in GoHighLevel, carriers like AT&T and Verizon will silently filter your messages. Your sub-account will show the text as sent, you will pay the segment fee, but your lead will never receive the message. This completely breaks core agency features like missed call text back and database reactivation.

Compliance is no longer optional for any business texting US numbers. The registration process proves to the carriers that you are a legitimate business and that you have explicit permission to text your contacts. When you onboard a new agency client, A2P registration must be the very first technical task you complete.

If you notice your messages failing immediately after setting up a new account, you are likely hitting a carrier block. You can consult our GoHighLevel SMS not sending: 2026 troubleshooting guide to confirm whether the issue is a software error or a missing A2P registration. In almost all cases for new accounts, unregistered traffic is the culprit.

Step 1: Prepare Your Business Profile Data

Before you touch the registration portal, you must ensure your sub-account data perfectly matches your official tax documents. The Campaign Registry uses automated systems to cross-reference your submission with IRS databases. A single misplaced comma or abbreviation will trigger an automatic rejection.

Navigate to Settings > Business Profile in your GoHighLevel sub-account. Locate the Legal Business Name field. You must enter your company name exactly as it appears on your IRS CP-575 or 147C letter. If your IRS document says "Raw Marketing Group, L.L.C.", you cannot enter "Raw Marketing Group LLC" in GoHighLevel. The punctuation must match flawlessly.

Next, verify your Employer Identification Number and your business address. The address in your Business Profile must be the address registered with the IRS, not necessarily your current physical storefront. If your client operates as a sole proprietor without an EIN, you will leave the EIN field blank, but the address and legal name must still match their official tax filings.

Step 2: Initiate Brand Registration in the Trust Center

Once your profile data is pristine, you can begin the actual registration process. Navigate to Settings > Phone Numbers > Trust Center. This dashboard is your central hub for all telecom compliance in GoHighLevel. Click the button to start your A2P registration.

You will face a choice between Standard Registration and Sole Proprietor Registration. Always choose Standard Registration if the business has an EIN. Standard Registration grants higher daily messaging limits and significantly better deliverability rates. You should only select Sole Proprietor if the client legitimately operates without an EIN.

During this step, you will pay a one-time vetting fee passed down from The Campaign Registry. This fee typically ranges from $15 to $25 depending on your exact registration path. GoHighLevel does not mark up this fee. After submitting the brand details, you must wait for the brand to be approved before moving to the campaign phase. Brand approval usually takes a few minutes to a few hours.

Step 3: Define Your Campaign Use Case

After your brand achieves verified status, you must register your messaging campaign. A campaign tells the carriers exactly what type of messages you intend to send. In the Trust Center, click the prompt to register your campaign.

You will need to select a Campaign Use Case. For the vast majority of local businesses and marketing agencies, you should select "Low Volume Mixed". This use case covers a variety of standard messages like appointment reminders, customer service replies, and basic promotional texts. It allows for up to 6,000 message segments per day, which is more than enough for standard local operations.

Next, you must write a Campaign Description. Do not be vague here. Reviewers want to know exactly how you interact with consumers. A compliant description looks like this: "This campaign is used to send appointment confirmations, scheduling reminders, and customer support replies to individuals who have explicitly opted in via our website contact form." Clear, specific descriptions pass vetting much faster than generic marketing claims.

Step 4: Craft Compliant Sample Messages

The vetting team requires at least two sample messages that represent your actual text traffic. These samples must align perfectly with the use case you selected. If you chose a mixed use case for appointment reminders, your samples must look like appointment reminders.

Every sample message must follow strict carrier rules. First, you must identify the sender in the message body. Second, you must include clear opt-out language. If you fail to include these two elements, your campaign will be rejected immediately.

Your first sample should look like this: "Hi John, this is Sarah from Raw Marketing Group. Your consultation is confirmed for tomorrow at 2 PM. Reply STOP to cancel." Your second sample should demonstrate a different interaction: "Hi John, Sarah from Raw Marketing Group here. We received your support ticket and will call you shortly. Reply STOP to unsubscribe." These samples prove to the reviewer that you respect consumer privacy and carrier guidelines.

Step 5: Document Your SMS Opt-In Process

Opt-in documentation is the most heavily scrutinized part of A2P 10DLC registration. You must prove exactly how a consumer gives you permission to text them. In the Trust Center, you will find a field asking for your opt-in message workflow. You must provide the direct URL to the page where users submit their phone numbers.

The page you link to must be live, publicly accessible, and fully functional. If your form is hidden behind a login screen, you must provide a link to a hosted screenshot of the form. The form itself must contain a dedicated SMS consent checkbox. This checkbox cannot be pre-ticked, and it cannot be bundled with your general terms and conditions.

The text next to your checkbox must explicitly state what the user is agreeing to. A compliant checkbox reads: "I agree to receive SMS messages from Raw Marketing Group regarding my inquiry. Message and data rates may apply. Reply STOP to opt out."

Additionally, your website footer must contain a link to your Privacy Policy. Your Privacy Policy must include a specific clause stating that mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. Reviewers will check your website for this exact clause.

The GHL GOAT A2P Compliance Checklist

To ensure your registration passes on the first attempt, verify these exact requirements before clicking submit.

1. Verify your Legal Business Name matches your IRS CP-575 form exactly.
2. Confirm your website footer includes a dedicated Privacy Policy link.
3. Add a mandatory SMS consent checkbox to all GoHighLevel forms.
4. Include "Reply STOP to cancel" in your sample messages.
5. Take a screenshot of your opt-in form to include in your submission.

For a complete visual walkthrough of this process, the full SOP with screenshots lives free in the GHL GOAT library at GHL GOAT SOPs.

Step 6: Link Your Phone Number to the Approved Campaign

Submitting your campaign is not the final step. Campaign vetting currently takes anywhere from three to five business days. You must monitor the Trust Center for your approval status. Once your campaign shows as approved, you must manually link your GoHighLevel phone numbers to the campaign to activate them.

Navigate to Settings > Phone Numbers. Locate the local phone number you purchased for your sub-account. You need to confirm that the number displays the green A2P Verified label. If the label is missing, click the three dots next to the number, select the configuration options, and link the number to your newly approved A2P campaign.

You must repeat this linking process every time you purchase a new phone number for the sub-account. Campaign approval does not automatically blanket every future number you buy. You can verify these exact linking steps in the official A2P Campaign Registration: Step by Step Guide and FAQs provided by HighLevel support.

Troubleshooting Common A2P Rejections

If your campaign is rejected, GoHighLevel will display a specific rejection reason in the Trust Center. Do not panic. Most rejections are easily fixable. The most common rejection reason is "Opt-in workflow does not meet requirements." This simply means your website form is missing the mandatory SMS consent checkbox or your Privacy Policy is missing the data sharing exclusion clause. Update your website, take a new screenshot, and resubmit the campaign.

Another common issue occurs when users think their automations are broken, but the real problem is a rejected A2P campaign. Before you spend hours reading a GoHighLevel workflow not triggering: 2026 troubleshooting guide, check your Trust Center. If your campaign is rejected or pending, your workflow will fire, but the SMS step will fail at the carrier level.

Telecom compliance requires the same attention to detail as email deliverability. Just as you would follow a fix GoHighLevel emails going to spam (2026 guide) to authenticate your sending domain, you must authenticate your phone numbers through A2P 10DLC. Take the time to build compliant forms, write clear privacy policies, and submit accurate tax data. Once your campaign is approved and linked, your text messages will achieve maximum deliverability across all major US networks.