Step-by-Step Guide
How to Send GoHighLevel Leads to WhatsApp
A new lead fills out a form in GoHighLevel, and then... nothing. No WhatsApp message, no instant touch, just a contact record sitting in a pipeline until someone remembers to follow up. Here's exactly how to close that gap — the real setup, not the marketing-page version of it.
On This Page
Why This Isn't as Simple as Flipping a Switch
GoHighLevel doesn't send WhatsApp messages through some unofficial backdoor — it connects to the WhatsApp Business Platform, which is Meta's official API for businesses (what most people just call the WhatsApp Cloud API). That's a good thing for deliverability and account safety, but it means the setup has real prerequisites: a verified Meta Business account, a dedicated phone number, and — this is the part almost every guide glosses over — approved message templates before you can message a lead who hasn't messaged you first. Get the order of operations wrong and you'll build a perfectly good workflow that silently fails to send a single message.
I've set this up for real estate teams, clinics, and service businesses across Dubai where a same-second WhatsApp reply is the difference between winning a lead and losing it to whichever competitor answers first. The steps below are the actual sequence I follow, in the order that avoids the most common stall points.
How It Actually Works
Six steps, in the order that actually gets a lead from a form submission to a WhatsApp message in their pocket.
Verify your Meta Business account
Before GoHighLevel can send a single WhatsApp message on your behalf, Meta needs to know who you are. That means a Meta Business Manager account with business verification completed — legal business name, address, and a way to confirm you actually run the business you say you do. Skip this step and every later step stalls, because GHL's WhatsApp setup routes through a 'Continue with Facebook' login tied to that verified business.
Get (or migrate) a WhatsApp Business Account number
You need a phone number dedicated to the WABA connection. It can be a brand-new number, or you can migrate an existing WhatsApp Business App number into the Cloud API — but a number already active in the regular WhatsApp Business App can't run both at once in most setups, so decide upfront whether this is a fresh number or a migration.
Connect the number inside GoHighLevel
Inside a GHL sub-account, go to Settings → Phone Numbers (or Conversations settings) and start the WhatsApp connection flow. You'll log in with the Facebook account tied to your verified Meta Business, pick or confirm the WABA, and verify the number with an OTP sent by SMS or voice call. Once connected, WhatsApp shows up as a channel right alongside SMS and email in the Conversations inbox.
Get your first message templates approved
Any message you want to send to a lead who hasn't messaged you first has to be a pre-approved Meta template — a lead capture form submission does not count as the lead messaging you. Write a simple utility template ('Hi {{1}}, thanks for your interest — when's a good time to talk?'), submit it for review inside GHL, and wait. Approval is usually quick but isn't instant, so this is the step that trips people up if they build the workflow first and only think about templates on launch day.
Build the workflow trigger
In GHL's Workflows, add a trigger such as 'Contact Created' or 'Form Submitted' scoped to the lead source you care about, then add a 'Send WhatsApp' action as the next step. Point that action at your approved template for the first outbound message. If you want a fully automated conversation instead of a one-off nudge, chain a wait step and a second WhatsApp action after it, or branch based on whether the lead replies.
Test with a real lead before you trust it
Submit a test form yourself, watch the workflow fire in GHL's execution log, and confirm the WhatsApp message actually lands on a phone — not just that the workflow says 'completed.' Template rejections, a wrong merge field, or a number that didn't finish verification all look fine in the workflow builder and only show up when you watch a real message try to send.
Common Mistakes & Gotchas
The five things that actually break this setup, based on what I run into when clients try it themselves before calling me.
The 24-hour window resets what you can send
Once a lead replies to you, a 24-hour customer service window opens and you can send free-form messages — no template needed. But the moment that window closes, you're back to templates only. A lot of 'why did my automation stop working' problems are actually just this window closing mid-sequence.
A form submission is not the same as a WhatsApp message
This is the single most common mistake I see. A lead filling out a GHL form has never messaged your WhatsApp number, so that first outbound message always needs a template — even if your workflow is otherwise fully automated.
Template rejections happen, and they cost you time
Templates that read as promotional, use unclear variables, or don't match their declared category (utility vs. marketing vs. authentication) get rejected. Build in a few days of buffer before you need this live, especially for a first-time WABA setup.
One number, one platform, mostly
A number running through the classic WhatsApp Business App generally can't also run through the Cloud API connection GHL uses, outside of specific coexistence setups Meta has been rolling out — so decide early whether you're keeping your existing number's app-based setup or moving it over.
This add-on has its own cost, on top of your GHL plan
The WhatsApp integration is a paid add-on per sub-account, and Meta charges separately for template-based conversations. Neither of those costs is bundled into your base GoHighLevel plan price, so budget for both before you commit to volume.
Frequently Asked Questions
Yes. GoHighLevel's WhatsApp connection runs through Meta's WhatsApp Business Platform, which requires a verified Meta Business Manager account before you can register a number. There's no way around this step — it's Meta's requirement, not GHL's.
Rather Not Wrestle With Meta's Approval Queue Yourself?
This guide gets you the real steps, but the WABA setup, template writing, and workflow logic still take real time to get right — and a rejected template or a mis-scoped trigger can quietly cost you leads while you debug it. I build this exact setup for Dubai businesses end-to-end, tested against real scenarios before it goes live.
Have a Question About Your Own Setup?
Fastest way to get an answer: message me directly on WhatsApp. Or send the details below and I'll get back to you.