GoHighLevel SMS Restrictions: What Changed in Nov 2026

Updated

Short answer: On November 10, 2026, HighLevel (GoHighLevel, or GHL) announced new rules for pausing a sub-account's texts. Standard pauses now last 12 hours, "compared with the previous 24 to 48 hours". A mature sub-account is paused at a 6% opt-out rate or a 25% Error 30007 rate, where the old rules lock it at 3% opt-outs or 10% delivery errors, and nothing triggers below 500 texts in 7 days. The new rules are "currently available to a selected group of sub-accounts as part of a phased evaluation". The others keep the old rules while HighLevel assesses the results.

What changed

HighLevel announced the change in its changelog and updated its help article on messaging quality monitoring the same day. Its restriction-history article and messaging policy still describe the old rules. Side by side:

Old rulesNew rules
Who has themSub-accounts outside the evaluation"a selected group of sub-accounts"
What countsOpt-outs, and delivery errors such as unreachable numbers, landlines and carrier filteringOpt-outs, and only Error 30007 (carrier filtering), over a rolling 7 days once 500 texts are sent
WarningsBy emailBy email, at 4% opt-outs or 15% Error 30007 in a mature sub-account
Texts pause at3% opt-outs or 10% errors6% opt-outs or 25% Error 30007 in a mature sub-account
How long a pause lasts24 hours, or until 00:00 UTC in the messaging policy12 hours, or 24 hours for a relapse within 72 hours
What pausesAll outbound SMS, except one-on-one conversations, test SMS, resend message and Missed Call Text BackBulk Actions, workflow "Send SMS" actions and Campaigns
Lifting a pause earlyAgency owners and admins, in agencies on HighLevel for at least 3 months and not in a trial (December 2024 changelog)Agency owners and agency admins, once every 24 hours, with each lift logged

The new rules also set separate thresholds for young sub-accounts, with "fewer than 7 days of SMS sending history", and for a relapse. They watch a mature sub-account for 72 hours after a restriction ends, leave RCS messages out of the count, and describe a manual review that only Support can clear. HighLevel says its initial testing showed "80% fewer messaging restrictions."

The full thresholds table, the pause lengths, lifting early and the old rules in detail are in why GoHighLevel paused your SMS.

Who gets the new rules

HighLevel's help article says:

"These improvements are rolling out to a selected group of sub-accounts as part of a phased evaluation. Other sub-accounts keep the existing safeguards while results are assessed. Existing safeguards for newly created sub-accounts remain unchanged."

The changelog says the same under "Gradual Rollout". Neither page says which sub-accounts are in the group, how long the evaluation will run, or how to tell which rules a sub-account has. HighLevel's restriction-history article, last changed in August 2026, still gives the old 3% and 10% limits. The help article also gives thresholds for young sub-accounts and does not say how they fit with the sentence on newly created sub-accounts.

What stays the same

  • The messaging policy. Quality monitoring "works alongside the LC - Phone Messaging Policy, which covers consent, opt-out language, sender ID, spam handling, DND, and daily sending limits." The 8-level ramp for new sub-accounts is part of that policy.
  • Replies. "As before, 1:1 messaging through Conversations remains available during temporary bulk messaging restrictions".
  • One sub-account at a time. "Rates are measured and restrictions are applied per sub-account."

A checklist for agencies

  1. Watch the inbox the emails go to. HighLevel's three emails, "Messaging quality alert", "SMS temporarily paused" and "Support review required", go to "the agency account owner and the administrators of the affected sub-account". HighLevel asks you to make sure the agency owner email on file "is actively monitored."
  2. Act on the warning. A warning pauses nothing. Pause the workflows, campaigns and bulk actions going to contacts without clear opt-in, and talk to the client before bulk sends resume.
  3. Decide who may lift a pause. Only an agency owner or agency admin can, once every 24 hours, and each lift is logged. Lifting "does not reset your rates", so fix the cause first.
  4. Plan for the 72 hours after a pause. In a mature sub-account, 10% opt-outs or 40% Error 30007 in that time brings a 24-hour restriction right away.
  5. Tell client teams what still works. Under both sets of rules, one-to-one replies and Missed Call Text Back keep working during a restriction. Under the new rules, RCS does too, while Bulk Actions, workflow "Send SMS" actions and Campaigns stop.
  6. Aim below both sets of limits. If you don't know which rules a sub-account has, keep its opt-out rate under 3%, and its delivery error rate and Error 30007 rate under 10%. That stays below the old lock and below every warning level in the new rules. HighLevel calls 0 to 1% opt-outs and 0 to 6% delivery errors good.
  7. Check Restriction History. Sub-account > Settings > Phone System > Messaging > Restriction History shows each restriction, why it happened and how it ended.

Precheckly's Pro plan checks the delivery of your texts every day: what failed, why and what to fix. The Agency plan does this across 10 sub-accounts and adds alerts when texts start failing. See pricing. These are platform and carrier rules, not legal advice.

Sources

We read these pages on November 16, 2026.

Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.