User Guide
Table Of Contents
- Cover Page
- Table of Contents
- List of Figures
- Figure 1 : Central Controller
- Figure 2 : Peripheral and Peripheral Gateway
- Figure 3 : Administrative Workstation
- Figure 4 : WebView Server
- Figure 5 : Diagram of System Components
- Figure 6 : ICM Data Environment
- Figure 7 : Real-Time Data Moves to AW Local Database
- Figure 8 : Icons for Graphs and Tables
- Figure 9 : Deployment with Enterprise Routing
- Figure 10 : Sample Script for Enterprise Routing
- Figure 11 : Script Example for Agent Level Routing
- Figure 12 : Sample Script for Hybrid Routing
- Figure 13 : Agent State and Task State Relationship
- Figure 14 : Sample Routing Script for Information Gathering and Queuing
- Figure 15 : Call Type Data for Calls that Abandon after Call Type is Changed
- Figure 16 : Call Type Data for Calls that Abandon before Call Type is Changed
- Figure 17 : MultiChannel Options
- Figure 18 : Agent State Hierarchy
- Figure 19 : Call Abandoned While On Hold Scenario
- Preface
- Chapter 1: System Architecture and Reporting
- Chapter 2: Understanding Reporting
- Chapter 3: Understanding Routing and Queuing
- Chapter 4: Planning for Reporting
- Planning for Reporting at Unified ICM Setup
- Planning for Your Deployment
- Planning for Configuration and Scripting
- Planning for Agent Reporting
- Planning for Call Types
- Planning for Custom Reporting
- Planning for the HDS
- Planning for Enterprise Routing and Enterprise Reporting
- Planning for Service and Enterprise Service Reporting
- Planning for Service Level
- Planning for Short Calls
- Planning for Skill Groups and Enterprise Skill Groups
- Planning for Transfer and Conference Reporting
- Planning for Translation Routing
- Planning for Unexpected Scripting Conditions
- Planning for VRU Application Reporting
- Chapter 5: Reporting on Agents
- What Agent Data do you Want to See?
- Reporting on Agent Activity in Skill Groups
- Reporting on Agent States
- Reporting on Average Speed of Answer for Agents and Skill Groups
- Reporting on Agent Logout Reason Codes
- Reporting on Agent Not Ready Reason Codes
- Reporting on Agent Task Handling
- Reporting on Agent Performance for Outbound Option Dialing Campaign Calls
- Reporting on Agent Redirection on No Answer
- Reporting on Agent Call Transfers and Conferences
- Reporting on Agent Teams
- Chapter 6: Reporting on Customer Experience
- Chapter 7: Reporting on Operations
- Chapter 8: Reporting in a MultiChannel Environment
- Chapter 9: Sample Call Scenario
- Chapter 10: Reporting Implications of Data Loss and Component Failover
- Chapter 11: Troubleshooting Report Data
- Appendix A: List of All Unified ICM Report Templates
- Appendix B: Reporting Entities and Databases
- Appendix C: Configuration and Scripting for Reporting
- Configuration for Agent Reporting
- Configuring Call Types
- Configuration and Scripting for Conferences and Transfers
- Configuring Services and Enterprise Services
- Configuring and Scripting for Service Level Threshold and Type
- Configuring Short Calls
- Configuring Skill Groups and Enterprise Skill Groups
- Configuration and Scripting for the VRU
- Configuring Translation Routes
- Index
•
Network VRU1 can be any Service Control VRU that can be used to provide initial call
treatment and serve as the telephony platform for queuing calls across all call center ACDs.
VRU1 can also be used for information gathering and self-service.
Routing and Scripting
In this deployment, Unified ICM software uses real-time reporting statistics gathered from the
different peripherals (ACDs) to make routing decisions to route calls to the ACD at a site that
is best suited to answer the call.
The following routing capabilities can be provided in this deployment.
•
Site Based Routing: The Unified ICM software, using the Unified ICM routing capabilities,
can use real-time reporting statistics gathered from the different peripherals (ACDs) to make
routing decisions to route calls to the ACD at a site that is best suited to answer the call.
Site selection can be scripted using real time Service and Skill Group metrics provided by
the Peripheral Gateway (PG).
Several metrics can be used to make the selection such as Agent availability, CallsInProgress,
and Minimum Expected Delay (MED) calculation.
Note: The Unified ICM scripts provide a predefined MED (Minimum Expected Delay)
calculation that can be used only with ICM Services.
•
Agent Level Routing: Not Supported.
A typical script used to route calls in this deployment is illustrated and explained below.
About this script:
•
The script is associated with a Call Type. The example is shown for an enterprise that has
two sites (Boston and New York), each running a call center.
•
The call center at either site can provide call treatment to handle “Support” calls. “Support”
is configured as a Service in Unified ICM.
•
Both call centers have agents trained to handle calls for either “Laptop Support” or “Server
Support”. These are configured as Skill Groups in Unified ICM. The relationship of the
Service to Skill Groups is configured as Service Members in Unified ICM.
•
The Boston call center has an Avaya ACD (peripheral) connected with an Avaya PG, and
New York call center has an Aspect ACD (peripheral) connected with the Aspect PG. Service
and Skill Groups are configured for each peripheral in Unified ICM.
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
44
Chapter 3: Understanding Routing and Queuing
Deployments with Enterprise Routing