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

Half-hour Boundary Issues
Counts that would typically match up for a day, such as CallsOffered and CallsHandled, might
not always match up over specific half-hour intervals. This is because the counts for some data
elements might be increased across half-hour boundaries.
Consider this example: at 8:55, a call comes in to the contact center and is answered by an agent.
The agent completes the call at 9:05.
•
In the historical database, the call is counted as offered in the 8:30:00 to 8:59:59 interval.
•
The call is counted as handled in the 9:00:00 to 9:29:59 interval.
•
If you run a report for the 9:00:00 to 9:29:59 interval, it appears that tasks handled does not
equal tasks offered for the interval.
You also might notice that tasks offered does not equal task abandoned + tasks handled for a
half-hour interval. Tasks offered reflects the number of calls and tasks that were offered to
agents in this interval, while tasks handled and tasks abandoned might include calls that were
offered in the last interval and completed in this interval. Some historical report templates group
statistics into "Completed Tasks" to indicate that the statistics represent all calls and tasks that
completed in this half-hour interval.
In general, half-hour boundary issues are reduced if you run daily reports. However, if your
contact center runs 24 hours a day, you might still notice half-hour discrepancies for the 11:30:00
to 11:59:59 and 12:00:00 to 12:29:59 intervals.
Skill Group and Enterprise Skill Group Reports
You can expect double counting in Enterprise Skill Group reports when a call is queued to
multiple skill groups on the same peripheral, and those skill groups are associated with the same
Enterprise Skill Group.
See also Planning for Enterprise Skill Group Reporting (page 72).
Call Type and Skill Group/Service Reports
Do not compare Call Type reports to Skill Group or Service reports. Skill Group and Service
reports might have statistics for calls that were routed directly to the ACD and not routed by
Unified ICM.
Certain statistics are computed differently when Enterprise queue are used. See Chapter 3 (page
37).
In Unified ICME with ACD environments, services define call treatment. All skill groups belong
to specific services and, therefore, skill group data rolls up to the service. Reports for services
provide call treatment information for all of the skill groups assigned to those services.
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
34
Chapter 2: Understanding Reporting
Comparing Data across Reports