Pre-routing is a routing decision that is executed before the call terminates at the call center. With pre-routing, the Network Interface Controller (NIC) receives the route request from the Interexchange Carrier (IXC) and passes the call information along to Unified CCE software.

Unified CCE bases pre-routing decisions on real-time data gathered by the PGs at the call center sites. Unified CCE then runs the appropriate script that defines how the call is to be routed.

A pre-routing request therefore determines the initial destination for a call.

Post-routing is a routing decision made after the call has initially been processed at a VRU or call center. Post-routing enables Unified ICM to process calls when an ACD, VRU, or PBX generates a route request via the PG.

Unified ICM executes scripts to process the route request and return the destination address. This directs the ACD/PBX to send the call to an agent, skill group, service or Call Type in the same call center or at a different call center. In making a post-routing decision, Unified ICM software can use all the same information and scripts used in pre-routing.

A post-routing is sent by the peripheral to refine the original route or redirect the call.

Note	Your ACD Supplement Guide describes the features of Unified ICM post-routing available with the ACD, as well as any considerations you should be aware of when using post-routing or Translation Routing on the PG.

Translation routing is the term used when additional information is sent along with a call.

This type of routing is necessary because the carrier can deliver voice, but has no way to deliver data to the peripheral.

Unified CCE software works with the PG to deliver the call to the final destination on the peripheral and to ensure that the appropriate information collected for the call is also delivered to the agent's desktop.

After the data is delivered to the peripheral, the PG receives back information about which agent the call is sent to.

You define Translation Routes with the Configuration Manager, using the Translation Route Wizard.

Note	Refer to your ACD Supplement Guide to see if your ACD supports translation routing and for any considerations when you use translation routing on the PG.

Translation routing is always used when a call moves from one peripheral to another. A call can also be translation routed from the network.

• The term ICM TranslationRoute is used when calls are translation routed to a peripheral that is an ACD.

• The term TranslationRouteToVRU is used when calls are translation routed to a peripheral that is a VRU.

Translation routing plays a significant role in the accuracy of reporting and allows for cradle-to-grave call tracking and reporting. Some reporting metrics gathered for Call Types and skill groups are applicable only if calls are translation routed.

Skills-based routing is a routing decision whereby a call is routed to the skill group that has agents with the appropriate expertise.

ACD queues are used to queue calls on a targeted ACD and are controlled by the ACD.

Unified ICM might route a call to the ACD, based on knowledge gathered by the PGs that a certain skill group or service at that ACD is best suited to answer the call.

Once the call arrives at the ACD, if an agent is not available, the ACD queues the call to the skill group. Optionally a call can be queued to a skill group on the ACD during agent transfers or resulting from a call treatment provided on the ACD.

Unified ICM controlsEnterprise queues using the Service Control Interface (SCI), irrespective of the telephony platform chosen to queue the call.

In this model, calls are held at a "network-level" VRU that has an enterprise view of available agents, based on the skill groups and services configured for the peripheral.

The following telephony platforms are supported for Enterprise queuing:

• Cisco Voice Portal and Cisco IP-IVR, when connected to Unified ICM by a VRU PG

• A third-party VRU that supports service control and is connected to Unified ICM by a VRU PG

• A VRU at the TDM Network that supports service control and is connected to Unified ICM by a NIC

• For deployments where Unified ICM provides integration to an ACD for agent level routing using the ARS PG, the ACD itself is used as the telephony platform that queues the call as the ICM directs.

Enterprise queues are an efficient way to route a call in your enterprise network. Enterprise queues are also a cost-effective way to save on toll charges before terminating a call on the ACD.

The Skill_Group_Real_Time database tracks calls offered and calls queued in separate fields.

Therefore, there is no double counting of calls queued and offered at the ACD and calls queued and offered at the network.

The use of enterprise queues affects Call Type, Skill Group, and Service reporting.

The reporting metrics that are affected include queued metrics, answered metrics, service level metrics, and abandoned metrics.

The reporting of these metrics is also affected by whether or not the call was routed when sent to an ACD. For more information, see, translation-routed.

Call Type Metrics

When a call is translation-routed:

• The AnswerWaitTime, ASA, and Service Level include both the time spent in the Enterprise queue and the time spent in the ACD queue.

  The measurement of AnswerWaitTime for a call begins when the call is queued. The measurement of Service Level begins when the call arrives at the routing script or when its Call Type is changed.

  This method of measurement means that if self-service is performed on a call before the call is queued to an agent, the routing script must be set up to change the Call Type when self-service is completed. Otherwise, the time spent in self-service will negatively impact the Service Level.

• Abandoned statistics are classified in three ways:

  • Calls that abandoned while ringing at the agent desktop.

  • Calls that abandoned in an Enterprise queue while waiting for an available agent.

  • Total number of calls that abandoned. This number includes calls that abandoned in a VRU (prompting), calls abandoned in both Enterprise queue and ACD queue, and calls that abandoned at the agent.

    Note	Although the total abandons includes calls that abandoned at the ACD, there is no separate count for only those calls that abandoned at the ACD.

When a call is not translation-routed:

• The Call Type Abandoned metrics allow you to determine the number of calls that abandoned in an enterprise queue while waiting for an available agent and the number of calls that abandoned while in self-service.

  However, they do not allow you to determine the number of calls that were abandoned after they left the VRU and before an agent answered them.

• The Call Type Answered metrics will always be zero and are not applicable.

• The Call Type Service Level metrics are not applicable.

Skill Group Metrics

When a call is translation-routed:

• The Skill Group Answered metrics include only time spent in the ACD queue.

When a call is not translation-routed:

• The Skill Group Queued metrics are applicable.

• The Skill Group Abandoned metrics allow you to determine the number of calls that abandoned in an enterprise queue while waiting for an available agent, but they do not allow you to determine the number of calls that abandoned after they left the VRU and before an agent answered them. The ACD report shows calls that abandoned after they arrived at the ACD.

• The Skill Group Answered metrics do not include any time spent in the enterprise queue and therefore are not applicable.

Note	None of the skill group metrics include time spent in self-service, or calls that ended during self-service. A call is not associated with a skill group until it is queued, and a call is queued after self-service is complete.

Service Metrics

If a Service Control VRU is used for VRU application, the Service metrics can be used to provide performance measures for the VRU service. The type of VRU and configuration determines the information and usefulness of the metrics reported for the VRU service.

The metrics reported for Unified ICM Services defined for the ACD peripherals do not include any time spent in the enterprise queue. Hence the service metrics are not useful when using an enterprise queue.