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

How Calls that Abandon Affect Call Type Reporting
This section explains how calls that abandon affect Call Type reporting when a Network VRU
is used for enterprise queuing and translation routing.
There are three types of abandon metrics: abandons at the VRU (prompt or self service), abandons
in the Enterprise queue, and abandons at the agent.
Unified ICM tracks the abandon counts for each of these abandons separately. The time spent
before these calls abandoned is also tracked.
The value represented by the “Aban” column on the Call Type reports provides total abandon
count for the Call Type, and includes calls that abandoned while at the VRU (prompting or self
service), calls that abandon in both Enterprise queue and the ACD queue, and calls that abandoned
while ringing at the agent's phone or en route to the agent's phone. This value is derived from
the TotalCallsAbandToHalf database field.
Reports also provide average time spent by these abandoned calls in the “Avg Aban Delay
Time” field. This field represents the average delay time of all abandoned calls that ended in
this Call Type during the current half-hour interval. This is derived from
Call_Type_Half_Hour.CallDelayAbandTimeToHalf /
Call_Type_Half_Hour.TotalCallsAbandToHalf.
To separate information gathering and queuing statistics, you can also determine the time spent
by a call only in the Call Type where the call abandoned. This is tracked in the
CTDelayTotalAbanTimeToHalf database field. This includes only the time spent in the Call
Type where the call abandoned and not all Call Types.
Consider this example:
•
A call spends 30 seconds in the information gathering Call Type, "Info_Call_Type".
•
The script then changes the Call Type to the queuing Call Type say Queue_Call_Type and
the call is queued.
•
After 15 seconds waiting in queue the call is abandoned.
In this case, the total time spent by the call before abandoning is 45 seconds. However the time
spent by the call in the “Queue_Call_Type” where the call abandoned is 15 seconds. The Call
Type statistics for the “Queue_Call_Type” is updated as follows:
Queue_Call_Type
•
CallDelayAbandTimeToHalf = 45 seconds
•
CTDelayTotalAbanTimeToHalf = 15 seconds.
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
104
Chapter 6: Reporting on Customer Experience
Reporting on Abandoned Calls