Interactive WhatsApp: buttons, lists, carousels.

WhatsApp gives you three interactive shapes on top of plain text: quick reply buttons, list messages, and carousel templates. Each one has a job. Each one has a way of feeling wrong.

The design work is figuring out which shape the moment calls for. The engineering work is respecting Meta's rules about what you can put in each shape and what you cannot.

Here is the honest read on each.

Quick reply buttons

Up to three buttons attached to a message. Each button carries a short label, up to 20 characters, and returns the label back to your webhook when tapped. That is it. No URLs, no images, no branching. Just three taps that mean three decisions.

The right use case is the yes or no or maybe question. Confirm your appointment. Reschedule. Cancel. Rate this experience one to three. Anything shaped like a small clean fork in a conversation.

The failure mode is trying to make three buttons do the job of a menu. If the choices need explanation, if the labels do not fit in 20 characters without abbreviation, if you find yourself trying to squeeze in a fourth option, the shape is wrong. Switch to a list.

Conversion on well placed quick replies is high. Numbers vary by vertical, but tap rates on a well framed three button question routinely clear 40 percent. Compare that to the click through on a link in a text message, which typically sits under 10.

List messages

A menu style component. A single button opens a sheet with sections and rows, up to 10 rows total, grouped into sections with headers. Each row has a title and an optional description, and returns a row ID to your webhook.

This is the shape for a real menu. Browse products by category. Pick your delivery slot. Choose the department you want to reach. Anything with enough options that three buttons would misrepresent the choice.

The trap is making the list feel like an IVR menu. Two things kill the experience: bloated section headers written in marketing copy, and row descriptions that repeat the row title. The customer opens the sheet, sees noise, closes it. Write section headers as short category labels. Write row descriptions only when the description adds information the title cannot carry.

Meta enforces a hard limit of 24 characters on the row title and 72 on the description. Both truncate on the small screen well before their limits. Aim for 18 and 50 respectively and you will avoid the awkward middle case where the text almost fits.

Carousel templates

Meta added carousel support in 2024. A single template can carry up to 10 cards, each with a media header, a body text block, and up to two buttons per card. The customer swipes horizontally to browse.

Carousels are the right shape when the choice is between several concrete items and each item has an image that matters. Product recommendations. Property listings. Restaurant menu items. The customer is choosing between things they need to see.

Carousels are the wrong shape when the choice is between abstractions or when the image is decorative. A carousel of "our services" is a carousel where every card looks the same and no one swipes past the first. A carousel that requires the customer to swipe five times to reach the option you actually want them to choose is a carousel that will underperform a simple list.

The image aspect ratio Meta enforces is 1.91 to 1 or 1 to 1. Both work. Mixing them inside the same carousel is not supported. Your creative pipeline needs to pick one and hold it.

The label discipline that makes all three work

Every rule above collapses into one habit: write the labels as if you were the customer reading them for the first time. Not as if you were the marketer writing them for a spec.

The tap rate on an interactive component follows the clarity of the label. A button that says "Yes, I'll be there" outperforms a button that says "Confirm attendance" every time, in every vertical we have looked at. The reason is not clever. It is that the first one reads like something the customer would think. The second one reads like something the system would say.

Meta reviews template copy. They enforce the character limits and the aspect ratios. They do not enforce clarity. The gap between a component that meets Meta's rules and a component that actually converts is exactly the length of the label.

“The rules are Meta's floor. The label is where the conversion lives.”