Interactive WhatsApp messages
Interactive outbound messages let contacts tap buttons, vote in polls, confirm events, pick list rows, or receive contact cards. In WhatGHL they are driven by structured tokens you (or automation) put in the GoHighLevel message body. The worker parses those tokens, talks to WhatsApp, and strips or normalizes text so the end user sees a clean experience.
What you can build
| Pattern | Typical use |
|---|---|
| Polls | Quick choices (“support / sales / billing”). |
| Events | Appointment proposals with confirm / decline. |
| Buttons | Up to three quick-reply style answers. |
| Lists | Menus with sections and rows. |
| Contact cards | Share a name and phone as a vCard-style message. |
Exact grammar (#POLL|…, #EVENT|…, #BUTTONS|…, #LIST|…, #CONTACT|…) is specified in the message codes reference — this page is the feature overview.
Where configuration matters
- Sub-account must have a working WhatsApp session and permissions to send the payload type.
- Routing (
#WH, session priority) decides which line sends the interactive message — see Outbound session routing. - Translation runs in a defined order relative to hashtags; interactive payloads must remain valid after processing — see Translation & AI and the codes doc.
Good practices
- Prototype new formats in a test sub-account or low-traffic number.
- Keep copy short; long button or list labels may truncate on devices.
- For video note behaviour tied to
#CIRCLE, read the dedicated section in Message codes from GoHighLevel.
Related
- Message codes from GoHighLevel — full syntax and examples.
- Voice (TTS) — TTS cannot share the same outbound with most interactive payloads.