1. Field of the Invention
The present invention relates to the field of telecommunications. More particularly, the present invention relates to a customer call routing menu employing an interactive voice response (IVR) system.
2. Acronyms
The written description provided herein contains acronyms which refer to various telecommunications services, components and techniques, as well as features relating to the present invention. Although some of these acronyms are known, use of these acronyms is not strictly standardized in the art. For purposes of the written description herein, acronyms will be defined as follows:
3. Description of Background Information
Many companies incorporate IVR call management systems in order to handle and route incoming telephone calls. This is especially true within customer service centers, also known as customer call centers, of companies. Typically, the IVR system plays an audible menu to the caller providing messages consisting of call routing options. The caller is then prompted to select from the call routing options. Often, the IVR system includes a main menu and one or more sub-menus. A caller is then required to navigate through the various levels of menus to reach a customer service representative that may provide assistance.
Until now, the IVR call management menus have been designed from a business-centric standpoint. That is, the design of IVR menus has been in part based upon the subjective judgment and experience of those persons directly involved in the management of customer service centers. Their perspective is, quite naturally, oriented towards the organization and how the people within the organization will assist the customer. For example, menu message options have been structured using corporate department designations, e.g., billing department, repair group, etc. The order in which the departments are arranged in the menu may be influenced by a variety of factors including company hierarchy. As a result, callers may have to listen to many, if not all, of the menu message options before deciding upon an option to select. In some instances, the caller makes an incorrect selection and is routed to a service representative not able to assist them in accomplishing their task. This leads to caller dissatisfaction and frustration, as well as the added cost of transferring the call to the appropriate service representative.
Some IVRs customize the menu for a particular caller, using for instance, automatic number identification (ANI). One example of an IVR system that uses ANI to identify the caller and individualize the menu was presented by POLCYN et al., U.S. Pat. No. 6,061,433. However, POLCYN et al., has many drawbacks, particularly with respect to customer service centers of telecommunications carriers. The nature of customer service centers for telecommunications carriers is not well suited to individualizing the menu for a particular caller because customer service centers for telecommunications carriers receive few repeat callers. Moreover, callers that do call back are usually calling for reasons unrelated to the previous call, e.g., to request a different service. Furthermore, individualizing the menu based upon a particular caller requires extra processing and places additional demands upon the system.
It has been observed that most customers call a customer service center number with a specific task in mind, not an organizational unit. As a result, it would be desirable to have a customer-centric IVR for call management that improves customer satisfaction. The present invention overcomes the problems associated with the prior art.
The present invention is further described in the detailed description that follows, by reference to the noted plurality of drawings by way of non-limiting examples of embodiments of the present invention, in which like reference numerals represent similar parts throughout several views of the drawings, and in which:
In view of the foregoing, the present invention, through one or more of its various aspects and/or embodiments is thus presented to provide a customer call routing menu for an IVR call management system.
Accordingly, one aspect of the present invention is to provide a method for processing a telephone call placed to an interactive voice response system of a customer service center of a telecommunications carrier. The method includes receiving a call from a caller and presenting a sequence of menu messages to the caller that represent caller tasks. The sequence of menu messages are arranged in an order so that more frequently requested tasks are played to the caller before less frequently requested tasks are played to the caller. The method also includes prompting the caller to select from one of the menu messages and routing the call in accordance with the caller's selection.
The method may include presenting a main menu to the caller and at least one sub-menu to the caller. At least one of the menu messages could be associated with a customer bill or payment. Another menu message may be associated with adding, changing, or removing an optional service. Yet another menu message may be associated with opening or closing an account. Further, another menu message could be related to moving or reconnecting telephone service or about obtaining information concerning telephone services.
Another aspect of the present invention is to provide a method for processing a telephone call placed to an interactive voice response system of a customer service center of a telecommunications carrier. The method includes receiving a call from a caller and presenting a sequence of main menu messages to the caller. At least one of the menu messages represent groups of customer tasks. The method further includes prompting the caller to select from one of the main menu messages and presenting a sequence of sub-menu messages to the caller. The method also includes prompting the caller to select from one of the sub-menu messages and routing the call in accordance with the caller's selection.
The method may include presenting a sequence of main menu messages in an order so that more frequently requested tasks are played to the caller before less frequently requested tasks are played to the caller. The method may further include presenting the sequence of sub-menu messages in an order so that more frequently requested tasks are played to the caller before less frequently requested tasks are played to the caller. At least one of the sub-menu messages may represent groups of customer tasks.
The method may include presenting a main menu to the caller and at least one sub-menu to the caller. At least one of the menu messages could be associated with a customer bill or payment. Another menu message may be associated with adding, changing, or removing an optional service. Yet another menu message may be associated with opening or closing an account. Further, another menu message could be related to moving or reconnecting telephone service or about obtaining information concerning telephone services.
Another aspect of the present invention is to provide a telecommunications system for receiving telephone calls at a customer service center. The system includes an interactive voice response unit that provides at least one menu of messages representing customer tasks requested by customers. The menu is arranged in an order so that more frequently requested tasks are played to the caller before less frequently requested tasks are played to the caller. Further, the caller is prompted to select a menu message and the call is routed in accordance with the caller's selection.
The selection of a menu message by a caller may cause a sub-menu to be presented to the caller, in which the sub-menu includes a sequence of menu messages. The selection of a menu message by a caller may also cause the call to be transferred to a customer service representative.
Another aspect of the present invention is to provide a computer readable medium for storing a computer program that processes a telephone call in an interactive voice response system. The computer readable medium includes a presenting source code segment that presents a sequence of menu messages to the caller that represent caller tasks. The sequence of menu messages are arranged in an order so that more frequently requested tasks are played to the caller before less frequently requested tasks are played to the caller. The computer readable medium also includes a prompting source code segment that prompts the caller to select from one of the menu messages. Further, the computer readable medium includes a routing source code segment that routes the call in accordance with the caller's selection.
The presenting source code segment of the computer readable medium may present a main menu to the caller and at least one sub-menu to the caller. Further, the presenting source code segment may present a sub-menu to the caller in response to the routing code segment's routing of the call in accordance with the caller's selection from the main menu. The routing source code segment may transfer the caller to a customer service representative. Further, the presenting source code segment may present at least one sub-menu to the caller in response to the caller's selection from another sub-menu.
The present invention relates to telephone call processing in an IVR call management system. In one embodiment, the IVR call management system of the present invention is directed to function in a customer service center for a telecommunications carrier. The IVR call management system supports a menu that is organized by customer tasks and is worded with terminology commonly used by customers. Further, the order of the menu messages in the IVR call management system is based upon the frequency of the tasks requested by customers. This approach to menu design is referred to as customer-centric.
If the caller selects “1” from the main menu, sub-menu 1 prompts the caller as follows: “To find out the balance due on your account, press 1”; “To discuss or get information about the long-distance portion of your bill, press 2”; “For information about your bill that does not concern long-distance, press 3”; and “To report a payment or to find out where to make a payment, press 4”. As a result of the caller's selection in sub-menu 1, the call is transferred to a customer service representative capable of assisting the customer with the identified task, i.e., obtaining account balance information, obtaining billing information for long distance calls, obtaining billing information for non-long distance calls, or obtaining payment information.
If the caller selects “2” from the main menu, sub-menu 2 prompts the caller as follows: “To add an optional service, press 1”; and “To change or remove an optional service, press 2”; “For information about your Caller ID equipment, press 3”. As a result of the caller's selection in sub-menu 2, the call is transferred to a customer service representative capable of assisting the customer with the identified task, i.e., adding an optional service, changing or removing an optional service, or obtaining information about caller ID equipment.
If the caller selects “3” from the main menu, sub-menu 3 prompts the caller as follows: “To open an account, press 1”; “To close your account, press 2”; “To move your service to another address, press 3”; “To change the name on your account, press 4”; and “To get your service reconnected, press 5”. As a result of the caller's selection in sub-menu 3, the call is transferred to a customer service representative capable of assisting the customer with the identified task, i.e., opening an account, closing an account, moving an account, changing the name on an account, or reconnecting service.
If the caller selects “4” from the main menu, the call is transferred to a customer service representative capable of assisting the customer. In all cases, the design of the customer-centric menu structure causes the call to be transferred to a customer service representative trained to assist the caller with the particular task selected by the caller.
As shown in
In an embodiment, the menu messages in the main menu and sub-menus are arranged in the order of the most frequently requested tasks, with the most frequently requested tasks presented first. The determination of which tasks are most frequently requested will be described herein later.
The main menu 102 prompts the caller to select one of the groups of tasks (blocks 103, 104, 105) or the individual task (block 106). If the caller selects group of tasks 1 through 4 (block 103), a sub-menu 107 is played to the caller including menu messages of individual tasks associated with groups of task 1 through 4, from which to choose. The sub-menu 107 prompts the caller to select from individual tasks 1 through 4, which are represented by blocks 108, 109, 110 and 111. It is clear that a different sub-menu is played to the caller based upon whether the caller selects block 103, 104, or 105 in the main menu. If the caller selects task 1 (block 108), the call is transferred to a service representative at block 121. If the caller selects task 2 (block 109), the call is transferred to a service representative at block 122. If the caller selects task 3 (block 110), the call is transferred to a service representative at block 123. If the caller selects task 4 (block 111), the call is transferred to a service representative at block 124.
If at the main menu 102, the caller selects group of tasks 5-7 (block 104) a sub-menu 107 is played to the caller including menu messages of individual tasks associated with group of tasks 5 through 7, from which to choose. The sub-menu 107 prompts the caller to select from individual tasks 5 through 7, which are represented by blocks 112, 113 and 114. If the caller selects task 5 (block 112), the call is transferred to a service representative at block 125. If the caller selects task 6 (block 113), the call is transferred to a service representative at block 126. If the caller selects task 7 (block 114), the call is transferred to an service representative at block 127.
If at the main menu 102, the caller selects group of tasks 8-12 (block 105) a sub-menu 107 is played to the caller comprising menu messages of individual tasks associated with group of tasks 8 through 12, from which to choose. The sub-menu 107 prompts the caller to select from individual tasks 8 through 12, which are represented by blocks 115, 116, 117, 118 and 119. If the caller selects task 8 (block 115), the call is transferred to a service representative at block 128. If the caller selects task 9 (block 116), the call is transferred to a service representative at block 129. If the caller selects task 10 (block 117), the call is transferred to a service representative at block 130. If the caller selects task 11 (block 118), the call is transferred to an service representative at block 131. If the caller selects task 12 (block 119), the call is transferred to a service representative at block 132.
If at the main menu 102, the caller selects individual task 13 (block 106), no sub-menu is played and the caller is transferred to a service representative at block 133.
For example, referring to
Additionally, the CTF table is used for identifying the terminology of words to be used in the menu messages, i.e., the language used by the customers. To assure that the callers can identify with the menu messages, the caller's actual choice of words obtained from the random sample is used in the CTF table, and subsequently, in the menu messages.
Over time, the demands of callers change and the services offered by the telecommunications carrier evolves. Thus, the process of conducting a random sample of callers and constructing the CTF table is repeated periodically.
If a “no” determination is made at step s10, the caller is transferred to the appropriate service representative at step s12 and the caller is assisted at step s14. The call is terminated at step s16. In general, if the caller selects a menu message that includes an individual task rather than a group of tasks, the call will be transferred to the appropriate customer service representative. However, if the caller selects a menu message that comprises a group of tasks, a sub-menu will be played to the caller. If a “yes” determination is made at step s10, a sub-menu is presented to the caller at step s15 and the caller's selection is received at step s8. The loop continues until a “no” determination is made at step s10, at which time the caller is transferred to a service representative at step s12 for assistance.
Although the invention has been described with reference to several exemplary embodiments, it is understood that the words that have been used are words of description and illustration, rather than words of limitation. Changes may be made within the purview of the appended claims, as presently stated and as amended, without departing from the scope and spirit of the invention in its aspects. Although the invention has been described with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed; rather, the invention extends to all functionally equivalent structures, methods, and uses such as are within the scope of the appended claims. For instance, it should be understood that callers may select menu messages via any means including DTMF input or spoken word.
In accordance with various embodiments of the present invention, the methods described herein are intended for operation as software programs running on a computer processor. Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement the methods described herein. Furthermore, alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.
It should also be noted that the software implementations of the present invention as described herein are optionally stored on a tangible storage medium, such as: a magnetic medium such as a disk or tape; a magneto-optical or optical medium such as a disk; or a solid state medium such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories. A digital file attachment to E-mail or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. Accordingly, the invention is considered to include a tangible storage medium or distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.
Although the present specification describes components and functions implemented in the embodiments with reference to particular standards and protocols, the invention is not limited to such standards and protocols. Each of the standards, including standards for the IVR system, represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same functions are considered equivalents.
Number | Name | Date | Kind |
---|---|---|---|
4310727 | Lawser et al. | Jan 1982 | A |
4694483 | Cheung | Sep 1987 | A |
4761542 | Kubo et al. | Aug 1988 | A |
4922519 | Daudelin | May 1990 | A |
4964077 | Eisen et al. | Oct 1990 | A |
5115501 | Kerr | May 1992 | A |
5204968 | Parthasarathi | Apr 1993 | A |
5206903 | Kohler et al. | Apr 1993 | A |
5263167 | Conner, Jr. et al. | Nov 1993 | A |
5299260 | Shaio | Mar 1994 | A |
5311422 | Loftin et al. | May 1994 | A |
5323452 | Dickman et al. | Jun 1994 | A |
5327529 | Fults et al. | Jul 1994 | A |
5329578 | Brennan et al. | Jul 1994 | A |
5335268 | Kelly, Jr. et al. | Aug 1994 | A |
5335269 | Steinlicht | Aug 1994 | A |
5384831 | Creswell et al. | Jan 1995 | A |
5388198 | Layman et al. | Feb 1995 | A |
5420975 | Blades et al. | May 1995 | A |
5479488 | Lennig et al. | Dec 1995 | A |
5495567 | Iizawa et al. | Feb 1996 | A |
5500795 | Powers et al. | Mar 1996 | A |
5519772 | Akman et al. | May 1996 | A |
5530744 | Charalambous et al. | Jun 1996 | A |
5533107 | Irwin et al. | Jul 1996 | A |
5533119 | McCallister et al. | Jul 1996 | A |
5535321 | Massaro et al. | Jul 1996 | A |
5537470 | Lee | Jul 1996 | A |
5561711 | Muller | Oct 1996 | A |
5566291 | Boulton et al. | Oct 1996 | A |
5586060 | Kuno et al. | Dec 1996 | A |
5586171 | McAllister et al. | Dec 1996 | A |
5586219 | Yufik | Dec 1996 | A |
5594791 | Szlam et al. | Jan 1997 | A |
5600781 | Root et al. | Feb 1997 | A |
5615323 | Engel et al. | Mar 1997 | A |
5657383 | Gerber et al. | Aug 1997 | A |
5659724 | Borgida et al. | Aug 1997 | A |
5668856 | Nishimatsu et al. | Sep 1997 | A |
5675707 | Gorin et al. | Oct 1997 | A |
5684870 | Maloney et al. | Nov 1997 | A |
5684872 | Flockhart et al. | Nov 1997 | A |
5706334 | Balk et al. | Jan 1998 | A |
5710884 | Dedrick | Jan 1998 | A |
5727950 | Cook et al. | Mar 1998 | A |
5729600 | Blaha et al. | Mar 1998 | A |
5734709 | DeWitt et al. | Mar 1998 | A |
5740549 | Reilly et al. | Apr 1998 | A |
5757644 | Jorgensen et al. | May 1998 | A |
5758257 | Herz et al. | May 1998 | A |
5771276 | Wolf | Jun 1998 | A |
5790117 | Halviatti et al. | Aug 1998 | A |
5793368 | Beer | Aug 1998 | A |
5802526 | Fawcett et al. | Sep 1998 | A |
5806060 | Borgida et al. | Sep 1998 | A |
5808908 | Ghahramani | Sep 1998 | A |
5809282 | Cooper et al. | Sep 1998 | A |
5812975 | Komori et al. | Sep 1998 | A |
5819221 | Kondo et al. | Oct 1998 | A |
5821936 | Shaffer et al. | Oct 1998 | A |
5822744 | Kesel | Oct 1998 | A |
5825856 | Porter et al. | Oct 1998 | A |
5825869 | Brooks et al. | Oct 1998 | A |
5832428 | Chow et al. | Nov 1998 | A |
5832430 | Lleida et al. | Nov 1998 | A |
5848396 | Gerace | Dec 1998 | A |
5864605 | Keshav | Jan 1999 | A |
5864844 | James et al. | Jan 1999 | A |
5870308 | Dangelo et al. | Feb 1999 | A |
5884029 | Brush, II et al. | Mar 1999 | A |
5899992 | Iyer et al. | May 1999 | A |
5903641 | Tonisson | May 1999 | A |
5923745 | Hurd | Jul 1999 | A |
5943416 | Gisby | Aug 1999 | A |
5953406 | LaRue et al. | Sep 1999 | A |
5974253 | Nahaboo et al. | Oct 1999 | A |
5991735 | Gerace | Nov 1999 | A |
5999611 | Tatchell et al. | Dec 1999 | A |
5999908 | Abelow | Dec 1999 | A |
6014638 | Burge et al. | Jan 2000 | A |
6016336 | Hanson | Jan 2000 | A |
6035336 | Lu et al. | Mar 2000 | A |
6044355 | Crockett et al. | Mar 2000 | A |
6058163 | Pattison et al. | May 2000 | A |
6058179 | Shaffer et al. | May 2000 | A |
6061433 | Polcyn et al. | May 2000 | A |
6067538 | Zorba et al. | May 2000 | A |
6088429 | Garcia | Jul 2000 | A |
6099320 | Papadopoulos | Aug 2000 | A |
6104790 | Narayanaswami | Aug 2000 | A |
6128380 | Shaffer et al. | Oct 2000 | A |
6134315 | Galvin | Oct 2000 | A |
6134530 | Bunting et al. | Oct 2000 | A |
6148063 | Brennan et al. | Nov 2000 | A |
6157808 | Hollingsworth | Dec 2000 | A |
6163607 | Bogart et al. | Dec 2000 | A |
6170011 | Macleod Beck et al. | Jan 2001 | B1 |
6173053 | Bogart et al. | Jan 2001 | B1 |
6201948 | Cook et al. | Mar 2001 | B1 |
6212502 | Ball et al. | Apr 2001 | B1 |
6236955 | Summers | May 2001 | B1 |
6236990 | Geller et al. | May 2001 | B1 |
6263051 | Saylor et al. | Jul 2001 | B1 |
6263052 | Cruze | Jul 2001 | B1 |
6269153 | Carpenter et al. | Jul 2001 | B1 |
6278976 | Kochian | Aug 2001 | B1 |
6282404 | Linton | Aug 2001 | B1 |
6295551 | Roberts et al. | Sep 2001 | B1 |
6330326 | Whitt | Dec 2001 | B1 |
6332154 | Beck | Dec 2001 | B1 |
6349290 | Horowitz et al. | Feb 2002 | B1 |
6353661 | Bailey, III | Mar 2002 | B1 |
6389400 | Bushey et al. | May 2002 | B1 |
6389403 | Dorak, Jr. et al. | May 2002 | B1 |
6389538 | Gruse et al. | May 2002 | B1 |
6405159 | Bushey et al. | Jun 2002 | B1 |
6411687 | Bohacek et al. | Jun 2002 | B1 |
6483523 | Feng | Nov 2002 | B1 |
6487277 | Beyda et al. | Nov 2002 | B1 |
6564197 | Sahami et al. | May 2003 | B1 |
6600821 | Chan et al. | Jul 2003 | B1 |
6778651 | Jost et al. | Aug 2004 | B1 |
20010014146 | Beyda et al. | Aug 2001 | A1 |
20010041562 | Elsey et al. | Nov 2001 | A1 |
20020076032 | Rodriguez et al. | Jun 2002 | A1 |
20020133394 | Bushey et al. | Sep 2002 | A1 |
20030143981 | Kortum et al. | Jul 2003 | A1 |
20030156706 | Koehler et al. | Aug 2003 | A1 |
20030158655 | Obradovich et al. | Aug 2003 | A1 |
20030161464 | Rodriguez et al. | Aug 2003 | A1 |
20040062371 | Maropis et al. | Apr 2004 | A1 |
Number | Date | Country | |
---|---|---|---|
20030026409 A1 | Feb 2003 | US |