This article describes the functioning, applications, and usage of the conditions card, available in the Bot Scenario section of iAdvize Automation.
Among the various types of cards available for creating your bot scenario, the Conditions card is one of the most interesting.
It allows you to adapt your scenario based on certain criteria :
- Variables (e.g., associated with an API)
- Custom data (e.g., if the visitor is identified in their customer account)
By adapting your bot scenario to specific conditions, you can personalize the content of responses, steps, or distribution based on different criteria !
For example, you can:
- Customize the scenario based on a customer's order status.
- Adjust the scenario based on the type of page your visitors are on.
- Direct only visitors with a certain cart total to your advisors.
- Offer a premium service to loyal customers if they are identified in their account.
The Conditions card allows your bot to adapt to a wider range of visitor situations and needs, rather than using multiple bots.
Updating is simpler, as is analyzing the performance of your scenario (everything remains within the same scenario rather than having multiple separate bots).
You can also simplify your engagement strategy because the bot is now capable of adapting itself based on the parameters you set.
Given its potential for personalization and creativity, it can be tempting to use many Condition cards in a scenario !
We encourage you to keep a few principles in mind:
- Readability: Ensure that the structure of your bot is clear for both you and your teams. A very complex scenario increases content and thus the chances of errors, and it also complicates performance analysis.
- Utility: For the reasons mentioned above, focus the use of the card on conditions that provide significant value to your visitors and your team.
Use the Condition card in your scenario
With just one condition
Imagine you want to differentiate the scenario offered to your visitors based on the price of the product they are viewing. For example, by transferring visitors looking at a product priced above €300 to a group of more available and qualified responders.
In a scenario that already includes a welcome card, choose a condition card as the second card. Name it "if price > €300. "Click on "Add a condition.", a modal will appear.
Configure your condition - in our example, you can retrieve custom data related to a price or product category (this article explains how to create custom data) by selecting the custom data "price," "greater than," and entering 300.
Determine the action to take if the price is greater than €300 - for example, lead to a "pre-qualification" multiple-choice card prior to distribution to a group of advisors.
Back on the card, determine the action to take if the condition is not met; for example, lead to a multiple-choice card managed autonomously by the bot.
If necessary, continue your two scenario variants by using and reusing the usual cards: the bot will now transfer to humans, only for visitors interested in items costing more than €300.
It is possible to list multiple conditions and different actions in the same Condition card - simply add an additional condition in the card space and provide as many different versions of the scenario as needed.
Let's take our previous example, imagining that we also want to offer qualified and available responders to brand-affiliated loyalty program customers who are identified in their customer account.
Take the previously configured card, click on "add a condition", which you will name "if loyalty program." Determine the chosen action, which can be the same or different from the action associated with the previous condition: for example, lead to a "pre-qualification" multiple-choice card prior to distribution to a group of advisors.
Your card now allows you to adapt the scenario if either of these conditions is met, but it also provides a "default" version.