GHL Scale Up - GoHighLevel Expert Agency
A2P 10DLCCampaign RegistrationGoHighLevel2026

A2P Campaign Registration in GoHighLevel:
Step-by-Step Guide (2026)

GHL Scale Up
GHL Scale Up Team
GoHighLevel Specialists · 200+ Builds Delivered · Updated July 2026

Once your A2P brand is approved in GoHighLevel, campaign registration is the next required step before you can send any automated SMS to US recipients. Campaign registration tells carriers what type of messages you will send, who receives them, and how contacts opted in. Getting the details right on the first attempt saves the 3 to 7 business day review cycle. GHL Scale Up has handled A2P campaign registration across hundreds of client accounts. This guide covers every required field, the rules around sample messages and consent, and the most common mistakes that cause rejection.

Important: Campaign Auto-Submission

You do not manually submit the campaign in GoHighLevel. Once your brand registration is approved, GHL automatically submits the associated campaign for review on your behalf.

This applies to both Standard Brand and Sole Proprietor registration flows. What you control is the campaign information you entered during the registration process that data is what gets submitted. Campaign review by carriers typically takes 3 to 7 business days after brand approval.

What's in this guide

1. What Is Campaign Registration and Why Is It Required?

A campaign in A2P 10DLC terminology represents a specific messaging use case the type of messages your business sends and the context in which contacts receive them. While brand registration establishes who is sending (your business identity), campaign registration establishes what you are sending and why.

US carriers require this information to evaluate whether your messages are legitimate, whether your opt-in process is compliant, and whether your content matches the use case you claim. Campaigns that pass review receive an approved status and are granted a message throughput level based on your brand's trust score.

For the foundational explanation of the full A2P system: What Is A2P 10DLC? →

For brand registration, which must be completed and approved before campaign review begins: A2P Brand Registration Guide →

2. What Is the Difference Between a Brand and a Campaign in A2P Registration?

AspectBrand RegistrationCampaign Registration
What it establishesWho is sending your business identityWhat you are sending your messaging use case
Information submittedBusiness name, EIN, address, website, industryCampaign description, use case, sample messages, opt-in method, opt-in language
Required beforeCampaign registrationSending any A2P SMS
Review timeline3 to 7 business days3 to 7 business days after brand approval
Submission methodYou enter data; GHL submits to TCRYou enter data during brand registration; GHL auto-submits campaign once brand is approved
Can you have multiple?One per legal business entity (EIN can register up to 10 brands)Yes one campaign per use case type. Separate use cases require separate campaigns.
WHEN DO YOU NEED MULTIPLE CAMPAIGNS

If your business sends meaningfully different types of messages, you may need to register more than one campaign. Example: a business sending both appointment reminders (transactional) and promotional offers (marketing) should register separate campaigns for each use case. Each campaign requires its own description, sample messages, and opt-in documentation. You may want to verify the current guidance in GHL's Trust Center for your specific situation, as use case policies can be updated by carriers.

3. How to Complete the Campaign Registration Fields

Campaign registration fields are completed during the same Trust Center session as brand registration. Once you submit brand details, you are taken to the campaign details page. Navigate to Settings Phone Numbers Trust Center in your GHL sub-account. Verify the current navigation path in your own account as the interface may update.

Field 1: Messaging Use Case

Select the use case that most accurately describes the primary purpose of your SMS campaign. This is one of the most critical fields in the entire registration process carriers approve or reject campaigns based on whether your messaging content, opt-in flow, and stated intent match the use case requirements.

Use caseWhat it coversBest forCommon mismatch to avoid
Customer CareOngoing customer support, service follow-up, account notificationsService businesses managing existing clientsDo not use for lead generation or new prospect outreach
MarketingPromotional messages, offers, new product announcementsBusinesses running offer-based SMS campaigns to opted-in listsDo not use if your messages are purely transactional
MixedCombination of marketing and transactional in the same campaignBusinesses whose SMS flow includes both reminders and promotional contentUse sparingly mixed campaigns face more scrutiny during review
Appointments and RemindersAppointment confirmations, reminders, schedulingHVAC, dental, medical, coaching, any appointment-based businessDo not use for marketing offers alongside reminders register separately
Two-Factor Authentication / OTPSecurity codes, login verification, one-time passwordsSaaS, fintech, any platform verifying user identity via SMSDo not mix OTP with marketing content in the same campaign
NotificationsTransactional alerts, order updates, account activityEcommerce, software platforms, delivery servicesDo not use for promotional content
THE RULE THAT CAUSES MOST USE CASE REJECTIONS

The campaign description must match your business niche. Carriers review whether your website supports the stated use case. A pizza restaurant registering under an 'appointment reminder' use case when their website shows no booking or scheduling functionality will be rejected. Your website, your business type, and your campaign use case must be consistent with each other. Verified from GHL's official A2P approval guide.

Field 2: Campaign Use Case Description

This field is the most important piece of written content in your entire A2P registration. It must answer three specific questions:

  • Who is the sender? Your full business name, including any DBA name if applicable. If you are operating under a DBA name, include the phrase 'We are doing business as [DBA Name]' in this field.
  • Who receives the messages? Describe who your recipients are and how they came into your contact database. Example: 'customers who booked an appointment through our website and opted in to receive SMS notifications.'
  • Why are messages being sent? Explain the specific purpose and content of the messages. Example: 'appointment confirmation messages and day-of reminders to reduce no-shows.'
EXAMPLE USE CASE DESCRIPTION

'This campaign sends appointment confirmation and reminder messages to customers of [Business Name] who have booked a service appointment through our website at [website URL] and provided explicit consent to receive SMS notifications during the booking process. Messages include appointment details, confirmation links, and reminder alerts. Business name and opt-out instructions are included in every message. Message frequency varies based on upcoming appointments.'

IMPORTANT

GHL's own guidance states that examples are for reference only copying them verbatim may cause rejection. Write a description specific to your actual business and messaging scenario. You may want to verify this warning is still current in GHL's Trust Center before submitting.

Field 3: Sample Messages

Sample messages show carriers the exact type of content you plan to send. They are reviewed against your use case description and your opt-in flow to verify consistency.

CONFIRMED REQUIRED ELEMENTS

Every sample message must include all four of these elements confirmed from GHL's official campaign registration guide: (1) The contact's name or a placeholder for it (e.g., [First Name]). (2) A staff member's name or business contact reference. (3) Your business name. (4) Opt-out language: 'Reply STOP to unsubscribe' or equivalent.

GHL's registration form includes two sample message fields:

  • Sample Message 1: For promotional or marketing content.
  • Sample Message 2: For transactional or informational content.
SAMPLE MESSAGE EXAMPLES

Transactional: 'Hi [First Name], this is Sarah from Peak HVAC. Your service appointment is confirmed for tomorrow at 2pm. Reply STOP to unsubscribe or HELP for help.'

Marketing: 'Hi [First Name], Peak HVAC here. Our spring AC tune-up special ends Friday book online at [link] and save $30. Reply STOP to opt out.'

CRITICAL

Your sample messages must reflect the content you will actually send. Do not write sample messages that promise content you do not send. Carriers compare sample messages against your actual traffic after approval.

4. Selecting Your Opt-In Method

You must document how contacts give consent to receive SMS from your business. GHL's Trust Center asks you to select one or more opt-in methods and provide a publicly accessible URL where the opt-in can be reviewed.

Opt-in methodDescriptionURL requirement
Website FormContact submits a web form with a phone number field and an SMS consent checkboxDirect URL to the specific form page not just the homepage. Must be publicly accessible without login.
Paper FormPhysical form signed in personPhotograph or scan of the form hosted at a publicly accessible URL
Facebook Lead FormLead ad with phone number collection and consent languageURL to the Facebook Lead Ad or a screenshot hosted at a public URL
QR CodePrinted QR code that leads to an opt-in formURL the QR code links to
KioskIn-person digital device where contacts opt inURL to the kiosk form or a screenshot at a public URL
VerbalVerbal confirmation of consent at time of contactWritten policy document hosted at a public URL describing the verbal consent process

These rules are confirmed from GHL's official support portal and the A2P approval best practices guide. Apply all of them before submitting.

  • Checkboxes cannot be pre-selected. The user must actively check the consent box. A box that is checked by default at page load is non-compliant and causes campaign rejection.
  • SMS consent must be optional, not required for form submission. If a contact can only submit your form by also consenting to SMS, that is forced consent and is not compliant. If phone number is a required field, the SMS consent checkbox must still be optional.
  • Marketing and non-marketing consent must be separated. If your campaign includes both promotional and transactional messages, use separate checkboxes for each type. A single combined checkbox is insufficient.
  • Opt-in consent and Privacy Policy/Terms of Service must be separate checkboxes. Do not combine SMS opt-in language with your general Privacy Policy acceptance into one checkbox.
  • Opt-in must be collected per campaign and is not transferable. Consent obtained for one type of messaging does not extend to another type. If a contact opted in for appointment reminders, you cannot use that consent to send promotional offers without separate explicit consent.
  • If using Chat Widget as your opt-in method: You must remove consent checkboxes from ALL other forms on your website. Having consent checkboxes on other forms while using Chat Widget as the designated opt-in method may result in campaign rejection confirmed from GHL's Pre-Built A2P Campaign guide.

For copy-paste compliant consent language that meets these requirements: A2P Opt-In Language Templates →

Privacy Policy and Terms of Service Requirements

Your Privacy Policy must include a specific statement about SMS data. Confirmed from GHL's official support portal: your Privacy Policy must state that no mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Information sharing with subcontractors in support services such as customer service is permitted.

  • Privacy Policy must be publicly accessible: The link must open without requiring a login. Use a direct link to the Privacy Policy page not the homepage.
  • Terms of Service must be separately linked: A combined Privacy Policy and Terms of Service page is acceptable as long as both are clearly present. Ensure the links are visible in the footer of every form used for opt-in.
  • No language about data sharing with affiliates: If your Privacy Policy mentions sharing user data with affiliates or third parties for any marketing purpose, this will likely cause rejection. Review and update your Privacy Policy before submitting.
  • Ensure links are not obscured: Pop-ups, overlays, or design elements that hide or cover the Privacy Policy and Terms of Service links will cause rejection.

6. What Happens After Campaign Review?

  • Approved: Your campaign is assigned an approved status. Phone numbers associated with this brand are cleared for A2P messaging under the registered use case. It can take up to 3 business days for all US carriers to receive the updated approval information. During this period you may see some message failures with an error indicating no A2P approval is found. This is normal and resolves as carrier records propagate.
  • Rejected: Your campaign dashboard in GHL shows a 'View required fixes' link next to each rejection reason. This was updated in March 2026 and now provides four structured fields per rejection: the error code, the rejection category, what it means, and the specific correction needed. For the complete rejection fix guide: A2P campaign rejected fix guide →
  • Edit and resubmit: If rejected, edit the existing campaign with all required corrections and resubmit. No additional vetting fee applies when you edit and resubmit. A new $15.75 fee applies if you delete the campaign and create a new one. Do not delete.

For the full breakdown of registration fees, monthly campaign fees, and carrier per-message charges: A2P 10DLC Fees Explained →

7. The Most Common Campaign Registration Mistakes

Use case does not match business website

What happens: Carrier reviewers check the website. A dental practice registering under "notifications" with no relevant content on their site gets rejected.

How to avoid it: Verify your website clearly reflects the business type and use case before submitting. The campaign description must be consistent with what a reviewer would see on your website.

Vague campaign description

What happens: Descriptions that say "we send marketing messages to customers" without specifying who receives them or why are rejected for insufficient detail.

How to avoid it: Answer all three questions explicitly: who is the sender, who are the recipients, and why are the messages being sent. Include your business name.

Sample messages missing required elements

What happens: Missing opt-out language, missing business name, or missing contact name placeholder causes rejection.

How to avoid it: Include all four required elements in every sample message: contact name or placeholder, staff name or business contact reference, business name, and "Reply STOP to unsubscribe."

Pre-selected consent checkbox

What happens: A consent checkbox that is checked by default fails carrier review.

How to avoid it: Never set a checkbox to checked by default. The user must take affirmative action to select it.

Privacy Policy missing SMS data clause

What happens: If your Privacy Policy does not state that mobile data will not be shared with third parties for marketing, the campaign is likely to be rejected.

How to avoid it: Add an explicit SMS data statement to your Privacy Policy before submitting. Verify it is live at the URL you provide.

Opt-in URL requires login to access

What happens: Carriers cannot review a form behind a login or paywall.

How to avoid it: Use a publicly accessible URL. If your form is behind a login, create a public landing page with the form visible for the review period.

Campaign description matches the GHL example verbatim

What happens: GHL explicitly states that copying their example descriptions may cause rejection.

How to avoid it: Write a description specific to your actual business, recipients, and message content.

FROM OUR REGISTRATION EXPERIENCE

The campaign registrations that pass on the first attempt share one characteristic: every field is internally consistent. The business website, the campaign description, the use case selection, the sample messages, and the opt-in URL all describe the same business doing the same thing for the same audience.

See how our clients use GHL SMS automations after A2P approval: real GoHighLevel results and case studies →

To have your A2P registration handled by our team: book a free strategy call at ghlscaleup.com/contact →

Once your campaign is approved and messaging is live, the first automation to build: GoHighLevel Missed Call Text Back →

8. Frequently Asked Questions

Do I manually submit my A2P campaign in GoHighLevel?

No. Once your brand registration is approved, GoHighLevel automatically submits the associated campaign for carrier review. You do not need to take any additional action to trigger the campaign submission. What you control is the campaign information you entered during the Trust Center registration process that data is what gets reviewed. This applies to both Standard Brand and Sole Proprietor registration flows. Campaign review typically takes 3 to 7 business days after brand approval.

What use case should I select for appointment reminders in GoHighLevel?

Select the Appointments and Reminders use case if your primary message type is confirming and reminding contacts about scheduled appointments. If your messages are purely appointment-related, this is the most accurate and specific use case. If you also send promotional messages to the same contacts, you would need to register a separate campaign for the marketing use case. You may want to verify the current use case options in GHL's Trust Center as carrier guidelines can be updated.

What must be included in A2P sample messages?

Every sample message submitted for A2P campaign registration must include four elements, confirmed from GHL's official campaign registration guide: (1) the contact's name or a placeholder such as [First Name]; (2) a staff member's name or a business contact reference; (3) your business name; (4) opt-out language 'Reply STOP to unsubscribe' or equivalent. Sample messages must accurately reflect the content you will actually send. Do not write sample messages that promise content you do not plan to send.

Can I require SMS consent to submit a web form for A2P registration?

No. Confirmed from GHL's official support portal: SMS consent must always be optional, even when a phone number field is required. You cannot make form submission conditional on the contact checking the SMS consent box. The checkbox must remain unchecked by default and the user must actively select it. Additionally, the SMS opt-in checkbox must be separate from the Privacy Policy and Terms of Service consent checkbox.

What must my Privacy Policy include for A2P campaign registration?

Your Privacy Policy must explicitly state that no mobile information will be shared with third parties or affiliates for marketing or promotional purposes. This is confirmed from GHL's official A2P compliance guide. Information sharing with subcontractors in support services such as customer service is permitted. The Privacy Policy must be publicly accessible without login, must be linked clearly in the footer of every form used for opt-in, and must not be obscured by pop-ups or other design elements.

Can I register more than one A2P campaign in GoHighLevel?

Yes. If your business sends different types of messages for example, appointment reminders and promotional marketing messages you should register separate campaigns for each use case. Each campaign requires its own description, sample messages, and opt-in documentation. You cannot use one campaign for multiple meaningfully different message types. You may want to verify the current guidance on multiple campaign registration in GHL's Trust Center, as policies can be updated.

How long does A2P campaign registration take in GoHighLevel?

Campaign review typically takes 3 to 7 business days after your brand is approved. Once both brand and campaign are approved, it may take up to 3 additional business days for all US carriers to receive the approval information. During this period you may see some message failures with an error indicating no A2P approval is found this is normal and resolves as carrier records propagate. If it persists beyond 4 business days after approval, contact GHL support.

What happens if my A2P campaign is rejected after I submit corrections?

If your campaign is rejected after resubmission, carriers may surface additional issues in the second review that were not flagged in the first. Treat each rejection cycle as a new review rather than a repetition of the same problem. Check the 'View required fixes' link in your GHL Trust Center for the specific new rejection reasons. If you believe the rejection is incorrect and your submission is fully compliant, you can contact GHL support to request a review. Editing and resubmitting does not incur an additional $15.75 vetting fee. Deleting and recreating the campaign does.

Need your A2P campaign registration handled correctly the first time?

GHL Scale Up handles A2P registration for agencies and their clients. Campaign description, use case selection, sample messages, opt-in documentation, and full Trust Center walkthrough managed end to end.

Book Your Free Strategy Call
GHL Scale Up
GHL Scale Up Team
GoHighLevel expert agency · 5+ years GHL experience · 200+ A2P registrations completed globally

All steps and rules in this guide are verified against GoHighLevel's official support portal as of July 2026. Navigation paths, fees, and carrier policies may change always verify in GHL's Trust Center before submitting. This is not official GoHighLevel documentation.

ghlscaleup.com