GoHighLevel WhatsApp Setup: A Practical Step-by-Step Guide

What you need before connecting WhatsApp to GoHighLevel

Prepare the business assets and access rights before opening the integration wizard. This reduces the chance of creating a WhatsApp Business Account under the wrong business or verifying a number that another system still controls.

• Access to the correct Meta Business Manager with sufficient administrative permissions.
• A WhatsApp Business Account, either already available or ready to be created during the Meta onboarding flow.
• Access to the business phone number that will receive an SMS or voice verification code.
• Agency-level GoHighLevel access if you are configuring the channel for multiple client sub-accounts.
• A test contact and a real device that can send and receive WhatsApp messages.
• A basic plan for who owns conversations, templates, escalations and opt-out handling.

Understand the WhatsApp and GoHighLevel structure

Several terms are easy to confuse during setup. Meta Business Manager is the business container that controls access to business assets. The WhatsApp Business Account, often called a WABA, holds WhatsApp business information, phone numbers and message templates. The phone number is the sending identity that customers see.

GoHighLevel provides the CRM and workflow layer where conversations, contacts, users and automations are managed. An agency account may then make the channel available to one or more sub-accounts. The exact permissions and allocation options depend on the current GoHighLevel and Meta configuration.

Operational observation: A connected channel is not the same as a usable workflow. It becomes operational only when ownership, routing, message rules and testing are clear.

Step 1: Open the WhatsApp integration in GoHighLevel

Start from the GoHighLevel agency area when the number will be shared across client sub-accounts. If the number is intended for only one business, confirm whether the current account structure requires agency-level setup or direct sub-account configuration.

1. Sign in with an account that has the required agency or sub-account permissions.
2. Open the integrations, settings or marketplace area where WhatsApp is offered.
3. Choose the WhatsApp connection option and launch the setup flow.
4. Record which agency or sub-account you are configuring before continuing.

Do not begin by creating a workflow. First establish the ownership and account level of the channel. A workflow built against the wrong sub-account can create confusing tests and duplicate configuration work.

Step 2: Authorize the correct Meta business

The setup flow will normally ask you to continue with Facebook or Meta. Sign in using the profile that can administer the intended Meta Business Manager. Select the business that should own the WhatsApp assets, not simply the first business displayed in the picker.

1. Continue to Meta from the GoHighLevel setup window.
2. Review the business and asset selections presented by Meta.
3. Choose the correct Meta Business Manager.
4. Allow the permissions required by the connection.
5. Return to GoHighLevel and confirm that the authorization completed.

Restricting a required permission can produce a partial connection. The initial screen may look successful while template synchronization, number management or message delivery remains unavailable.

Step 3: Create or select the WhatsApp Business Account

After authorization, Meta may let you select an existing WABA or create a new one. Select an existing account only when its business identity, phone number ownership and intended use are understood.

1. Choose the existing WABA or start the creation process.
2. Enter or confirm the business display information requested by Meta.
3. Check that the business details are consistent with the selected Meta business.
4. Accept the applicable WhatsApp Business terms and continue through any verification prompts.

Avoid creating multiple WABAs simply because the first selection is unclear. Duplicate accounts make ownership, templates and future administration harder to manage. If Meta requests additional verification, complete that process before treating the connection as ready.

Decision rule: If you cannot answer who owns the WABA and which phone number belongs to it, stop the setup and resolve ownership before adding automations.

Step 4: Add and verify the WhatsApp phone number

Add the phone number that customers should use to contact the business. Enter it in the correct country format and choose the available verification method. The number must be able to receive the code through SMS or voice call.

1. Choose the option to add a phone number.
2. Select the country and enter the complete business number.
3. Choose SMS or voice verification when prompted.
4. Enter the code received on the number.
5. Confirm that Meta shows the number as verified and associated with the intended WABA.

Before verification, check whether the number is already connected to another WhatsApp product or provider. Existing registration can affect eligibility or require a separate migration or removal process. Do not assume that a number can be connected to multiple systems at the same time.

Use a number that the business can retain. Changing the number later can affect customer recognition, templates, routing, contact records and published communication instructions.

Step 5: Finish the GoHighLevel connection

When Meta has completed the WABA and number steps, return to GoHighLevel. Select the verified number and save the association with the intended agency or sub-account.

1. Return to the GoHighLevel WhatsApp integration area.
2. Select the verified phone number shown by the connection flow.
3. Confirm the agency or sub-account association.
4. Save the configuration and wait for the channel to finish synchronizing.
5. Refresh the account and check that the channel is available for conversations and workflows.

If the number does not appear, check the Meta business selection, WABA ownership, verification status and granted permissions before repeating the setup. Repeating the wizard without correcting the underlying asset relationship rarely solves the problem.

Step 6: Assign WhatsApp to the correct sub-account

Agency users often need to make the connected number available to a particular client or business unit. Treat this as an allocation decision, not a routine toggle. The number should be assigned where the contacts, users, inbox and workflows are maintained.

1. Open the agency account and locate the relevant sub-account.
2. Open its settings, phone numbers or messaging configuration.
3. Choose the connected WhatsApp number.
4. Save the assignment and confirm that permitted users can access conversations.
5. Repeat only for sub-accounts that are genuinely meant to use the number.

Do not share one number across unrelated businesses merely because the platform allows a broad agency configuration. Customers need a clear business identity, and internal teams need unambiguous conversation ownership.

For broader pipeline, routing and ownership design, see ConsultEvo CRM Consulting. The important question is not only whether WhatsApp is connected, but whether every incoming conversation has a defined destination and owner.

Step 7: Configure WhatsApp message templates

Business-initiated WhatsApp messages generally require approved templates, particularly when the business is starting or resuming a conversation outside the permitted customer service window. Template approval and category rules are controlled by Meta and can change, so review the current requirements shown in your account.

1. Open the WhatsApp template area in the relevant GoHighLevel or Meta configuration.
2. Review templates that have synchronized successfully.
3. Create a template with the correct language, category and variables.
4. Write the message for a specific business purpose, such as appointment confirmation or service update.
5. Submit it for review and wait for approval before using it in automation.

Templates should describe a meaningful communication event, not act as a generic substitute for every possible conversation. Keep variable names and fallback values understandable so a workflow cannot send an incomplete message.

Operational observation: A message template is part of a process. It should have a trigger, an intended recipient, an owner for replies and a clear next action.

Step 8: Test the complete conversation path

A successful test checks more than outbound delivery. It should confirm that the message reaches the intended device, the reply returns to GoHighLevel, the correct contact is matched and the responsible user can act on the conversation.

Use a simple test first. A hypothetical appointment reminder test might confirm the template, delivery and reply routing without also triggering lead scoring, payment messages and multiple follow-up workflows.

Common setup problems and how to diagnose them

The number is missing

Check that the number was verified under the intended WABA, that the correct Meta business was selected and that the GoHighLevel authorization still has the required permissions.

Messages fail to send

Check number assignment, contact formatting, template approval and the type of message being sent. A workflow may also be triggering before its required contact data is available.

Replies do not appear in the CRM

Check the inbound channel, contact matching and sub-account assignment. If the message reaches the phone but not the CRM, the problem is likely in the connection or routing layer rather than the message copy.

The workflow sends the wrong message

Review the trigger, conditions, template variables and ownership rule. Automation should follow a known business state, such as an appointment being confirmed, rather than a vague event such as a contact existing in the database.

For connected systems and workflow automation beyond the initial WhatsApp setup, you can review ConsultEvo systems and automation services. A process-first review is often more useful than adding another integration before the current routing logic is understood.

Keep the integration maintainable after launch

Document the Meta business, WABA, phone number, GoHighLevel account, responsible administrators and approved templates. Store the procedure where the team can update it when platform screens or internal ownership change.

Review failed messages and unassigned conversations as operational signals. If reporting shows delivery but no completed follow-up, the issue may be a handoff or ownership gap rather than a technical integration failure.

More tools do not automatically create a better communication system. Once the basic connection works, improve the workflow in this order: clarify the business state, define the owner, create the smallest useful automation, test the exception path and then add reporting that supports a decision.

ConsultEvoClient Work: Automation, CRM and Operations SystemsExamples of connected systems designed around operational problems, workflow clarity and usable business data.→