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

For Enterprise Queuing, when the agent activates the transfer or conference button and selects
a number to which to transfer or conference the call, the dialed number is sent to the Router
from the agent's PG. This dialed number determines the Call Type, which in turn selects the
transfer routing script. The Unified ICM script must include a Queue to Skill Group node that
references the appropriate skill group based on the dialed number to which the call is to be
queued.
If an agent is available in the selected skill group, a message is sent to the source agent's PG,
containing a label or dialable number. The PG transfers the call from the source agent’s phone
to the target agent using the label returned from the Central Controller. For these types of
transfers and conferences, TransferOut or ConferenceOut is incremented for the source agent
and TransferIn or ConferenceIn is incremented for the target agent.
If no agents are available for a transfer in the selected skill group, the Router sends the source
agent's PG the label to forward the call to the VRU. For these types of transfers and conferences,
TransferOut or ConferenceOut is incremented for the source agent.
How Database Fields Are Affected by Transfers and Conferences
Transfers and conferences affect fields in the Agent_Skill_Group_Half_Hour database table.
The TransferIn field is incremented for the target agent if all of the following conditions are
true:
•
The call was transferred (blind or consultative) by an agent to a Unified ICM Call Type script
or to an application script on the ACD that checks for agent availability
•
For blind transfers only, an agent within the same peripheral was available at the time that
the transfer was initiated.
The ConferenceIn field is incremented for the target agent receiving the conference call if all
of the following conditions are true:
•
The call was conferenced by an agent to a Unified ICM Call Type script or to an application
script on the ACD that checks for agent availability.
•
An agent within the same peripheral was available at the time that the conference was initiated.
The TransferOut field is incremented for the agent initiating either a blind or consultative transfer
when the initiating agent disconnects from the transfer.
The Conference Out field is incremented for the agent initiating a conference when the initiating
agent disconnects from the conference.
The ConsultativeCalls field is incremented for the initiating agent when the consultative call
disconnects and wrap-up is complete. Note that consultative transfer is not supported for systems
using CVP as the VRU and therefore this field is never incremented if you are using CVP.
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
94
Chapter 5: Reporting on Agents
Reporting on Agent Call Transfers and Conferences