Go High Level & WhatsApp Business: Features & Setup | GHLCRM.US

GoHighLevel connects WhatsApp Business with its CRM, Conversations, contacts, workflows, templates, automation, and other customer-management tools. Businesses can connect an existing WhatsApp Business App through Coexistence, create a new WhatsApp Business Account, or migrate an existing WhatsApp setup from another supported Business Solution Provider.

The biggest advantage is centralization.

Instead of:

WhatsApp → Separate Phone → Manual Follow-Up → Separate CRM

a business can build:

WhatsApp → HighLevel Conversations → Contact → Workflow → Opportunity → Appointment → Follow-Up

For businesses already using WhatsApp, HighLevel's Coexistence functionality is particularly important because an eligible existing WhatsApp Business App can continue operating on the phone while the same number is connected to the CRM.

For a broader overview of the connection, see our GoHighLevel WhatsApp Integration guide.

The Go High Level WhatsApp integration connects an eligible WhatsApp Business setup with a HighLevel sub-account through LeadConnector and Meta's WhatsApp Business Platform infrastructure.

Once connected, WhatsApp can become part of the same environment used for:

The objective is not simply to send WhatsApp messages from another dashboard.

The real value comes from connecting those conversations with customer data and business processes.

HighLevel's current onboarding experience provides three main paths.

Use this when the business already actively uses the WhatsApp Business App and wants to continue using it.

The same number can operate through:

WhatsApp Business App + HighLevel CRM

This avoids forcing an established business to abandon its familiar mobile workflow simply to gain CRM integration.

Use this when the business is starting fresh.

The business can connect an appropriate new or unused number through the current Meta onboarding process.

Use this when the business already uses the WhatsApp Business Platform through another Business Solution Provider and wants to move the connection to LeadConnector.

The correct path depends on the current WhatsApp setup.

Do not start by creating new assets unnecessarily.

First identify what the business already has.

Start Your GoHighLevel 30-Day Free Trial →

WhatsApp Coexistence allows an eligible business to use the same WhatsApp Business number through both:

WhatsApp Business App

and:

HighLevel CRM

simultaneously.

This is a major improvement for businesses that already rely on the mobile application.

Previously, businesses moving into API-based CRM workflows could face difficult decisions about how an existing WhatsApp number would be used.

Coexistence creates a more flexible architecture:

Customer

↓

WhatsApp Number

↙　　　　　　　　　↘

Business App　　　 HighLevel CRM

Both environments can participate in supported messaging.

Current HighLevel documentation identifies several important capabilities.

Businesses can:

That makes Coexistence especially useful for businesses moving gradually from phone-based WhatsApp management toward centralized CRM operations.

Coexistence also has limitations.

Under the current implementation:

Eligibility can also depend on Meta/WhatsApp requirements.

Not every phone number should be assumed to qualify automatically.

Choose Coexistence when:

Existing WhatsApp Business App + Existing Customers + Existing Conversations + Desire for CRM Integration

describes the business.

For example, imagine a local service company that has used WhatsApp Business for three years.

Customers already know the number.

Employees already use the app.

Changing the number could create unnecessary disruption.

Coexistence can allow the company to preserve that customer-facing workflow while adding:

CRM + Automation + Workflows + Centralized Conversations

behind it.

Starting fresh may make more sense when:

A clean setup can be easier when there is no existing WhatsApp infrastructure to preserve.

Businesses already using the WhatsApp Business Platform through another BSP can use HighLevel's supported migration path.

HighLevel's redesigned onboarding process uses Meta's Embedded Signup flow for supported BSP migration.

Current documentation says supported migration can preserve assets including:

This is important because moving providers should not automatically mean rebuilding the entire WhatsApp business identity from zero.

Review all prerequisites before beginning the migration.

The current setup starts inside the relevant HighLevel sub-account.

Confirm that you are inside the location that should own the WhatsApp connection.

This is particularly important for agencies.

The correct architecture is:

Client A → Client A WhatsApp

not:

Client A → Client B WhatsApp

Navigate to:

Settings → WhatsApp

HighLevel's current onboarding screen will display the available setup paths.

Select:

Connect Your WhatsApp Business App With Coexistence

or:

Create a New WhatsApp Business Account

or:

Migrate From an Existing BSP

Do not simply choose the first option.

Match the onboarding method to the current business setup.

HighLevel displays requirements for the selected path.

Check them before continuing.

For Coexistence, for example, you should have access to the current WhatsApp Business App and appropriate Meta/Facebook credentials.

Continue through the Meta authentication and Embedded Signup process.

Use the account that legitimately manages the relevant business assets.

Select or create the appropriate WhatsApp Business assets according to the chosen onboarding method.

Review:

before confirming.

Complete the applicable verification steps.

Coexistence may involve confirming the existing number and scanning a QR code through the WhatsApp Business App.

Complete the HighLevel onboarding prompts.

Then return to:

Settings → WhatsApp

and verify the account status.

Before creating automation, confirm that basic inbound and outbound messaging behaves as expected.

Test the connection with an appropriate contact.

Do not build a complex automation system before verifying the underlying channel.

One of the most useful Coexistence features is historical synchronization.

HighLevel currently supports importing up to:

6 months of WhatsApp chat history

during the supported Coexistence process.

This helps provide context when a business transitions into CRM-based communication.

Instead of:

New CRM → No Previous Context

the team can begin with recent conversation history available in the connected environment.

This can be valuable for sales and customer-support teams.

After setup, supported WhatsApp messages can appear inside HighLevel Conversations.

This changes the operational model.

Instead of an employee checking:

WhatsApp Phone

then:

CRM

then:

Email

the relevant communication can become more centralized.

A contact record and conversation context can work together.

The team can more easily understand:

Who is this person?

What did they ask?

What happened previously?

What should happen next?

That is where CRM integration becomes more valuable than simply having WhatsApp on a desktop screen.

The WhatsApp customer service window is essential to understanding how messaging works.

When a customer sends a message, a:

24-Hour Customer Service Window

opens.

Each subsequent customer message can reset that timer.

During an active customer service window, the business can use supported free-form messaging.

When the window closes, business-initiated messaging generally requires an appropriate approved template.

Think:

Customer Messages Business

↓

24-Hour Window Opens

↓

Free-Form Reply Available

↓

24 Hours Pass Without Customer Message

↓

Window Closes

↓

Approved Template Required to Reinitiate Supported Messaging

This rule should influence workflow design.

HighLevel provides a workflow condition specifically for checking whether the WhatsApp Customer Service Window is open.

That allows a workflow to branch.

For example:

Need to Send WhatsApp Message

↓

Check Customer Service Window

Send Appropriate Free-Form Message

Use Approved Template Where Appropriate

This is better than blindly attempting the same message regardless of WhatsApp's messaging rules.

WhatsApp templates are pre-approved structured messages used for supported business-initiated communication.

Templates are especially important when contacting someone outside the active customer service window.

Current categories can include:

Each category has a different purpose and pricing treatment.

Marketing templates can cover promotional communication such as:

Marketing messages are currently charged per delivered message according to the applicable destination market and pricing structure.

Do not classify a promotional message as utility simply to seek a lower rate.

Template classification should accurately reflect the content and purpose.

Utility templates relate to an existing transaction or expected service update.

Examples can include:

From October 1, 2026, utility messages are charged per delivered message whether they are sent inside or outside an open customer service window.

This is a significant pricing change for businesses with high WhatsApp automation volume.

Authentication messages are used for authentication-related experiences such as supported verification flows.

They are distinct from ordinary marketing or service communication.

A coaching business should not use an authentication template for a promotional campaign simply because both involve sending a message.

Use the correct category.

Service messages are free-form messages sent within an active customer service window.

The pricing rules changed on:

October 1, 2026

From that date, HighLevel's current documentation says service messages are charged on a per-message basis.

However, the first:

1,000 service messages per phone number per month

remain free.

That allowance resets monthly.

This change matters for businesses that previously designed their WhatsApp economics around service messaging being entirely free.

WhatsApp messaging in HighLevel now primarily follows a:

Per-Delivered-Message

pricing structure.

The exact amount depends on factors such as:

Therefore, there is no single universal cost for every WhatsApp message.

A marketing message delivered to one country can have a different cost from a utility message delivered to another.

Always review the current rate table when estimating large campaigns.

Two major changes took effect on October 1, 2026.

Previously free service messaging moved to per-message billing.

The first 1,000 service messages per phone number each month remain free.

After that allowance, applicable per-message charges apply.

Utility messages delivered inside an open 24-hour customer service window are also now billed per delivered message.

Before October 2026, this scenario had different pricing treatment.

Agencies using older WhatsApp cost calculators should update their assumptions.

WhatsApp becomes substantially more useful when connected with HighLevel Workflows.

A workflow can send supported WhatsApp messages after appropriate triggers.

For example:

Appointment Booked

↓

Wait Until Reminder Time

↓

Check Messaging Conditions

↓

Send WhatsApp Reminder

Another workflow could use:

New Lead

↓

CRM Contact

↓

Qualification

↓

WhatsApp Follow-Up

↓

Calendar

The specific implementation must follow current WhatsApp template, consent, and customer-service-window requirements.

A service business might create:

Appointment Scheduled

↓

24 Hours Before Appointment

↓

WhatsApp Utility Template

↓

Reminder Delivered

The message could contain supported appointment information using approved template variables.

This can be useful for:

The business should still monitor message costs and consent requirements.

Suppose someone submits a lead form and has appropriately agreed to WhatsApp communication.

The process could become:

Form → Contact → Opportunity → WhatsApp Follow-Up

If the applicable messaging window is not open, an approved template may be required.

If the customer responds:

Customer Reply → Service Window Opens → Free-Form Conversation

The salesperson can then continue the supported conversation through HighLevel Conversations.

A WhatsApp journey could also support qualification.

For example:

Lead → WhatsApp Conversation → Collect Information → Update CRM → Appropriate Next Step

The next step might be:

Qualified → Calendar

or:

Needs Human Review → Salesperson

or:

Not Ready → Nurture

The objective is to connect communication with CRM decisions.

HighLevel can also combine supported WhatsApp communication with Conversation AI.

This can allow AI to participate in configured customer interactions rather than requiring a human to answer every routine question manually.

Potential use cases include:

A possible architecture is:

WhatsApp Lead

↓

Conversation AI

↓

Understand Request

↓

Answer Routine Question

↓

Collect Information

↓

Book or Route

This can be useful outside normal business hours.

Start Your GoHighLevel 30-Day Free Trial →

Do not assume every WhatsApp conversation should be automated.

A useful system might route:

Routine FAQ → AI

Basic Qualification → AI

Booking → AI/Automation

Complex Problem → Human

Complaint → Human

Sensitive Request → Human

The objective is not:

AI Answers Everything

It is:

AI Handles Appropriate Repetitive Work → Humans Handle Judgment and Exceptions

HighLevel also supports Snippets for WhatsApp communication.

Snippets are reusable blocks of content that can help employees respond more consistently during active conversations.

Examples might include:

Snippets and WhatsApp Templates are not the same thing.

Snippet → Reusable content for supported active conversations

WhatsApp Template → Meta-approved message structure used according to WhatsApp messaging rules

Understanding this difference prevents operational confusion.

Current HighLevel functionality also provides improved template handling.

Users can preview WhatsApp Templates before sending them and see information such as:

Supported template media can also be replaced during appropriate sending flows.

This is useful for businesses that maintain multiple templates across different campaigns and languages.

HighLevel supports sending approved WhatsApp Templates through supported bulk-action workflows.

This can be useful for legitimate communication such as:

Bulk capability should not be treated as permission to message arbitrary contact lists.

The business remains responsible for appropriate consent, messaging policies, template rules, and applicable law.

WhatsApp is a highly personal communication channel.

A business should not automatically copy its entire email-marketing strategy into WhatsApp.

For example:

5 Promotional Emails per Week

does not mean:

5 WhatsApp Promotions per Week

is appropriate.

Message based on:

Permission + Relevance + Timing + Customer Expectation

A smaller number of useful messages can create a better customer experience.

HighLevel provides channel-specific Do Not Disturb controls for WhatsApp.

Businesses should use communication-preference controls to respect contacts who no longer want WhatsApp messages.

A good automation system includes:

Send

and:

Know When Not to Send

Ignoring opt-outs can damage trust and create compliance problems.

Businesses should maintain appropriate evidence of consent where required.

For example, a form may include a clear WhatsApp communication option explaining what the person is agreeing to receive.

Avoid:

Consent should match the type of communication being sent.

HighLevel's WhatsApp Settings also includes support for WhatsApp Flows.

WhatsApp Flows can create more interactive experiences within the messaging environment.

Instead of only:

Message → Reply

a supported Flow can provide a more structured interaction.

Potential use cases can include:

This expands WhatsApp beyond ordinary text messaging.

WhatsApp can be particularly useful where customers already prefer the channel.

A local service journey might look like:

Website → WhatsApp → Question → Qualification → Appointment → Reminder

The CRM retains the customer context while WhatsApp provides the communication interface.

Agencies can manage WhatsApp as part of a broader client technology stack.

For example:

Client Sub-Account

├── CRM

├── WhatsApp

├── Workflows

├── Calendars

├── Pipeline

└── Reporting

The agency can design the process around the client's actual customer journey rather than deploying WhatsApp as an isolated messaging tool.

An ecommerce business might use WhatsApp for appropriate:

The distinction between Marketing and Utility templates becomes particularly important because category and destination affect messaging costs.

Appointment-based businesses can use WhatsApp around:

Inquiry → Booking → Reminder → Follow-Up

Examples include:

The channel is most valuable when customers actually prefer using WhatsApp.

HighLevel provides WhatsApp billing and rebilling functionality for agencies.

This means agencies can potentially make WhatsApp part of a client service offering.

The economics can involve:

Meta/Underlying Message Cost → HighLevel/LeadConnector Billing → Client Charge

Eligible agency configurations can apply supported rebilling or markup structures depending on the HighLevel plan and current feature rules.

Agencies should understand actual message costs before setting client pricing.

A workflow that sends ten messages per day has different economics from one sending tens of thousands.

Before scaling, estimate:

Contacts × Messages per Contact × Category × Destination Rate

Then monitor actual billing.

AI and automation can make messaging extremely easy to scale.

That makes cost controls more important, not less important.

WhatsApp business messaging is not only about cost.

Meta also considers quality and messaging behavior.

Businesses should monitor relevant account status and avoid practices that create poor customer reactions.

A campaign producing high blocks or negative feedback is not successful merely because messages were delivered.

Optimize for useful customer interaction.

Do not create a new WhatsApp setup when Coexistence or BSP migration better matches the existing environment.

With eligible Coexistence setups, the WhatsApp Business App can continue operating alongside CRM.

Free-form messaging depends on the customer service window.

Use appropriate approved templates when the customer service window is closed.

Marketing content should not be disguised as utility communication.

October 2026 introduced important changes to service and utility message pricing.

A technically functional workflow can still create a poor or non-compliant customer experience.

WhatsApp should not become another spam channel.

AI and automation need clear handoff paths.

Before launch, test:

Inbound → CRM → Reply → Workflow → Template → Contact → Conversation

Do not test only one side of the connection.

Before using WhatsApp in production, verify:

A connected number is only the beginning.

The complete customer journey should work correctly.

Yes. HighLevel integrates with WhatsApp Business through its supported LeadConnector and Meta onboarding infrastructure, allowing WhatsApp communication to work with CRM contacts, Conversations, workflows, templates, and other supported features.

Yes, if the number is eligible for the appropriate onboarding method. Coexistence is designed specifically for businesses that want to connect an existing WhatsApp Business App while continuing to use it.

Yes, with Coexistence. The same eligible number can send and receive messages through both the WhatsApp Business App and HighLevel CRM.

Coexistence currently supports syncing up to six months of WhatsApp chat history into the CRM.

Not currently. HighLevel's current Coexistence documentation limits this setup to one phone number.

No. Under the current Coexistence implementation, approved template messages are sent through CRM rather than the WhatsApp Business App.

It is the messaging window opened by a customer's WhatsApp message. During the active window, supported free-form replies can be sent; once it closes, an appropriate approved template is generally required to restart business-initiated messaging.

Not generally. WhatsApp primarily uses per-message pricing, with rates depending on message category and destination. From October 1, 2026, service messages also became billable after the first 1,000 service messages per phone number each month.

No longer. From October 1, 2026, utility messages are charged per delivered message even when sent inside an active customer service window.

Yes. HighLevel Workflows include WhatsApp actions and a Customer Service Window Check that can help route messaging based on whether the 24-hour window is open.

Yes, using an appropriate approved WhatsApp Template according to current WhatsApp rules.

Yes, for supported configurations. Conversation AI can participate in WhatsApp customer interactions for use cases such as FAQs, qualification, information collection, and appointment-related conversations.

Yes, eligible HighLevel agencies can use supported WhatsApp rebilling capabilities. Exact options depend on the agency plan and current billing configuration.

Not necessarily. Coexistence can allow an eligible existing WhatsApp Business App number to continue operating while connected to HighLevel.

Yes. HighLevel provides a supported BSP migration path through Meta's Embedded Signup process, subject to current eligibility and migration requirements.

No. WhatsApp is most valuable when the target customers already use and prefer the channel. Businesses should evaluate audience behavior, consent, messaging costs, operational requirements, and customer expectations before adding it.

Go High Level and WhatsApp Business become most useful when WhatsApp is treated as part of the customer journey rather than as an isolated messaging application.

The integration can create:

WhatsApp → Conversations → CRM → Workflow → Opportunity → Calendar → Customer

Coexistence makes that architecture particularly attractive for established businesses because an eligible existing WhatsApp Business App can remain active while the same number becomes available inside CRM.

HighLevel then adds another layer through:

Templates + Workflows + Customer Service Window Checks + Conversation AI + CRM Data + Agency Rebilling

But successful implementation requires more than connecting a phone number.

Businesses need to understand:

Consent + 24-Hour Window + Template Categories + Message Pricing + Automation + DND + Human Escalation

The October 2026 pricing changes make cost management especially important. Service messaging is no longer universally free, and utility messages inside the customer service window are now billable.

Build the WhatsApp system around useful customer communication first.

Then use HighLevel automation and AI to make that communication faster, more organized, and more scalable.

Start Your GoHighLevel 30-Day Free Trial →