Type options | Settings tab | Exits tab |
Time: Set exit conditions based on a specific time range and time zone. For example, 9 to 5 PM, Monday to Friday. | No additional settings available |
Exit 1, Exit 2, …: Click Add Exit to add more exit conditions, then change these settings.
Note: If you have multiple exits, time periods can't overlap with each other.
-
Timezone: Select the associated time zone for the time ranges. Click Edit Time to set the time ranges.
-
Name: Enter a display name for the exit condition.
-
Map Exit to Skill: Select or search for a skill category and skill to map to this exit to better match consumers to agents with the relevant skill. For example, if you're using the Condition widget to verify input from a CollectInput variable, you can define an exit for "Press 1 for English support" and map it to the English skill.
Note: The skill category and skill must be added to the associated agent routing profile of the flow's queue. -
Next Widget: Select the destination widget if the exit condition is met (caller is routed during the specified time ranges).
No Match: Select the destination widget if the exit condition isn’t met..
|
Date: Set exit conditions based on a specific range of days. For example, Monday to Friday. | Not applicable |
Exit 1, Exit 2, …: Click Add Exit to add more exit conditions, then change these settings.
Note: If you have multiple exits, time periods can't overlap with each other.
-
Timezone: Select the associated time zone for the time ranges.
-
Date: Select the date range.
-
Name: Enter a display name for the exit condition.
-
Map Exit to Skill: Select or search for a skill category and skill to map to this exit to better match consumers to agents with the relevant skill. For example, if you're using the Condition widget to verify input from a CollectInput variable, you can define an exit for "Press 1 for English support" and map it to the English skill.
Note: The skill category and skill must be added to the associated agent routing profile of the flow's queue. -
Next Widget: Select the destination widget if the exit condition is met (caller is routed during the specified date range).
No Match: Select the destination widget if the exit condition isn’t met.
|
Operating Hours: Route based on if the current time is within the available or unavailable period determined by the associated business hours and closure set. | For details, see the article about operating hours. |
For details, see the article about operating hours.
|
Variable: Set exit conditions based on a variable from another widget, or custom or global variable. |
Variable: Select a variable from another widget, or custom or global variable.
For example, you can use this to verify input from the Collect Input widget by select one of the CollectInput variables.
|
Exit 1, Exit 2, …: Click Add Exit to add more exit conditions, then change these settings.
-
Variable Condition: Select the variable condition that determines the relationship between the Variable in the Settings tab and the Value.
-
Value: Specify the value for the exit condition. To specify multiple values, separate values with a semi-colon (;). The condition is met if any of the values are matched.
-
Add Condition: Add another variable condition and value. Make sure to specify the And/Or operator.
-
And operator: All conditions separated by And need to be true for the exit setting to be in effect.
-
Or operator: Any of the conditions separated by Or can be true for the exit setting to be in effect.
-
Name: Enter a display name for the exit condition.
-
Map Exit to Skill: Select or search for a skill category and skill to map to this exit to better match consumers to agents with the relevant skill. For example, if you're using the Condition widget to verify input from a CollectInput variable, you can define an exit for "Press 1 for English support" and map it to the English skill.
Note: The skill category and skill must be added to the associated agent routing profile of the flow's queue. -
Next Widget: Select the destination widget if the exit condition is met.
No Match: Select the destination widget if the exit condition isn’t met.
|
Get Queue Data: Route based on queue data. | For details, see the article about routing based on queue data. |
For details, see the article about routing based on queue data.
|