Chatbots with buttons and menus: guiding the customer step by step

Ask a customer to type 'what time do you open?' and half of them will write it with typos, abbreviations, or three different ways your system doesn't recognize. But show them a button that says 'See hours' and all they have to do is tap it. That's the idea behind chatbots with buttons and menus: instead of guessing what the customer types, you hand them clear options to pick from.

WhatsApp offers these tools natively, with nothing for the customer to install. They're called interactive messages, and they're the difference between a conversation that flows and one that stalls. Let's look at how they work and when to use them.

Reply buttons for quick decisions

Reply buttons are the simplest option. According to Meta's developer documentation, you can show up to three buttons per message, and each button allows a maximum of 20 characters of text. The customer taps one and the system knows exactly what they chose.

They're perfect for yes-or-no questions, or three-way forks. 'Want to book, reschedule, or cancel?' with three buttons solves in one tap what free text would take several back-and-forth messages to do.

• Maximum 3 buttons per message, up to 20 characters each.
• Ideal for confirming, choosing among a few options, or moving to the next step.
• The system captures which button was tapped, so there's no ambiguity.

List menus for more options

When three buttons aren't enough, list messages step in. Meta's documentation states that a list can show up to 10 options, organized into sections (up to 10 sections). The customer taps a button, a menu drops down, and they choose from there.

This is ideal for service catalogs. A barbershop can list 'Cut,' 'Cut and beard,' 'Color,' 'Kids'; a clinic can list its specialties. Each list option has a title of up to 24 characters and a description of up to 72 characters, enough to clarify price or duration.

Every time you replace an open question with a button, you take a hard decision off the customer and hand them an easy one.

Fewer errors, less drop-off

The real value of buttons isn't looks, it's the funnel. Every time the customer has to type, there's a chance they'll make a mistake, hesitate, or get distracted and not finish. A menu removes that friction: the option is already there, just tap it.

It also standardizes the answers. If your system expects the customer to say 'haircut' but they type 'I want my hair cut,' a basic bot gets lost. With a button, the answer always arrives in the format your system understands.

Design the menu as a tree, not a maze

The most common mistake is stuffing too many options into one level. A good menu works like a tree: a few big branches that open into smaller ones. First 'What do you need?' with three buttons, and based on the answer, a more specific list.

• Start wide and simple: at most 3 buttons on the first screen.
• Group list options into named sections when there are many.
• Always leave an exit: a 'Talk to a person' button for when the menu doesn't fit.
• Use button text that names a clear action: 'Book appointment,' not 'Option 1.'

When a button isn't enough

Buttons are great for guiding, but not for everything. There are moments when the customer needs to explain something in their own words: a specific question, an unexpected change, a complaint. Forcing everything through menus frustrates people. The best design mixes menus for the routine and free conversation for the rest.

This is where an assistant like Lidia helps: it uses buttons and lists to route the common stuff (book, reschedule, see services) and understands free text when the customer goes off script. The customer doesn't notice the difference, they just feel well taken care of.

Takeaway

WhatsApp buttons and menus turn an open conversation into a guided path: up to 3 buttons for quick decisions, up to 10 options in a list for catalogs. They cut errors, speed up replies, and make booking a matter of taps, not typing. Design your menu as a clear tree, always leave an exit to a person, and save free conversation for what truly needs it.

Sources

• Meta for Developers — Sending Interactive Messages — https://developers.facebook.com/docs/whatsapp/guides/interactive-messages/
• Meta for Developers — Interactive reply buttons messages — https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/interactive-reply-buttons-messages
• Meta for Developers — Interactive list messages — https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/interactive-list-messages
• respond.io — How to Set Up WhatsApp Interactive Message — https://respond.io/blog/whatsapp-interactive-message