Why are my SMS messages failing in GoHighLevel? Error codes explained

By / Published Nov 12, 2026 / Updated Nov 12, 2026

Heads up: the trial and plan buttons on this page use my affiliate links. If you sign up through one I get a commission. It doesn't cost you more.

When a GoHighLevel text fails, the error code tells you why: 30034 means the number isn't linked to an approved A2P campaign, 30007 means the carrier filtered it, 21610 means the contact opted out, and 30003 to 30006 mean the number can't take texts. Open the contact in Conversations, hover the red warning next to the message marked Unsuccessful, read the code, then match it to the table below.

I run my agency on HighLevel, and failed texts are the bug clients notice last and care about most. Below is every code from HighLevel's own help docs (read Nov 12, 2026) with the cause and the fix, then how to get alerted when texts fail, carrier filtering, opt-outs, international sending, segments, and the new SMS safeguards HighLevel announced on Nov 10, 2026. Registration itself is covered in A2P 10DLC registration.

Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Short version

  • 01Find the code: Conversations > open the contact > hover the red warning on the Unsuccessful message > Learn More.
  • 0230034 is A2P: link the number to the approved campaign and give carriers up to 24 hours. 30032 is an unverified toll-free number.
  • 0330007 is filtering: fix consent, STOP language, links and wording before you send again. Repeat 30007s can push the contact to DND.
  • 0421610 means they replied STOP. Only the contact can undo it by texting START or YES.
  • 0530003, 30004, 30005 and 30006 turn on SMS DND for that contact by themselves.
  • 06Failed texts don't retry on their own. Build a Messaging Error - SMS workflow so someone hears about it.
  • 07Since Nov 10, 2026, some sub-accounts get warnings at 4% opt-outs or 15% filtering and 12 hour pauses instead of 24 to 48.

Find the error in 60 seconds

  1. 01

    Open the failed message

    Go to Conversations, search the contact and open the thread. The failed text is marked Unsuccessful with a red warning next to it.

  2. 02

    Read the code

    Hover over or click the red warning. You get the error description and a Learn More link to HighLevel's help article for that problem. Write the number down (30034, 30007, 21610 and so on).

  3. 03

    Check the scope

    One contact failing is a recipient problem. Every text from one number or the whole sub-account failing is a registration, sender or account problem. Look at a few other recent sends before you change any settings.

  4. 04

    Check the other places it shows

    The contact's activity timeline also lists failed SMS with the error. If a workflow sent it, open that workflow's Execution Logs. On your own Twilio account (BYOT), the Twilio message logs have extra detail.

  5. 05

    Fix the cause, then test once

    Match the code to the table below and fix that first. HighLevel says not to resend over and over: repeat sends to opted-out, invalid, filtered or unregistered numbers make your messaging health worse.

GoHighLevel SMS error codes: meaning and fix

Every code below comes from HighLevel's Understanding Common SMS Delivery Errors article and the LC Phone Error Code and Warning Dictionary. Most are the same codes Twilio uses, so they read the same on LC Phone or your own Twilio.

CodeWhat it meansWhat to do
21211Invalid "To" numberFix the number and use E.164 format (+ country code + number). Also fails if you text a short code, an alphanumeric sender, or the same number you're sending from.
21408Texting that country isn't enabledLC Phone: contact HighLevel support. Your own Twilio: turn the country on in Twilio's Geo Permissions.
21606"From" number can't send to this destination or accountUse an SMS-capable number owned by this sub-account. Check porting or hosting has finished.
21610Contact replied STOP or has SMS DND onStop texting them. Only the contact can opt back in by texting START or YES.
21612This To and From combination can't be usedCheck E.164 format and use a sender that's allowed in the destination country (a US number can't text the UK).
21614"To" number isn't a valid mobileUsually a landline or a typo. Get a mobile number for the contact.
21635"To" number is a landlineUse another number for the contact. Contact support only if you know it's a mobile.
21661"From" number isn't SMS-capableCheck Settings > Phone Numbers, then pick or buy a number with SMS.
30002Account suspended before the text went outContact HighLevel support (balance or policy).
30003Number unreachable or out of servicePhone off or no signal. Retry later. Repeated 30003s on long codes can be carrier filtering. Turns on SMS DND.
30004Message blocked by the destinationCheck DND and opt-out status. A toll-free number texting someone who sent STOP gets this too. Turns on SMS DND.
30005Number inactive or doesn't existCorrect or remove the number. Turns on SMS DND.
30006Landline or unreachable carrierUse a mobile number or another channel. Turns on SMS DND.
30007Filtered by LeadConnector or the carrierFix consent, STOP language, links and wording before resending. Full section below.
30008Unknown error from the carrierSend a shorter, plain message with no special characters. Still failing: 3+ examples under 48 hours old to support.
30011MMS not supported by that phone or regionSend text only.
30023Daily cap for your A2P brand reachedPause sending. The cap is per brand (EIN) and counts segments to T-Mobile. Contact support if it's unexpected.
30024Numeric sender ID not provisionedFor countries that need sender registration. Send support 3+ message IDs if it should already be done.
30032Toll-free number not verifiedFinish toll-free verification and wait for Verified. Pending toll-free numbers have been blocked since Jan 31, 2024.
30033A2P 10DLC campaign suspendedContact support for the reason and recovery steps.
30034Number not fully registered for A2PLink the number to the approved campaign, then allow up to 24 hours. Sole Proprietor allows one local number.
30035Number still being configured for A2PRegistration is still processing. Wait about 24 hours.
30037Outbound messaging disabled on the accountContact support.
11751MMS attachment too bigCompress it or send a link. HighLevel suggests about 500 KB for broad carrier support.
11200HighLevel couldn't fetch the media or linkCheck the branded API domain under Business Profile.
Not SMS-capable"From number is not SMS-capable" (rejected before sending)Number is voice only, belongs to another location, isn't linked to A2P, or was typed without E.164. See below.

From HighLevel's SMS error articles (modified Sep 8 and Oct 28, 2026), read Nov 12, 2026.

Texts failing before A2P is done (30034, 30032, 30035)

This is the one that catches new agencies. A brand new sub-account can look fully set up, the workflow runs, and every text to a US number fails with 30034 because the number isn't linked to an approved A2P campaign. Nobody sees it unless they open Conversations.

Approval doesn't link the number for you. The linking steps, the green A2P Verified label and the Sole Proprietor one-number limit are in A2P rejected? Fixes, along with what to do if the campaign itself got rejected. After linking, carriers can take up to 24 hours, and during that window you may see 30035 (number still being configured). Don't keep testing through it. Toll-free numbers have their own process, and an unverified one fails with 30032.

If all local-number texts in a sub-account stop at once, HighLevel's checklist is A2P campaign status, number association, account restrictions, and codes 30033, 30034 or 30037. If only toll-free texts fail, it's verification and 30032.

Get alerted when texts fail: the Messaging Error - SMS trigger

HighLevel doesn't retry a failed text, and it doesn't email you either. So build the alert yourself. This is super underrated, and it's the one workflow I'd put in every client account.

Go to Automation > Workflows, create a workflow, and add the trigger Messaging Error - SMS. Add an Error Code filter. The trigger can filter on 20 codes: 30002, 30003, 30004, 30005, 30006, 30007, 30008, 30011, 30023, 30032, 30033, 30034, 30037, 21211, 21408, 21606, 21610, 21614, 21635 and 21661. Then add If/Else branches so each group of codes gets the right action, and publish.

How I'd split it. Account problems (30034, 30032, 30033, 30037, 30002, 30023): send an Internal Notification to whoever owns the account, because every text in the sub-account is about to fail. Bad numbers (21211, 21614, 21635, 30005, 30006): add a tag like bad-mobile and move the follow-up to email or a call task. Filtering (30007): notify and tag, so you can spot a template that's getting blocked. Opt-outs (21610): do nothing, the contact is already blocked and that's correct.

Don't make the workflow resend the text. HighLevel says an error workflow "should not blindly resend every failed SMS". Build the recovery around the specific code. If the trigger never seems to fire, the debugging checklist is in Workflow not triggering.

Error 30007: carrier filtering and how to fix your content

30007 means LeadConnector's own filter or the carrier blocked the message because it looked like spam, broke a messaging policy, or was missing consent or sender details. It can hit an approved A2P campaign, and HighLevel says a 30007 can mark the contact DND. Carriers filter differently, so the same text can reach someone on AT&T and get blocked on Verizon.

HighLevel's rules to stay out of it: only text people who opted in, name the business, and include STOP language at least once every 30 days to the same contact. Creative versions like "Reply 2 to unsubscribe" get filtered. Reconfirm opt-in every 18 months so you don't text recycled numbers. Don't use public link shorteners like bit.ly (AT&T blocks them outright and T-Mobile bans URL cycling), keep to one redirect, and only use links on the domain you put in your A2P registration. Skip emojis, excessive punctuation, ALL CAPS and bad spelling. And don't spread the same campaign across extra numbers to dodge filters (snowshoeing).

Spacing helps for the same reason. Reviewing an AI-built reactivation workflow, I said "what this missed, is the wait step... right now they're going back-to-back" and that I'd "wait probably 24 hours or a day and then send the second SMS." Two texts in a row to an old lead is how opt-outs and filtering start.

Think it's a mistake? HighLevel wants at least 3 contacts from the past 7 days that show 30007. In Conversations, search the contact, click the contact image and copy the browser URL for each one, then send those links to support. There's no tool to test whether a message will be filtered.

Error 21610, opt-outs and DND

21610 means the contact opted out or has SMS DND on. The opt-out keywords are STOP, STOPALL, UNSUBSCRIBE, CANCEL, END and QUIT. To opt back in, the contact texts START or YES to your number. You can't re-subscribe them yourself, and you're not charged for the blocked attempt.

DND also turns on without anyone pressing a button. HighLevel switches on SMS DND when a contact replies STOP or UNSUBSCRIBE, and when the carrier returns 30003, 30004, 30005 or 30006. Open the contact and check the DND section at the bottom of the left column, and Conversations shows whether a workflow, a user or the contact turned it on.

Temporary DND can be switched off in the contact record. Permanent SMS DND needs the contact to text START, or proof of opt-in sent to HighLevel support. A number that never opted out can still be blocked if the carrier reassigned it to someone new, which is exactly why HighLevel says to reconfirm opt-in every 18 months.

If a contact entered a workflow and got tags but never got the text, DND is the usual reason. The workflow ran, the SMS step just couldn't send.

"From number is not SMS-capable" (and 21661, 21606)

This one fails before the text ever reaches a carrier. HighLevel or the phone provider rejected the sender. Successful calls don't prove a number can text: some numbers are voice only.

Check in this order. On LC Phone, open Settings > Phone Numbers, open the number and confirm Messaging is on. On your own Twilio, check the number's Capabilities include SMS in the Twilio console. Make sure the number belongs to this sub-account and not another location or a disconnected Twilio account. For US local numbers, confirm it's linked to the approved A2P campaign. And if the number is typed into a workflow, API call or integration, write it in E.164 (+15551234567).

New or ported numbers can take 24 to 48 hours before they can text. If you just moved a number, re-select it everywhere it's stored: Conversations sender settings, workflow and campaign senders, default settings, user-assigned numbers and any integration. Which phone system you're on changes where you check, and the trade-offs are in Phone system.

International texts: 21408, 21612 and country rules

21408 means your account isn't allowed to text that country. On LC Phone, HighLevel's dictionary says to contact support to enable the region. On your own Twilio, Twilio's doc says new accounts can only text their home country until you turn on more under Messaging > Settings > Geo Permissions in the Twilio console. Some places can't be enabled at all: LC Phone stopped delivering to Iran on March 15, 2025.

21612 means the sender can't reach that destination. HighLevel's own example: a US number texting a UK mobile fails with 21612. UK texting needs a UK long code connected to an approved Regulatory Compliance bundle (required for all UK long codes since Sep 30, 2024), an alphanumeric sender ID for one-way messages, or a short code. Alphanumeric senders don't work in the US or Canada, and nobody can reply to them.

Turkey is the other one to know. Since April 1, 2026, international business texts to Turkish numbers can't contain any link at all, including custom values that turn into a URL, and blocked ones can come back as 30007. If you have clients texting abroad, check each country's sender rules before you build the automation.

Segments, emojis and long messages (30008, 30011)

A text is billed in segments. With normal characters (GSM-7) one segment is 160 characters, and 161 characters makes it two. One emoji switches the whole message to Unicode, which drops each segment to 70 characters. HighLevel charges once a delivery attempt is made, even if the text then fails, and doesn't refund undelivered texts. So a bad list costs money as well as reputation.

Encoding shows up in errors too. HighLevel's fix for 30008 is to try a shorter, plain message with no special characters, because the failure can come from splitting a long message or from character encoding. Text pasted from Word or a website can carry curly quotes and hidden characters that do the same thing.

MMS is its own thing. 30011 means the phone or region doesn't support MMS, so send text only. 11751 means the file is too big: HighLevel's general limit is 5 MB, but it recommends about 500 KB to work on most carriers, or just send a link.

When the whole sub-account stops texting: restrictions and the Nov 10 change

HighLevel watches each sub-account's opt-out rate and delivery error rate, and pauses SMS when they get too high. You can see every warning and pause under Settings > Phone System > Messaging > Restriction History (far-right tab), with the date, type, reason and the rate at the time. Times are in UTC.

Under the existing rules (Restriction History doc, Aug 10, 2026), a sub-account gets locked out of texting for 24 hours when its opt-out rate hits 3% or its delivery error rate hits 10%. HighLevel calls 0 to 1% a good opt-out rate and 0 to 6% a good error rate.

On Nov 10, 2026 HighLevel announced fairer safeguards, rolling out to a selected group of sub-accounts first. Under the new rules you get a warning above a 4% opt-out rate or a 15% carrier filtering rate, and a temporary pause above 6% opt-outs or 25% filtering. Only 30007 counts toward the filtering rate, and it's judged on the last 7 days of sending, so one bad blast doesn't decide it. Standard pauses are 12 hours, down from 24 to 48, agency owners can review and resume messaging themselves when eligible, and the notifications now say how long a pause lasts. HighLevel says early testing showed 80% fewer restrictions. New sub-accounts keep the existing safeguards, and very high rates can still mean more pauses or a manual review.

Either way, 1:1 texts from Conversations keep working during a temporary bulk restriction. And if you got a violation email, HighLevel's advice is to stop every workflow, campaign and bulk action going to people who didn't opt in, and turn on opt-out language and sender ID.

Separate from restrictions, a sub-account can hit its Messaging Limit or be in Messaging Ramp. When that happens a workflow's Send SMS step fails and isn't retried later, so check the workflow's Execution Logs for who missed out.

How I'd keep client texts delivering

Turn on Number Intelligence (Settings > Phone System > Additional Settings). It checks a number before the first text goes out and puts a temporary DND on contacts that can't receive SMS, which keeps landlines from wrecking your error rate. Agency admins can switch it on for every new sub-account under Agency Settings > Phone Integration > Account Creation. Check the lookup cost in HighLevel's phone pricing guide first.

Put the business name and "reply STOP to unsubscribe" in the first text to every new contact. Use the client's own domain for links. Build the Messaging Error - SMS alert on day one. And look at Restriction History once a month.

Old lists are where this goes wrong. As I said about reactivation, "a lot of these dental clinics, they have a lot of leads, but they're not constantly emailing or SMSing these leads." Only text the ones who actually opted in, and never buy an "unlimited SMS" gateway or blast a cold list to get around this. The money is made in the follow-ups, but only if they arrive. This isn't legal advice: for TCPA and consent rules, check with someone qualified.

Start the 30-day trial and set up texting the right way →
Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Other ways to start

My bonuses come with every one of these.

Best if you're new and want live help setting up

30-day trial + a free live setup bootcamp

Best if you're not sure which plan you need

Compare all 3 plans first

Best if you'll resell HighLevel as your own software

Go straight to the $497 Founder plan

FAQ

Why are my GoHighLevel texts not delivering?

Open the contact in Conversations and hover the red warning on the Unsuccessful message to see the code. The most common are 30034 (number not linked to an approved A2P campaign), 30007 (carrier filtering), 21610 (opted out) and 30003 to 30006 (number can't receive texts).

What is error 30007 in GoHighLevel?

The message was filtered by LeadConnector or the carrier as spam or non-compliant. Fix consent, add sender name and STOP language, remove public link shorteners and spammy wording, then send support 3+ examples from the last 7 days if compliant texts still fail.

How do I fix error 21610?

You can't from your side. The contact replied STOP (or similar) or has SMS DND on, and only they can opt back in by texting START or YES to your number.

Why do I get 30034 when my A2P campaign is approved?

The number usually isn't linked to the campaign yet, carriers are still activating it (allow up to 24 hours), or a Sole Proprietor brand has more than one local number.

How do I fix error 21408?

Your account isn't allowed to text that country. On LC Phone, ask HighLevel support to enable it. On your own Twilio, enable the country in Twilio's Messaging Geo Permissions.

Does GoHighLevel resend failed texts automatically?

No. Fix the cause, then resend only to contacts who can still receive texts. Use the Messaging Error - SMS workflow trigger to get notified when a text fails.

Why did HighLevel pause SMS on my sub-account?

Its opt-out or delivery error rate went over the limit. Check Settings > Phone System > Messaging > Restriction History. Under the new safeguards (Nov 10, 2026, phased rollout) pauses last 12 hours, and 1:1 texts from Conversations keep working.

Sources / last checked Nov 12, 2026

  • HighLevel help docs: SMS errors. Troubleshooting SMS Delivery Issues (modified Oct 28, 2026), Understanding Common SMS Delivery Errors (Oct 28, 2026), LC Phone System Error Code and Warning Dictionary (Sep 8, 2026), Error 21610 Recipient Unsubscribed (Sep 8, 2026) and Error: The "From" Number Is Not SMS-Capable (Sep 3, 2026), read Nov 12, 2026.
  • HighLevel help docs: filtering and restrictions. How to Prevent SMS Filtering by Carriers: Error 30007 (Jul 23, 2026), Shortened URLs and SMS Deliverability (Jul 23, 2026), Best Practices for SMS Deliverability (Sep 4, 2026), Track SMS Restriction History (Aug 10, 2026) and How to Increase Messaging Limits (Sep 11, 2026), read Nov 12, 2026.
  • HighLevel help docs: workflows, DND and costs. Workflow Trigger - Messaging Error Code - SMS (May 27, 2025), Workflow Trigger - Number Validation (Sep 18, 2026), How to Use Do Not Disturb (Sep 28, 2026) and How to Calculate SMS and MMS Costs (Jul 23, 2026), read Nov 12, 2026.
  • HighLevel help docs: international. International SMS Compliance: UK & Turkey Regulations (Sep 4, 2026), read Nov 12, 2026.
  • Twilio docs. Error 21408: Message blocked, permissions disabled for the destination region, twilio.com/docs/api/errors/21408, read Nov 12, 2026.
  • HighLevel changelog. Fewer SMS Restrictions, More Confidence in Messaging (Nov 10, 2026), ideas.gohighlevel.com/changelog, read Nov 12, 2026.
  • My videos. My review of an AI-built reactivation workflow (Jul 2026) for the wait step and old-leads lines, quoted only and not embedded, and my Feb 2026 video for the follow-ups line. I don't have a video on SMS errors, so there's no video on this page.
Hamza Baig (Hamza Automates)

Author

Hamza Baig / Hamza Automates

Founder, Hexona Systems

I run Hexona Systems on GoHighLevel. HighLevel gave it the SaaSpreneur Platinum award in 2024 and Diamond in 2025 and 2026, and I spoke at their LevelUp event in 2026. Hexona powers 1,000+ agencies, we've served 1,500+ businesses, and I've taught 45,000+ students. Everything on this hub is something I use myself or have shown on camera.

Platinum SaaSpreneur
2024
Diamond SaaSpreneur
2025, 2026
LevelUp speaker
2026
YouTube subscribers, Oct 2026
34,200

Keep reading

Start your 30-day free trial →

30 days free + 1:1 setup call + my bonus / affiliate link