Real buttons, not a workaround
Interactive buttons cut friction in half — instead of typing "yes" or reading three lines of options, your contact taps once and moves on. The problem is that on the official WhatsApp Business API, sending interactive buttons requires a Meta-approved Business Account and template approval before you can use them.
CenGHL sends real, tappable WhatsApp buttons through the same QR-linked connection you already use for everything else — no Business Account, no template review.
Why this usually doesn't work — and why it does here
Most third-party tools that try to send interactive buttons without the official API hit the same wall: WhatsApp's servers accept the message, mark it as delivered, then quietly drop it before it reaches the recipient's phone. CenGHL's connection includes the specific protocol node WhatsApp's servers look for before forwarding an interactive message — so the button message actually arrives, and it arrives as real, tappable buttons, not a screenshot or a workaround.
Five button types, one message
- Quick reply — tapping it sends a reply automatically, exactly as if the contact had typed it themselves.
- Open a link — opens any URL directly from the message, no need to copy it into a browser.
- Call a number — one tap dials the number you set, useful for "talk to a human" escalations.
- Voice call — starts a WhatsApp voice call to the number, without the contact hunting for it in their contacts.
- Copy a code — copies a discount code, order number, or confirmation code to the clipboard in one tap.
Mix and match these in a single message — a common pattern is one quick-reply button plus a link button underneath it.
Building one — no code required
Open the Builder tab in your CenGHL dashboard. Write your message title and body, add buttons one at a time picking the type you want, and CenGHL generates a snippet. Copy it, paste it into the message field of any GHL workflow action, and every message that workflow sends goes out with those buttons attached.
What happens if a message can't be delivered as buttons
If native delivery ever fails for a given message, CenGHL automatically falls back to a clean, formatted text version instead of dropping the message entirely — bolded title, the body, link/call/copy options listed with icons, and quick-reply options as a numbered list with a "reply with a number" hint. The contact always gets a usable message either way; the fallback just isn't tappable.
Getting started
Interactive buttons are available on every CenGHL plan from day one. Open the Builder tab, put together your first message, and paste it into a workflow — no Meta approval, no waiting.