GoHighLevel WhatsApp: How the Integration Actually Works

How GoHighLevel WhatsApp Setup Actually Works

Connecting GoHighLevel WhatsApp to a sub-account isn't a single button. The platform offers three separate paths into Meta's system.

Each one assumes a different starting point: a business already messaging customers through the WhatsApp Business App, one starting from zero, or one migrating off another provider entirely. Picking the wrong path means redoing phone verification, or worse, losing chat history built up over years.

The first option, coexistence, suits a business that won't give up its phone app. It links an existing WhatsApp Business App number to the CRM.

That link syncs contacts and up to 180 days of conversation history, and lets messages go out from both the app and GoHighLevel under the same number.

Real limits come with it. Coexistence allows one phone number per account, isn't available for numbers registered in Nigeria or South Africa, and caps throughput at 20 messages a second.

Group chats and voice or video calls stay off the table. Profile details still have to be edited inside the WhatsApp app itself, not the CRM.

The second path skips the existing app entirely. A sub-account can open Settings, create a new WhatsApp Business Account, log in through Facebook, and register a fresh number through an OTP sent by text or voice call, picking Meta business assets along the way.

The third option, migration, moves an account off an existing Business Solution Provider. It transfers those assets and re-verifies the number as part of a broader GoHighLevel setup process.

Method	Starting point	What you keep
Coexistence	Existing WhatsApp Business App number	Phone app access, 180 days of history
New business account	No prior WhatsApp Business presence	A clean number built for the CRM only
BSP migration	Already live with another provider	Existing Meta business assets, re-verified

What Agencies Pay to Turn WhatsApp On

Enabling WhatsApp for a client costs the agency $10 a month per location, billed separately from whatever the agency charges the client through its own Stripe account. That's the wholesale rate.

Agencies set their own resale pricing from the Reselling tab, or skip reselling and absorb the fee themselves.

Messaging adds its own cost on top. Outbound template messages, the kind sent outside an active conversation, get billed by country and by template category: marketing, utility, authentication or service.

None of that is padding. It's what makes an unprompted WhatsApp message possible under Meta's rules, and any white-label support arrangement needs to price around it rather than against it.

Interactive Messages Turn a Reply Into a Tap

Once a contact messages a business on WhatsApp, workflow automation inside GoHighLevel can answer with more than plain text. Five formats are available:

• Quick reply buttons, up to three per message, each capped at 20 characters
• Location messages, shown as a clickable map card with latitude, longitude and address
• Contact messages, carrying a name, phone number, email and address in one card
• List messages, structured into sections and rows, with a display timeout from five minutes to two days
• A visit-website button mapped to a clean, tappable link

Only one of those formats fits in a single message, and all of them ride on the customer service window that opens the moment a contact messages first. That window lasts 24 hours from the user's last message, and it resets every time they message again.

Inside that window, non-template messages are free, and so are utility templates. Marketing templates get billed whether the window is open or not. Outside the window, only a paid template can reach the contact at all.

That's the real reason to weigh this against plain two-way SMS before building a workflow around it.

A quick-reply button sent the moment a lead messages in costs nothing and gets answered before the window closes. Firing off a template message the next morning instead is a different economics problem entirely.

Cover photo by Pixabay on Pexels