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

•
Set up a one Call Type to collect statistics prior to the queue (that is, the initial Call Type
designated for the script via Call Type mapping.
•
Set up other Call Types used specifically to collect queue and agent statistics.
•
In your routing scripts, include the Requalify or Call Type nodes to submit the call to the
Call Type used to collect queuing information.
•
Calls can queue to more than skill group and service level metrics are updated for each skill
group to which a single call queues.
Service Levels could be adversely affected if calls abandon within or outside the service level
threshold in such cases. Consider queuing to a single skill group if you include abandons in
your Service Level calculations and don’t want abandons to affect Service Levels adversely.
If you follow these recommendations, the first Call Type to which the call was initially mapped
will gather statistics before the call is queued to the skill group. The script will then pass the
call to the Call Type set up specifically to collect information after the call is queued to the skill
group.
See also:
Planning for Service Level (page 69)
Reporting on Service Level (page 105)
Configuring Short Calls
A short call is a call that is either abandoned or answered very quickly.
You can configure the number of seconds for an abandoned short call and the number of seconds
for an answered short call.
To configure abandoned short calls:
1. Select Tools > Explorer Tools > PG Explorer.
2. Click Retrieve and select a peripheral.
3. Click the Peripheral tab.
4. Set Abandoned Call Wait Time to a value in seconds.
This value is the length of time during which terminated calls are considered abandoned.
Note: If you do not want to track abandoned calls, leave this field blank.
To configure answered short calls:
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
196
Configuration and Scripting for Reporting
Configuring Short Calls