Bot Actions in Responses

When you create a dialogueClosed Bot stories and rules in Bot Builder. or a flowClosed A graphical representation of a conversation used to train a bot., you can choose which type of action the bot will take as its response. The bot will always respond with the response you configure when it recognizes the intentClosed The meaning or purpose behind what a contact says/types; what the contact wants to communicate or accomplish. set in the dialogue.

Bot responses can be simple or as complex as you want to make them. Bots can:

  • Reply with information or questions. 
  • Display images, GIFs, videos, or links to web pages.  They can include buttons or lists that the contact can interact with.
  • "Choose" which action to take using conditions. You can configure multiple possible responses based on what the contact says.
  • Follow a form to collect information from the contact.
  • Escalate the interaction to a human agent.

Bot responses consist of one or more bot actions. All bot actions are available on a menu that pops up when creating the bot response, as shown in the following image. If you've created custom bot actions with scripting or API integrations, they're also available on the bot action menu.

All Bot Actions

Action type Details
Message

The bot sends a text-based message to the contact.

When working with stories and rules, you can choose Message from the bot actions A robot head. menu.

When working with flows, you can choose List Picker from the bot actions Icon of a plus sign in a circle. menu.

You can add buttons or quick replies to the message or choose to leave it as regular text. If a message has buttons or quick replies with an intent defined, the intent shows up next to the message on the bot response configuration page. You can click on them to see all stories and rules where they are used.

For channels that don't support this option, you can customize the rich messaging fallback for this response. By default, the bot will use what is configured in rich messaging fallback.

Multimedia

The bot sends a multimedia file, such as images, videos, PDFs, or MP3s. You can upload a file that meets supported file types and sizes.

Multimedia is supported on certain channels only. For channels that don't support multimedia, rich messaging fallback is used.

When working with stories and rules, you can choose Multimedia from the bot actions A robot head. menu.

When working with flows, you can choose Multimedia from the bot actions Icon of a plus sign in a circle. menu.

Cards

Cards can combine images, structured text, and buttons into one message. This keeps the interface cleaner than sending several responses back to back. You can add up to 10 cards to be sent at a time. The customer will be able to swipe back and forth to view them.

For channels that don't support this option, you can customize the rich messaging fallback for this response. By default, the bot will use what is configured in rich messaging fallback.

When working with stories and rules, you can choose Cards from the bot actions A robot head. menu.

When working with flows, you can choose Cards from the bot actions Icon of a plus sign in a circle. menu.

List Picker

The bot sends the contact a list of options to choose from. You can provide an introductory message. A list can contain up to 10 options.

For channels that don't support this option, you can customize the rich messaging fallback for this response. By default, the bot will use what is configured in rich messaging fallback.

When working with stories and rules, you can choose List Picker from the bot actions A robot head. menu.

When working with flows, you can choose List Picker from the bot actions Icon of a plus sign in a circle. menu.

Rich Link

The bot can send a URL with an image included. The contact can click on the link or image to visit the URL.

For channels that don't support this option, you can customize the rich messaging fallback for this response. By default, the bot will use what is configured in rich messaging fallback.

When working with stories and rules, you can choose Rich Link from the bot actions A robot head. menu.

When working with flows, you can choose Rich Link from the bot actions Icon of a plus sign in a circle. menu.

Adaptive Cards

The bot can send Adaptive Cards to contacts. They are a method of sending rich messaging content.

For channels that don't support this option, you can customize the rich messaging fallback for this response. By default, the bot will use what is configured in rich messaging fallback.

When working with stories and rules, you can choose Adaptive Cards from the bot actions A robot head. menu.

When working with flows, you can choose Adaptive Cards from the bot actions Icon of a plus sign in a circle. menu.

Fill Slot

This bot action allows you to have a slotClosed Entity extracted from contact's message and saved for use in bot responses. Similar to a variable. filled with a value. You can select from your existing slots or create a new slot from the bot action in the story, rule, or flow. If you create a new slot, you must open the Slots panel and configure the slot so it works the way you need it to.

When working with stories and rules, you can choose Fill Slot from the bot actions A robot head. menu.

When working with flows, you can choose Fill Slot from the bot actions Icon of a plus sign in a circle. menu.

This bot action instructs the bot on what it needs to do. The contact does not see a message in the chat window when you include this action a bot response.

Slot Condition

You can use the slot condition bot action to train your bot to use different responses based on the value the slot holds. When you include this bot action in a bot response, the value of the specified slot becomes a condition that determines which path the bot takes.

When working with stories and rules, you can choose Slot Condition from the bot actions A robot head. menu.

When working with flows, you can choose Slot Condition from the bot actions Icon of a plus sign in a circle. menu.

This bot action instructs the bot on what it needs to do. The contact does not see a message in the chat window when you include this action a bot response.

Handover

This bot action allows you to have a contact message trigger the handoverClosed The transfer of a contact from a bot to a live agent. rule.

This option uses digital routing queuesClosed Determine which agents to route digital cases to, using criteria such as the agent having expertise in that type of case.. You can choose a specific routing queue or allow the system to automatically route the contact. If you use digitalClosed Any channel, contact, or skill associated with Digital Experience.ACDskillsClosed Used to automate delivery of interactions based on agent skills, abilities, and knowledge. for routing, you can still use this option. Every ACD skill has a corresponding routing queue that's automatically created in Digital Experience. You can configure it when you want to use the handover bot action.

When working with stories and rules, you can choose Handover from the bot actions A robot head. menu.

When working with flows, you can choose Handover from the bot actions Icon of a plus sign in a circle. menu.

This bot action instructs the bot on what it needs to do. The contact does not see a message in the chat window when you include this action a bot response.

Add Tag

You can add one or more tags to the interaction. Tags allow you to identify patterns in conversations.

If the tag you want doesn't exist, you can create it from this bot action in the bot response workspace or in the Tags section of Preferences icon, which looks like a gear..

When working with stories and rules, you can choose Add Tag from the bot actions A robot head. menu.

When working with flows, you can choose Tag from the bot actions Icon of a plus sign in a circle. menu.

This bot action instructs the bot on what it needs to do. The contact does not see a message in the chat window when you include this action a bot response.

Checkpoint

Checkpoints provide a simple way to connect different stories within the same dialogue.

When working with stories and rules, you can choose Checkpoint from the bot actions A robot head. menu.

This option is currently not available for flows.

This bot action instructs the bot on what it needs to do. The contact does not see a message in the chat window when you include this action a bot response.

Forms

Forms allow you to collect multiple pieces of information from a contact. You can add a form as a bot action when you want to activate a form during an interaction.

When working with stories and rules, the bot actions menu has a Forms tab that displays the available forms. You can add a form as a bot action from this menu.

This option is currently not available for flows.

APIs

API integrations allow you to connect your bot to web services via APIs. They create custom bot actions that you can add to bot responses. You can add one to a response when you want to trigger an API call during an interaction.

When working with stories and rules, the bot actions menu has an APIs tab that displays the bot actions from the integrations you have set up. You can add an API action from this menu.

This option is currently not available for flows.

Scripts

Bot Builder supports custom scripts. You can create custom scripts. Custom scripts may also be installed with bot skills added from the Skill Store. You can use the Scripts bot action in a response when you want to trigger that script during an interaction.

When working with stories and rules, the bot actions menu has a Scripts tab that displays the custom scripts that have been enabled in Bot Builder. You can add a script action from this menu.

When working with flows, you can choose Script from the bot actions Icon of a plus sign in a circle. menu, then select the script you want to use.

Scripts must be enabled in the Script Integrations section of Bot Builder to show up on the Scripts tab or as a Script flow action.