WhatsApp Buttons in GoHighLevel: Quick Replies, CTAs, and List Menus (Full Syntax)

When a contact receives a plain-text message asking them to reply, two things happen. First, they have to interpret the request. Second, they have to act on it in a medium (typing) that most people associate with effort. WhatsApp's own internal UX research has consistently shown that tappable UI elements reduce drop-off at action points.

Buttons solve the interpretation problem too. A button labeled 'Book a Call' carries no ambiguity. A message saying 'Reply BOOK to schedule a call' leaves open the question of whether 'book' needs to be capitalized, whether the system is case-sensitive, and whether the reply will actually trigger something or just vanish.

For agencies managing dozens of client sub-accounts, this compounds. Every percentage point of improvement in a booking confirmation flow, a coupon redemption prompt, or a service intake menu multiplies across every contact every campaign fires at. That is the practical case for using the button syntax rather than text-only instructions.

One honest trade-off: older WhatsApp clients (particularly on budget Android devices running outdated app versions) may not render interactive buttons. The GoGHL documentation recommends including a fallback line such as 'Reply 1, 2, or 3 if buttons do not show' in any high-volume campaign where device diversity is a concern.

Every interactive button message starts with the `#btn` prefix. The full structure is one line of pipe-delimited fields, with sub-fields separated by asterisks inside the button definitions.

Use the literal string `undefined` for any optional parameter you want to skip. Leaving it blank will break formatting.

GoGHL supports four button types. Each serves a different conversion action. Button text labels must stay at or under 20 to 25 characters - longer labels get truncated in the WhatsApp UI.

The `quick_reply` type sends a predefined reply back to the conversation when the contact taps. This is the right choice for yes/no confirmations, NPS responses, or simple intake branches.

The `cta_url` type opens a URL inside WhatsApp's in-app browser. Use it for booking links, lead-magnet downloads, or product pages. The `cta_call` type dials a phone number directly - include the number in full international format starting with the country code.

The `cta_copy` type is the most underused. It copies a value (a coupon code, a referral code, a confirmation number) directly to the contact's clipboard with one tap. No typing, no screenshotting, no 'I lost the code' support tickets.

When a contact needs to choose from more than three options, buttons start to feel cluttered. WhatsApp list messages render as a native expandable dropdown menu, which handles longer option sets cleanly without overwhelming the message body.

The `#list` syntax is similar to buttons but uses a section-and-item hierarchy. Sections group related items; items are the individual selectable options. A slash separates sections; an asterisk separates fields within each section and item.

The same `undefined` rule applies here. Skipping optional fields without the literal `undefined` placeholder will break rendering. Use the Button Builder at builder.goghl.ai to validate complex list structures before deploying them to a live workflow.

The syntax above is enough to write button messages by hand in a workflow action. For agencies building these on behalf of clients, the no-code Button Builder at builder.goghl.ai provides a visual interface that validates structure, escapes special characters, and outputs the ready-to-paste syntax.

Agencies on GoGHL can embed the builder inside their client sub-account portals via Agency Settings → Company → Whitelabel → Custom JS. That means the client sees a branded tool, not an external link, and the agency controls the experience end to end.

This matters for scale. An agency managing 30 sub-accounts cannot QA raw syntax strings across every client's workflows. The builder reduces that audit load significantly. One install of GoGHL covers all sub-accounts, no per-sub-account licensing required.

Recipe 1: Appointment confirmation quick-replies in a workflow. After a lead fills a form, a GHL workflow sends a button message with two quick_reply options - 'Confirm My Spot' and 'Reschedule'. The reply ID triggers the relevant branch: one branch sends a calendar link, the other fires a date-picker message. No human needed until the call itself.

Recipe 2: Coupon-copy promo broadcast. A bulk campaign to an existing customer segment sends a `cta_copy` button with a discount code. The contact taps once and the code is on their clipboard. Pair this with smart drip mode to pace the broadcast at roughly 15 seconds per message so the volume does not spike the account's risk score.

Recipe 3: Service-menu list for intake. A new inbound contact gets an automated list message with a `#list` structure grouping your agency's core service areas - 'SEO & Content', 'Paid Media', 'Web Design' - each with two or three sub-items. The ItemId from the contact's selection flows into a custom field, routing them to the right onboarding sequence without a manual qualification call. For more advanced routing logic using external data, see n8n + GoHighLevel automations agencies bill for.

All three recipes work in the same unified inbox as your SMS and iMessage conversations - no tab-switching between channels.