Branching node types

This node type allows branching based on an area-code group. Country codes or area codes may be organised into groups, which may be used to route the call to the correct part of the call flow. A best-match scheme for routing based on the CLI of the originating number is used.

The following parameters can be set:

Parameter	How many?	Type	Description
Area Code	1	AreaCodeGroup	The area-code group to match. An area-code group can contain numbers, geographical locations and postcodes. Note: If required, this parameter can be set to User-configurable so that it can accept a value specified by a company administrator. For more information, see Adding user-configurable values.

The following branches can be taken:

Branch	How many?	Description
Matched	1	The branch to take if the area-code group is matched (the area code of the originating call falls within the defined group).
Not Matched	1	The branch to take if the area-code group is not matched.

Note: If you have call barring turned on, this will not work if an international number books a Callback. To ensure you have blocked calls to outbound numbers, use the Area Codes feature and set up a +44 area code.  You can then create an outbound call flow using Branch On Area Code to ensure you are only calling national numbers.

This node type allows branching based on a list of destination number prefixes, enabling specific outbound numbers to be blacklisted (blocked) or whitelisted (allowed).

To branch on specific destination number prefixes, you need to add different string variables.

The following parameters can be set:

Parameter	How many?	Type	Description
Number List	1	Number List	The number list to match. Note: If required, this parameter can be set to User-configurable so that it can accept a value specified by a company administrator. For more information, see Adding user-configurable values.
Number	0 to ###	String	A destination number prefix to match.

The following branches can be taken:

Branch	How many?	Description
Matched	0 to 10	The branch to take if a specific destination number prefix in the number list is matched.
Not Matched	1	The branch to take if the number list is not matched.

To create and use the Branch on Number List node simply follow these steps:

• Ensure the required Number List is available on the system – For more information on Number Lists please see this article
• Create a ‘Branch on Number List’ node from the Node Library and add it to your Call Flow
• Click the title of the Branch on Number List node to open its parameters
• Choose the required Number List from the drop down ‘Number List’ menu
• Connect the Matched and Not Matched branches to complete the caller’s journey as required

This node type allows branching based on a time-range value. Calls may be routed based on the time of day and the day of the week, allowing different routing behaviour inside and outside of business hours.

Note: Time ranges can be added in one of two ways: by using tags data (the legacy method) or by using start and end dates/times. This node type is used for time ranges that use tags data.

The following parameters can be set:

Parameter	How many?	Type	Description
Legacy Time Range	1	TimeRange	The time range to match. Note: If required, this parameter can be set to User-configurable so that it can accept a value specified by a company administrator. For more information, see Adding user-configurable values.

The following branches can be taken:

Branch	How many?	Type	Description
Not Matched	1		The branch to take if the current time does not fall within the time range.
Match	1 to 30		The branch to take if the current time falls within the time range.
Tag		String	The rule to match. Note: If required, this parameter can be set to User-configurable so that it can accept a value specified by a company administrator. For more information, see Adding user-configurable values.

This node type allows branching based on a time-range value. Calls may be routed based on the time of day and the day of the week or date in the month, allowing different routing behaviour inside and outside of business hours.

Note: Using the Contact web interface, administrators can add time ranges in one of two ways: either by configuring start and end parameters (days/dates and times) or by configuring tags data (the legacy method). This node type is used for time ranges that use start and end parameters.

In this node, you may select predefined time ranges to be used as branches.

Note: The branches are attempted to be matched in the order in which they are defined in the node, so you must ensure that the branches are in the correct order of priority. This allows for quick changes to the order of time ranges without having to add and delete branches.

There are no parameters for this node type.

The following branches can be taken:

Branch	How many?	Type	Description
Match	1 to 30		The branch to take if the current time falls within the time range.
Time Range		TimeRange	The time-range rule to match. Note: If required, this parameter can be set to User-configurable so that it can accept a value specified by a company administrator. For more information, see Adding user-configurable values.
Not Matched	1		The branch to take if the current time does not fall within the time range.