Skip to main content

Sessions

Open Sub Accounts → select a location → Sessions tab.

After onboarding, one of the first operational tasks is creating a WhatsApp session and linking it with QR.

What a session is​

A session is a WhatsApp number connected to a sub-account (a GHL location). Think of it as the “phone line” that WhatGHL uses for that location.

  • Inbound: messages that arrive on that WhatsApp number are received by WhatGHL and can appear in GoHighLevel.
  • Outbound: automations, workflows, and manual replies from GHL are sent through an active session.
  • One sub-account, several sessions: you can link more than one WhatsApp number to the same location (for example sales and support). Each number is a separate session.

Without at least one active session, that sub-account cannot send or receive WhatsApp through WhatGHL.

Typical flow​

  1. Open Sub Accounts and select the location.
  2. In the sub-account detail, open the Sessions tab.
  3. Click Add session, give the session a clear name, and confirm creation.
  4. Open the QR code shown on screen.
  5. On the phone with that WhatsApp number, go to Settings → Linked devices (or WhatsApp Web) and scan the QR.
  6. Wait until the session status in WhatGHL shows as active or connected.

The first session of a sub-account usually includes a 5-day free period so you can validate the setup before full billing. Your organization may adjust trial policies — always check what the UI shows for that sub-account.

Video walkthrough​

Create a new WhatsApp session for a sub-account and link it by scanning the QR code.

QR management tips​

  • Expired QR: codes are time-limited. If it expires before you scan, use refresh or regenerate on the same screen and scan the new code.
  • Stable connection: use reliable Wi‑Fi or mobile data on the phone while scanning; a weak connection often causes failed pairing.
  • Correct number: scan with the phone that owns the WhatsApp account you want to link — not another line on the same device unless that is intentional.
  • Do not duplicate: if a session is reconnecting, wait before creating another session for the same number; duplicates can confuse routing and billing.
  • Keep the phone online: the linked device should stay connected to the internet so the session remains healthy.

Linked session screen​

Once WhatsApp is linked, each session appears as a card on the Sessions tab (name, phone number, creation date, and action buttons). The screenshot below shows a session already connected. Match each colored marker in the legend with the same color on the image:

WhatsApp session tab with priority, team assignment, and sync options

Session priority. Each sub-account can have up to 5 paid sessions (five different WhatsApp numbers). The number you see here — for example Priority: 1 — tells WhatGHL which line comes first when the system must choose among several connected numbers (automations, campaigns, or messages without a specific routing code). Priority 1 is usually the main line; 2, 3, and so on are secondary lines in order. Click the pencil (edit) icon next to the priority to change it when your agency reorganizes lines (for example moving support from priority 2 to 1). If you use codes like #WH2 in GHL, they refer to these same priority numbers — see Connection for routing details.
Assigned team member. The Select assigned user dropdown links this WhatsApp session to a person on the GHL team for that location. Use it when you want outbound traffic or internal logic to associate this number with a specific user (for example “this line belongs to María from sales”). You can leave it unassigned if the number is shared by the whole team. This does not replace GHL user permissions — it helps WhatGHL know which session corresponds to which team member when rules or workflows depend on assignment.
Sync contacts. The Sync Contacts switch controls whether contacts saved on the linked WhatsApp are copied into GoHighLevel for this location. When it is on, new or updated contacts on the phone can appear in GHL so your CRM stays aligned with WhatsApp. When it is off, WhatGHL does not push those address-book changes into GHL. Turn it on if your workflow depends on GHL having the same contact list as the WhatsApp account; leave it off if you manage contacts only inside GHL or want to avoid automatic imports.
Sync labels. The Sync Labels switch does the same idea for labels (tags) used in WhatsApp: when it is on, labels applied in WhatsApp can be reflected in GoHighLevel so segments and automations in GHL can use the same classification. When it is off, label changes on WhatsApp are not synced automatically. Enable it if your team tags conversations in WhatsApp and wants those tags visible in GHL; disable it if you prefer to manage tags only in GHL to avoid duplicates or naming conflicts.
  • Connection — outbound routing uses session priority from this tab.
  • Onboarding — agency linking before first session.