How to Set Up WhatsApp in a GoHighLevel Sub-Account

What you need before connecting WhatsApp

Prepare the business assets before opening the GoHighLevel integration screen. This prevents the most common setup problem: starting the connection before the phone number, business access, or provider account is ready.

• An active GoHighLevel account with access to the target sub-account.
• Administrative access to the relevant Meta Business account and WhatsApp Business assets.
• A business phone number that can receive an SMS or voice verification code.
• A decision about whether the number will be used exclusively for the WhatsApp Business Platform or remains attached to another WhatsApp product.
• Access to the WhatsApp provider used by your GoHighLevel configuration, such as 360dialog where that option is available.
• A defined owner for incoming conversations, failed messages, template maintenance, and consent records.

Step 1: Open the correct GoHighLevel sub-account

Log in to GoHighLevel and select the sub-account that should own the WhatsApp connection. Do not assume that a connection made at the agency level will automatically be available in every sub-account. Confirm the account name and permissions before making changes.

1. Open the intended GoHighLevel sub-account.
2. Go to Settings.
3. Look for WhatsApp, WhatsApp API, or a similar communications integration area.
4. Confirm that the page refers to the current sub-account, not another location in the agency.

If the WhatsApp option is missing, check user permissions, account availability, and the current GoHighLevel interface. Do not treat a missing menu as proof that the integration is unavailable. It may indicate an access or configuration issue.

Step 2: Connect the WhatsApp provider

GoHighLevel may use a supported WhatsApp Business API provider to establish the connection. In the original setup sequence described here, that provider is 360dialog. The exact onboarding screens can change, but the underlying relationship remains the same: the provider connects the WhatsApp Business assets, while GoHighLevel uses the connection for conversations and workflow actions.

1. From the WhatsApp settings area, select Connect, Add WhatsApp Account, or the equivalent option.
2. Sign in to an existing provider account or begin provider registration.
3. Authorize access to the relevant Meta Business and WhatsApp Business assets.
4. Select the WhatsApp Business Account and phone number intended for this sub-account.
5. Review the destination sub-account before confirming the connection.

Keep a record of which business, WhatsApp Business Account, number, provider account, and GoHighLevel sub-account are linked. These entities are related but are not interchangeable. A valid provider login does not prove that the correct sender is connected to the correct CRM location.

Step 3: Verify the business phone number

Enter the phone number that will send and receive WhatsApp messages through the business platform. Use the international format requested by the onboarding screen and make sure the number can receive the selected verification method.

1. Enter the number in the provider onboarding flow.
2. Choose SMS or voice verification if both options are offered.
3. Retrieve the verification code from the number.
4. Enter the code and complete registration.
5. Confirm that the number is associated with the intended WhatsApp Business Account.

A number that is already registered in a WhatsApp mobile or WhatsApp Business application may need to be released, migrated, or handled according to the provider’s current process. Do not remove a live number without checking what will happen to existing conversations and customer expectations.

Step 4: Confirm business identity and display name

Review the business information and display name shown during onboarding. The display name should represent the business that customers expect to contact. Submit accurate information and monitor any pending review in the relevant Meta or provider interface.

Approval status can affect when the sender is fully usable. A number may be verified while another business or display-name review remains pending. Record the status of each part separately instead of treating all setup stages as one approval.

Step 5: Check the connection in GoHighLevel

Return to the target GoHighLevel sub-account after provider onboarding. Open the WhatsApp settings area and inspect the connection status, phone number, and account details.

• The status should indicate an active or connected state rather than pending or failed.
• The displayed phone number should match the number you verified.
• The connection should belong to the intended sub-account.
• The available channel should be selectable in the conversation and workflow areas.

If the status has not updated, refresh the page and allow time for the provider connection to synchronize. If it remains pending, compare the provider account, WhatsApp Business Account, number, and permissions before reconnecting repeatedly.

Make WhatsApp usable in conversations and workflows

Once the channel is connected, test it in a controlled way before adding it to every automation. Use a test contact and verify both directions: a message leaves GoHighLevel, and a reply returns to the expected conversation record.

Test the conversation path

1. Open Conversations in the correct sub-account.
2. Find a test contact with a valid WhatsApp number and appropriate consent.
3. Select WhatsApp as the sending channel when available.
4. Send a short test message.
5. Reply from the recipient side and confirm that the response appears in the correct thread.
6. Confirm that the responsible user or team can see and act on the reply.

This test checks more than delivery. It also checks contact matching, conversation visibility, reply ownership, and whether the team knows where a response requires action.

Test a workflow path

After the conversation test succeeds, open Automation and Workflows. Add a WhatsApp action only after the trigger, audience, consent condition, message type, and follow-up owner are clear.

1. Choose a narrow test trigger, such as a test appointment or controlled pipeline change.
2. Select the connected WhatsApp sender.
3. Use the required approved template or message format.
4. Define what happens if the message fails, the contact replies, or no reply arrives.
5. Run the workflow with a test record before activating it for live contacts.

Automation should represent a known business decision, not simply an opportunity to send another message. If the team cannot explain what a recipient should do next, the workflow is not ready.

Templates, consent, and message quality

WhatsApp messaging can have different requirements depending on the message purpose, conversation context, and current platform rules. Marketing and notification messages may require approved templates, while other message types may be subject to conversation-window or consent conditions. Check the current requirements in the provider and platform interfaces before publishing a workflow.

Keep templates specific and operationally useful. A good template should identify the business context, explain the next step, and make it clear how the recipient can respond or obtain help. Store the purpose and owner of each template so outdated messages can be removed rather than reused indefinitely.

Common setup problems and diagnostic questions

When WhatsApp does not work as expected, check the relationship between systems rather than changing random settings.

• Number cannot be verified: Can the number receive the chosen code, and is it still attached to another WhatsApp product?
• Connection is pending: Has the provider completed onboarding, and are the business and display-name reviews finished?
• Wrong sender appears: Is the selected phone number connected to the intended WhatsApp Business Account and sub-account?
• Messages are unavailable in workflows: Is the channel active, is the sender selectable, and is the message using the required format?
• Replies are missed: Does the incoming conversation have a visible owner, notification path, and follow-up status?
• Contacts receive duplicate messages: Are multiple workflows or channels responding to the same business event?

Use the connection as part of a CRM operating model

WhatsApp is most useful when it fits an existing customer process. Decide which business states justify a message, which system holds the source of truth, and who owns the next action. A CRM stage should represent a meaningful business state, not simply the fact that a WhatsApp message was sent.

For example, a hypothetical service business might send a WhatsApp confirmation after an appointment is genuinely booked. If the customer replies with a change request, the conversation should create a clear task or status change for the responsible team. The important design is not the message itself. It is the handoff from appointment status to customer response to owned resolution.

Review the wider pipeline, contact fields, permissions, and integrations as part of the implementation. ConsultEvo’s CRM consulting service covers CRM architecture, lead management, automation, and integrations that can support this type of channel design. For broader system planning, the systems and automation services page provides a wider view of implementation work.

Final verification before going live

Before activating a live workflow, test the full path from business event to message delivery and response handling. Check the contact record, sender identity, template, timing, conversation visibility, and assigned owner. Then document what the team should do when delivery fails, a customer opts out, or a reply falls outside the expected process.

Once the technical connection and operating rules are both clear, WhatsApp can become a dependable GoHighLevel channel rather than an isolated integration. Keep the setup record current whenever the number, provider, templates, workflows, or ownership changes.