GoHighLevel WhatsApp Integration: Setup & Pricing (2026)
GoHighLevel WhatsApp Integration: Setup & Pricing (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 9 August 2026 · 10 min read
GoHighLevel connects to the WhatsApp Business Platform natively through LeadConnector, so threads land in the same Conversations inbox as SMS and email and can be triggered from Workflows. You enable it at agency level, then switch it on per sub-account for US$10 per month, rebillable through SaaS Mode. On top of that you pay Meta directly — a few cents for utility messages, around AUD 0.13 per marketing template to an Australian number.
On this page: What the GoHighLevel WhatsApp integration actually is · Setting up the GoHighLevel WhatsApp integration step by step · What it costs: GHL fees and Meta's per-conversation pricing · Template messages and getting them approved · Using WhatsApp inside Workflows · Managing the WhatsApp inbox · Opt-in and compliance for Australian senders · Rebilling WhatsApp to clients · Limitations worth knowing before you commit · Common mistakes to avoid · Frequently asked questions · Related articles
The GoHighLevel WhatsApp integration lets you send and receive WhatsApp Business messages inside your sub-account, against the same contact record, tags and pipelines you already use. It is not a Zapier bridge or third-party middleware — it is a native channel on Meta's WhatsApp Business Platform, delivered through LeadConnector, so messages sit in Conversations alongside SMS, email and Instagram DMs and fire from any Workflow.
For Australian agencies this matters. Plenty of client bases — migration and education agents, clinics with international patients, anyone selling into Asia — reply on WhatsApp when they ignore SMS. The catch: it is not a free SMS replacement. Meta charges per conversation or template, the rules on who you can message are strict, and template approval adds a step. Below is the setup, the real AUD numbers, and the traps that catch people in month one.
What the GoHighLevel WhatsApp integration actually is
HighLevel WhatsApp is a first-party channel. Enabling it provisions Meta's WhatsApp Business Platform (the API product, not the free phone app) with LeadConnector as the Business Solution Provider. Your sub-account gets a WhatsApp tab in Conversations, a Send WhatsApp Message action in Workflows, and WhatsApp as a trigger source.
What you get
- Two-way messaging threaded under the same contact as your SMS and email history.
- Template sending for outbound-initiated conversations, managed inside GHL.
- Workflow actions and triggers, including Customer Replied branching and Conversation AI.
- Media support — images, PDFs, short video — useful for quotes and appointment cards.
What you do not get
No group messaging, no Status posting, no broadcast lists — every message is one-to-one. You also cannot run the WhatsApp Business phone app on the number once it is on the API.
Setting up the GoHighLevel WhatsApp integration step by step
1. Confirm your plan
WhatsApp is an agency-level activation, so you need a GoHighLevel agency plan (Unlimited or Agency Pro); a single-account subscription will not surface the option. Agency Pro also brings SaaS Mode, needed for rebilling. Tiers sit on the GoHighLevel pricing page.
2. Enable WhatsApp at agency level
In the agency view, go to Settings then WhatsApp and accept the terms. This unlocks the per-sub-account toggle; nothing is live yet.
3. Turn it on for the sub-account
Open the sub-account, go to Settings then WhatsApp, and activate. The US$10 monthly add-on starts billing to your agency card here, so only enable it where it will be used — I have seen agencies quietly paying for fifteen dormant activations.
4. Complete Meta Business verification
The step that stalls most builds. The client needs a Meta Business Manager account verified with ABN or company documents, a matching business name, a website with visible contact details, and a business email on the domain. Allow a few business days. Start it before you promise a launch date.
5. Connect a dedicated phone number
Register the number during the embedded signup flow inside GHL. It must not be active on the consumer WhatsApp or WhatsApp Business app — if it is, delete that account and wait for deregistration. Use a spare number, not the client's main line, keeping it separate from the GoHighLevel phone system and call tracking running through Twilio.
6. Set the display name and profile
The display name must reasonably match the business name Meta verified. Fill in description, address, website and category — they show in the contact card recipients see.
7. Test the WhatsApp tab in Conversations
Send a test, reply from your handset, confirm the inbound lands on the right contact. If no contact exists GHL creates one from the number, so standardise phone fields to +61 format first.
What it costs: GHL fees and Meta's per-conversation pricing
Two separate charges, constantly conflated. The US$10 per sub-account per month goes to GoHighLevel. Message costs go to Meta, billed against the payment method on the WhatsApp Business Account.
Meta's model has been a 24-hour conversation window: the first message in a category opens the window and everything inside it is one charge. From 2025 into 2026 Meta has been shifting marketing to per-template-message pricing, so each marketing template bills individually while utility and service keep window-based or free treatment. Rates vary by country and change — check the official WhatsApp Business Platform pricing page before quoting a client.
| Category | What it covers | Typical AUD cost (Australian recipient) |
|---|---|---|
| Marketing | Promotions, offers, re-engagement, abandoned-cart nudges | ~AUD 0.11–0.14 per template message |
| Utility | Order updates, appointment reminders, receipts tied to a transaction | ~AUD 0.03–0.05 per conversation |
| Authentication | One-time passcodes and login verification | ~AUD 0.03–0.05 per conversation |
| Service | Free-form replies to a customer-initiated thread inside 24 hours | Free |
The practical read: support costs nothing, reminders are cheap, marketing is where the meter runs. A clinic sending 400 appointment reminders a month pays roughly AUD 15–20 in Meta fees; an ecommerce client sending 5,000 marketing templates is closer to AUD 600. Put that spend in the client's proposal, not your P&L.
Template messages and getting them approved
Outside the 24-hour service window you cannot send free-form text — only an approved template. Templates are submitted through the WhatsApp Manager linked to the business account and reviewed by Meta, usually within hours, occasionally a day or two.
Building templates that pass
- Use variables sparingly with realistic sample values — a template that is mostly
{{1}} {{2}}gets rejected as unclear. - Map variables to GHL custom fields; a blank variable fails the send.
- Categorise honestly. Labelling a promotion as utility gets it rejected and repeat offences hurt your quality rating.
- Avoid all-caps, excessive emoji, and anything reading like a loan offer.
Quality rating
Meta scores each number on user feedback. Too many blocks or report taps and your messaging limit drops — the strongest argument for tight opt-in lists over bulk imports.
Using WhatsApp inside Workflows
WhatsApp behaves like any other channel in the Workflow builder, so you drop it into existing automations rather than rebuilding them. Our guide to GoHighLevel workflow triggers covers the trigger types you will be wiring into.
Recipe 1: speed-to-lead follow-up
Trigger on Form Submitted or an inbound from the GoHighLevel chat widget. Email immediately, wait two minutes, then send a WhatsApp template with the rep's name and a booking link. Branch on Customer Replied — remove the awaiting-first-contact tag and move the opportunity to Contacted, or drop to SMS at four hours.
Recipe 2: appointment reminders
Trigger on Appointment Status, filter to Confirmed, then send utility-category templates at 24 hours and 2 hours before start with date, time and address merged in. Cheap, and read rates beat SMS for most client bases.
Recipe 3: abandoned-cart style nudges
Trigger on an abandoned order form or a tag from your store integration, wait 45 minutes, then send a marketing template referencing the product. Cap it at two touches — these cost per send and irritate people quickly.
Conversation AI on WhatsApp
Point Conversation AI at inbound threads to answer FAQs, qualify and book. Replies inside the window are free-form and free of charge, making this the cheapest place in GHL to run an AI responder. The comparison of Conversation AI vs Voice AI helps decide how much to hand over.
Managing the WhatsApp inbox
WhatsApp threads live in Conversations with the standard filters. Habits that keep it usable at volume:
- Assign conversations so the 24-hour window is somebody's responsibility, not everybody's.
- Use snippets for the replies your team sends fifty times a week.
- Tag on outcome (
whatsapp-booked,whatsapp-no-answer) so reporting is possible later. - Watch the window clock — once 24 hours lapse you are back to templates, and a free-form reply simply fails.
To push WhatsApp data into an external system, use the GoHighLevel API and private integrations, not the WhatsApp channel itself.
Opt-in and compliance for Australian senders
Two rulebooks apply at once. The Spam Act 2003 requires consent, accurate sender identification and a functional unsubscribe on commercial electronic messages, and WhatsApp marketing sits squarely inside that. Meta's Business Messaging policy separately requires opt-in where the person understands they will receive WhatsApp messages from your specific business.
What good opt-in looks like
- An unticked checkbox on your GHL form: "Yes, message me on WhatsApp about my enquiry."
- Consent captured into a custom field plus a timestamped
whatsapp-optintag as evidence. - A workflow filter that will not send unless the tag is present — belt and braces beats an apology to the ACMA.
- An opt-out line in every marketing template, plus a workflow that catches STOP, adds a suppression tag and removes the contact from active sequences.
Keep the consent record. If a complaint lands, "we had their number in the CRM" is not a defence.
Rebilling WhatsApp to clients
With SaaS Mode on Agency Pro, the US$10 per sub-account fee is rebillable. Most Australian agencies fold it into the plan price rather than itemising — a AUD 397/month package absorbs it. If you itemise, a 2x–3x markup is defensible given the setup, verification and template work you carry.
Meta message costs bill to the WhatsApp Business Account payment method, not GHL's wallet, so decide upfront who owns that card. Cleanest: the client's own Business Manager and card, and you charge a management fee. If you own the Business Manager you wear the spend and must invoice it back with margin.
Once the build works, save it as a snapshot so the next deployment is a load, not a rebuild. The WhatsApp connection does not travel in a snapshot — each sub-account needs its own number and verification — but templates, workflows, custom fields and tags do.
Limitations worth knowing before you commit
- One number per sub-account. Three locations wanting three WhatsApp lines means three sub-accounts and three US$10 fees.
- Template approval delays. Usually fast, sometimes not. Never launch a campaign that depends on a template approved the same morning.
- No group messaging. One-to-one only.
- Messaging limits. New numbers start at 250 business-initiated conversations per 24 hours and scale with good quality — do not plan a 5,000-contact launch on a week-old number.
- Number lock-in. Migrating a number off the API later is possible but fiddly, so choose deliberately.
Common mistakes to avoid
- Treating WhatsApp as free SMS. Marketing templates bill per message and the invoice climbs fast. Model the cost before promising a broadcast strategy.
- Connecting the client's main mobile. Once a number is on the API the handset app stops working for it. Use a dedicated number nobody is currently using.
- Leaving Meta Business verification until last. Agencies build the whole workflow, then discover verification takes a week. Start it on day one.
- Miscategorising templates to save money. Labelling promotions as utility gets them rejected and damages the number's quality rating, which caps sending limits.
- No opt-in tag gating the sends. Without a tag filter, one bad import sends marketing templates to people who never consented — a Spam Act problem and a fast route to blocks.
- Ignoring the 24-hour window in workflow design. A wait step over 24 hours followed by a free-form WhatsApp message silently fails. Use a template after the window closes.
If you want WhatsApp wired into your GoHighLevel follow-up without the compliance guesswork, book a strategy call with the HL Growth Partner team.
Frequently asked questions
How much does the GoHighLevel WhatsApp integration cost in total?
US$10 per month per sub-account to GoHighLevel, plus Meta's messaging charges. Service replies inside a customer-initiated window are free, utility and authentication run around AUD 0.03–0.05, and marketing templates roughly AUD 0.11–0.14 per message to an Australian number. Most small services businesses land under AUD 30 a month.
Do I need an agency plan to use WhatsApp in GoHighLevel?
Yes. WhatsApp is activated at agency level then enabled per sub-account, so an agency subscription is required. To rebill the US$10 add-on to clients you need Agency Pro, because that is the tier that includes SaaS Mode.
Can I use my existing WhatsApp Business app number?
Not while it is still registered to the app. Delete the app account, wait for deregistration to clear, then verify the number in GoHighLevel. After that the handset app can no longer use that number.
Why did my WhatsApp message fail to send from a Workflow?
Usually the 24-hour window closed on a free-form message, the template is unapproved or paused, a merge field came through blank, or the contact's number is not in valid international format. The conversation log names the specific rejection reason.
Is WhatsApp better than SMS for Australian businesses?
It depends on the audience. For multicultural communities, international students, migration and education agents, or anyone selling into Asia, WhatsApp usually beats SMS on reply rates. For a mainstream domestic list, SMS still wins on reach. Run both for a month and compare.
