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

System Architecture and Reporting
Cisco Unified ICM software distributes incoming telephone calls and web-initiated requests to
the appropriate available agent across multiple contact centers.
It does this by tracking activity on all monitored devices. This includes tracking the current call
handling state of each agent, the number of agents in a particular state, and the time that agents
spend in these states.
Unified ICM also collects data about the call status and activity at each contact center, such as
the number of calls in progress, number of calls in queue, calls handled, and how calls were
routed.
These collected data, which are essential to intelligent enterprise routing, are also made available
for enterprise-wide reporting of agent performance, customer experience, and system operations.
This chapter provides a high-level overview of key system components that make up the Unified
ICM architecture and explains how those components are relevant for routing and reporting.
Note: For clarity, the content and illustrations in this chapter describe the interaction of logical
components. They do not represent physical models, which are typically provisioned in a
duplexed manner.
Note also that the terms 'call', 'task', and 'contact' are used generically and interchangeably
throughout this guide to refer to traditional telephone calls as well as to communications such
as e-mails and text chats from Cisco multi-media channels.
This chapter contains the following topics:
•
Central Controller, page 8
•
Peripherals and Peripheral Gateways, page 9
•
Administrative Workstations, page 15
•
Historical Data Server, page 16
•
WebView Server, page 17
•
Agent/Supervisor Desktops, page 18
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
7
Chapter 1