Exits

Time-based Exits

On the Exits tab, you can configure several exits to allow routing according to calendar-based rules. These rules will only apply to the phone numbers associated with the flow.

Timezone​: Define to which timezone the rule will be applied.

Time range​: The options​ allow you to define whether specified times represent business hours or non-business hours in reporting. Note: You must select the option "Report as: Inside Business Hours", and configure the respective hours, so that the calls are reported as "Inside Business Hours". In case the time ranges you are defining are incompatible, (for example, if the “To” time occurs before the “From” time), a warning message will be displayed. In addition, please be aware that whenever an overnight time range is defined, Studio will consider the following day of the week for the overnight time range, so the calls will be routed through the desired exit from, for example, 9:00 pm of a given day until 2:00 am of the following day. Note: The system doesn't route calls based on this parameter. You must still use the Send to menu to define where calls will be sent.

Add time range: ​Add more time ranges to the previously defined ones.

Exit name​: Choose a name to be given to an exit and to be seen at the flow level.

Send to: ​Choose the next component for the call to be routed to in case the rule is applied.

Add exit:​ If needed, you can create more exits and define rules to be applied to them.

No Match

If none of the conditions are met and there is no match, you can define what the next component will be.

📘

Notes

• When a call exits through the No match exit, it will be reported as outside business hours.
• When there are several “Time Based Rules” steps in the same path of a Studio flow, the last one to be executed is the one used to calculate if it is inside or outside business hours.

Error Handling

You can use the “Error Handling” section to define the behavior for unexpected failure during the execution of a component. For more information on this section, please refer to the "Error handling" documentation.