What are interactive messages

Interactive messages are a type of WhatsApp Business message that includes buttons, lists, or dropdown menus so the customer can respond by tapping an option instead of typing free text. They work through Meta's official WhatsApp API (WhatsApp Cloud API) and are used to streamline conversations, offer clear options, and reduce friction in customer service.

Why do they matter to your SME?

If your business receives dozens or hundreds of messages per day, you know that every minute counts. Interactive messages allow the customer to choose an option with a single tap: for example, selecting a product, confirming an appointment, or choosing a delivery time. This speeds up the conversation, reduces errors, and makes customer service much more efficient.

Additionally, they are ideal for combining with artificial intelligence: a tool like Wando can suggest responses based on the customer's message, and the business team approves them with a click. In that flow, interactive messages help the AI offer concrete options and the customer does not have to type anything.

Concrete example

Imagine you have an online clothing store and a customer writes to you: "What time can you deliver it to me?". With an interactive message, you can send them a list with three options: "Before 12:00", "Between 12:00 and 18:00", or "After 18:00". The customer taps an option and that's it, without typing anything. This type of interaction reduces back-and-forth and improves the experience.

Common mistakes

• Offering too many options: more than 3 or 4 buttons confuses the customer. Better fewer and clearer.
• Using interactive messages for everything: they do not replace a real conversation. Use them for concrete options, not for open-ended questions.
• Not testing on different devices: sometimes buttons look different on Android or iPhone. Test before sending.
• Forgetting that interactive messages have limits: the number of buttons and the format can vary depending on WhatsApp's update. Check Meta's official documentation for the exact limits.

How it works in practice: a complete example

Let's look at a real LatAm case: a beauty salon that receives messages all day. With the Meta API and a tool like Wando, the team sets up an interactive message with buttons for when someone asks about appointments. The customer taps "Available appointments" and the AI suggests a response with times. The team approves it with one click and that's it.

The complete flow: the customer writes, the AI interprets, suggests a response with a button or list, the business approves it and it's sent. The customer chooses with a tap and the conversation moves forward without back-and-forth. That's human-in-the-loop: the AI proposes, the human decides.

In Wando, the AI also learns from the responses you approve. If you always choose the same option for a question, next time it suggests it first. There's no need to program flows: it adapts on its own to how your team works.

• Customer asks about an appointment
• AI suggests a response with buttons
• Team approves it with one click
• Customer taps an option and the conversation moves forward

What it's confused with and how it differs

Interactive messages are often confused with flow chatbots, but they're not the same. A flow chatbot is a tree you program: if the customer taps A, it goes to B; if they tap C, it goes to D. It's designed once and maintained manually, and any change requires editing the flow.

Interactive messages, on the other hand, are just a message format: buttons or lists sent within a conversation. They are not a bot or a flow. They are the raw material for building a guided conversation, not the conversation itself.

They are also confused with templates (HSM). Templates are pre-approved messages sent outside a 24-hour session, and they can include buttons. Interactive messages are also used within an active session, in response to a query. They are different things that are combined.

• Interactive message: format with buttons or lists
• Flow chatbot: programmed tree that decides the conversation
• Template (HSM): pre-approved message, can include buttons
• Wando: AI that suggests responses, not a fixed flow

What happens if you ignore it

If your business handles WhatsApp without interactive messages, the cost is concrete: more time per conversation, more errors, and more customers who get tired of typing. Every minute a customer waits for a response increases the chance they will go to the competition.

Think of a restaurant that receives 50 inquiries per day about reservations. Without buttons, the team types the same response over and over. With interactive messages, the customer taps "Reserve" and the conversation is resolved in seconds. The difference is noticeable in the number of completed reservations.

Also, without interactive messages, you lose the opportunity to guide the conversation. The customer can go off on tangents, ask anything, and support becomes chaotic. With clear options, you control the direction and the customer feels accompanied.

How it relates to Meta's official API

Interactive messages are not a magic feature: they are part of Meta's WhatsApp Cloud API. That means they only work if your business uses the official API, not the regular WhatsApp app. The API defines message types, limits, and how they are sent.

Meta sets rules: how many buttons you can include, what types of interaction exist (reply buttons, lists, etc.), and how they are charged. Those rules change over time, so the best approach is to consult Meta's official documentation for current values.

Wando uses that official API. When we suggest a response with buttons, we do so within the limits Meta allows. And since template approval can take up to 48 hours, plan ahead if you're going to use interactive messages in campaigns.

When it does NOT apply or is not advisable

Interactive messages are not for everything. If the query is open-ended, like "What do you recommend for curly hair?", a button doesn't help: the customer needs to type. Forcing options in those cases worsens the experience.

They are also not advisable if your message volume is low and your team responds quickly. If you handle 10 messages per day, setting up buttons may be more effort than benefit. They are a tool for scaling, not for starting.

Moreover, they don't replace a real conversation. If the customer has a complaint or a complex query, buttons frustrate. Use them for concrete options and always leave the door open for free typing. Wando's AI, for example, detects when a query deserves a human response and flags it.

Common mistakes of those who are just starting to understand it

The biggest mistake is thinking that interactive messages are a bot. They are not: they are a format. Another mistake is using too many buttons: more than 3 or 4 confuses. Meta limits the quantity, but even if it didn't, less is more.

There is also the temptation to use them for everything, even for open-ended questions. That annoys the customer. And another classic: not testing on different devices. Buttons look different on Android than on iPhone, so test before sending.

Finally, not reading Meta's documentation. Limits and formats change, and what worked last month may not work today. If you use Wando, the tool updates with these changes, but if you do it manually, stay up to date.