WhatsApp Buttons and List Messages: Which Interactive Type to Use

This guide is for product, CX and marketing teams designing WhatsApp journeys who want customers to tap rather than type. You will learn which interactive message type fits each job, the limits Meta sets, the design patterns that keep conversations short, and the mistakes that make buttons frustrating.

What are WhatsApp interactive messages?

Interactive messages are structured session messages that let customers respond with a tap: a button, a menu row, a link or a product. They reduce typing errors, make replies machine-readable and shorten conversations.

They differ from templates in one important way. Interactive messages do not require pre-approval, but they are free-form session messages, so they can only be sent inside the 24-hour customer service window that opens when a customer messages you. To start a conversation, or to reply after the window closes, you send an approved template, which can carry its own buttons. See template categories and approval.

Which interactive message type should you use?

Choose by the number of options and the action you want. The table summarises Meta's limits as published in its developer reference at the time of writing.

Meta also offers other types, such as location requests and WhatsApp Flows for multi-screen forms. They are outside the scope of this guide but follow the same session-window logic.

When should you use reply buttons?

Use reply buttons when the customer has two or three clear choices and you want an answer now. They are the highest-signal format because every option is visible without opening a menu.

Good uses:

• "Confirm appointment" / "Reschedule" / "Talk to us"
• "Yes, deliver tomorrow" / "Choose another day"
• "English" / "العربية" as a language selector at the start of a chat

Keep labels short and verb-led. Twenty characters disappear fast, especially in Arabic, where some words are long; test both languages on a real phone.

When should you use a list message?

Use a list when there are more than three options but no more than ten. The customer taps one button and sees a menu, which keeps the chat tidy.

Group rows into sections when it helps scanning, for example "Dubai" and "Abu Dhabi" branches. Use the 72-character description for the detail that helps someone choose, such as opening hours or "next slot 4 pm". If you have more than ten options, narrow first with a reply button or list, then show a second list.

When should you use a CTA URL button?

Use it when the task is better done on a web page: paying an invoice, tracking a shipment, completing a long form. Meta notes that customers can hesitate to tap long or obscure URLs, and the CTA button maps the link to a clear label instead.

Use your own domain, make the label describe the destination ("Pay invoice", "Track order") and make sure the page is mobile-friendly and loads fast on mobile data.

When should you use carousels and product messages?

Use media carousels to compare a small set of options visually, such as three room types or four plans. Every card must use the same button setup, so design the cards as a set.

Use product messages when you sell from a catalog connected to your WhatsApp account. Meta describes multi-product messages as best for guiding customers to a relevant subset rather than the full catalog, such as re-ordering previous items or showing a category. Because they pull live catalog data, price and stock stay current. Your catalog must be accurate; if none of the items matches your catalog, Meta returns an error and nothing is sent. For a full commerce flow, see WhatsApp for ecommerce.

How do you design good button flows?

Treat each message as one decision. A short checklist:

1. One question per message. Do not ask for a date and a branch in the same step.
2. Always offer an exit. Include "Talk to an agent" or "Something else" so customers are never trapped.
3. Use stable IDs. The webhook returns the ID you set; IDs like branch_jbr survive wording and translation changes.
4. Accept typed replies too. Some customers will type "yes" instead of tapping. Handle common text answers.
5. Handle stale taps. Customers may tap an old button hours later; check that the option is still valid before acting.
6. Mirror language. Send Arabic labels to Arabic speakers; mixed-language buttons look careless.
7. Confirm the outcome. After a tap, reply with what happened: "Booked: Tuesday 10:30, Marina branch."

Worked example: a Jeddah car service centre

A synthetic example. "Corniche Auto" sends an approved utility template the day before a service booking, with quick-reply buttons "Confirm" and "Reschedule".

When a customer taps "Reschedule", the window is open, so the system sends a list message titled "Choose a new slot" with two sections, "Tomorrow" and "This week", holding eight time slots. After the customer picks one, a reply-button message asks for confirmation. When the car is ready, a CTA URL button labelled "Pay invoice" opens the payment page. Every step offers "Talk to an advisor", which routes the chat to a human. Customers rebook in a few taps without typing a date in different formats.

Common mistakes and limits

• Sending interactive messages outside the window. They fail; use a template.
• Too many choices. Ten list rows is a ceiling, not a target.
• Truncated labels. Labels over the character limit fail validation, and near-limit labels can look cramped. Write them for small screens.
• No fallback for old apps or desktop. Write body text that still makes sense if a component does not render as expected.
• Treating buttons as consent. A tap on "Yes, send me offers" is evidence of a choice, but store it with a timestamp as part of your opt-in records.
• Limits change. Meta updates character and item limits; check the reference before launching.

How OmniChannels.ai helps

OmniChannels.ai, powered by BroadNet Technologies, lets teams create WhatsApp templates with variables, media and buttons, check them in a phone preview and track approval. Interactive messages, WhatsApp Flows and catalogs are supported, approved templates can be sent through campaigns with Excel or CSV upload, scheduling and duplicate filtering, and agents can send templates, media and attachments from the Omni Inbox. Arabic and English are supported, and delivery reports with CSV export show how each send performed. The public REST API connects interactive messages to your own systems.