GoHighLevel WhatsApp Integration: Setting Up Business Messaging (2026)
GoHighLevel WhatsApp Integration: Setting Up Business Messaging (2026)
WhatsApp has quietly become one of the highest-engagement channels a business can use — open rates well above email, replies that feel like a real conversation, and a customer base that already lives in the app every day. For Australian businesses serving customers who prefer messaging over phone calls, connecting WhatsApp to GoHighLevel means every chat lands in the same conversations inbox as your SMS and email, and can be driven by the same Workflows and Conversation AI you already run.
In this guide I will walk through setting up WhatsApp business messaging inside GHL via LeadConnector — connecting the number, working with approved message templates, handling opt-in and compliance, and then putting WhatsApp to work in Conversation AI, Workflows and the two-way conversations inbox. The setup has a few more moving parts than plain SMS because WhatsApp is governed by Meta's rules, but once it is live it is one of the most powerful channels in the platform.
Setting up WhatsApp via LeadConnector
GHL offers WhatsApp through its LeadConnector integration, which provisions a WhatsApp Business number connected to the WhatsApp Business Platform (the Cloud API). You enable it from the sub-account under Settings, then WhatsApp, and follow the connection flow that links a Meta Business account and a verified phone number. The number you use for WhatsApp must not already be active on the consumer WhatsApp or WhatsApp Business app — it needs to be dedicated to the API.
During setup you will complete Meta Business verification and register a display name, which Meta reviews before approving. Build in a few business days for this, because the approval is out of your hands. Once approved, WhatsApp appears as a channel alongside SMS and email, and you can send and receive messages directly from the conversations inbox.
Message templates and the 24-hour window
This is the part that trips up most newcomers. WhatsApp distinguishes between two situations. Inside a 24-hour service window — the period after a customer messages you — you can send free-form replies. Outside that window, to initiate contact, you must use a pre-approved message template. Templates are submitted to Meta for review and fall into categories such as marketing, utility and authentication.
I always create a small library of approved templates up front — an appointment reminder, an order update, a re-engagement message — so the business can legitimately start conversations. Templates support variables (the customer's first name, an appointment time) that GHL populates from contact fields. Plan these early, because template approval also takes time and you do not want to be stuck unable to reach customers because nothing is approved.
Opt-in and compliance
WhatsApp messaging is bound by both Meta's business policy and Australian law. Under Meta's rules you must have a clear opt-in before messaging a customer on WhatsApp — they must have agreed to be contacted on that channel specifically, and you should record where and when that consent was given. I store the opt-in source in a custom field so there is an audit trail.
On the Australian side, the Spam Act still applies to commercial electronic messages, so the same consent, identification and unsubscribe principles you follow for SMS carry across. The detail of the local rules is worth reading in full — I cover them in my guide to GoHighLevel SMS compliance in Australia and the ACMA rules, and the same discipline applies to WhatsApp. Marketing-category templates in particular should only go to contacts who have explicitly opted in to promotional messages.
| Scenario | What you can send | Requirement |
|---|---|---|
| Customer messaged you in last 24 hours | Free-form replies, any content | Within the service window |
| You initiate after 24 hours | Approved template only | Template pre-approved by Meta |
| Marketing / promotional message | Marketing-category template | Explicit opt-in to promotions |
| Appointment reminder / order update | Utility-category template | Valid opt-in, accurate variables |
Using WhatsApp in Conversation AI and Workflows
Once WhatsApp is connected, it becomes a channel your automations can use. In Workflows you can add a "Send WhatsApp message" action, choosing a template for out-of-window sends or free-form text for in-window replies. This means an appointment reminder, a missed-call follow-up or a review request can all go out over WhatsApp instead of, or alongside, SMS — and you can branch on the customer's preferred channel.
The bigger opportunity is Conversation AI. The same bot that handles SMS and webchat can answer WhatsApp messages, qualify the enquiry and book appointments without a human touching the keyboard. Because WhatsApp conversations stay open and threaded, the AI handles back-and-forth naturally. If you are setting up an AI booking assistant, my walkthrough of the GoHighLevel Conversation AI bot for appointment booking applies directly to the WhatsApp channel.
Combining WhatsApp with other channels
WhatsApp works best as part of a multi-channel sequence rather than in isolation. A common pattern is to follow up a missed call with a WhatsApp message instead of SMS, since many customers prefer it. That builds neatly on the missed-call recovery approach I describe in my guide to GoHighLevel missed-call text-back automation — same trigger, different channel for the audiences who live in WhatsApp.
Two-way chat in the conversations inbox
Every WhatsApp message, whether sent by automation or a human, lands in the unified conversations inbox alongside SMS, email, Facebook and Instagram. Your team replies from one screen, sees the full contact history, and never has to switch to a separate WhatsApp app. Inbound WhatsApp messages can trigger Workflows, apply tags and create opportunities, exactly like any other inbound message.
This unified inbox is the practical payoff of the integration. A customer who started on WhatsApp, then emailed, then called, shows up as one threaded conversation, so whoever picks up the chat has the complete picture. For service businesses, that continuity is the difference between a customer feeling remembered and feeling like a stranger every time they reach out.
Strong use cases
The channels where WhatsApp earns its place are appointment reminders and confirmations, order and delivery updates, AI-handled enquiry qualification, missed-call follow-up, and re-engaging quiet leads with a utility-style template. For international or travel-related businesses it is often the primary channel, since customers may not have local SMS but always have WhatsApp.
Common mistakes to avoid
- Trying to use a phone number that is already active on the consumer WhatsApp app — the API needs a dedicated number.
- Sending free-form messages outside the 24-hour window instead of an approved template, which Meta will block.
- Leaving template creation until the last minute and getting stuck waiting on Meta approval.
- Messaging contacts without a recorded WhatsApp opt-in, breaching both Meta policy and the Spam Act.
- Sending marketing-category templates to people who only consented to service messages.
- Treating WhatsApp as a one-off blast tool rather than a two-way conversational channel.
- Forgetting to honour unsubscribe requests, which carry across from your SMS and email compliance.
If you want WhatsApp business messaging set up properly in GoHighLevel — connected, compliant and wired into your AI and Workflows — book a strategy call with the HL Growth Partner team.
Frequently asked questions
How do I connect WhatsApp to GoHighLevel?
You connect it through the LeadConnector WhatsApp integration in the sub-account settings, which links a Meta Business account and a dedicated phone number to the WhatsApp Business Platform. You will complete Meta business verification and register a display name, both of which Meta reviews before the channel goes live.
What is the 24-hour window in WhatsApp?
It is the service window that opens when a customer messages you. Within 24 hours you can send free-form replies of any content. Outside that window, to initiate contact, you must use a message template that Meta has pre-approved.
Do I need opt-in to message customers on WhatsApp?
Yes. Meta's policy requires a clear opt-in before you message a customer on WhatsApp, and Australia's Spam Act applies the same consent, identification and unsubscribe rules you follow for SMS. Record where and when consent was given, and only send marketing templates to contacts who opted in to promotions.
Can Conversation AI answer WhatsApp messages?
Yes. Once WhatsApp is connected as a channel, the same Conversation AI bot that handles SMS and webchat can answer WhatsApp messages, qualify enquiries and book appointments. Because WhatsApp threads stay open, the AI handles back-and-forth conversation naturally.
Does WhatsApp appear in the same inbox as SMS and email?
Yes. Every WhatsApp message lands in the unified conversations inbox alongside SMS, email and social channels. Your team replies from one screen with full contact history, and inbound WhatsApp messages can trigger Workflows, apply tags and create opportunities like any other channel.
