Business Services Industry

IVR technology and the virtual call center

Telemarketing & Call Center Solutions, Jan 1998 by Luster, Michael C

Many companies have long seen the value in using IVR technology within their call centers. For years they have located IVRs behind ACDs to fulfill customer requests for mutual fund balances or flight arrival times. Customer requests are answered without straining a company's expensive agent resources, plus more customers are served. This allows agents to be reserved to answer complicated questions or provide answers that an IVR system cannot handle. However, a basic configuration that limits the IVR to physical connectivity at the ACD level cannot meet today's sophisticated customer service requirements.

The Traditional IVR Model

The traditional ACD-centric model, with the IVR connected behind the ACD via analog phone lines, relies on the ACD for the exchange of data for basic call-routing and reporting. An analog interface is only capable of a simple hook-flash and digits dialed to control the routing of calls transferred out of the IVR and does not support the dialed number identification system (DNIS) or calling line identification (CLID). Hence, data pertaining to the call can't be passed from the ACD to the IVR. In this traditional configuration, ACD and IVR ports are used up unnecessarily transferring calls back and forth. The process is inefficient and inadequate. To compensate, a company often sets up a complex IVR menu tree to gather information.

Reporting is limited because the ACD is only aware of the number and duration of calls, and has no knowledge about the transactions performed by the IVR. In addition, the IVR often reports conflicting data regarding call statistics, and can't report on network data or track how transferred calls are handled. If the caller requests a transfer to an agent, the IVR does not have access to any call center performance or agent skill data to assist in determining the appropriate call destination. Upon receiving the transferred call, the ACD applies its routing logic, but can provide only rudimentary data to the selected agent about the caller's needs. For companies deploying a virtual call center strategy, these issues are limiting and insurmountable.

IVR In The Virtual Call Center

IVR technology, included as an integral part of a virtual call center, enables companies to provide cost-effective yet personalized customer service. Depending upon the specific parameters of the IVR implementation, a company can use information gathered in the callrouting process to initiate special treatment based on caller attributes, learn more about customer expectations and requirements, and maximize the use of information at the desktop in support of business goals. Underpinning these elements is the notion of delivering value to the caller, while the company enjoys the ability to better track, deliver and make business decisions about the call and the call detail.

This makes segmenting callers of strategic importance. Call segmentation deals with the "who" and "why" questions of the call. Who is calling? Why is the individual calling? The "who" can either be a specific individual or be a category of customer. An individual caller can be identified based upon the number he or she dialed, where the person is calling from or information he or she inputs in response to a network or IVR prompt. For example, "Please enter your Social Security or account number." The "why" can be determined by prompting the caller for the desired transaction - "Press one for quotes," "Press two for account balances," or by searching a customer-profile database to determine the caller's preference, or if the caller has any outstanding transaction or service requests in progress.

Transaction fulfillment deals with "what" and "where": What answering resource is best suited to respond to this transaction request, and where is it located? Many times, the "what" can be an IVR application. For an IVR, the "where" can be one of several premises-based IVR systems, a network IVR system or an IVR application provided by a service agency. Also, hybrid transactions involving an IVR application and an agent are common. For example, a caller may be encouraged to provide basic account information to an IVR before being transferred to an agent for another transaction.

Benefits of enterprise IVR in the virtual call center include:

* Improved caller segmentation. In many cases, an IVR is the only way to uniquely identify a caller or his or her motive for calling.

* Promotion of self-service. A caller can receive a high level of service because the call is immediately answered and the issue resolved, with the transaction directed entirely by the caller.

* Automation of simple transactions. Calls can be handled, completed and terminated at the IVR rather than consume agent resources.

* Reduction of calls handled by agents. By handling calls via an IVR, the number of calls handled by agents decreases.

* Consolidated reporting. By including IVRs as a subsystem within an enterprisewide virtual capability, a company has unparalleled real-time and historical monitoring and reporting capabilities.

 

BNET TalkbackShare your ideas and expertise on this topic

Please add your comment:

  1. You are currently: a Guest |
  2.  

Basic HTML tags that work in comments are: bold (<b></b>), italic (<i></i>), underline (<u></u>), and hyperlink (<a href></a)