1. Availability
1.1 Bot opening hours
If required, you can make your bot's availability subject to opening hours. To do this, you'll need to add a time condition to the corresponding targeting rule(s).
1.2 Availability at the level of the Bot's commitment (following a notification)
The availability check for a Bot that needs to start a conversation will look to see if at least one of the transfers it will have to make during the scenario is available.
- Case 1: the scenario only contains transfers to synchronous routing rules
At least one of the transfers to one of the routing rules must be with availability.
- Case 2: The scenario contains only transfers to asynchronous routing rules.
The availability of an asynchronous rule is based on the threshold, and not on the availability of an agent, so the bot will not be available as soon as all the rules have reached their maximum conversations threshold.
- Case 3: the scenario contains a mix of synchronous and asynchronous rules
At least one of the transfers to one of the routing rules must have availability, so in this case, the availability will be calculated both by taking into account the number of available agents and the maximum conversation queuing thresholds.
2. The Proactivity of a Bot
Here are some examples of possible configurations for a proactive bot:
Case N°1: I need a proactive bot => Distribution rule with only one bot in its distribution group
Case N°2: I need a proactive multi-language bot => distribution rule with only 1 bot of each language in its own distribution group
Case n°3: I want to engage on the chat channel with a bot and on video or call channels with human agents => the distribution rule with a bot in its distribution group + another cascade group containing only agents which do not have the chat channel activated in their user profile
- Only one bot per language in the routing rule (the bots will always be proactive if there is an EN bot and an FR bot).
- At least one multiple choice question or open-ended question anywhere in the bot scenario
2. The transfers during a Bot scenario
- Case 1: transfer to a synchronous routing rule
The availability check for a Bot that has to transfer to a synchronous routing rule, will try for 30s to get an agent availability by default. If no availability is detected after the 30s, a check of the availability of an alternative to transfer is made, if it is configured, otherwise the transfer fails.
- Case 2: transfer to an asynchronous routing rule
The availability check for a bot that has to transfer to an asynchronous routing rule, will try for 30s by default to get an available agent or a spot in the waiting queue of the routing rule. If no availability is detected after the 30s, a check of the availability of the alternative to transfer is made, if it is configured, otherwise the transfer fails.
You can configure the delay of the availability check in the bot identity section.
For more information about the bot :
- Steps to launch your bot