Media Type: All
Purpose: Routing decision to assign an interaction to a particular agent based upon their name, extension, or specific attribute.
Attributes:
Output Legs:
Common Use Case:
Media Type: All
Purpose: Used to make a routing decision based upon any data elements available. This is the most dynamic node in ECS and can be used to solve a majority of routing needs.
Filter Attributes:
Output Legs: The leg(s) for a Brach node is dynamic. The number of legs is dependent on the number of filters created.
Common Use Case:
Media Type: All
Purpose:
Routing decision based upon agent availability in the queue.
Output Legs:
Common Use Case:
This node is used in a scenario when the routing logic needs to ensure an Interaction will be presented to a Ready agent.
Media Type: All
Purpose: Routing decision based upon agent availability in the queue.
Output Legs:
Common Use Case:
Similar to the “Check BP Agents” Activity, this node provides more granular control on how to route interactions based upon Agent availability. If all agents are in a mix of unavailable and busy the call will follow the “All Busy” output leg.
Check Demand
Media Type: All
Purpose: Used to make a routing decision if particular Agent Skills/Demands have been activated.
Output Legs:
Common Use Case:
A check demand node can determine what demand/skill is currently active within the handling flow. It can then take action based on that demand, forwarding to a specific agent, BP or channel specific to that demand. When dealing with multiple demands/skills the “Check Demand” activity acts as a checkpoint to verify you are sending the interaction to the appropriate destination.
Media Type: All
Purpose: Routing decision that determines if the Contact Center or Channel or Business Process is currently open or closed based upon the defined Operating Hours and whether it is a “Special Day” (i.e. Holiday).
Output Legs:
Note:
The Operating Hours and Special Days can be defined at the Organization, Channel, or Business Process level. These hours are inherited down from the Organization to the Channel to the Business Process. If these hours are not defined at the BP level, the conditions will be taken from the Channel. If these hours not defined at the Channel level, the conditions will be taken from the Organization.
Tip: If your contact center is 24×7 the “from” and “to” times should be 12:00 AM and all days should be selected.
Media Type: All
Purpose: Make routing decision based upon pre-defined Overflow thresholds set for the BP
Attributes: These attributes will trigger a “Yes” or “No” call path based on the values set on the “Handling Timeous” tab of the Business Process.
Output Legs:
Common Use Case:
The “Check Overflow” Activity is used to route Interactions that waited or are estimated to wait longer than desired. The Handing Timeouts are defined for each Business Process. Once the threshold is met, an Interaction is often routed to another Business Process, Channel, or 10-digit phone number.
Media Type: All
Purpose: Removes any previously assigned agent from that interaction
Output Legs: N/A
Common Use Case:
This is used in conjunction with the “Assign Agent” and “Select Agent” Activities.
Media Type: All
Purpose: Marks the end of an interaction and terminates any open connection.
Common Use Case:
When the flow will reaches this Activity, the interaction immediately ends. This node is also used as a final endpoint to terminate a successful interaction.
Day of Week
Media Type: All
Purpose: Routing decision based upon the day of week (and Time Zone)
Attributes: Time Zone
Output Legs:
Common Use Case:
Route interactions based upon the day of the week regardless of the current time.
Media Type: Outbound Voice
Purpose: Generates an outbound call and route it based upon the connection status (answer, fax, answering machine, busy, etc.)
Output Legs:
Common Use Case:
Establish conversation is used for outbound dialer call flows. Disposition Codes are often assigned to each Output for reporting purposes.
The flow can be configured to play a message or leave a voicemail through the use of the “Simple Play” Activity on the Answering Machine leg.
Media Type: Telephony
Purpose: Forward the interaction to an internal or external number
Common Use Case:
Typically used send a caller to a 10-digit phone number.
Media Type: All
Purpose: Route Interaction to a specific agent
Common Use Case:
This Activity is used to send the Interaction directly to a specific agent bypassing a queue.
Media Type: All
Purpose: Route Interaction to a different Business Process for handling
Attributes: List of all Business Processes.
Common Use Case:
To forward an Interaction to a particular business process either based upon a selection from a “Prompt and Collect Selection” Activity or specific queueing thresholds.
Media Type: All
Purpose: Forwards that interaction to a different Business Process for handling based upon a variable.
Attributes: This will reference a variable which is specified via the Customer Data upload from the application portal. The template for this data upload can be found via the ECS portal. Once you assign a number along with Business Process name you can then begin to configure the call flow to reference this variable.
Output Legs:
Common Use Case:
Pass to Business Process by Name can route thousands of numbers dynamically in a single Activity through the use of the Customer Data upload to specify the Business Process associated with the number dialed (Destination DID) or originating from (Origin DID).
Media Type: All
Purpose: Forwards that interaction to a different channel for handling
Common Use Case:
This node would be used if you want to send the Interaction directly to another channel. This is commonly used to route to another menu structure.
Media Type: All
Purpose: Queue Interaction for agent assignment with multiple sub-flows triggered based upon time elapsed.
The inside of this Activity will look different depending on the type of Routing Strategy assigned to the BP – Skill Based or Agent Idle Time (assigned in the “General” tab).
Common Use Case:
The Queue node is the preferred method of routing calls to agents. Multiple Threshold Flows allow the customer’s experience to change as they wait by activating different routing treatments over time such as a Callback or Voicemail or an Overflow. The Queue also allows for true agent skilling by setting target Demand Filters and Search Periods to relax each skill requirement as the Interaction waits.
Inside View of Node: Skill Base
Inside View of Node: Agent Idle Time
This node is no longer in use.
Inside View of Node
Media Type: Voice
Purpose: Creates a Call Back Interaction where the system delivers an inbound Interaction to the Agent which is an Outbound Call to the party that requested it.
Attributes:
Common Use Case:
For any type of callback this node is necessary to initiate that Interaction into the Queue. The callback delay time serves as the initial timeframe in which the call will be re-presented back into queue (additional callback information).
Media Type: All
Purpose: This selects the best agent to handle the interaction and defines the queue experience for that customer. This Activity has been replaced by the Queue activity and should only be used in rare instances.
Output Legs:
Common Use Case:
Select agent will be used if you want to route a call to a specific agent. Possibly the agent who last spoke with that caller or one that is proficient for that particular customer (with the inclusion of “Assign Agent”) The select agent node can be configured to exit after a maximum waiting time or within the subflow of the node. Upon exiting best practice is for the caller to either be directed into voicemail or to the queue node to be answered.