Interactive messages
You can only send an interactive message up until 24 hours after receiving a message from the user. If you have not received a message from the user within this time, you will need to start a new conversation by sending a Template message.
Interactive messages contain buttons, menus, or custom actions that invite users to interact with the business besides only typing texts.
They achieve significantly higher response rates and conversions compared to text-based messages.
The following messages are considered interactive:
List Messages: Messages including a menu of up to 10 options. This type of message offers a simpler and more consistent way for users to make a selection when interacting with a business.
Reply Buttons: Messages including up to 3 options —each option is a button. This type of message offers a quicker way for users to make a selection from a menu when interacting with a business. Reply buttons have the same user experience as interactive templates with buttons.
Reaction Messages: Reaction Messages allow you to react to messages. This feature is currently available in the Cloud API. There is no information on whether it will be introduced in the on-premises API.
Single Product Message: Messages with a Single Product item from the business’ inventory. See Products and Catalogs for more information.
Multi-Product Message: Messages containing a selection of up to 30 items from a business’ inventory. See Products and Catalogs for more information.
Location Request Messages: Location request messages contain body text and a Send location button that users can tap. Tapping the button displays a location sharing screen which the user can then use to share their location. See Location Request Messages.
Businesses from India need to comply with extra rules to use product messages. See them here.
Interactive Message Specifications
Interactive messages can be combined together in the same flow.
Users cannot select more than one option at the same time from a list or button message, but they can go back and re-open a previous message.
List or reply button messages cannot be used as notifications. Currently, they can only be sent within 24 hours of the last message sent by the user. If you try to send a message outside the 24-hour window, you get an error message.
Supported platforms: iOS, Android, and web.
Cloud API has Reaction Messages. It is not available for on-premises.
See how text messages compare to interactive messages:
Sending Interactive Messages
Interactive messages include List Messages and Reply Buttons.
To send interactive messages, make a POST
call to /messages
and attach a message object with type=interactive
. Then, add an interactive
object.
List Messages sample request:
Reply Button sample request:
A successful response includes an object with an identifier prefixed with wamid
. Use the ID listed after wamid
to track your message status.
Reaction Messages
Reaction Messages allow you to react to messages. This feature is currently available in the Cloud API. There is no information regarding an estimated time of availability or whether it will be introduced in the on-premises API.
Reaction Object
To send reaction messages, make a POST
call to /messages
and attach a message
object with type=reaction
. Then, add a reaction
object.
Sample request:
If the message you are reacting to is more than 30 days old, doesn't correspond to any message in the conversation, has been deleted, or is itself a reaction message, the reaction message will not be delivered and you will receive a webhook with the code 131009
. See Cloud API Error Codes.
A successful response includes an object with an identifier prefixed with wamid
. Use the ID
listed after wamid
to track your message status.
Last updated