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
Agent_Skill_Group_Half_HourService_Real_Time
AvailTimeToHalf: +12 sec.N/A
LoggedOnTimeToHalf: +12 sec
Sample Reports for Call Abandoned While On Hold Scenario
The table below explains fields in the agent23 report that are updated as a result of the events
in Call Scenario 1.
The table on the next page lists other WebView reports that are affected by the Call Abandoned
While On Hold scenario.
Table 19: How the agent23: Agent Performance Summary Half Hour Report is Affected by Call Scenario 1
Notes on the Column UpdatesColumns Affected
This field is incremented by 1. The value is derived from
Agent_Skill_Group_Half_Hour.CallsHandledToHalf
Completed Tasks Incoming: Handled
This value is derived from the calculation
Agent_Skill_Group_Half_Hour.HandledCallsTimeToHalf /
Completed Tasks Incoming: AHT
Agent_Skill_Group_Half_Hour.CallsHandledToHalf. For this scenario,
The numerator is increased by 59 secs and the denominator is increased
by +1.
This field is incremented by 1. The value is derived from
Agent_Skill_Group_Half_Hour.IncomingCallsOnHoldToHalf
Completed Tasks Incoming Hold Tasks:
Held Tasks
This value is derived from the calculation
(Agent_Skill_Group_Half_Hour.IncomingCallsOnHoldTimeToHalf /
Completed Tasks Incoming Hold Tasks:
Avg Hold Time
Agent_Skill_Group_Half_Hour.IncomingCallsOnHoldToHalf). For this
scenario, The numerator is increased by 40 secs and the denominator is
increased by +1.
The 10 secs from the that the agent talked on this call (from
Agent_Skill_Group_Half_Hour.TalkInTimeToHalf) is added to the
calculation that generates the value in this column.
Agent State Times: Active Time
The 40 secs. that this call was on hold is added to the value in this column,
which is derived from: Agent_Skill_Group_Half_Hour.HoldTimeToHalf
Agent State Times: Hold Time
This value is derived from:
(Agent_Skill_Group_Half_Hour.HoldTimeToHalf /
Agent State Times: Hold %
Agent_Skill_Group_Half_Hour.LoggedOnTimeToHalf). For this scenario,
the numerator is increased by 40 secs. and the denominator is increased
by 71 secs.
The 9 secs from Agent_Skill_Group_Half_Hour.WorkReadyTimeToHalf
is added to the calculation that produces this value. That calculation is
Agent State Times: Wrap Up Time
derived from:
(Agent_Skill_Group_Half_Hour.WorkNotReadyTimeToHalf +
Agent_Skill_Group_Half_Hour.WorkReadyTimeToHalf)
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
141
Chapter 9: Sample Call Scenario
Call Abandoned While On Hold Scenario