WhatsApp reply buttons are useful, but ecommerce support workflows often need more than three choices. This guide explains how to design better customer journeys using buttons, lists, and custom chatbot menus.
Compare AI ChatBot →
See Guide Contents
These terms are related but not identical. Use this comparison to decide what your team needs.
| Format | Best For | Use When | Typical Ecommerce Examples |
|---|---|---|---|
| 3 Reply button | Speed and simple choices | The customer has only a few clear options | Track order • Return/Exchange • Talk to support |
| List Messages | More menu options in one step | You need a cleaner menu without too many visible buttons | Order status • Complaint status • Delivery policy • Store locations |
| Custom Chatbot Menus | Flexible, multi-step support journeys | You need routing logic, ticketing, order context, or human handoff | Complaint intake • Returns flow • COD exceptions • Support routing |
How can an ecommerce brand give customers more than three useful options on WhatsApp without making the journey confusing?
✓ Use buttons when: the customer has only a few clear choices.
! Limitation: if the journey has more than three common paths, you need list messages or custom menus.
A list lets the customer scan options without forcing every journey into three visible buttons.
But be careful: more options do not always mean better support. The goal is to help the customer reach the right next step quickly.
The bot can guide the customer through multiple steps, collect structured details, create tickets for exceptions, and hand the conversation to an agent with context.
Option selected
Track my order
Bot asks
System checks
Outcome
The bot collects reason and required details, then guides the next step.
The bot checks or routes the case and keeps follow-up accountable.
The system hands over to an agent with context instead of forcing the customer to repeat everything.
Use buttons when the journey is short and choices are clear.
Smart where needed
Use lists and custom menus when the journey needs structure or more options.
Human when necessary
Hand off exceptions with context, create tickets when follow-up must be tracked.
The real goal is not more buttons.
The real goal is better customer support: clear journeys for customers and control for support teams.
Conversations
Customers choose the right journey without typing long messages.
Context
Where configured, order or customer context helps the team answer faster.
Control
Exceptions become tickets, and agents handle cases with context.
Use three buttons for the top actions, list messages for more menu options, or a custom chatbot menu when the journey needs routing, context, ticketing, or handoff.
Use reply buttons when the customer has only a few clear choices, such as Track order, Return/Exchange, or Talk to support.
Use list messages when the customer needs to choose from more options in one step, such as order status, returns, complaints, store locations or delivery policy.
Use a custom menu when the journey needs flexibility, multiple steps, routing logic, order context, ticket creation, or human handoff.
Most teams should use both: interactive menus for structured journeys and AI for natural-language questions, FAQs, and flexible support handling.
A practical starter menu includes Track my order, Return or exchange, Complaint status, Product availability, Delivery policy, Store locations, and Talk to support.