Cisco Cisco IP Contact Center Release 4.6.1 User Guide

Page of 173
Using a separate call type not only enables you to redirect calls that are not answered to a
script that queues the calls at a higher priority, but also enables you to report on activity for
the Redirection on No Answer call type. Viewing data for this call type helps you gain insight
into the number of calls that redirect on no answer and to see how the calls are finally handled.
Planning for Redirection on No Answer Reporting with Customer Voice Portal
Note: In Releases prior to Release 3.0, the Customer Voice Portal (CVP) product was named
Internet Service Node (ISN)
If you are implementing Redirection on No Answer and have deployed CVP as the VRU, follow
these guidelines to obtain accurate and useful data from Redirection on No Answer situations.
Decide how long a call ring before being redirected to a new agent or skill group.
You configure the ring no answer time in two places: CVP software and ICM/IPCC software.
Configure the CVP Ring No Answer timeout in the CVP Voice Browser Administration
application. This timer will be used to requery the call if the call is not answered. Configure
the ICM/IPCC Agent Desk Settings Ring no answer time. This time determines when the
agent is made Not Ready so that additional calls are not assigned to the agent. CVP Ring No
Answer timeout be approximately 2 seconds higher than the Ring no answer time configured
in Agent Desk Settings. The CVP Ring No Answer timeout also be less than 30 seconds
because the ICM/IPCC Central Controller waits up to 30 seconds for a response to arrive
from the CVP. If the response is not received within 30 seconds, the call fails.
Within the routing script, plan to enable the Target Requery option in the routing script.
Target Requery is available from the Queue, Queue to Agent, Label, Select, and RouteSelect
nodes. Change the call type in the script after the requery and create a path for calls that are
requeried within the script. Queue calls that are requeried at a higher priority.
Using a separate call type enables you to report on activity for that call type. Viewing data
for this call types helps you gain insight into the number of calls that are requeried and to
see how the calls are finally handled.
Planning for VRU Application Reporting
For all deployments, follow these guidelines to obtain accurate and useful data for VRU
applications:
If you have Self-Service or Information Gathering IVR applications and want to separate
self-service/digit collection metrics from queuing metrics, plan to change the call type in the
routing script before the call is queued. This ensures that you can report on both the
self-service/digit collection section of the call and the queuing section of the call using Call
Type reports.
Reporting Guide for Cisco Unified Contact Center Enterprise & Hosted 7.5(1)
18
Chapter 1: Planning the IPCC Enterprise System to Meet Reporting Needs
Planning for Redirection on No Answer Reporting with Customer Voice Portal