A condition in Tidio is a chatbot node that checks whether specific visitor criteria are met to trigger the bot.
In this article, you'll learn:
How Conditions work
The conditions in Tidio allow you to narrow down the targets of your bot's actions by setting up requirements. A Condition can be used to apply a filter; for example, it allows you to change the way the bot will behave depending on your chat status, the visitor's browser, or their current URL on your website.
Moreover, the condition can also check if the visitor's browser language is Spanish and later send them the message in Spanish. If the visitor's browser language weren't Spanish, the message would be sent in English.
Those are just a few examples of what conditions can do in your bot.
Here's a list of all of the Conditions that you can use:
- Based on Contact Property
- Operating system
- Returning visitor
- Current URL
- Mailing subscriber
- Chat status
You'll find all the conditions listed on the right-hand side menu, inside the visual chatbot editor, next to the triggers and actions.
Based on Contact Property
Based on Contact Property Condition allows you to select a Contact Property that will determine the flow of your chatbot. See our article about Contact Properties to learn more.
You can use attributes like 'is equal,' 'contains,' or even 'ends with' to determine exactly how the bot should behave.
The browser condition lets you determine how the chatbot should proceed based on the visitor's browser. You can, for example, display some messages of the bot only to the users who have a specified web browser.
Similar to the condition above, the Operating system condition lets you control the chatbot based on the visitor's operating system (you can choose from both desktop and mobile operating systems).
You can choose if the operating system should be equal (or not equal) to Windows, OS X, Unix, Linux, Android, or iOS.
Returning visitor condition enables your bot to act differently towards new and returning visitors on your site. It's different than using the 'Visitor returns to the site' Trigger in your bot - because you can create a flow with another Trigger that you need (e.g. 'Visitors clicks on chat icon') and attach that Condition, creating a scenario that isn't possible with just the 'Visitor returns to the site' Trigger.
Day condition lets you determine chatbot actions based on the days of the week. Similar to the previous conditions, you can use "equal" and "not equal" attributes to manage the flow.
The Current URL Condition lets you determine chatbot behavior based on the page your visitor lands on. Let's say that you wish to activate a chatbot when a visitor moves their mouse cursor out of the browser window - but you only want that to happen on a specific URL. You can achieve this thanks to the 'Current URL' Condition.
The Language Condition lets you create a bot that will send automated messages in more than one language (or carry out other actions based on language). The bot will detect the visitor's default browser language and base its actions on that.
You can read more about implementing the language condition in the article How to Create a Multilingual Bot.
The mailing subscriber condition allows your bot to filter visitors by their subscription status, and perform actions based on that.
In the example below, the bot sends a warm welcome message to every mailing subscriber who enters a specific page. The bot then asks for an email address and subscribes to every non-subscriber.
The Chat status condition lets you adjust your chatbot's behavior depending on your chat status: online or offline.
This feature comes in handy when you wish to display a specific chatbot message when your chat is online and a different one when your chat is offline.
The example above presents a chatbot that sends a warm welcome message to your visitors when your chat status is online but asks for an email and informs them that you will reach out to them later on when you cannot respond to the request.
Thanks to the Mobile node, you can create different paths for users on the mobile device.
With this node, you can create different rules & experiences that activate depending on the user's device. For instance, you could create a path that offers mobile users a more streamlined checkout process while desktop users are presented with a more detailed product catalog.
This node is particularly useful for creating a personalized user experience, improving engagement, and increasing conversion rates for your business.