WhatsApp is one of the most powerful communication channels inside
GoHighLevel,
especially for appointment reminders, follow-ups, confirmations, and automated workflows.
But sometimes students, leads, or customers don’t receive your WhatsApp messages—even though GHL shows “Not Delivered” or the message appears stuck in a workflow.
This guide explains exactly why WhatsApp messages fail in GoHighLevel and how to diagnose and fix each issue using message logs, workflows, and provider settings.
But sometimes students, leads, or customers don’t receive your WhatsApp messages—even though GHL shows “Not Delivered” or the message appears stuck in a workflow.
This guide explains exactly why WhatsApp messages fail in GoHighLevel and how to diagnose and fix each issue using message logs, workflows, and provider settings.
1. The Contact Is Outside WhatsApp’s 24-Hour Window
WhatsApp only allows freeform messages inside a **24-hour conversation window**.
If the contact has not replied in 24 hours, GoHighLevel can only send a **pre-approved WhatsApp template**.
If you try to send a normal message inside a workflow (e.g., “Hello, just checking in”), GHL will mark it as: Failed — Outside Session Window.
Fix:
If the contact has not replied in 24 hours, GoHighLevel can only send a **pre-approved WhatsApp template**.
If you try to send a normal message inside a workflow (e.g., “Hello, just checking in”), GHL will mark it as: Failed — Outside Session Window.
Fix:
- Use a WhatsApp template message instead of “Custom Message”
- Check the 24h cutoff in the Message Log
- Trigger a new conversation only with a template
2. The Message Template Was Not Approved by Meta
For WhatsApp Business API inside GHL (Twilio, 360Dialog, Cloud API), templates must be
approved inside Facebook Business Manager.
A message fails when:
“Template not approved / template does not exist”.
Fix:
A message fails when:
- The template is still pending review
- The template was rejected
- Variable placeholders were inserted incorrectly (e.g. {{name}} mismatch)
- The flow attempted to use an old or deleted template
“Template not approved / template does not exist”.
Fix:
- Verify the template in Meta → WhatsApp Manager → Message Templates
- Check if the template name matches exactly (case-sensitive)
- Ensure all placeholders {{1}}, {{2}}, {{name}} are provided correctly in GHL
3. The Recipient Is Not a Registered WhatsApp User
GHL cannot deliver WhatsApp messages to numbers that:
Fix:
- Don't have WhatsApp installed
- Deleted the account
- Use a landline
- Recently changed their number
Fix:
- Confirm the number is an active WhatsApp user
- Ensure E.164 format (+1 XXX XXX XXXX)
- Clean your contact lists before sending workflows
4. The Contact Blocked Your WhatsApp Business Number
When a lead blocks your WhatsApp Business number:
Fix:
- The message will show “Sent” but never “Delivered”
- GHL logs will show repeated delivery attempts
- Your workflow will continue but WhatsApp will permanently reject the message
Fix:
- Switch to SMS or Email fallback
- Use GHL workflows to detect failed WhatsApp attempts and retry via another channel
5. Invalid Number Formatting Inside GHL
WhatsApp requires phones in **E.164 format**:
+15551234567
GHL messages fail if numbers contain:
Fix:
+15551234567
GHL messages fail if numbers contain:
- Parentheses
- Dashes
- Spaces
- Country code missing
Fix:
- Use GHL’s phone number validation field
- Clean numbers via workflow → “Format Number” action
- Always store numbers with +CountryCode
6. WhatsApp Provider Issues: Twilio, 360Dialog, or Cloud API
GHL relies on external WhatsApp providers:
Common symptoms in GHL:
- Twilio WhatsApp API
- 360Dialog
- WhatsApp Cloud API (Meta)
Common symptoms in GHL:
- Workflow messages stuck at “Queued”
- Multiple reattempts fail instantly
- Error codes appear in Message Logs
- Check provider status pages
- Verify API credentials in GHL → Settings → Phone Numbers
- Rebuild your WhatsApp connection if credentials expired
7. WhatsApp Quality Score or Rate Limit Restrictions
WhatsApp monitors message quality across your business number.
If too many users:
GHL will show: Message failed — rate limit exceeded.
Fix:
If too many users:
- Block your number
- Mark messages as spam
- Do not respond
GHL will show: Message failed — rate limit exceeded.
Fix:
- Send fewer cold messages
- Warm up your WhatsApp number gradually
- Send more conversational, less sales-heavy templates
8. Workflow Misconfiguration Inside GoHighLevel
Many “Not Delivered” errors are not WhatsApp-related—they happen because the workflow logic is incorrect.
Common workflow issues:
Fix:
Common workflow issues:
- Contact missing required custom fields for templates
- Branch conditions skipping WhatsApp steps
- Message step placed before contact is created/updated
- Conflicting triggers sending multiple messages
Fix:
- Test workflow steps using a test contact
- Pause and streamline duplicate triggers
- Move WhatsApp steps after tagging, updating fields, or form submissions
How to Diagnose WhatsApp Failures Inside GoHighLevel
GHL provides several tools for debugging:
- Conversations → Message Log — shows exact failure reasons
- Workflows → Execution Log — shows which step failed
- Phone → Provider Logs — Twilio / 360Dialog errors
- Audit Logs — checks if automation was triggered correctly
Need Help Fixing WhatsApp in Your GoHighLevel Account?
If your WhatsApp messages inside GHL are consistently failing, our team can help diagnose and fix:
- Workflow automation errors
- WhatsApp template issues
- Twilio / 360Dialog configuration
- Message log delivery failures
- Quality rating and rate-limit problems
- Incorrect phone formatting
Want this set up in your account?
Book a CallOur GoHighLevel experts can build it for you — fast.
