Learn about the Recognition, Conditional, End of Flow, and Timeout components
In this article, you will learn how these components are used and how they work so that you can apply them to your flows.
Recognition Component
Conditional Component
End of Flow Component
Timeout Component
Recognition
This component recognizes if the person interacting in the flow is already a customer who is part of your contact base, thus avoiding asking for information that you already have.
Conditional
The conditional component allows you to create conditions to determine the flow of actions according to the customer's response. Branches can be added to evaluate different conditions, allowing you to segment navigation dynamically.
Types of evaluations available:
Information fields:Based on a field such as email, you can compare its value and, depending on the result, direct the conversation through different branches. It also allows the use of nested conditions:AND:All conditions must be met for the action to be executed.OR:Only one of the established conditions needs to be met.In addition, it is possible to compare information fields with dynamic values, such as date of birth or email, to validate that the data provided by the customer matches the data stored in the CRM via an HTTP Request.
Information fields:Based on a field such as email, you can compare its value and, depending on the result, direct the conversation through different branches. It also allows the use of nested conditions:
AND:All conditions must be met for the action to be executed.
OR:Only one of the established conditions needs to be met.
In addition, it is possible to compare information fields with dynamic values, such as date of birth or email, to validate that the data provided by the customer matches the data stored in the CRM via an HTTP Request.
HTTP Request:Based on the response obtained through an HTTP request, it is possible to compare this value with information stored in the information fields and redirect the conversation according to the result.
HTTP Request:Based on the response obtained through an HTTP request, it is possible to compare this value with information stored in the information fields and redirect the conversation according to the result.
Schedules:Allows you to select specific times and dates to determine the flow of the conversation, redirecting it according to the established schedule.
Schedules:Allows you to select specific times and dates to determine the flow of the conversation, redirecting it according to the established schedule.
🎯 Precision in the values evaluated by conditionals
TheConditionalcomponent in Flowbuilder allows you to make logical decisions based on values stored in information fields. However, it is important to keep in mind thatthe comparison made by the conditional is exact, so it may fail if the value entered by the user or saved in a field hasminimal variations.
⚠️ Warning: Exact and sensitive comparison
When you configure a condition based on a variable, the system comparesexact characters, including:
Accents (Atlantico≠Atlántico)
Accents (Atlantico≠Atlántico)
Uppercase and lowercase (barranquilla≠Barranquilla)
Uppercase and lowercase (barranquilla≠Barranquilla)
Invisible spaces or at the end (Resto del país≠Resto del país )
Invisible spaces or at the end (Resto del país≠Resto del país )
💡Real example:In a flow, it was expected to assign a specific group if the user selected "Atlántico". However, the value compared in the conditional was "Atlantico" (without the accent), which caused an incorrect assignment to the wrong group.
✅ Best practices to avoid errors
Copyand paste the valuesdirectly from the original source(for example, from the button or the database that loads the options).
Copyand paste the valuesdirectly from the original source(for example, from the button or the database that loads the options).
Avoid manually typing the values in the conditional.
Avoid manually typing the values in the conditional.
Normalize the fields previously, if possible, using homogeneous formats (all in uppercase, or all without accents).
Normalize the fields previously, if possible, using homogeneous formats (all in uppercase, or all without accents).
Useclosed optionsin buttons or selection options, instead of waiting for free text input.
Useclosed optionsin buttons or selection options, instead of waiting for free text input.
Verify the value that is saved using the simulator and reviewing the data in the conversation.
Verify the value that is saved using the simulator and reviewing the data in the conversation.
🧪 How to test if your conditional works?
Simulate the conversation in the Flowbuilder.
Simulate the conversation in the Flowbuilder.
Check in the console what value was actually saved in the field (for example,Department).
Check in the console what value was actually saved in the field (for example,Department).
Make sure that valuematches exactlywith the one you are using in the Conditional component.
Make sure that valuematches exactlywith the one you are using in the Conditional component.
End of Flow
This component is used to end the execution of those branches where it is not required to continue the interaction.
Timeout
This component allows you to apply a waiting time between one action and another within the flow. The waiting time can be configured in:
Seconds
Minutes
Hours
Days
Weeks
Usage Tip:
Use this component to set pauses between actions in a flow. It is recommended:
Configuration in seconds:When there are several consecutive messages and multimedia files are sent. This ensures that the messages arrive in the correct order.Suggestion for:Images:2 to 3 seconds of waiting.Videos:4 to 5 seconds of waiting.
Suggestion for:Images:2 to 3 seconds of waiting.Videos:4 to 5 seconds of waiting.
Images:2 to 3 seconds of waiting.
Videos:4 to 5 seconds of waiting.
This setting guarantees a better experience for customers, preventing multimedia messages from being sent in a disorganized manner or overlapping.