GoHighLevel WhatsApp Integration: Setup & Pricing (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 16 July 2026 · 10 min read

On this page: What the integration is · Prerequisites · Step-by-step setup · Pricing breakdown · Templates vs session messages · Automation use cases · WhatsApp vs SMS in Australia · Common mistakes · FAQ

GoHighLevel WhatsApp integration is the feature clients ask me about most weeks, and for good reason. WhatsApp sits on the majority of Australian smartphones, open rates routinely beat email, and there is no 160-character straitjacket. Yet most businesses I audit have either ignored it or bolted on a third-party tool that does not talk to their pipelines, tags or calendars.

The good news: HighLevel ships a native WhatsApp channel, so no Zapier duct tape is required. This guide covers how the integration works, the prerequisites, the real costs, and the automations I set up for Australian clients — from booking reminders to Conversation AI answering enquiries at 9pm on a Sunday. Everything reflects the platform as of July 2026; on pricing, verify against the official pages linked below.

What the GoHighLevel WhatsApp integration is and how it works

GoHighLevel connects to WhatsApp through the WhatsApp Business API (the WhatsApp Cloud API), provisioned via LeadConnector — HighLevel's own communications layer. This is the official, Meta-sanctioned route: a proper API connection registered against your Meta Business Manager account, not the consumer app on a staff member's phone or WhatsApp Web in a browser tab.

Once connected, WhatsApp appears as a channel inside the Conversations tab of the sub-account, alongside SMS, email, Facebook Messenger and Instagram DMs. Every inbound message attaches to the contact record, so your team sees tags, custom fields, pipeline stage and appointment history in one place. Outbound, WhatsApp becomes an action inside Workflows — any trigger that fires a Workflow (form submission, missed call, appointment booked, pipeline stage change, tag added) can now send a WhatsApp message.

Structural points worth knowing:

• The integration is activated per sub-account — an agency running twenty client sub-accounts enables and pays for WhatsApp on each one.
• One dedicated WhatsApp number connects to one sub-account; it cannot simultaneously be registered to the consumer WhatsApp apps.
• Snapshots carry your WhatsApp Workflows between sub-accounts, but the number connection and Meta template approvals must be redone in each new account.

Prerequisites: what you need before setup

Most failed setups I get called in to fix trace back to skipping one of these:

• A Meta Business Manager (Business Portfolio) account with you as admin. If your Facebook and Instagram ads already run through Business Manager, you have this.
• Business verification with Meta. Verification unlocks higher messaging limits and eligibility for a verified display name; unverified accounts start with tight daily caps. Expect to supply documents such as your ASIC registration matching your legal entity name, and allow a few days.
• A dedicated phone number. It must receive a one-time verification code by SMS or voice call, and must not be active on any consumer WhatsApp app. Many clients use a fresh Australian virtual number rather than sacrificing their main trading line.
• Agency-level activation. The add-on is enabled from the agency view first, then switched on per sub-account. Agencies can resell it to clients through the SaaS configurator.
• A display name that matches your brand. Meta reviews the display name against your Business Manager details; mismatches cause rejections.

Step-by-step setup

With prerequisites in place, the connection usually takes under thirty minutes:

1. Enable WhatsApp at agency level. In the agency dashboard, open the reselling settings, activate WhatsApp for the sub-accounts that need it, and set your resale price if billing clients through SaaS mode.
2. Open the sub-account and start the connection. Go to Settings → WhatsApp and click to begin. This launches Meta's embedded signup flow in a popup, so disable popup blocking.
3. Log in to Facebook and select the Business Portfolio that owns (or will own) your WhatsApp Business account.
4. Create or select a WhatsApp Business account, then register your number and confirm it with the one-time code.
5. Set your display name and category. This is what recipients see — keep it identical to your trading name.
6. Confirm the channel appears in Conversations. Message the connected number from a personal phone and check it lands in the sub-account inbox.
7. Submit your first message templates for approval immediately — approvals can take minutes to a couple of days, and you cannot initiate conversations without them.

Then map your custom fields (appointment time, first name, service type) into templates and add WhatsApp actions to key Workflows, testing with your own number first.

Pricing breakdown: what it actually costs

There are two layers of cost, and conflating them causes most of the confusion.

Layer 1: the HighLevel add-on

HighLevel charges approximately USD $10 per month per sub-account for the WhatsApp add-on — the platform access fee covering the LeadConnector integration, Conversations channel and Workflow actions. Agencies can absorb this or resell it at a markup through the SaaS configurator. Check current pricing on the official GoHighLevel pricing page, as add-on rates have shifted before and may again.

Layer 2: Meta's messaging fees

On top of the add-on, Meta charges for the messages themselves — historically per 24-hour "conversation", now shifting to per-message pricing for templates. Rates vary by country and template category: marketing templates cost the most, utility and authentication less, and service replies within the 24-hour window are generally free. Meta adjusts this pricing periodically, so treat any per-message figure in a blog post as indicative and check current pricing on Meta's WhatsApp platform pricing page before modelling campaign costs.

In practice, a typical Australian service business sending booking confirmations, reminders and replies pays only a few dollars a month in Meta fees, because utility messages and session replies dominate. Costs climb only when you push marketing broadcasts at volume.

Message templates vs session messages: the 24-hour window

This is the most important concept in WhatsApp automation, and the one that trips up teams coming from SMS. WhatsApp splits business messaging into two modes:

• Session messages (free-form). When a contact messages you, a 24-hour messaging window opens. Inside it you can send anything — free text, images, PDFs, voice notes — with no pre-approval. Every new inbound message resets the clock.
• Template messages. Outside the window, or to initiate a conversation, you can only send Meta-approved message templates: pre-written messages with variable placeholders (Hi {{1}}, your appointment is confirmed for {{2}}) submitted through GHL for Meta's review, categorised as marketing, utility or authentication.

The implication: your Workflows must respect the window. A booking reminder firing 24 hours before an appointment almost always falls outside an open session, so it must use an approved utility template. But when the client replies "can we make it 3pm instead?", the window opens and your team — or Conversation AI — can reply freely.

Approval tips from the trenches: bound variables with static text, avoid spammy phrasing ("FREE!!!", all-caps urgency), and choose the category honestly — Meta rejects templates that claim to be utility but read as marketing.

Automation use cases with Workflows

Here is where the HighLevel WhatsApp integration earns its keep — the three builds I deploy most often for Australian clients.

Booking confirmations and reminders

Trigger: Appointment Booked. The Workflow sends an instant WhatsApp confirmation template pulling date, time and location from custom fields, then reminder templates 24 hours and 2 hours out. Contacts confirm or reschedule in the same thread, and an If/Else branch on their reply updates the appointment status and moves the opportunity along the pipeline. Clinics and trades businesses I work with consistently see no-show rates drop once reminders move from SMS to WhatsApp — people simply see them faster.

Missed-call follow-up

Trigger: Call Status is Missed. The Workflow waits sixty seconds, then sends a template along the lines of "Sorry we missed you — reply here and we'll sort it out." The moment they reply, the 24-hour window opens and a human or AI takes over. This pairs naturally with the classic missed-call text-back automation — I run SMS and WhatsApp in parallel and let the contact reply on whichever channel they prefer.

Conversation AI on WhatsApp

Conversation AI works on WhatsApp the same way it does on SMS and web chat: train it on your services, pricing and FAQs, connect a calendar, and it answers enquiries and books appointments inside the WhatsApp thread — within the 24-hour session window, no templates needed. For after-hours lead capture it is genuinely transformative. My guide to Conversation AI for SMS, chat and booking covers the training and calendar wiring, all of which carries straight over to WhatsApp.

Other builds worth stealing: review requests when a pipeline stage moves to Won, abandoned-quote nudges via a tag-added trigger, and re-engagement templates to dormant contacts (marketing category — watch cost and frequency).

WhatsApp vs SMS in Australia: which channel when?

The honest answer is both, orchestrated. Here is how they compare:

SMS still matters — it reaches every mobile regardless of installed apps, and it remains my Workflow fallback when a contact has no WhatsApp presence. But SMS in Australia carries its own regulatory homework around sender registration and consent; if you run both channels, read my breakdown of SMS and A2P compliance for Australian GHL users so the SMS leg does not get filtered.

Common mistakes to avoid

• Connecting a number still registered on the consumer WhatsApp app. Registration will fail or disconnect the existing account. Deregister first or use a fresh number.
• Skipping Meta business verification. You hit low messaging tier limits fast, and marketing templates to new contacts may simply not send.
• Sending marketing content through utility templates. Meta's classifiers catch this, templates get paused, and repeat offences hurt your quality rating.
• Ignoring the 24-hour window in Workflow design. A free-form WhatsApp action firing outside an open session silently fails. Anything time-delayed must be a template.
• Blasting broadcasts like it's email. Blocks and reports tank your number's quality rating; Meta throttles or suspends low-quality senders. Frequency caps and easy opt-outs are non-negotiable.
• Forgetting that snapshots don't carry template approvals. After deploying from a snapshot, resubmit templates in the new sub-account and wait for approval before switching Workflows on.

If you want WhatsApp, SMS and email follow-up wired into one GoHighLevel system for your business, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

How much does the GoHighLevel WhatsApp integration cost?

HighLevel charges roughly USD $10 per month per sub-account for the add-on, and Meta charges separately for template messages, with rates varying by category and country. Replies within the 24-hour window are generally free. Both figures change over time, so check current pricing on the GoHighLevel and Meta pricing pages before budgeting.

Do I need a separate phone number for WhatsApp in GHL?

Yes. The WhatsApp Business API requires a dedicated number not active on the consumer WhatsApp apps. It can be virtual or landline as long as it can receive a one-time verification code. Most of my Australian clients provision a new virtual number rather than migrating their main trading line.

Can Conversation AI reply to WhatsApp messages?

Yes. Once connected, Conversation AI treats WhatsApp like any other channel — answering enquiries, qualifying leads and booking appointments inside the WhatsApp thread, operating freely within the 24-hour session window that opens whenever a contact messages you.

What is the 24-hour messaging window on WhatsApp?

When a contact messages your business, Meta opens a 24-hour window during which you can reply with free-form messages. Outside that window, or to start a conversation, you may only send Meta-approved message templates. Every new inbound message resets the clock.

Should Australian businesses use WhatsApp or SMS in GoHighLevel?

Use both. WhatsApp wins for rich, conversational follow-up and AI-driven chat, while SMS reaches every mobile regardless of apps installed. The strongest Workflows send WhatsApp first and fall back to SMS, letting the contact continue on whichever channel they answer from.