# WhatsApp Interactive Messages

When configuring the [*Menu* node](/flow/user-facing-nodes/branch-logic-split/menu-nodes-menu-with-options.md), [*Multiple Choice Input* node](/flow/user-facing-nodes/branch-logic-split/menu-nodes-multiple-choice-input.md), and [*Dynamic List*](/flow/user-facing-nodes/branch-logic-split/menu-nodes-dynamic-list.md) node, you can select how you want to display the menu options to the customer using the [*Configure Display Type*](/flow/channel-capabilities/configure-channel-display-type.md) modal. 

For the WhatsApp channel, there are two types of interactive messages to select from:

1. [**List messages**](#list-messages)**:** Add a longer list with up to 10 options for users to select from.
2. [**Reply buttons**](#reply-buttons)**:** Add up to 3 buttons, each presenting an option for the user to select. 

{% hint style="info" %}
To send interactive WhatsApp messages **directly** via One API, see the [API reference documentation](https://docs.clickatell.com/channels/one-api/one-api-reference/).
{% endhint %}

## List Messages

List Messages are ideal for presenting longer lists of options to customers.

{% hint style="info" %}
**Examples:** Customer care or FAQ menu, take-out menu, list of nearby stores/locations, available reservation times.
{% endhint %}

List Messages support up to **10 options**. Any additional options (marked with a yellow warning icon) will not be displayed to customers on WhatsApp.

{% hint style="warning" %}

* List Messages **do not currently support images**. Even if a flow-builder adds an image to the node, it is not displayed to the customer on WhatsApp.
* Formatting options are **not** supported in the Menu Header or Sub Header. It is only supported in the Body Text. The Menu Header is **bolded** automatically. 
* Sub Header is displayed in all caps and limited to **26 characters**.
  {% endhint %}

![Warning when more than 10 options have been added to the node](/files/WkwOshqxJLdaoi0GrnPD)

![Example of an interactive message (list message) as displayed to customers on WhatsApp.](/files/BR7wuE7FXrHGBUTAgwg6)

## Reply Buttons

Reply Buttons are ideal when customers must select a quick response from a limited set of options. 

{% hint style="info" %}
**Examples:** Airtime recharge, changing personal details, reordering a previous order, choosing a payment method.
{% endhint %}

Button menus support up to **3 buttons**. Any additional options (marked with a yellow warning icon) will not be displayed to end-users on WhatsApp. 

Text on buttons is limited to **20 characters** each. 

{% hint style="warning" %}

* Reply Buttons **do support images**. However:
  * If an image is added, the Menu Header text will not be displayed. 
  * If no image is added, the Menu Header text will be displayed. 
* Formatting options are **not** supported in the Menu Header or Sub Header. It is supported in the Body Text. The Menu Header is **bolded** automatically. 
  {% endhint %}

![Warning when more than 3 options have been added to the button list.](/files/PR5hJRN7j2FAXzOmHLlB)

![Example of an interactive message (reply buttons) as displayed to customers on WhatsApp](/files/bzOYPzgwpqppFx0PTa8h)

### Combining interactive lists and buttons in a flow

#### Example 1:

![Telecoms: recharge airtime](/files/WJmaVzP6JQNjxy6I08su)

#### Example 2:

![Financial services: handle customer queries](/files/ektGYkaEFCK41Z1gZKYs)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.clickatell.com/flow/channel-capabilities/use-whatsapp-with-chat-flow/whatsapp-interactive-messages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.