Why GoHighLevel Paused Your SMS: Opt-Out and Error Limits

Updated

Short answer: HighLevel (GoHighLevel, or GHL) is moving some sub-accounts to new SMS restriction rules, while the others keep the old ones: a 24-hour lock on texting once the opt-out rate hits 3% or the delivery error rate hits 10%. The new rules count opt-outs and Error 30007 over a rolling 7 days, only once a sub-account has sent 500 texts, send a warning first and pause bulk and automated texts, usually for 12 hours. New sub-accounts can also be stopped for 24 hours by the daily ramp. Under either set, text only people who opted in, remove numbers that cannot receive SMS, and avoid content that carriers filter.

Two sets of rules

On November 10, 2026, HighLevel's changelog announced changes to its "SMS Compliance Safeguards", "to make messaging restrictions fairer and temporary pauses shorter." Its help article on messaging quality monitoring, updated the same day, says who gets them:

"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."

Neither page says how to tell which set a sub-account has, and HighLevel's restriction-history article still gives the old limits. So this guide covers both. For a side-by-side of what changed and a checklist for agencies, see what changed in November 2026.

The new rules

What counts

HighLevel tracks two rates for each sub-account. Either one alone can lead to a warning or a restriction.

  • Opt-out rate: "The percentage of contacts who reply with a standard opt-out keyword (e.g., STOP) after receiving your SMS".
  • Error 30007 rate: the share of messages carriers "flagged as filtered or blocked". HighLevel's changelog adds: "Only messages flagged by downstream providers with error 30007 count toward the carrier filtering rate."

"Both rates are measured over a rolling 7-day window for mature accounts, and only once a sub-account has sent at least 500 SMS in that window. Below 500 messages, no warnings or restrictions are triggered." RCS messages "are excluded from these calculations and from restriction enforcement entirely." Rates are measured, and restrictions applied, per sub-account, so one client's restriction does not pause another's.

The thresholds

The limits depend on how long the sub-account has been sending texts, and on whether it has just come out of a restriction. Young means "fewer than 7 days of SMS sending history", and mature means 7 days or more. A sub-account becomes mature on its own as it builds history.

Sub-accountOpt-out warningOpt-out restrictionError 30007 warningError 30007 restriction
Young3%10%10%50%
Mature4%6%15%25%
First relapse: mature, within 72 hours after a restriction ends4%10%15%40%

Each limit applies at that rate or above. HighLevel's advice is to stay under the warning levels, which it calls "the ceiling, not a healthy target."

How long a restriction lasts

A restriction pauses bulk, workflow and campaign texts. How each stage ends:

StageHow it ends
WarningNothing pauses. You get an email, and the warning "Clears on its own once your rates come back down".
First restriction, young sub-accountAfter 12 hours, or sooner if lifted. Then it clears.
First restriction, mature sub-accountAfter 12 hours, or sooner if lifted. Then 72 hours of monitoring.
Relapse during monitoringAfter 24 hours, or sooner if lifted. Then another 72 hours of monitoring.
Manual reviewOnly when HighLevel Support clears it.

If a mature sub-account reaches "10% opt-out or 40% Error 30007" during the 72 hours of monitoring, "a 24-hour restriction applies right away". Young sub-accounts have no monitoring period after a restriction. "Exceptionally high opt-out rates or significant carrier-reported filtering may lead to a manual review", which "has no automatic expiry and can't be lifted early".

Lifting a restriction early

"An agency owner or agency admin can end a 12-hour or 24-hour restriction early from the sub-account's phone settings." Regular users do not have the control. It can be used once every 24 hours, each use is recorded in the audit log, and it is not available while a manual review is open. HighLevel's November 2026 changelog says this works "when eligible" and does not list the conditions.

Lifting "restores sending but does not reset your rates." If the same messages go out again, another restriction follows, and a relapse lasts longer. Before you lift it, pause the workflows or campaigns that drove the rate up and clean the list they were sending to.

Manual review

To ask for a review, go to Sub-account > Settings > Phone Numbers and submit the Messaging Quality Review form, which creates the Support request. Only one review can be open per sub-account. Support looks at "your messaging practices, contact consent, and recent sending history" first, and bulk sending stays paused until it clears the review.

What keeps working

Paused during a restrictionKeeps working
Bulk Actions from the Contacts areaOne-to-one messages in Conversations
Workflow "Send SMS" actionsMissed Call Text Back, if you set it up
CampaignsRCS messaging

In HighLevel's words: "Replying to leads one-to-one in Conversations is never paused."

Emails and Restriction History

HighLevel sends three emails, all to "the agency account owner and the administrators of the affected sub-account":

EmailWhat it means
Messaging quality alertA rate crossed a warning threshold. Nothing is paused.
SMS temporarily pausedA restriction applies, and bulk and automated sending is paused.
Support review requiredThe sub-account needs a manual review, or a review outcome needs your attention.

HighLevel asks you to make sure the agency owner email on file "is actively monitored." The Restriction History tab is at Sub-account > Settings > Phone System > Messaging > Restriction History. It lists every restriction with its date and time, its type (temporary or manual review), the reason and the rate or count behind it, and how it ended, including whether it was lifted early. It has date filters, and HighLevel's restriction-history article says the times are in UTC.

The old rules: 3%, 10% and 24 hours

Sub-accounts outside HighLevel's evaluation keep the existing safeguards. HighLevel's article on SMS restriction history gives both limits:

  • "Once the opt-out rate hits 3%, the sub-account will be locked for sending text messages for 24 hours."
  • "Once the error rate hits 10%, the sub-account will be locked for sending text messages for 24 hours."

Its threshold table, in short:

MetricGoodTargetLockout (24 hours)
Opt-out rate0 to 1%Stay below 2 to 3%At 3%
Delivery error rate0 to 6%Keep under 10%At 10%

The old error rate is broader than the new one. HighLevel says a high delivery error rate means "you are sending SMS to contacts that are no longer in service, are unreachable, or use a non-SMS-capable device such as a landline", or that carrier filters are refusing your texts. It lists the typical causes of warnings and restrictions as "Daily / weekly sending limit violations", "High opt-out rate" and "High delivery error rate (including carrier filtering such as Error 30007)". Error 30007 is Twilio's code for a message that was "filtered (blocked) by Twilio or by the carrier."

HighLevel's LC Phone messaging policy describes the lock this way: "Once an account enters temporary suspension, all outbound SMS will fail until 00:00 UTC, when the suspension is automatically lifted." Some sending continues: "One-on-one conversations, test SMS, resend message, and Missed Call Text Back are still allowed even while an account is suspended." HighLevel's pages describe the length differently: 24 hours in the restriction-history article, until 00:00 UTC in the messaging policy, and "24 to 48 hours" in the November 2026 changelog.

On ending it early, the messaging policy says: "The suspension lifts automatically within 24 hours." HighLevel's changelog of December 17, 2024 adds that agency owners and admins can lift these restrictions themselves, but only in agencies that have been on HighLevel for at least 3 months and are not in a trial, and not for carrier suspensions.

The ramp for new sub-accounts

Since February 1, 2024, new LC Phone sub-accounts "follow an 8-level ramp". "All subaccounts start at Level 1, enabling 500 SMS within 24 hours." Once a sub-account sends its full level limit within 24 hours, "the subaccount is temporarily restricted from sending SMS for the next 24 hours." The ramp "starts on the day the first successful SMS message is sent", not on the signup date.

This stop comes from the ramp, not from your opt-out or error rates, and it is stricter about replies. Asked whether one-to-one messages can go out during this 24-hour restriction, HighLevel's policy answers "No" and says "that exemption has been removed."

The chart lines are not the limits

HighLevel's messaging analytics draw a 2% opt-out line and a 10% failure line. HighLevel says these lines "are analytics reference markers" and that "Messaging-policy warnings and suspensions use separate criteria based on factors such as sending volume, ramp level, error count, and opt-out performance." So crossing a chart line is not the same as reaching a limit under either set of rules. HighLevel considers an opt-out rate of about 0 to 1% healthy.

How to keep opt-outs low

  • Text only people who opted in. "Consent can't be bought, sold, or exchanged", and "SMS should only be sent to opted-in contacts." CTIA's guidance is the same: "Message Senders should not use opt-in lists that have been rented, sold, or shared to send messages."
  • Don't treat a form fill as consent. "Collecting a contact's phone number does not by itself establish consent to receive SMS messages." See SMS opt-in language.
  • Say who you are. HighLevel's policy requires the first message to a contact to identify the sender and to include wording such as "Reply STOP to unsubscribe". HighLevel adds that line and a sender line to first messages automatically.
  • Don't over-message. HighLevel warns that "repetitive outreach drives opt-outs faster than anything else."
  • Respect STOP. When someone replies STOP, "All upcoming and queued messages will fail, and a permanent DND is enabled at the contact level." The contact can undo it by replying START, YES or UNSTOP.

How to keep error rates low

  • Check numbers before you send. HighLevel's Number Intelligence "looks up the number before sending and applies a temporary DND on the contact if it is not SMS-capable."
  • Let failed numbers drop out. HighLevel sets Do Not Disturb (DND) by error code. It sets a temporary DND for 30003 (unreachable), 30005 (inactive user or a number that does not exist) and 30006 (landline). It sets a permanent DND for 30004 and does nothing for 30008.
  • Clean your list. HighLevel says to "remove invalid numbers, landlines, and prior opt-outs before a bulk send." CTIA: "Message Senders should process telephone deactivation files regularly (e.g., daily) and remove any deactivated telephone numbers from any opt-in lists."
  • Avoid content carriers filter. HighLevel says "heavy promotional language in cold outreach is exactly what carrier filters look for." Public link shorteners are another known risk, and HighLevel says they "can harm SMS deliverability". See URL shorteners in SMS and Twilio error 30007.

If you get a warning email

HighLevel calls a warning "your free chance to fix things". Its steps for a warning email:

  1. "Pause the workflows, campaigns, and bulk actions going to contacts without clear opt-in consent."
  2. "Check that opt-out language and sender identification are in your messages."
  3. "Review the contact list for invalid numbers, landlines, and prior opt-outs."
  4. "Talk to your client before resuming any bulk outreach."

Its messaging policy also asks agencies to "Enable and customize the Opt-Out Language and Sender ID message for your use case, so upcoming messages aren't flagged", and to confirm with the client that no bulk messages, blasts or cold-prospecting campaigns go out until they have replied to the support ticket. Keep what you send in line with your A2P registration, too. See HighLevel A2P registration. These are carrier and platform rules, not legal advice.

Sources

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