GoHighLevel How-To Guides

By Damian Qualter | GoHighLevel Expert | 200+ Implementations

Have you used the GoHighLevel WhatsApp Integration yet? WhatsApp has 2 billion active users globally. In the UK, it’s the default messaging app for a large segment of the population — more reliable than email as a contact channel for many consumer-facing service businesses. The open rate on WhatsApp messages is significantly higher than that of email. For businesses where the prospect is typically a consumer rather than a corporate buyer — such as mortgage brokers, estate agents, personal trainers, and wellness practitioners — it’s a channel worth taking seriously.

GoHighLevel supports WhatsApp messaging. The setup requires the WhatsApp Business API (not the standard WhatsApp Business app) and a Meta Business account. The compliance requirements for bulk and automated messaging are more involved than for standard SMS. This guide covers the setup, the limitations, the compliance picture, and how to build automations that actually reach people where they’re most likely to respond.

Standard WhatsApp Business vs WhatsApp Business API: The Critical Distinction

Before building anything in GoHighLevel, understand this distinction — it determines whether the integration is even possible.

WhatsApp Business (the app): The free mobile app designed for small businesses. Manual messaging only. Cannot be connected to GoHighLevel or any CRM/automation platform. Not relevant for GHL integration.

WhatsApp Business API: Meta’s programmatic access to WhatsApp, designed for businesses that need to send messages at scale or automate messaging through software. Required for GoHighLevel integration. Has associated costs based on Meta’s per-conversation pricing model and requires Meta Business verification.

WhatsApp Business API pricing (UK-destined conversations, approximate): Marketing conversations (outbound promotional) cost around $0.062 (approx. 5p) per conversation. Utility conversations (transactional—confirmations, reminders, order updates) cost approximately $0.020 (approx. 1.6p) per conversation. Service conversations (user-initiated within a 24-hour window) are free for the first 1,000 per month, then around $0.020 (approx. 1.6p) each. A conversation covers all messages exchanged within a 24-hour window, not per individual message. Pricing varies by destination country and changes periodically — verify current rates at developers.facebook.com/docs/whatsapp/pricing before building cost projections.

GoHighLevel connects to the WhatsApp Business API, not the app. If you’re currently using the WhatsApp Business app manually, you cannot simply connect it to GHL — you need to migrate to the API, which involves a new number or porting your existing number through Meta’s verification process.

Prerequisites Before Connecting to GoHighLevel

Meta Business Account (verified)

Go to business.facebook.com and create or access your Meta Business account. Complete business verification — Meta requires a registered business name, a business address, and typically a website. Verification can take several days. Without verification, you won’t be able to access WhatsApp Business API features.

A dedicated phone number for WhatsApp Business API

The number you use for the WhatsApp Business API must not be registered to the standard WhatsApp app or WhatsApp Business app. You can either:

Use a new SIM or virtual number not previously associated with WhatsApp
Port an existing number from the WhatsApp Business app to the API (this involves deleting the WhatsApp Business app account — a one-way process with a 30-day data export window)

For most businesses, using a dedicated number is simpler than porting. The number can be a UK mobile, UK geographic, or UK 0800 number. Twilio, LC Phone, and most virtual number providers support WhatsApp Business API registration.

Meta Business Suite — WhatsApp account setup

In Meta Business Suite → WhatsApp accounts → Create account. Follow the verification steps for your phone number. Set your WhatsApp Business profile: business name, category, description, address, website.

Connecting WhatsApp to GoHighLevel

In GoHighLevel: Settings → Integrations → WhatsApp

Click Connect WhatsApp. You’ll be redirected to Meta’s business connection flow. Grant GoHighLevel the required permissions for your WhatsApp account. Once connected, your WhatsApp number appears in GHL’s integrations panel.

Once connected, WhatsApp becomes available as a channel in your GoHighLevel conversations inbox and in workflow actions alongside SMS and email.

WhatsApp Message Templates: What They Are and Why You Need Them

This is the most important compliance and operational concept for WhatsApp Business API users.

WhatsApp distinguishes between two message categories:

Session messages (free-form): Messages sent within 24 hours of a contact’s last inbound message to you. During this 24-hour window, you can send any message — personalised, conversational, promotional. No template required.

Template messages (pre-approved): Messages sent outside the 24-hour window, or outbound first-contact messages. These must use a pre-approved template submitted to and approved by Meta. Templates can contain personalisation variables ({1}, {2}) but cannot contain promotional language that Meta hasn’t approved.

For automation purposes, most automated GoHighLevel workflows that include WhatsApp will send template messages because the automation fires at a time unrelated to a recent inbound message from the contact. This means every WhatsApp automation message needs a corresponding approved Meta template.

Creating templates:

In Meta Business Suite → WhatsApp Manager → Message Templates → Create Template. Select category (Marketing, Utility, or Authentication). Write the template body with your personalisation variables. Submit for Meta’s review. Approval typically takes a few hours to a few days. Rejections are common if the language is overly promotional — write templates factually and avoid sales language.

In GoHighLevel: When building a WhatsApp workflow action, select the approved template from the template dropdown and map GoHighLevel contact fields to the template variables.

Building WhatsApp Workflows in GoHighLevel

Once templates are approved, WhatsApp actions work in GHL workflows exactly like SMS or email actions.

Lead response workflow with WhatsApp:

Trigger: Contact Created (from Facebook Lead Ads, form submission, or other source)

Action 1: Wait 30 seconds. Action 2: WhatsApp — Send Template “lead_acknowledgement_v1”

Variable {1}: Contact First Name
Variable {2}: Service they enquired about (from GHL custom field)

Action 3: Wait 2 hours (if no reply received — use workflow condition) Action 4: WhatsApp — Send Template “follow_up_v1”

The 30-second delay before the first WhatsApp message prevents an instant message from feeling robotic. People expect a slight pause between enquiry and first contact.

Appointment reminder workflow:

WhatsApp is particularly effective for appointment reminders — the open rate is significantly higher than email, and the 24-hour reminder is where it earns its place. The conversation context (the contact can reply directly to the reminder) also makes WhatsApp a more natural channel for rescheduling requests than a one-way email reminder.

UK Compliance Considerations

GDPR and consent: WhatsApp messaging is subject to the same consent requirements as email marketing under UK GDPR. For marketing messages, you need explicit prior consent for WhatsApp messaging specifically — a generic “contact me” form submission doesn’t constitute specific consent for WhatsApp. Collect WhatsApp consent explicitly at the point of opt-in.

PECR: The Privacy and Electronic Communications Regulations apply to electronic marketing messages, including WhatsApp. Commercial WhatsApp messages without prior consent from an individual subscriber are a PECR violation. The ICO’s direct marketing guidance covers electronic marketing broadly — the WhatsApp channel is not exempt.

Transactional vs marketing: As with SMS and email, transactional WhatsApp messages (appointment confirmations, reminders, service updates) have different requirements from marketing messages. A booking confirmation sent via WhatsApp is a service communication — consent for marketing isn’t required. A promotional offer sent via WhatsApp to the same contact is a marketing message — prior consent is required.

Opt-out: Every WhatsApp automation sequence should include a clear opt-out mechanism. In practice, this means including opt-out instructions in the first template message (“Reply STOP to unsubscribe from WhatsApp messages”) and building a workflow that tags the contact as opted out and removes them from future WhatsApp sequences when they reply with an opt-out keyword.

WhatsApp vs SMS for UK Service Businesses: Choosing the Right Channel

Both channels have higher open rates than email. The practical distinction:

WhatsApp is appropriate when: your contact base is consumer-facing and WhatsApp is their primary messaging app; you want rich messaging capabilities (images, documents, voice notes); and you’ve obtained specific WhatsApp consent. Higher friction to set up, but higher engagement when used correctly.

SMS is appropriate when: you need universal reach across all phone types (WhatsApp requires a smartphone and internet connection), you want simpler compliance without template pre-approval, or your contact base includes people who are less likely to use WhatsApp (some older demographics, corporate contacts using work phones).

Many UK service businesses run both channels in parallel — SMS as the default for transactional messages, WhatsApp as an opt-in channel for contacts who prefer it.

Frequently Asked Questions

Does GoHighLevel integrate with WhatsApp? Yes. GoHighLevel integrates with the WhatsApp Business API (not the standard WhatsApp or WhatsApp Business app). The connection requires a Meta Business account, a WhatsApp Business API-enabled number, and Meta Business verification. Once connected, WhatsApp is available as a channel in the conversations inbox and in workflow actions.

How do I connect WhatsApp Business to GoHighLevel? Go to GoHighLevel Settings → Integrations → WhatsApp. You’ll be redirected to Meta’s business connection flow. Prerequisites: a verified Meta Business account, a phone number registered for WhatsApp Business API (not the standard app), and completed Meta business verification. Once connected, WhatsApp appears as a channel in GHL.

Can GoHighLevel send automated WhatsApp messages? Yes. WhatsApp automation in GoHighLevel workflows uses pre-approved Meta message templates for outbound messages. Templates are created and submitted for approval in Meta Business Suite → WhatsApp Manager → Message Templates. Once approved, they’re available in GHL workflow actions with dynamic personalisation variables.

Do I need the WhatsApp Business API for GoHighLevel? Yes. The standard WhatsApp Business app cannot connect to GoHighLevel or any CRM platform. The WhatsApp Business API is the programmatic access layer required for CRM integration and automation. It has per-conversation pricing from Meta and requires Meta business verification.

Are WhatsApp messages sent through GoHighLevel GDPR-compliant? Compliance depends on your consent collection and message content, not the platform. Marketing WhatsApp messages require explicit prior consent under UK GDPR and PECR. Transactional messages (confirmations, reminders) don’t require marketing consent but must relate directly to a transaction the contact initiated. Include opt-out mechanisms in all marketing sequences.

What are WhatsApp message templates, and why do I need them? Message templates are pre-written, Meta-approved messages required for all WhatsApp Business API messages sent outside a 24-hour response window (i.e., any outbound automated message not triggered by a recent contact reply). Templates are submitted to Meta for review, approved in your Meta Business account, and then used in GoHighLevel workflow actions with personalisation variables.

Ready to add WhatsApp to your GoHighLevel automation stack?

to discuss your setup requirements.