GoHighLevel A2P Sub-Account Registration Guide (2026)

There is a gap that trips up almost every agency that scales past a handful of GoHighLevel clients. They get their own A2P 10DLC registration sorted, their workflows start firing, everything looks fine in the GHL dashboard, and then they start onboarding clients. The client SMS goes out. GHL marks it delivered. The client calls to ask why nobody texted them back.

The reason is that each client sub-account is a separate registered entity under the A2P system. The agency's own approved campaign does not extend to client businesses. It never did. The carriers verify the brand that is doing the sending, and the brand on a client sub-account is the client's business, not the agency. Running live SMS automations under an unregistered client brand is the same risk exposure as running no registration at all.

This guide is for agencies who have handled their own A2P registration and now need to understand what compliance looks like at scale. The registration approval process itself is covered in a separate guide. This one focuses on the per-client requirement, what happens when it is missing, and how to audit your current client base.

Why does every client sub-account need its own A2P registration?

The A2P 10DLC system was designed around brands, not platforms or resellers. When a carrier evaluates an SMS message, it checks: which brand registered this sending number, what campaign purpose was declared, and whether the message content matches that declared purpose. The answer it is looking for is the business that owns the number, which in a GoHighLevel agency model is the client, not the agency.

The key distinction is between the sub-account ownership structure in GHL and the brand-level structure the carriers see. In GHL, the agency holds a master account and each client runs inside a sub-account. From the carrier's perspective, each of those sub-accounts is a distinct brand. HighLevel's own documentation is explicit: one approved campaign cannot be reused across unrelated businesses. A dental clinic sub-account needs a dental clinic brand registration. A real estate sub-account needs a real estate brand registration.

This applies regardless of what plan the agency is on. Unlimited sub-accounts on the Agency Pro plan does not include blanket A2P coverage for all those sub-accounts. The messaging compliance layer sits at the carrier level, outside GoHighLevel's pricing structure.

What happens when a client sub-account runs without A2P registration?

Two things happen, both bad and neither visible at the moment they occur.

The first is message blocking. All major US carriers have blocked unregistered 10DLC traffic since February 2025. There is no grace period and no warning sent to the GHL account. The workflow executes inside GoHighLevel, the platform marks the message as sent, and the carrier drops it before delivery. The client's CRM shows no indication of failure. The business thinks its SMS automation is working. The lead or customer never receives the message.

This is the failure mode that costs agencies the most. A missed appointment reminder, a lead follow-up that never arrived, a re-engagement campaign that sent to zero people. The revenue damage from silent SMS blocking is invisible until the client asks why their booked-call rate dropped or their re-engagement campaign generated no responses.

The second issue is fine exposure. While message blocking happens to every unregistered sender, T-Mobile enforcement fines apply to the entity whose traffic is being reviewed. The fine structure matters here because the amounts are meaningful.

What are the T-Mobile fines for unregistered SMS?

T-Mobile's enforcement framework distinguishes between general non-compliance and content-specific violations.

The most relevant fine for agencies whose clients are simply not registered is the text-enablement violation: $10,000 for text-enabling a 10-digit number and sending messages prior to carrier verification. This is per BCM One's published carrier documentation, sourced from T-Mobile's A2P code of conduct. Source: BCM One: 10DLC Registration Fees and Non-Compliance Fines.

There is also a program evasion fine of $1,000 per incident for practices like snowshoeing (spreading traffic across unregistered numbers to avoid detection) or unauthorized number replacement.

For content violations, the Severity-0 fine structure effective February 15, 2024 applies to all A2P products on the T-Mobile network:

Source: GoHighLevel Changelog: New Sev-0 Fines on Prohibited A2P Traffic, effective February 15, 2024.

The practical risk for most agencies is not the content tiers. It is the basic text-enablement fine for running SMS through unregistered sub-accounts. An agency with 20 clients that has not completed per-client registration is sitting on $200,000 in potential exposure across a T-Mobile enforcement action. That math tends to focus people quickly.

How much does A2P registration cost per client?

The registration fees are low enough that the cost of compliance is not a real barrier. Per HighLevel's published fee schedule:

One-time registration fee per client:

Monthly campaign fee per client:

Source: HighLevel: A2P 10DLC Messaging Fees.

The realistic cost for a standard client sub-account is $24.50 one-time plus $10.00 per month. For 20 clients that is $490 in one-time setup and $200 per month in ongoing fees, against a potential $10,000 per-violation fine for the agency. Any agency passing compliance costs to clients (which is standard practice) covers this easily.

One note on additional campaigns: if a client needs a campaign under an already-registered brand, that runs $15.00 one-time. Rejected campaign resubmissions are free.

How do you audit your agency for A2P compliance?

A three-step check covers the current state of any GoHighLevel agency account.

Step 1: Pull the sub-account list. In the agency master account, navigate to Sub-Accounts and export or scroll through all active clients. Flag any with SMS workflows enabled. These are the accounts that need verification.

Step 2: Check A2P status per sub-account. Open each flagged sub-account, go to Settings, then Phone Numbers, then A2P Registration. The status column shows Approved, Pending, Rejected, or Not Started. Any sub-account showing Not Started or Rejected with live SMS workflows is actively sending through an unregistered path.

Step 3: Prioritize by SMS volume. Not Started sub-accounts with high outbound SMS volume are the highest-risk entries. Address these first. Pending accounts are in-flight; do not restart them. Rejected accounts need to identify the rejection reason and resubmit, which is free.

The widget-first registration path described in the GoHighLevel A2P registration guide is the fastest path for clients whose websites support it. For clients who cannot embed the LeadConnector chat widget as their sole SMS opt-in, the classic manual registration path is the fallback.

What is the fastest way to register multiple client sub-accounts?

There is no single bulk-registration tool that covers all sub-accounts simultaneously. Each client brand registers independently. The efficiency gains come from process, not automation.

Three practices that reduce per-client registration time:

Standardize the onboarding checklist. Every new client signs off on A2P registration as a condition of SMS activation, not as an afterthought. Collect the information that registration requires before their first workflow goes live: legal business name, EIN or SSN (sole proprietors), physical address, business website, and description of the SMS use case.

Use the widget-first path for every eligible client. The widget-first flow removes the hand-written consent language that drives most rejections. It generates locked, carrier-compliant disclosure text and validates the widget installation against a public URL before submission. This path is not available for every use case, but it is the right default for standard marketing and transactional campaigns.

Audit before activation, not after. The most expensive A2P failure is a client whose SMS automations go live before registration completes. A simple workflow rule in the agency account that checks A2P status before enabling SMS-based workflows catches this at the account level rather than the carrier level.

For clients whose campaigns are rejected, the rejection code tells you what the reviewer flagged. The most common rejections come from consent language that does not match the opt-in mechanism on the website, and from campaign descriptions that do not match the actual message content. These are fixable with documentation, not additional fees. Resubmission is free.

Is there an agency-level A2P registration that covers all clients?

No. There is no single GoHighLevel agency registration that covers client sub-accounts. Each client brand is registered as a separate entity with the Campaign Registry, and the approval or rejection belongs to that brand, not to the agency account that manages it. This is by design at the carrier level: the compliance obligation belongs to the business that is sending the messages, not to the platform or reseller facilitating it.

The practical implication is that compliance is part of client onboarding, not something handled once for the whole agency. Agencies that build it into their standard client setup process report fewer SMS failures and essentially zero surprise compliance issues. Agencies that treat it as optional until a problem appears tend to encounter that problem at scale.