Fixing GHL SMS Failures: A Comprehensive Guide to Compliance

Your GoHighLevel SMS stopped delivering. Your numbers were working last month. Now they're not. You added new numbers, submitted the registration, and they got rejected — again. You have no idea if it's A2P, Twilio, your brand registration, your campaign use case, or some combination of all four. This is the most common failure state in GHL phone infrastructure right now, and almost nobody who documents it online explains what's actually happening at the carrier and regulatory layer. This post does.

The brief: a client with two GHL subaccounts, existing numbers that stopped sending, new numbers getting rejected during A2P and regulatory approval, needing reliable SMS delivery to the United States, United Kingdom, and Australia — all simultaneously. Three existing numbers to restore, three new numbers to fully operationalize, and a compliance architecture that doesn't collapse the next time a carrier updates its filtering rules.

What follows is the complete diagnostic and build. Why numbers fail, why registrations get rejected, how A2P 10DLC, Toll-Free verification, UK regulatory bundles, and Australian sender compliance each work, and the exact configuration sequence that resolves all of it. No trial-and-error. No generic "submit your brand registration" advice. The full system.

Why GoHighLevel SMS Stops Working: The Five Root Causes

Most GHL users who hit SMS delivery failures assume the problem is in GHL itself. It rarely is. GHL's phone system runs on Twilio's infrastructure (marketed as LC Phone when provisioned directly through GHL). The failures happen at four layers above GHL — and understanding which layer is failing determines everything about the fix.

For the client in this brief — two subaccounts, six numbers across three countries, a mix of existing failures and new rejections — all five failure layers were present simultaneously. The fix is not a single action. It is a sequenced remediation across each layer, in the right order, because some registrations are prerequisites for others.

"SMS delivery failures in GHL are almost never a GHL problem. They are a compliance infrastructure problem. The platform is fine. The registration architecture underneath it is broken." Arsalan Faysal — Revenue Systems Architect, GoHighLevel Expert Partner

The Diagnostic Framework: Reading Twilio Error Codes

Before touching any registration, run a complete audit of what's actually failing and why. GHL's conversation logs show message status but not the carrier-level error code. For that, you need the Twilio console (or LC Phone logs if you're on GHL's native phone).

Step 1: Pull Twilio Error Logs

In Twilio console: navigate to Monitor → Logs → Messaging. Filter by date range and direction (outbound). Every failed message shows an error code. These codes are the diagnostic ground truth — not the GHL conversation status.

Map every failing number to its error code. This is your repair sequence. Numbers throwing 30034 and 30035 have different fixes. Do not run both fixes simultaneously — complete and confirm each registration before layering the next one.

Step 2: Audit GHL Subaccount Configuration

In GHL, navigate to each subaccount → Settings → Phone Numbers. For every number, confirm:

• The number appears in the subaccount phone list (not just at the agency level)
• SMS capability is toggled on (some numbers are provisioned voice-only)
• The number is assigned to the correct subaccount (agency-level numbers need explicit subaccount assignment)
• The LC Phone integration status shows "Active" — not "Pending" or "Error"

Document the status of all six numbers in a tracking sheet before touching anything. Numbers that look broken in GHL but are fine at the Twilio layer just need subaccount reassignment. Numbers that look fine in GHL but failing at Twilio need compliance remediation. The two problems have different root causes and different fix sequences.

US SMS Fix: A2P 10DLC Registration in GoHighLevel

A2P 10DLC (Application-to-Person, 10-digit long code) is the US carrier framework that governs all business SMS sent from standard US phone numbers. It has been mandatory since 2023. Every business sending SMS to US numbers — regardless of platform — must register a brand and at least one campaign through The Campaign Registry (TCR), linked to their sending numbers.

In GHL, this registration lives at: Agency Settings → Phone → A2P Registration (or within each subaccount's Settings → Phone Numbers → A2P Registration, depending on your GHL version).

The Three-Layer A2P Stack

LAYER 1 — BRAND REGISTRATION (one per business entity)
──────────────────────────────────────────────────────────────────
  Required fields:
  • Legal business name (must match EIN/TIN exactly)
  • EIN / Tax ID
  • Business type (LLC, Corp, Sole Prop, etc.)
  • Business address (must be US address for US brand)
  • Website URL (must be live and reference SMS opt-in)
  • Business contact (name, phone, email)
  • Vertical (e.g., Healthcare, Professional Services, Marketing)
  
  Common rejection reason: EIN does not match IRS records.
  Fix: Use exact legal name from EIN confirmation letter.
  Vetting fee: $4 (one-time, non-refundable via Twilio/TCR)

LAYER 2 — CAMPAIGN REGISTRATION (one per use case)
──────────────────────────────────────────────────────────────────
  Required fields:
  • Campaign use case (must match actual message content)
  • Sample messages × 2 (must include brand name + opt-out language)
  • Opt-in method description
  • Privacy policy URL
  • Terms of service URL
  • Message flow description
  
  Most common rejection reason: Sample messages don't include
  opt-out language ("Reply STOP to unsubscribe") OR brand name
  is missing from message body.
  
  Campaign fee: $10/month ongoing (paid to TCR via Twilio)

LAYER 3 — NUMBER ASSOCIATION
──────────────────────────────────────────────────────────────────
  Each sending number must be explicitly associated with an
  approved campaign. In GHL/Twilio, this happens automatically
  once the campaign is approved — but verify in Twilio console:
  
  Messaging → Services → [Your Service] → Phone Numbers
  
  If numbers are not listed here, add them manually.

Why Brand Registrations Get Rejected

There are five rejection patterns that cover 90%+ of failed A2P brand registrations:

1. EIN mismatch. The legal business name field must be an exact character-for-character match with what the IRS has on file for that EIN. "Arsalan Faysal LLC" and "Arsalan Faysal, LLC" are different strings. Pull the original EIN confirmation letter and copy the name exactly.
2. Sole proprietor registered as a business. TCR treats sole proprietors differently. If no EIN exists, register as an individual with SSN. Do not attempt to register a sole prop as an LLC — it will fail the IRS lookup.
3. Website does not have an SMS opt-in disclosure. Your website must have a visible privacy policy that mentions SMS communications and a terms-of-service page. Carrier vetting bots check for this. A landing page with no legal pages will fail.
4. Vertical mismatch. Registering as "Healthcare" but sending marketing messages gets flagged. Your vertical, campaign use case, and sample message content must be internally consistent.
5. Duplicate brand registration. If a previous (failed) brand registration exists in TCR under the same EIN, submitting a new one creates a conflict. You must delete or appeal the failed registration before resubmitting.

Why Campaign Registrations Get Rejected

Campaign rejections are almost always content-related. The two non-negotiable elements that must appear in every sample message:

Toll-Free Number Verification (US)

If the client's existing US numbers are toll-free (800, 833, 844, 855, 866, 877, 888 prefixes), A2P 10DLC does not apply — but Toll-Free Verification (TFV) does. These are completely separate registration systems.

Since August 2023, all toll-free numbers sending more than a minimal volume of messages to US carriers must be verified. Unverified TFN traffic is hard-blocked by AT&T, T-Mobile, and Verizon. This is likely the primary cause of the "previously worked, now doesn't" failure pattern described in the brief.

TFV submission lives in the Twilio console under Phone Numbers → Manage → Toll-Free Verification. Required fields:

• Business name and address
• Business website with SMS opt-in disclosure
• Message use case description
• Sample message (same content requirements as A2P — brand name + opt-out)
• Estimated monthly message volume
• Opt-in method (web form, point-of-sale, verbal confirmation)

Approval timeline: 3–7 business days. There is no expedited path. Submit it before anything else in this engagement because it is time-gated and cannot be parallelized.

UK SMS Fix: Regulatory Bundles and Ofcom Compliance

The UK does not use A2P 10DLC. UK phone number provisioning is governed by Ofcom (Office of Communications) and regulated through Twilio's UK regulatory bundle system. Every UK local phone number requires a verified address bundle before it can be activated for SMS.

This is the most common reason new UK numbers get immediately rejected in GHL/Twilio — the regulatory bundle either doesn't exist or was submitted with incorrect documentation.

UK Regulatory Bundle: What It Is and How to Build It

A UK regulatory bundle in Twilio is a verified collection of business identity documents linked to a UK address. Twilio submits this to Ofcom on your behalf. Without an approved bundle, UK numbers cannot be activated.

UK REGULATORY BUNDLE ARCHITECTURE
──────────────────────────────────────────────────────────────────

STEP 1: Create a UK Address in Twilio
  Path: Console → Phone Numbers → Regulatory Compliance → Addresses
  
  Required:
  • Street address (must be a real UK address — not a PO Box)
  • City, postcode
  • Country: United Kingdom
  
  Note: If the client does not have a UK physical address, a
  registered agent address or virtual office address is acceptable
  PROVIDED it is registered to the business entity. Mail forwarding
  services without business registration are rejected.

STEP 2: Create a Regulatory Bundle
  Path: Console → Phone Numbers → Regulatory Compliance → Bundles
  
  Select: UK Local Phone Number
  Business Profile: Link to existing business profile (or create)
  
  Required documents:
  • Business registration (Companies House number for UK entities
    OR equivalent for international businesses operating in UK)
  • Proof of address (utility bill, bank statement — issued within 90 days)
  • Authorized representative ID (passport or driving licence)

STEP 3: Submit Bundle for Twilio Review
  Twilio reviews the bundle before submitting to Ofcom.
  Review timeline: 2–5 business days.
  Status path: Pending → Twilio Review → Provisionally Approved → Active

STEP 4: Associate Bundle with UK Number
  Once bundle is approved, navigate to the UK number settings
  and associate the approved bundle.
  Numbers cannot be activated without this association.

Why UK Bundles Get Rejected

In order of frequency:

1. Address is a PO Box or unregistered virtual office. Twilio explicitly rejects PO Box addresses for UK bundles. The address must have a physical presence association.
2. Proof of address is more than 90 days old. Bank statements and utility bills must be current. A statement from last year fails immediately.
3. Business registration document doesn't match the trading name. If the GHL account is operated under a trading name that differs from the Companies House registered name, both names must be present in the documentation.
4. International business without UK nexus. A US-incorporated business that wants UK numbers needs to demonstrate legitimate UK operational presence. A UK phone number for a company with no UK address, no UK customers, and no UK trading history will be rejected. The workaround: provision UK numbers through a UK MVNO or use Twilio's international A2P routing where the business establishes a thin UK entity or partner arrangement.

UK SMS Content Rules (ICO / PECR Compliance)

Beyond number provisioning, UK SMS content is regulated by the Information Commissioner's Office (ICO) under PECR (Privacy and Electronic Communications Regulations). Key requirements that affect GHL workflow SMS:

• Explicit consent required for marketing SMS. Unlike the US, where implied consent frameworks exist in some contexts, UK PECR requires documented opt-in consent for marketing messages. This must be captured at the lead intake stage and stored in GHL as a custom field.
• Sender identification. Every marketing SMS must clearly identify the sender. This is separate from Twilio compliance — it's a content requirement.
• Opt-out mechanism. "Reply STOP" or equivalent must be present in every marketing message. Transactional messages (appointment reminders, booking confirmations) have more flexibility but best practice is to include opt-out regardless.

Australia SMS Fix: Sender ID Registration and ACMA Compliance

Australia is the most technically distinct of the three markets. The Australian SMS landscape does not use 10DLC or toll-free verification systems. Australian carriers — Telstra, Optus, Vodafone AU — route business SMS through Alpha Sender IDs: alphanumeric strings (your brand name) that replace the sending number in the recipient's inbox.

The Australian Communications and Media Authority (ACMA) Spam Act 2003 governs all commercial electronic messages, including SMS. Violations carry penalties of up to AUD $2.2 million per day for corporations.

How Australian SMS Actually Works

AUSTRALIAN SMS DELIVERY ARCHITECTURE
──────────────────────────────────────────────────────────────────

OPTION A: Alpha Sender ID (Recommended for brand recognition)
─────────────────────────────────────────────────────────────
  What the recipient sees: "BRANDNAME" instead of a phone number
  Character limit: 11 characters (alphanumeric)
  Example: "ARSALANFAY" or "REVOPSARCH"
  
  Registration: Via Twilio → Messaging → Sender ID Registration
  Required: Business name, use case, sample messages
  Timeline: 5–10 business days for AU carrier approval
  
  IMPORTANT: Alpha Sender IDs cannot receive replies.
  Two-way SMS to Australia requires a Long Number or Shared Short Code.

OPTION B: Virtual Long Number (VLN)
─────────────────────────────────────────────────────────────
  What the recipient sees: An Australian +61 mobile number
  Supports two-way messaging
  
  Provisioning: Via Twilio as +61 4XX XXX XXX number
  Regulatory: Standard Twilio AU number provisioning
  Filtering: Sent through AU carrier gateways directly
  
  Note: AU carriers filter high-volume VLN traffic aggressively.
  Keep message volumes below carrier thresholds or use
  multiple numbers with sending rotation logic in GHL.

OPTION C: Shared Short Code (Legacy — not recommended)
─────────────────────────────────────────────────────────────
  What the recipient sees: A short number (e.g., 19XXXX)
  Status: Being phased out by most AU carriers
  Do not provision new shared short code infrastructure.

ACMA Spam Act Compliance Requirements

Three requirements that every Australian commercial SMS must satisfy:

1. Consent. The recipient must have given express consent or have an existing business relationship (implied consent). Express consent requires documentation — a form submission, a checkbox, a verbal confirmation with a log record.
2. Sender identification. The message must clearly identify who sent it. If using an Alpha Sender ID, the brand name in the ID satisfies this. If using a VLN, the message body must include the business name.
3. Unsubscribe mechanism. Every commercial message must include a functional unsubscribe mechanism that the sender acts on within 5 business days. "Reply STOP" is acceptable. A link to an unsubscribe page is acceptable. Silence after STOP is a Spam Act violation.

Configuring Australian SMS in GHL

GHL does not natively expose Alpha Sender ID configuration in its phone settings UI (as of mid-2025). The configuration must be done at the Twilio layer:

• In Twilio console, navigate to Messaging → Sender ID Registration
• Submit the Alpha Sender ID string, business details, and use case description
• Once approved, create a Messaging Service in Twilio that uses the Alpha Sender ID as the sender for AU-destined messages
• In GHL, configure the relevant workflow SMS steps to route through the Twilio Messaging Service SID (not a direct phone number) for AU contacts

The GHL routing logic for AU contacts is typically handled by a contact tag or custom field (country = Australia) that triggers a different workflow branch using a different Twilio sending path. This requires a conditional logic split in your GHL automation workflows.

The Full Architecture: GHL SMS Across US, UK & Australia

With all three compliance layers understood, here is the complete system architecture for a GHL deployment that reliably delivers SMS to all three markets from two subaccounts.

GHL MULTI-COUNTRY SMS ARCHITECTURE
──────────────────────────────────────────────────────────────────

AGENCY LEVEL (Twilio / LC Phone)
  ├── US Number Pool
  │   ├── TFN-001 (Toll-Free) → TFV submitted + approved
  │   ├── 10DLC-001 (Local)  → Brand registered, Campaign approved
  │   └── 10DLC-002 (Local)  → Same campaign, additional number
  │
  ├── UK Number Pool
  │   ├── UK-001 (Local +44) → Regulatory Bundle approved + associated
  │   └── UK-002 (Local +44) → Same bundle (one bundle covers multiple UK numbers)
  │
  └── AU Sending Layer
      ├── Alpha Sender ID: "BRANDNAME" → AU carrier approved
      └── AU VLN-001 (+61) → Backup for two-way AU conversations

SUBACCOUNT 1 (Primary business operations)
  ├── Assigned numbers: TFN-001, 10DLC-001, UK-001
  ├── Workflows use contact country field to route:
  │   IF country = US → send via TFN-001 or 10DLC-001
  │   IF country = UK → send via UK-001
  │   IF country = AU → send via Twilio Messaging Service (Alpha ID)
  └── A2P Campaign: linked to 10DLC-001

SUBACCOUNT 2 (Secondary / overflow)
  ├── Assigned numbers: 10DLC-002, UK-002, AU VLN-001
  ├── Same routing conditional logic
  └── A2P Campaign: same TCR brand, separate campaign registration

MESSAGE FLOW (simplified)
──────────────────────────────────────────────────────────────────
  GHL Contact Created
        │
        ▼
  [Workflow Trigger fires]
        │
        ▼
  [Conditional Branch: contact.country]
        │
  ┌─────┴─────┬─────────────┐
  ▼           ▼             ▼
 US          UK            AU
  │           │             │
  ▼           ▼             ▼
TFN / 10DLC  UK Local     Alpha Sender ID
  │           │             │
  ▼           ▼             ▼
Twilio US   Twilio UK    Twilio AU Gateway
Carriers    (Ofcom        (Telstra/Optus/
            compliant)    Vodafone AU)

The Remediation Sequence: Restoring 3 Numbers, Approving 3 New Ones

Sequence matters. Some registrations depend on others being completed first. Running them out of order costs approval time.

Total elapsed time from Step 1 to completed, stable infrastructure: 7–14 calendar days, with the majority of the wait being regulatory approval windows rather than active build time. Active implementation hours: approximately 15–20h for an experienced GHL + Twilio specialist.

Keeping It Stable: Long-Term SMS Compliance Architecture

Fixing a broken SMS infrastructure once is the easy part. Keeping it from breaking again requires understanding the ongoing maintenance obligations that most GHL users ignore until the next failure.

What Breaks Registered Numbers Over Time

• Opt-out handling failures. If STOP messages are received but not processed (contacts not removed from sending sequences), US carriers will flag the number for spam patterns. In GHL, ensure the STOP keyword is configured in Settings → Business Info → Compliance and that it triggers an automatic contact opt-out tag that suppresses from all workflow steps.
• Message volume spikes on 10DLC numbers. Sudden volume increases on a registered 10DLC number trigger carrier filtering. If you're scaling a campaign, spread volume across multiple registered numbers rather than hammering one number. This is what the second 10DLC number (10DLC-002) in the architecture above is for.
• Campaign use case drift. A registered campaign for "Appointment Reminders" that starts sending promotional messages will eventually be flagged. If your use case expands, register a new campaign — don't shoehorn new content types into an existing registration.
• UK bundle documentation expiry. Proof of address documents submitted to Twilio for UK bundles can be flagged as stale during periodic Ofcom compliance reviews. Set a calendar reminder to refresh UK bundle documentation annually.
• Website changes that break compliance pages. Carrier vetting bots periodically re-crawl sender websites. If your privacy policy, opt-in disclosure, or terms of service pages are removed or changed to remove SMS references, re-vetting can result in suspension.

The Real Cost Structure: What Multi-Country SMS Actually Costs

The brief priced this at $25–$65/hour. That rate range is correct for someone who can do basic troubleshooting. It is significantly below market rate for someone who can navigate simultaneous US A2P, UK regulatory bundle, and AU sender ID compliance without trial-and-error. Here is the actual cost breakdown for running this infrastructure ongoing.

For a GHL deployment sending 5,000 messages/month across all three markets (roughly 60% US, 25% UK, 15% AU), the infrastructure cost is approximately $280–$350/month all-in including number rental, campaign fees, and message volume. The implementation cost to get the architecture correctly built and compliant is a one-time investment that pays back in the first month of avoided compliance failures.

Final Thoughts: SMS Compliance Is Infrastructure, Not a Checkbox

Every GHL operator who has hit this failure pattern — numbers that worked, then stopped; new numbers that get rejected on registration — treats it as a technical support problem. Submit a ticket, wait for Twilio to respond, hope someone fixes it.

It is not a support problem. It is an infrastructure architecture problem. The registration systems for US A2P, UK Ofcom compliance, and Australian ACMA regulations are not self-healing. They require correct initial setup, correct ongoing maintenance, and someone who understands what each error code means and which layer of the stack it's coming from.

The build documented here — six numbers, two subaccounts, three countries, fully compliant and stable — takes 15–20 hours of focused implementation work and 7–14 calendar days of approval windows. For a business whose GHL automations depend on SMS delivery, every day of non-delivery is pipeline leakage. The compliance infrastructure is not optional. It is the precondition for everything downstream — lead nurture, appointment reminders, follow-up sequences, and closed revenue — to function.

Build it right once. Document it. Maintain it quarterly. It does not break if it is built correctly.