GoHighLevel WhatsApp Integration: Setup Guide

In short

GoHighLevel connects to WhatsApp through Meta's WhatsApp Business API. You add WhatsApp in a sub-account under Settings, connect a Meta Business account and a dedicated phone number, then send, schedule, and automate messages from Conversations and Workflows. The base add-on is $97 per month, and each message is billed per send inside the app.

• WhatsApp shows up as a channel in Conversations, next to SMS and email.
• It runs on Meta business API, so you need Meta verification and a clean number.
• Agencies can rebill WhatsApp usage to sub-accounts as SaaS-mode revenue.

What does WhatsApp inside GoHighLevel actually do?

WhatsApp becomes a channel in the Conversations inbox, right next to SMS, email, and social messages. Every thread lands in one place, so your team answers WhatsApp the same way they answer everything else.

It runs on Meta WhatsApp Business API, not the free phone app. That means you can send two-way messages, use approved message templates, add WhatsApp actions to workflows, and track replies against a contact record.

One honest note first: rocketlauncher.ai is a live GoHighLevel showcase, and we earn a referral commission if you start GoHighLevel through our link. We run WhatsApp on our own sub-accounts, so this is written from real setups.

How do you add WhatsApp to a GoHighLevel sub-account?

WhatsApp is turned on per sub-account, not once for the whole agency. Open the sub-account you want, then follow the steps below.

How do you send and schedule messages, and add CTA buttons?

Open a contact in Conversations, pick the WhatsApp channel, type your message, and send. Within 24 hours of a contact’s last inbound message, you can free-type any reply. Outside that 24-hour window, Meta requires an approved message template.

Templates are where CTA buttons live. A WhatsApp template can carry quick-reply buttons (like Yes or No) and call-to-action buttons (like Visit Website or Call). You build the template, submit it to Meta for approval, then send it once it clears.

To schedule, set a future send time on the message, or let a workflow send it at the right step. Scheduling through a workflow is the cleaner path when the send depends on a tag, an appointment, or a reply.

How do you trigger a workflow on an inbound WhatsApp message?

This is the automation part. Build a workflow, add the Customer Replied trigger, and set the channel filter to WhatsApp. Now the workflow fires whenever a contact replies on WhatsApp.

From there, add actions: tag the contact, send a WhatsApp template back, start an internal notification, or move a deal in a pipeline. A common setup is: contact replies, workflow tags them, then sends the next approved template automatically.

If you are new to inbound triggers, the same pattern powers our Instagram guide, so the muscle carries over.

How do agencies rebill WhatsApp usage to sub-accounts?

This is the money angle. In SaaS mode, an agency can rebill conversation usage, which includes WhatsApp messages, to each sub-account. You set the price your client pays per message, and the difference between that price and your cost is your margin.

You turn this on in Agency settings under the SaaS Configurator and company billing. Each sub-account loads a wallet, and WhatsApp sends draw down from it at the rate you set. When the wallet runs low, it tops up automatically.

Rebilling turns WhatsApp from a cost into recurring revenue. It is the same model that makes white-label GoHighLevel work, so read our SaaS mode and white-label guides if you plan to resell.

What does WhatsApp in GoHighLevel cost, and what are the limits?

The WhatsApp add-on starts at a $97 per month base per sub-account. On top of that, usage is billed per message, and you should check the current per-message rate in the app, because it changes. Meta also charges its own conversation fees, which pass through.

The real limits are approval, not price. You need Meta business verification, a dedicated number that is not on a personal WhatsApp, and approved templates for any outbound message sent outside the 24-hour reply window. Plan for a short review wait before you can send at volume.