Rich Messaging

Bot Builder supports several kinds of rich media for use in your bot's messages. Rich media enhances messaging with options such as list pickers, buttons, and links. This allows you to provide a richer experience for your contacts compared to plain text messages.

When you include rich media in bot messages, always set up rich messaging fallback. This ensures that the contact receives the message even if the channel doesn't support the media type.

Supported Rich Media Types

Bot Builder supports the following rich media types: 

Rich Media Type Details
Buttons

Description: Create a set of buttons that contacts can click.

Buttons are persistent in the conversation history. This means that later in the conversation, contacts can scroll up in the chat window and use a button.

Channel support:

  • Digital Experience Chat
  • Facebook Messenger

For channelsClosed A way for contacts to interact with agents or bots. A channel can be voice, email, chat, social media, and so on. that don't support buttons, click rich message fallback icon, represented by two boxes with an arrow pointing from one to the other. to customize the fallback response. The fallback response for rich messaging is different from the other fallback you can configure.

Max number per message: 3

Variable support: Yes

Button actions: Trigger an intent or open an URL

Cards

Description: Cards can combine images, structured text, and buttons into one message.

Channel support:

  • Digital Experience Chat
  • Facebook Messenger

For channelsClosed A way for contacts to interact with agents or bots. A channel can be voice, email, chat, social media, and so on. that don't support cards, click rich message fallback icon, represented by two boxes with an arrow pointing from one to the other. to customize the fallback response. The fallback response for rich messaging is different from the other fallback you can configure.

Max number per message: 10

Variable support: Yes

Button actions: Trigger an intent or open an URL

Rich Links

Description: Send a URL with an image included. The contact can click on the link or image to visit the URL.

Channel support:

  • Apple Messages for Business
  • Digital Experience Chat
  • Facebook Messenger
  • Google Business Messages
  • WhatsApp

For channelsClosed A way for contacts to interact with agents or bots. A channel can be voice, email, chat, social media, and so on. that don't support rich links, click rich message fallback icon, represented by two boxes with an arrow pointing from one to the other. to customize the fallback response. The fallback response for rich messaging is different from the other fallback you can configure.

Max number per message: 1

Variable support: Yes

Click actions: Open URL (default option, cannot be modified)

List pickers

Description: Create a list of options the customer can choose from.

Channel support:

  • Apple Messages for Business
  • Digital Experience Chat
  • Facebook Messenger
  • Google Business Messages
  • WhatsApp

For channelsClosed A way for contacts to interact with agents or bots. A channel can be voice, email, chat, social media, and so on. that don't support list pickers, click rich message fallback icon, represented by two boxes with an arrow pointing from one to the other. to customize the fallback response. The fallback response for rich messaging is different from the other fallback you can configure.

Max number per message: 10 options

Variable support: Yes

Click actions: Trigger an intent or send text

Multimedia

Description: Upload a multimedia file.

Supported file types:

  • Images in PNG, JPG, GIF, or BMP format that are smaller than 5 MB.
  • Videos in AVI, MPEG-4, or WEBM format that are smaller than 200 MB.
  • Audio files in MP3 format that are smaller than 15 MB.
  • PDF or Microsoft Word, Excel, or Powerpoint files that are smaller than 15 MB.

Channel support:

  • Apple Messages for Business
  • Digital Experience Chat
  • Facebook Messenger
  • X (Twitter)  Direct Messaging (images only)
  • WhatsApp

Max number per message: 1

Variable support: Yes

Click actions: Can click to open the multimedia, depending on the channel.

Quick Replies

Description: Similar to buttons; offer a list of options for the customer to choose from, usually to help narrow down their intent.

Quick replies are not persistent in the conversation history. This means they don't remain available for use later in the conversation. After a new message appears in the chat, the quick replies disappear.

Channel support:

  • Apple Messages for Business
  • Digital Experience Chat
  • Facebook Messenger
  • WhatsApp

For channelsClosed A way for contacts to interact with agents or bots. A channel can be voice, email, chat, social media, and so on. that don't support quick replies, click rich message fallback icon, represented by two boxes with an arrow pointing from one to the other. to customize the fallback response. The fallback response for rich messaging is different from the other fallback you can configure.

Max number per message: 12

Variable support: Yes

Click actions: Trigger an intent or send text

Adaptive Cards

Description: Developed by Microsoft, Adaptive Cards An icon of a square with an arrow  pointing from the center out to the upper right corner. are a method of creating rich messagingClosed Elements in digital messaging such as buttons, images, menus, and option pickers. content. They're an open card exchange format that allows you to send UI content in a common and consistent way.  Learn more about using Adaptive Cards with your bot.

Channel Support

  • Digital Experience Chat
  • Microsoft Teams

For channelsClosed A way for contacts to interact with agents or bots. A channel can be voice, email, chat, social media, and so on. that don't support adaptive cards, click rich message fallback icon, represented by two boxes with an arrow pointing from one to the other. to customize the fallback response. The fallback response for rich messaging is different from the other fallback you can configure.

Max number per message: 1

Variable support: Yes

Click actions: Submit or open URL

Variables in Rich Media

You can use variables in most of the supported rich media types. In Bot Builder, slotsClosed Entity extracted from contact's message and saved for use in bot responses. Similar to a variable. are used as variables. The value the slot contains replaces the variable when the bot sends the message. You must ensure that the slot collects the correct value before using it as a variable during the interaction. This allows you to substitute information into messages containing rich media, as long as you have a slot that captures the information.

To add a variable, use this syntax: {slot_name}. If the slot contains a nested JSON object, you can access the values in the object using dot notation:  {slotName.parameter}.

For example, if you want the bot to greet the contact with their first name, you would need a slot to hold the first name and a way to fill the slot, such as a pre-chat form. If the slot is contact_firstName, you would enter this text in the greeting message the bot sends: Hello {contact_firstName}!

Rich Media Click Actions

Many rich media types are interactive. The contact can click them and cause something to happen in the chat. There are three possible click actions. Each rich media type supports up to two of the three possible actions. The click actions are: 

Adaptive Cards have their own on-click actions that are separate from what's listed in this section. Refer to the Adaptive Cards An icon of a square with an arrow  pointing from the center out to the upper right corner.documentation for more information.

Rich Messaging Fallback

Rich messages contain options that are more than just plain text. Some digital channelsClosed Any channel, contact, or skill associated with Digital Experience., like digital chat, support rich messages. Other channels, like SMS, only support plain text.

Rich messaging fallback is a plain text alternative you can configure. Channels that don't support rich messages display the fallback instead of the rich message. You can configure a default fallback option for each rich message content type. You can override the default for individual messages.

Rich messaging fallback is different from action or NLU fallback, which is fallback used when the bot's confidence in the predicting the intent doesn't neet the configured threshold limit.

Rich Message Support by Channel

Use the following table to determine which channels will send which types of rich content. Any rows with a red X and any channels not listed will use rich messaging fallback.

  Buttons Cards Multimedia* Quick Replies Rich Links List Picker
Apple Messages for Business Red X, indicating "not supported"

Red X, indicating "not supported"

Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported"
Digital Experience Chat Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported"
Facebook Messenger Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported"
Google Business Messaging Red X, indicating "not supported" Red X, indicating "not supported" Red X, indicating "not supported" Red X, indicating "not supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported"
Twitter Red X, indicating "not supported" Red X, indicating "not supported" Green checkmark, indicating "supported"

images only

Red X, indicating "not supported" Red X, indicating "not supported" Red X, indicating "not supported"
WhatsApp Red X, indicating "not supported" Red X, indicating "not supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported" Green checkmark, indicating "supported"
Other Channels Red X, indicating "not supported" Red X, indicating "not supported" Red X, indicating "not supported" Red X, indicating "not supported" Red X, indicating "not supported" Red X, indicating "not supported"

*Multimedia file type and size restrictions apply:

  • Images: PNG, JPG, GIF, or BMP format; 5 MB or smaller
  • Videos: AVI, MPEG-4, or WEBM format; 200 MB or smaller
  • Audio: MP3 format; 15 MB or smaller
  • PDF, Microsoft Word, Excel, or Powerpoint: 15MB or smaller