One of the most frustrating reports I get is this: "I set everything up in GoHighLevel, but my messages aren't going through." The lead enters the CRM, the workflow fires, and everything looks fine on screen — but the client never got anything. It's not a platform bug. It's almost always one of five specific causes, and each one is checked and fixed differently depending on whether the channel is SMS or WhatsApp.
First, understand SMS and WhatsApp are two different systems
Even though both live inside GoHighLevel, SMS runs through US phone carriers (with their own compliance rules) and WhatsApp runs through Meta's official API (with its own template rules and time windows). Diagnosing "why aren't my messages going out" starts with identifying which of the two channels is failing — because the cause and the fix are completely different.
Why your SMS isn't going out
Unapproved A2P 10DLC
By far the number one reason SMS doesn't reach US numbers. Carriers (AT&T, Verizon, T-Mobile) require any business sending automated messages to register its brand and campaign under the A2P 10DLC system. If that registration isn't complete or approved, carriers filter your messages — sometimes blocking them entirely, sometimes delivering them late or only to part of your contacts, with no visible error on the GoHighLevel side.
A phone number with a poor reputation
If a number has been reported as spam multiple times (say, from sending messages too frequently or without clear opt-in), carriers can lower its quality rating, which reduces how much of your traffic they deliver. This shows up under Phone Numbers inside Settings.
Why your WhatsApp messages aren't going out
The number never finished verification
Connecting WhatsApp Business API to GoHighLevel isn't instant — it goes through a verification process with Meta that includes confirming the number, verifying the business (Business Manager), and sometimes waiting on brand approval. If that process was left half-done, the number can look "connected" in the interface without actually being enabled to send.
Empty messaging credits
WhatsApp in GoHighLevel runs on a credit wallet that's consumed per conversation. If the balance hits zero, outbound messages stop with no dramatic alert — they just stop going out. It's worth checking your balance under Billing regularly, especially if your message volume has grown.
A rejected or pending template
Any message your business initiates (not a reply to something the client wrote) has to use a template Meta has pre-approved. If the template was rejected — for overly promotional language, badly formatted variables, or not matching its declared category — that specific message won't go out, even though the rest of your WhatsApp works fine.
Outside the 24-hour window
This is a WhatsApp rule, not a GoHighLevel one: if more than 24 hours have passed since the client's last message to you, you can't send a free-form message — it has to be an approved template. Plenty of businesses read this as "GoHighLevel stopped working" when it's really just Meta's policy applying normally.
How to confirm which cause applies to you
- Identify the channel — is it SMS, WhatsApp, or both?
- For SMS: check your A2P 10DLC status under Settings → Phone Numbers → Compliance. If it says "pending" or "rejected," that's your answer.
- For WhatsApp: check your number's status under Settings → WhatsApp. If it doesn't show "Connected" with a green check, verification never finished.
- Check your messaging balance under Billing — a zero balance stops everything with no on-screen warning.
- Check your WhatsApp template statuses — anything marked "Rejected" or "Pending" can't be used yet.
- Confirm whether the specific contact is outside the 24-hour window before assuming it's a technical issue.
How each cause gets fixed
- A2P 10DLC pending: complete the brand and campaign registration with your business's correct legal information (EIN, address, business type). If it was rejected, it's almost always inconsistent data between what you entered and what shows up in public records.
- WhatsApp unverified: finish the business verification process in Meta Business Manager before configuring anything else.
- Empty credits: top up the wallet and, if your volume is steady, turn on auto-recharge so it doesn't happen again.
- Rejected template: read the rejection reason (Meta almost always states it), rewrite the copy removing aggressive promotional language, and resubmit it for approval.
- Outside the 24-hour window: use an approved template to reopen the conversation, or wait for the client to message first.
A typical case
In accounts I review regularly, I see this pattern: a business connects its WhatsApp number, everything looks fine the first few weeks, and then automated messages suddenly stop going out mid-campaign. It almost always turns out to be an empty credit wallet — because message volume grew (more leads, more active automations) and nobody adjusted the top-up to the new volume. The fix takes five minutes once identified, but finding it without knowing where to look can take days of frustration.
Avoid it happening again
Connecting WhatsApp correctly from the start — with A2P registration done early, business verification fully completed, and templates approved before you urgently need them — is exactly what gets covered when connecting WhatsApp Business inside a properly configured CRM. Getting it right once saves months of messages quietly disappearing without anyone noticing why.
Are your messages not going out?
If you've checked all this and still can't find the cause, or you'd rather have someone experienced look directly at your account, book 15 minutes and we'll figure out together where your WhatsApp or SMS is getting stuck. For a full account review with a written diagnosis, the $99, 2-hour consultation covers this too.