How to Create and Edit a Chatbot Flow (Step-by-Step Tutorial) | Tidio

Understanding the Chatbot Editor Interface [0:08]

• Users can access the chatbot editor by clicking the "bols" icon on the left side of the interface.
• Within the editor, users have the option to modify pre-existing bot templates or construct a bot entirely from the ground up.

  The main idea behind building the bots is to create maps that show the chat what to do exactly and when.

Core Components: Triggers, Actions, and Conditions [0:25]

• The fundamental building blocks of a chatbot are nodes, categorized into three types: triggers, actions, and conditions.
• Triggers dictate when a bot should initiate its sequence of operations.
• Actions define the specific tasks the bot will perform within the chat.
• Conditions serve as filters to determine what actions should or should not be executed.

  Triggers are divided into three categories: launched by visitors, launched by operators, and by clicking the buttons or typing with the bot.

Managing Trigger Frequency [0:42]

• Triggers can sometimes be repetitive, and the editor offers an option to limit how many times a specific trigger can be activated for an individual user.
• This limitation can be set to a defined number, controlling the bot's responsiveness to repeated user engagement.
• After setting up a trigger, the next step involves defining the subsequent action the bot will perform.

  Once you set up the trigger you need to define what should be the next step in the bot.

Actions and Connection Logic [0:42]

• Actions are used to implement specific functionalities, such as sending a message to a visitor.
• The chatbot editor functions like a map, requiring all nodes (triggers, actions, conditions) to be connected in a logical sequence.
• This orderly connection ensures the chat understands the intended flow and where to proceed next.
• Attempting to connect nodes in an illogical or backward order will result in an error message, indicating a logic failure.

  The map just can go backward.

Implementing Conditions for Branching Logic [02:02]

• Conditions are used to branch out the bot's flow, allowing for dynamic responses based on specific criteria.
• Before executing an action, the bot can check for certain information, like whether a visitor has provided their name.
• This is achieved by adding a condition node, which branches the flow into two paths: one for when the condition is met ("yes") and another for when it is not met ("no").
• In the example, the condition checks if the visitor has provided a name.

  Conditions branch out to two paths; if the condition is met you can select a yes or no path.

Handling Missing Information and Saving Data [02:54]

• If a visitor has not provided their name, the bot can be configured to ask for it.
• The input received can be validated as a name and then saved as a contact property.
• This allows the bot to personalize subsequent messages by referencing the saved contact property, such as the visitor's name.
• The "yes" path from the condition is used when the visitor has already provided their name, leading to a personalized message.

  We want to save the contact property as a name.

Testing and Saving the Chatbot [04:02]

• After constructing the bot's map, users can test its functionality using the "test hour" button.
• A new window opens, simulating a chat interaction with the bot, allowing for real-time testing of the flow.
• Once satisfied with the bot's performance, it can be saved by clicking the green save button in the upper right corner.
• Users are prompted to provide a name for the bot, which helps in future recommendations and adjustments based on user needs.
• Saved bots can be accessed anytime from the "my childhood section".

  Awesome your boat is now ready you can find your boat anytime in the my childhood section.