The Four Elements of ActionBot
Brief Overview
The WalkMe ActionBot is a powerful tool that consists of four elements that work collaboratively to achieve its functionality. These elements include bots, launchers, conversations, and actions. Understanding each of these elements is crucial to unlocking the full potential of the ActionBot.
This article will provide an in-depth overview of these elements to help you comprehend how they work together. If you're unfamiliar with the WalkMe ActionBot and want to learn more about its features and potential use cases, start with this article:
The Four Elements
1. Bots
A bot is a “container” for conversations, designed to be deployed anywhere. Its primary function is to comprehend the user's intent by analyzing the conversations it has stored.
To create a bot in the WalkMe Console, you can customize and design various aspects such as messaging, design, and settings. Although there are mandatory components that must be included in the creation process:
- Greeting messages: This will be the first message to the user when the bot is initiated. Once the greeting message is displayed, the bot tries to match a conversation to the user's input
- Assign conversations: Conversations are dialogues between a user and an automated chatbot designed to perform specific actions.
- When creating your bot, you'll select conversations that are relevant to the bot. The bot will search these conversations and try to match one of its assigned conversations to the user's input
- Add launchers: A launcher is a button placed on a website that, when clicked, will trigger the ActionBot, opening the chat interface.
- When creating your bot, you'll select different launchers that to start your bot. If no launcher is select, WalkMe will create a default launcher for you, which can be edited later
- End conversation messages: This message appears when the conversation has ended successfully and the bot has performed an action, or presented the final conversation step
2. Conversations
A conversation is a set of messages, questions, conditions, and actions. Once the bot has understood the user's intent, it will converse with the user up until reaching the end step or a specific action the bot should perform.
To create a conversation in the console, you can navigate to the Conversations Page. You can then add conversation steps to the flow diagram to guide your users through a specific task.
Here's an example of a "Take time-off" conversation:
Take Time-Off Conversation |
1. Greeting message: The bot asks for user input by asking a question (Greeting message in created in the bot building process) |
2. User input: When the user responds, the bot searches for the best conversation to match |
3. Message step: The bot starts the "Request absence" conversation and responds with an opening message to let the user know that the conversation has started |
4. Question step: Using a 'date entry' question, the bot extracts the time-off dates |
5. User Input: The user's input is captured as a variable to use for the automation process later |
Once the conversation is complete (the user has answered all of the bots questions and collected data for the user's inputs), the action step will activate. In this example, the ActionBot uses the data it has gathered in the conversation to auto-fill a leave of absence form for the user.
3. Launchers
A launcher is a button placed on a website that, when clicked, will trigger the ActionBot, opening the chat interface.
Your launchers will appear in the bot building process in General page under 'Assign launcher'. If you haven't created any launchers yet or didn't assign a launcher to the bot, then WalkMe will create a default launcher for you that will be added to your WalkMe Editor's list.
Creating a launcher can be done from the Launcher App in the WalkMe Editor. Follow these steps in this article to create a launcher.
- After reaching the action dropdown, choose Open ActionBot. Then, select the specific ActionBot you want the launcher to open from the dropdown menu
4. Actions
Actions in are automated tasks that the bot can perform on behalf of the user during a conversation. These actions can range from triggering WalkMe items like Smart Walk-Thrus, surveys, and ShoutOuts, to opening integrated Live Chat windows, and even calling external APIs.
During the conversation building process, actions steps are labeled as either WalkMe Steps or Cross-system steps. These steps are added to the conversation flow diagram when creating a conversation.
How does it work?
ActionBot performs data mapping in action steps through a structured process that involves collecting data from user inputs during a conversation and then using this data to trigger specific actions. Here's a brief summary of how it works:
- Collecting data: During a conversation with the user, ActionBot asks questions and collects responses
- Defining variables: The collected data is assigned to variables that have already been mapped out when an action step was created in the console
- This is done in the console by entering a variable name in the Name as field for the data collected. These variables are used to store the data temporarily
- Automated data transfer: The data is transferred to the WalkMe item or connection, allowing for personalized and automated responses or tasks based on the collected data