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

Call Type ASA is applicable only when calls are translation routed and includes time spent in
the Enterprise Queue as well as time spent in the ACD queue.
ASA for the Service is computed based on the AnswerWaitTime as reported from the peripheral.
This includes the time spent on the ACD after the call was offered up until the time the call was
answered. If an Enterprise Queue is used, ASA reported for the service does not include time
spent in the Enterprise Queue.
Reports that show ASA
These are some reports that contain ASA statistics for Call Types and Services:
•
caltyp20: Call Type Real Time Report
•
caltyp21: Call Type Half Hour
•
persvc07: Peripheral Service Tasks, Averages and Service Levels Real Time Report
•
entsvc08: Task and Agent Status Real Time Report
For the complete list of templates, see Appendix A (page 165).
Reporting on Abandoned Calls
A call is considered abandoned if the caller hangs up before being connected to an agent.
A high number of abandoned calls might be an indication that callers are waiting in the queue
for too long.
Abandoned calls are reported against the following:
•
Service
•
Call Types
•
Skill Groups
Service reports provide cumulative statistics for all abandoned calls. Call Type reports provide
additional visibility on where calls are abandoning
Note: If a call abandons before the Abandon Call Wait Time threshold, it is considered a Short
Call (page 116).
For example, if you configure the abandoned call wait time for 10 seconds, and a caller
disconnects at nine seconds, that call is a short call—it is not considered offered or abandoned.
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
103
Chapter 6: Reporting on Customer Experience
Reporting on Abandoned Calls