Skip to main content

Outbound session selection

When a sub-account has more than one WhatsApp session (number), WhatGHL must decide which session sends each outbound message from GoHighLevel. You control that with session priority, routing rules on the sub-account, and optional #WH / #WHN codes in the GHL message body.

Where to configure​

  1. Sub Accounts → open the sub-account → Connection tab.
  2. Configure outbound session selection (rule list, reorder, enable/disable steps as the UI allows).
  3. Set session priority on each WhatsApp number under WhatsApp Numbers when you use priority-based routing.

Exact labels match the live app; the goal is: define order and fallbacks so automation and humans know which line is “first” for a given send.

Using #WH in the composer​

Including #WH (or a priority variant like #WH2) in the outbound text tells WhatGHL to prefer a specific session or priority for that message. The worker strips the token from what is sent to WhatsApp.

Full syntax, edge cases, and other codes are documented in Message codes from GoHighLevel.

Good practices​

  • Keep at least one reliable fallback in the rule list so messages are not stuck if one session is down.
  • Match priority numbers to what your team documents in SOPs (#WH1 = sales line, etc.).
  • After changing rules, test with a low-risk outbound before large campaigns.