(Marked this version for translation) |
(Updated via BpDeleteTranslateTags script) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | = Omnichannel Routing= | |
Bright Pattern Contact Center enables contact center agents to handle multiple interactions of different media types simultaneously. The agent’s availability to handle an interaction is determined via a capacity model that takes into account how much of the agent’s capacity is occupied by interactions of various media types that the agent is already handling, how much spare capacity the agent must have to be able to handle an interaction of a specific media type, and relative priorities of various media types. | Bright Pattern Contact Center enables contact center agents to handle multiple interactions of different media types simultaneously. The agent’s availability to handle an interaction is determined via a capacity model that takes into account how much of the agent’s capacity is occupied by interactions of various media types that the agent is already handling, how much spare capacity the agent must have to be able to handle an interaction of a specific media type, and relative priorities of various media types. | ||
| − | |||
To configure agent capacity, select the '''Omni-Channel Routing''' option from the '''Call Center Configuration''' menu. | To configure agent capacity, select the '''Omni-Channel Routing''' option from the '''Call Center Configuration''' menu. | ||
| − | |||
[[File:Omni-Channel-Routing-50A.png|thumb|800px|center|Call Center Configuration > Omni-Channel Routing]] | [[File:Omni-Channel-Routing-50A.png|thumb|800px|center|Call Center Configuration > Omni-Channel Routing]] | ||
| − | == Screen Properties == | + | == Screen Properties == |
The ''Omni-Channel Routing'' screen properties are described as follows. | The ''Omni-Channel Routing'' screen properties are described as follows. | ||
| − | === Capacity share taken by each interaction === | + | === Capacity share taken by each interaction === |
This setting specifies the percentage of total agent capacity occupied by a single interaction of the given media type. | This setting specifies the percentage of total agent capacity occupied by a single interaction of the given media type. | ||
| − | |||
In the default settings shown, the capacity share is: | In the default settings shown, the capacity share is: | ||
* Voice: 100% | * Voice: 100% | ||
| Line 23: | Line 20: | ||
* Email: 25% | * Email: 25% | ||
| − | |||
Using those capacity share settings as an example, an agent handling a single call will be 100% busy, while an agent handling a single chat session will have 75% spare capacity (i.e., 100% – 25% = 75%). | Using those capacity share settings as an example, an agent handling a single call will be 100% busy, while an agent handling a single chat session will have 75% spare capacity (i.e., 100% – 25% = 75%). | ||
| − | |||
For multimedia interactions such as rich contact, the total capacity share is the sum of capacity shares of all media types involved. | For multimedia interactions such as rich contact, the total capacity share is the sum of capacity shares of all media types involved. | ||
| − | === Required spare capacity to receive interaction === | + | === Required spare capacity to receive interaction === |
This setting specifies the percentage of spare capacity that the agents must have to be delivered an interaction of the given media type. | This setting specifies the percentage of spare capacity that the agents must have to be delivered an interaction of the given media type. | ||
| − | |||
In the default settings shown, the required spare capacity is: | In the default settings shown, the required spare capacity is: | ||
* Voice: 50% | * Voice: 50% | ||
| Line 39: | Line 33: | ||
* Email: 100% | * Email: 100% | ||
| − | |||
Using those required spare capacity settings as an example, an agent handling three service chats may still receive another chat, but not email because the agent's spare capacity of 100% is only sufficient for the agent to get one more chat. | Using those required spare capacity settings as an example, an agent handling three service chats may still receive another chat, but not email because the agent's spare capacity of 100% is only sufficient for the agent to get one more chat. | ||
| − | === Precedence === | + | === Precedence === |
''Precedence'' is the order in which interactions of the given media type will be distributed to agents relative to interactions of the other media types (i.e., when competing for the same available agent). | ''Precedence'' is the order in which interactions of the given media type will be distributed to agents relative to interactions of the other media types (i.e., when competing for the same available agent). | ||
| − | |||
In the default settings shown, the precedence is: | In the default settings shown, the precedence is: | ||
* Voice: 1 | * Voice: 1 | ||
| Line 52: | Line 44: | ||
* Email: 3 | * Email: 3 | ||
| − | |||
Using those precedence settings as an example, if an agent becomes simultaneously available for a chat and an email interaction waiting in queue, the chat interaction will be delivered to that agent first, regardless of how long either of those interactions has been waiting in queue. | Using those precedence settings as an example, if an agent becomes simultaneously available for a chat and an email interaction waiting in queue, the chat interaction will be delivered to that agent first, regardless of how long either of those interactions has been waiting in queue. | ||
| − | |||
This parameter can be set to the same value only for voice and chat. If it is set to the same value, the delivery order of voice and chat interactions will be determined by only their position in queue. Generally, it is recommended that each media type has a different precedence value. | This parameter can be set to the same value only for voice and chat. If it is set to the same value, the delivery order of voice and chat interactions will be determined by only their position in queue. Generally, it is recommended that each media type has a different precedence value. | ||
| − | == How the System Routes Interactions == | + | == How the System Routes Interactions == |
When a new interaction arrives and its skill requirements are identified, the system will look for agents with matching skills and sufficient spare capacity (i.e., occupied at less than 100 – ''Required spare capacity to receive interaction'' of the given media type). | When a new interaction arrives and its skill requirements are identified, the system will look for agents with matching skills and sufficient spare capacity (i.e., occupied at less than 100 – ''Required spare capacity to receive interaction'' of the given media type). | ||
| − | |||
If multiple agents satisfying these conditions are found, the system will select one of these agents using the following criteria in the specified order: | If multiple agents satisfying these conditions are found, the system will select one of these agents using the following criteria in the specified order: | ||
| − | |||
# The agent with the highest skill level(s); the highest level is determined by the following formula:<br /><br />''Service Skill Level'' x 100 + (''sum of Auxiliary Skill Levels'') / 100 + ''no. of auxiliary skills''.<br /><br /> | # The agent with the highest skill level(s); the highest level is determined by the following formula:<br /><br />''Service Skill Level'' x 100 + (''sum of Auxiliary Skill Levels'') / 100 + ''no. of auxiliary skills''.<br /><br /> | ||
# The least busy agent at the moment; based on ''Capacity share taken by each interaction'' currently processed by this agent<br /><br /> | # The least busy agent at the moment; based on ''Capacity share taken by each interaction'' currently processed by this agent<br /><br /> | ||
| Line 72: | Line 60: | ||
| − | |||
When an agent’s load decreases (an agent completes processing of an interaction), the system will look for interactions with matching skill requirements that the agent may have sufficient capacity to handle. The interactions will be considered in the order of ''Precedence''. If multiple interactions within the same precedence are found, the system will select one of these interactions using the following criteria: | When an agent’s load decreases (an agent completes processing of an interaction), the system will look for interactions with matching skill requirements that the agent may have sufficient capacity to handle. The interactions will be considered in the order of ''Precedence''. If multiple interactions within the same precedence are found, the system will select one of these interactions using the following criteria: | ||
| − | |||
* For voice and chat, the interaction with the highest value of ''(priority x wait time)''; for more information, see the description of the [[scenario-builder-reference-guide/SetPriority|Set Priority]] block in the ''Scenario Builder Reference Guide'' | * For voice and chat, the interaction with the highest value of ''(priority x wait time)''; for more information, see the description of the [[scenario-builder-reference-guide/SetPriority|Set Priority]] block in the ''Scenario Builder Reference Guide'' | ||
* For emails, interaction with the highest priority; in case of multiple interactions of the same priority, the closest one to the [[contact-center-administrator-guide/EmailTab|SLA breach]]. | * For emails, interaction with the highest priority; in case of multiple interactions of the same priority, the closest one to the [[contact-center-administrator-guide/EmailTab|SLA breach]]. | ||
* For preview records, the record is determined by the [[contact-center-administrator-guide/ListsTab|order in which records are selected within a campaign]]. | * For preview records, the record is determined by the [[contact-center-administrator-guide/ListsTab|order in which records are selected within a campaign]]. | ||
| − | |||
For more information about how routing happens within scenarios, see the ''Scenario Builder Reference Guide'', section [[Scenario-builder-reference-guide/FindAgent|Find Agent]]. | For more information about how routing happens within scenarios, see the ''Scenario Builder Reference Guide'', section [[Scenario-builder-reference-guide/FindAgent|Find Agent]]. | ||
| − | |||
| − | |||
| − | |||
Latest revision as of 04:08, 29 May 2024
Omnichannel Routing
Bright Pattern Contact Center enables contact center agents to handle multiple interactions of different media types simultaneously. The agent’s availability to handle an interaction is determined via a capacity model that takes into account how much of the agent’s capacity is occupied by interactions of various media types that the agent is already handling, how much spare capacity the agent must have to be able to handle an interaction of a specific media type, and relative priorities of various media types.
To configure agent capacity, select the Omni-Channel Routing option from the Call Center Configuration menu.
Screen Properties
The Omni-Channel Routing screen properties are described as follows.
This setting specifies the percentage of total agent capacity occupied by a single interaction of the given media type.
In the default settings shown, the capacity share is:
- Voice: 100%
- Preview: 100%
- Chat: 25%
- Email: 25%
Using those capacity share settings as an example, an agent handling a single call will be 100% busy, while an agent handling a single chat session will have 75% spare capacity (i.e., 100% – 25% = 75%).
For multimedia interactions such as rich contact, the total capacity share is the sum of capacity shares of all media types involved.
Required spare capacity to receive interaction
This setting specifies the percentage of spare capacity that the agents must have to be delivered an interaction of the given media type.
In the default settings shown, the required spare capacity is:
- Voice: 50%
- Preview: 50%
- Chat: 25%
- Email: 100%
Using those required spare capacity settings as an example, an agent handling three service chats may still receive another chat, but not email because the agent's spare capacity of 100% is only sufficient for the agent to get one more chat.
Precedence
Precedence is the order in which interactions of the given media type will be distributed to agents relative to interactions of the other media types (i.e., when competing for the same available agent).
In the default settings shown, the precedence is:
- Voice: 1
- Preview: 4
- Chat: 2
- Email: 3
Using those precedence settings as an example, if an agent becomes simultaneously available for a chat and an email interaction waiting in queue, the chat interaction will be delivered to that agent first, regardless of how long either of those interactions has been waiting in queue.
This parameter can be set to the same value only for voice and chat. If it is set to the same value, the delivery order of voice and chat interactions will be determined by only their position in queue. Generally, it is recommended that each media type has a different precedence value.
How the System Routes Interactions
When a new interaction arrives and its skill requirements are identified, the system will look for agents with matching skills and sufficient spare capacity (i.e., occupied at less than 100 – Required spare capacity to receive interaction of the given media type).
If multiple agents satisfying these conditions are found, the system will select one of these agents using the following criteria in the specified order:
- The agent with the highest skill level(s); the highest level is determined by the following formula:
Service Skill Level x 100 + (sum of Auxiliary Skill Levels) / 100 + no. of auxiliary skills. - The least busy agent at the moment; based on Capacity share taken by each interaction currently processed by this agent
- The longest idle agent; based on the sum of times of continuous Ready and Not Ready states since the last handled interaction
- The least occupied agent; based on agent occupancy since login; occupancy is defined as:
Busy time / login time – Not Ready time
In that instance, Busy time is the sum of handling times of all interactions processed by the agent multiplied by Capacity share taken by each interaction, depending on the media type.
When an agent’s load decreases (an agent completes processing of an interaction), the system will look for interactions with matching skill requirements that the agent may have sufficient capacity to handle. The interactions will be considered in the order of Precedence. If multiple interactions within the same precedence are found, the system will select one of these interactions using the following criteria:
- For voice and chat, the interaction with the highest value of (priority x wait time); for more information, see the description of the Set Priority block in the Scenario Builder Reference Guide
- For emails, interaction with the highest priority; in case of multiple interactions of the same priority, the closest one to the SLA breach.
- For preview records, the record is determined by the order in which records are selected within a campaign.
For more information about how routing happens within scenarios, see the Scenario Builder Reference Guide, section Find Agent.