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 run Enterprise Service reports, use the WebView Services by Enterprise report templates
(page 175).
See also
•
Configuring Services and Enterprise Services (page 194)
•
Service Reports (page 101)
Planning for Service Level
Service level help you to set and measure goals for answering calls. Service levels are
configurable.
Two important configuration parameters contribute to the calculation of Service Level:
Service Level Threshold (page 69)
Service Level Type (page 70)
See also:
•
Configuring and Scripting for Service Level Threshold and Type (page 195)
•
Reporting on Service Level (page 105)
Service Level Threshold
The service level threshold is the number of seconds you set as a goal for connecting a call with
an agent.
For example, your goal might be to answer 80% calls within two minutes. In this case, you
would set the Service Level Threshold to 120 seconds. Reports show you the percentage of calls
that are answered within that time threshold, enabling you to see whether you are meeting your
goal.
This value is configured at the peripheral and at the service. Typically, these values match.
•
When you set up a peripheral, you can specify a default service level threshold for all services
associated with that peripheral.
Different peripherals use slightly different formulas to calculate service level. Unified ICM
software provides a uniform calculation across all peripherals.
•
When you set up each service, you can choose to either use the default threshold set for the
peripheral or specify a threshold for the service itself in the Service Level Threshold field.
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
69
Chapter 4: Planning for Reporting
Planning for Service Level