From Bright Pattern Documentation
< 3.15:Virtual-queue-tutorial
Revision as of 18:50, 18 December 2017 by Tracy (talk | contribs) (How It Works)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
• 3.10 • 3.11 • 3.12 • 3.13 • 3.14 • 3.15 • 3.16 • 3.17 • 3.18

Contents

Overview

The Bright Pattern Contact Center Virtual Queue Tutorial explains Bright Pattern's virtual queue option, how to configure it, and how enabling it can affect reporting statistics.

Virtual Queuing, also referred to as the Callback Option, is an enhancement of the regular automatic call distribution method (ACD) used in inbound call centers. During periods of significant wait times, this option allows customers to hang up the call while keeping their position in the service queue and to receive a callback when it is their turn to be connected to an agent. The benefits of using virtual queuing include:

  • Improved customer satisfaction – After requesting a callback, customers get back to their normal activities instead of being tied on the phone.
  • Reduced abandonment rates – Customers who can continue their normal activities are less likely to abandon their service requests (i.e., to ignore the callback).
  • Reduced talk time – Customers waiting in a virtual queue are less likely to spend any time venting their frustration with a long wait when they are finally connected to an agent.
  • Lower telco costs – Customers waiting in a virtual queue do not occupy physical voice channels.


How It Works

Bright Pattern Contact Center Virtual Queue works in the following way:

For each incoming service call, the system calculates its estimated waiting time (EWT) in queue. If this time exceeds a threshold EWT value preconfigured for the given service, the system notifies the calling customer about the wait time and offers the customer the option of receiving a callback when it is the customer's turn to be connected to an agent. The customer can request the callback to be made to the phone from which the customer is calling, or to a different number that the customer can enter using the phone keypad. The original live call is then disconnected while the customer’s position in the service queue is maintained by the system as if the customer had remained on the line (hence the name Virtual Queuing). When it is the customer’s turn to be connected to an agent, the system makes an outbound call to the designated callback number. Upon answer, this call is connected to an available agent. To the agent, the answered callback appears as a regular incoming call.

If an agent becomes available for a given virtual call before the EWT, the callback is made at the moment when the agent becomes available. Otherwise, the callback attempt is made a few seconds before EWT expiration based on the prediction that an agent will have become available by the time the callback is answered by the customer. If an agent does not become available at that time, the answered call is placed in the first position in the service queue to be connected to the next available agent. An interactive voice response (IVR) announcement can be played for the answered callback to prevent the customer from hanging up a call if it cannot be immediately connected to an agent.

Subsequent processing of answered callbacks delivered to agents is no different from the processing of calls waiting in the queue.

An agent may be reserved by setting the property Start Dialing on the Request Callback scenario block to a value of "0". This will reserve a skilled ready agent for the callback. During this time, agent may not change skill.


Next >
Next >