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
To MonitorUse this WebView Category
Customer ExperienceService (page 175)
See Chapter 6 (page 99).
•
Enterprise (page 175)
•
Peripheral (page 176)
•
Array (page 177)
Agent Performance and ProductivitySkill Group (page 178)
System Operations
•
Base Only (page 178)
See Chapter 5 (page 77) and Chapter 6 (page 109)
•
Enterprise (page 179)
•
Peripheral (page 180)
System OperationsTrunk Group (page 182)
See Chapter 7 (page 109).
•
Network (page 182)
•
Peripheral (page 182)
Comparing Data across Reports
This section explains why certain report data cannot be compared for reasons of configuration,
scripting, or timing.
For another discussion of reporting data inconsistency, see Reporting Implications of Data Loss
and Component Fail over (page 143).
ACD and Unified ICM Reports
Data collected and presented on the Unified ICM WebView reports to measure customer
experience and agent performance is expected to differ from data collected and presented in the
ACD reports.
Unified ICM WebView reports give an enterprise-wide view of all your call centers. ACD
reports are specific to a particular call center.
Here are some of the reasons that cause the variations:
•
Differences due to timing and transmission delays
All times computed in WebView reports, such as various state transitions, are based upon
event arrival time at the Unified ICM Central Controller, not the actual event occurrence on
the ACD. Network transmission delays cause variations in reported times between reporting
data seen on WebView reports and ACD reports.
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
32
Chapter 2: Understanding Reporting
Comparing Data across Reports