US9197752B2 - Method for designing an automated speech recognition (ASR) interface for a customer call center - Google Patents

Method for designing an automated speech recognition (ASR) interface for a customer call center Download PDF

Info

Publication number
US9197752B2
US9197752B2 US14312310 US201414312310A US9197752B2 US 9197752 B2 US9197752 B2 US 9197752B2 US 14312310 US14312310 US 14312310 US 201414312310 A US201414312310 A US 201414312310A US 9197752 B2 US9197752 B2 US 9197752B2
Authority
US
Grant status
Grant
Patent type
Prior art keywords
call center
identifying
routing
use
caller
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US14312310
Other versions
US20140314228A1 (en )
Inventor
Robert R. Bushey
Benjamin A. Knott
John M. Martin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nuance Communications Inc
Original Assignee
AT&T Intellectual Property I LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Grant date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/523Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
    • H04M3/5232Call distribution algorithms
    • GPHYSICS
    • G10MUSICAL INSTRUMENTS; ACOUSTICS
    • G10LSPEECH ANALYSIS OR SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING; SPEECH OR AUDIO CODING OR DECODING
    • G10L15/00Speech recognition
    • G10L15/08Speech classification or search
    • G10L15/18Speech classification or search using natural language modelling
    • G10L15/1822Parsing for meaning understanding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/487Arrangements for providing information services, e.g. recorded voice services, time announcements
    • H04M3/493Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • GPHYSICS
    • G10MUSICAL INSTRUMENTS; ACOUSTICS
    • G10LSPEECH ANALYSIS OR SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING; SPEECH OR AUDIO CODING OR DECODING
    • G10L15/00Speech recognition
    • G10L15/08Speech classification or search
    • G10L15/18Speech classification or search using natural language modelling
    • G10L15/183Speech classification or search using natural language modelling using context dependencies, e.g. language models
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2201/00Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/40Electronic components, circuits, software, systems or apparatus used in telephone systems using speech recognition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2203/00Aspects of automatic or semi-automatic exchanges
    • H04M2203/35Aspects of automatic or semi-automatic exchanges related to information services provided via a voice call
    • H04M2203/355Interactive dialogue design tools, features or methods

Abstract

A method of designing a customer interface for a service center, such as an automated speech recognition (ASR) self-service center. Customer activity to an existing service center is monitored, providing customer model, which includes a collection of customer tasks. These tasks are assigned to action-object pairs, which are further assigned to routing destinations. Dialog modules are designed, based on the customer model data, including disambiguation dialogs.

Description

The present patent application is a continuation of U.S. patent application Ser. No. 13/681,970, filed Nov. 20, 2012 (issuing as U.S. Pat. No. 8,761,381 on Jun. 24, 2014), which is a continuation of U.S. patent application Ser. No. 12/326,630, filed Dec. 2, 2008 (now U.S. Pat. No. 8,315,360), which is a continuation of U.S. patent application Ser. No. 10/852,342, filed May 24, 2004 (now U.S. Pat. No. 7,460,650), the entirety of which are hereby incorporated by reference. Pursuant to 37 CFR §1.78(a)(3), an application data sheet containing a reference to the previously filed applications, unless submitted previously, is submitted contemporaneously herewith.

TECHNICAL FIELD OF THE INVENTION

This invention relates to customer call center services, and more particularly to a method for designing customer interfaces for telephone-based or web-based customer service systems.

BACKGROUND OF THE INVENTION

Customer call centers are increasingly using automated self-service applications. Self-service call center applications are much less expensive than those using service agents. A well designed self-service application can cost as little as 10% as an application using service agents.

Because of this potential savings, today's call center service providers desire to increase the number of self-service calls relative to agent-assisted calls. However, when deciding among various designs for self-service applications, there are considerations in addition to savings. Specifically, the service provider must consider whether, in addition to reducing agent costs, a particular design cars achieve quality of service goals, such as high customer task completion, high customer satisfaction, and short call duration. Conversion of a call center system from agent-assisted to self-service can be accomplished incrementally. The overall goal becomes performing more and more customer tasks with self-service applications, while holding or improving task completion and customer satisfaction.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:

FIG. 1 illustrates a method of designing an interface in accordance with the invention.

FIG. 2 illustrates Steps 104 and 105 of the method of FIG. 1.

FIG. 3 illustrates Step 106 of the method of FIG. 1.

FIGS. 4A and 4B illustrate a how-to-use customer interface, designed in accordance with the invention.

FIG. 5 illustrates a computer system for implementing the method of the invention.

DETAILED DESCRIPTION OF THE INVENTION

The following invention is directed to a method of designing an interface for an automated customer call center. A feature of the method is that it is directed to making design decisions on the basis of customer data rather than designer opinion. The method is a systematic, data-driven method of interface design that ensures that the resulting customer interface is tailored for the intended user population, resulting in higher customer acceptance and satisfaction.

Customer Interface Design Method

FIG. 1 illustrates a method of designing a customer interface in accordance with the indention. The examples set out below in connection with FIG. 1 are examples of a customer interface for routing calls among various call centers of a telephone service provider. The customer interface is to be implemented using automated speech recognition (ASR) techniques.

The same concepts may be applied to designing any customer interface for any type of business enterprise. Furthermore, as explained below, the interface could be for a service agent or a web-based service center, as well as for an automated (ASR) call center, or some combination of agent, ASR, or text entry, interaction between the customer and the business enterprise.

Step 101 is creating a customer model. The model is based on customer tasks, which may be collected by recording opening statements of customers to a service center. For example, opening statements made to a agent could be recorded. Or, customer data could be collected during visits to a web site, via the Internet. Typically, the customer data is collected during customer visits (by telephone or via the Internet) to an “existing” service center (call center or web service site) that is to be updated or enhanced to become a self-service center in accordance with the design method of the present invention.

The customer model can also be used to determine “personas” used in designing interface modules, as described below. For example, customer persona data could be used to determine whether language alternatives should be presented and which language choices should be available. As explained below, customer model data can also be used to determine disambiguation techniques, when customer responses are not immediately indicative of a routing destination.

Step 102 is creating a task model. This model represents a taxonomy, from the customer task list collected in Step 101, of “actions” versus “objects” in a matrix. Some matrix cells will be more frequent in their occurrence than other cells. Some cells are not logical and do not exist in actual customer-call center interactions.

Step 103 is creating a business rules model. This step involves gathering business rules from one or more call centers. These rules may be dispersed in the sense that each call center may modify, to some extent, business rules in accordance with that call center's unique circumstances and location. This model determines where customer calls (by type) are to be routed.

Step 104 is linking the customer model to the task model. In other words, the customer opening statements (from the customer model) collected in Step 101 are assigned to the action-object pairs (from the task model) created in Step 102.

Two examples of the results of Step 104 are:

acquire-basic—for customers who wish to order phone service

pay-bill—for customers who wish to pay their bill

Step 105 is linking the task model to the business rules model. In other words, action-object pairs (from the task model) are linked to routing destinations (from the business rules model). Examples of routing destinations are a call center agent, a queue, a self-service speech recognition application, or the internet.

FIG. 2 is an example of action-object pairs and their routing destinations. In the example of FIG. 2, the routing destinations are ASR systems associated with specific call centers. A single business enterprise might have a number of call centers, such as for billing, customer retention, ordering, how-to-use, returns, etc.

Step 106 is creating an action-object frequency table. Each action-object pair is listed in its order of frequency of use. The list is in descending order of frequency.

FIG. 3 illustrates an example of a portion of an action-object frequency table in accordance with Step 106.

Step 107, is designing ASR dialog modules. Typically, each module is designed in the sequential order of the action-object frequency table list, beginning with the most frequent action-object pairs.

In designing the modules, the persona data acquired in Step 101 may be used to influence various features of the module. Persona may influence the frequency, detail level, and style of dialog between the ASR system and the customer, as well as the wording of prompts. For example, a highly sophisticated customer base might allow for a more terse, brief dialog.

A feature of the interface module design is that customer tasks can have only two alternative routing destinations. A “direct route” destination occurs when there is sufficient information to directly route the call to the correct location. A “further clarification” destination occurs when clarification or further information is needed to route the call.

A first example of “further clarification” routing would occur if the customer said “I have a question about my long distance service”. This statement would be handled by a dialog module corresponding to the “Inquire; Long Distance” action-object pair. This dialog module asks: “Is your long distance with X Company?” If the response is “yes”, the customer is transferred to the appropriate call center for company x long distance service. If the response is “no”, the customer is transferred to a standard pre-recorded message instructing the customer to call their long distance provider.

A second example of “further clarification” routing would occur if the customer said: “I'd like to cancel my service”. This statement would be transferred to a Cancel-Basic dialog module. This dialog module asks: “Is this for your basic telephone service?” If the response is “yes”, the call is transferred to the Disconnect call center. If the response is “no”, appropriate dialog is provided such that the customer can select among services corresponding to various dialog modules. Once the service desired to be cancelled is selected, the selection serves as an entry point to the corresponding module.

FIGS. 4A and 4B, described below, illustrate examples of dialog modules for a customer interface for a “how-to-use” call center. The common routing destination is the how-to-use call center, and the dialog modules correspond to action-object pairs. The dialog modules of FIGS. 4A and 4B further illustrate various “further clarification” techniques, and various alternatives for disambiguating customer responses.

During implementation of the dialog modules, data is collected to ensure that the customer has a positive experience. Various means exist for gathering data about success rates of voice recognition, call routing, and overall customer satisfaction.

In other embodiments, the above-described interface design method could be used to design a web-based interface. In this embodiment, the customer would interact with the web interface by text (keyboard) entry, voice, or some combination of both. As Internet, telephonic, and two-way visual communications become increasingly intertwined, the application of the invention will similarly be applicable to various combinations of live, ASR, and web-based communication media.

How-to-Use Customer Interface Example

FIGS. 4A and 4B illustrate an example of a customer interface designed using the above-described interface design method. The interface is a “how to use” (HTU) interface for an ASR (self-service) customer call system. More specifically, the example of FIGS. 4A and 4B is an HTU interface for telephone services, on behalf of a telephone service provider.

As explained below, the HTU interface comprises a number of dialog modules, each activated in response to a routing decision. Each can be associated with an action-object pair, using the techniques described above.

As explained below, the system provides a caller with an interactive self-service series of verbal prompts, voice recognition entry points, and messages, the combination of which provide the caller with the desired information about how to use a selected service. Once a caller has selected a service of interest, then a topic of interest, the system provides the appropriate instructions.

As explained below in connection with FIG. 5, the dialog of FIGS. 4A and 4B is implemented using computer hardware, which is programmed in accordance with the process steps described below. The HTU system allows callers to easily access instructions for a variety of services or products within a single phone call by using speech input. The system uses a combination of natural language and directed dialog elements, allowing callers to retrieve instructions through several different paths. Specifically, callers can identify a topic of interest in three ways: by saying the name of the service or product, by selecting the topic from a menu, or by verbally describing what the service or product does in the caller's own words. This approach is achieved by using both statistical language models and grammar-based recognition techniques.

Although the dialog is especially useful for voice recognition of voice responses from the caller, it also recognizes keypad input. In some steps, keypad input is requested by prompting, such as “Enter 1 for . . . . ” or “Enter your area code and phone number”. In general, each of the caller's responses described herein could be substituted with a keypad entry, and DTMF recognition used rather than voice recognition.

Step 1000 is a Welcome state. It is a play-prompt state, and like the other play-prompt states described herein, it plays a waveform, or a series of waveforms, to the caller who hears the waveforms as a spoken message. As an example of a welcome play-prompt, the caller may hear, “Welcome to the How to Use Guide for your phone services”.

Step 1020 is an Offer Spanish interaction dialog module. Like the other interaction states described herein, Step 1020 prompts the caller for input. Interaction states also handle default timeout and retries, and typically continue to a next state upon a successful voice recognition.

An example of an Offer Spanish prompt is: “Para continuar en Espanol por favor oprima el uno”. If the caller enters “1”, the input is recognized as a DTMF signal and the call is transferred to a Spanish version of the dialog. After a pause, and if no DTMF signal is received, the dialog proceeds to Step 1025.

Step 1025 is a Get Phone Number interaction dialog module. Step 1025 typically follows Step 1020. An example of the message played in Step 1025 is: “I'll help you find out how to use any of the phone services we provide for our residential customers. To get started, I'll need your area code and home phone number. You can either say it or enter it.”

The caller then responds by speaking or entering a number. If a number is recognized, the caller is thanked and the dialog proceeds to Step 1050. If no number is recognized, various timeouts and retry messages are delivered, and upon failure of these, the dialog is exited.

Step 1050 is a Get Service Name interaction dialog module, and typically follows Step 1025. It may also be entered from Step 1310, Step 2015, or Step 4000, explained below.

When entering from Step 1025, an example of a message to the caller is: “Now, please tell me which phone service you'd like to find out about. [pause] To hear your choices, say list them”.

Natural language techniques are used so that the caller may freely speak the names of services or describe them in natural language. If the caller responds by naming or describing a service, the dialog proceeds to Step 1200. If the caller responds by speaking “List them”, the dialog proceeds to Step 1075.

If the caller has entered Step 1050 from Step 2015 or from Step 4000, the dialog speaks a message such as “If you're finished hearing about phone services, say “I'm finished”. [pause] Otherwise, . . . . ” If the caller speaks “I'm finished”, the dialog proceeds to Step 5000, explained below. If the caller does not say “I'm finished”, the dialog proceeds as when entering from Step 1025.

Natural language techniques are also used to recognize when the caller has named an unsupported service. If the caller names an unsupported service, the dialog proceeds to Step 4000. Step 4000 is a process whereby the system recognizes a number of unsupported services. For example, if the caller speaks “discount packages”, the system responds with a message such as: “I'm sorry. Right now, I don't have any information about discount packages. If you want more information about this topic, you'll need to speak with a representative who can help. Would you like me to transfer you now?”. If the caller speaks “Yes”, the caller is transferred. If the caller speaks “No”, the caller returns to Step 1050, hears an appropriate message, and is given another opportunity to select a service.

Step 1075 is a Get Category Name interactive dialog module, performed if the caller has requested a list in Step 1050. An example of a message that the caller hears is: “I have the services grouped into categories based on what each service does. I'll read the categories, and when you hear the one you want, just say it. Call Answering, Caller Identification, Call Forwarding, Call Screening, Three-way Calling, Automatic Dialing, Personalized Ring, Local Plus.” The caller may then speak the name of the service category, and the dialog proceeds to Step 1200.

After the message of Step 1075, the caller is offered various retries and timeouts if there is no response or the response is not understood. Also, after a category name is spoken, the caller receives a confirmation message such as “Automatic dialing. Is that correct?”

Step 1200 is a Disambiguation Check internal decision step. If the caller has selected a service category having more than one type of service, it may be necessary to ask an additional question to determine the specific service name. Step 1200 determines whether to continue with the call dialog or to first go to a disambiguation state.

The disambiguation check of Step 1260 depends on which service the caller has selected. Some categories have only one associated service, and need no disambiguation. For those services, the dialog proceeds to Step 1300. However, other categories have more than one associated service. In this case, the dialog proceeds to Step 1210.

Step 1210 is a disambiguation process. For example, if the caller has selected the category of Automatic Dialing in Step 1050 or Step 1210, the caller might hear the following message: “There are four services that can automatically dial a number for you. Say “Auto Redial, Call Return, Speed Calling, Direct Reply, or say Help for a brief explanation of each”. The caller's response is recognized as the selected service of interest.

Step 1300 is a Check Service Name internal decision step. This state determines which of the various services the caller has asked for in Step 1050 or Step 1210, and links to a dialog module associated with that service.

Step 1310 is playing the dialog module linked in Step 1300. Each dialog module has a message that briefly describes its associated service and lists topics associated with that service.

For example, if the caller has selected the Call Notes service, the caller hears the following message: “Call Notes voicemail records a message from callers when your phone is busy or you don't answer the call. To pick a different service, say Start over. [pause] There is also a related service called Call Notes Plus, which adds a few additional features. To find out about that, say Call Notes Plus. [pause] I have several topics related to Call Notes—thirteen in fact. I'll start reading the first set of topics, and when your hear the one you want, just interrupt me and say it. [pause] Here are the first four topics. Setup, retrieve messages, change number of rings, change passcode. [pause] Was it one of these?” If the caller responds, with “Yes” or the topic name, the dialog proceeds to Step 2000. If the caller responds “No”, the dialog continues with additional topic selections.

As with other interactive steps, each of the dialog modules of Step 1310 provides the caller with various timeout and retry options, and with a confirmation message after a topic is selected. The caller may also be given an option to speak “Start over” and return to Step 1050. During or after the playing of the dialog module, the caller may say “Repeat that” to have the topics of that dialog module repeated.

Services having numerous topics may have their dialog module divided into parts, so that the caller may hear only a portion of the topics in each part of the dialog module. The example above, listing the first four topics for Call Notes is an example of such a service. The partitioning of the topics permits the dialog module to prompt for and receive the caller's request to “start over” or “Repeat that.”

A feature of Steps 1050, 1075, and 1310 is that services and topics are presented to the caller in frequency order. That is, the most frequently requested services and topics ere offered to the caller first.

In Step 1310, one of the available topics may be a Pricing topic. Because pricing may depend on the caller's service location, if the caller selects the pricing topic, it is next determined whether the caller's phone number has been obtained in Step 1025.

Step 1625 is performed if the caller has selected a Pricing topic, and if the caller's phone number has been entered and recognized. In Step 1625, a database is queried and appropriate pricing information is accessed and reported to the caller. The dialog then proceeds to Step 2010.

Step 1600 is an interactive dialog module, performed if the caller has selected a Pricing topic and the caller's phone number has not been entered or recognized. In Step 1600, an example message to the caller is: “To get accurate pricing information, I'll need to transfer you to an SBC representative who can help. Would you like me to transfer you now?” If the caller responds, “Yes”, the call is transferred. If the caller responds “No”, the dialog proceeds to Step 2015. If desired, Step 1600 may include an additional message to request the caller's phone number, so that the dialog may then proceed to Step 1625.

Step 2000 is a Get Information dialog module, performed after the caller responds with a topic in Step 1310 and if the information is too lengthy to be played from a single dialog module. If the information is sufficiently short to be played in a single dialog module, the dialog proceeds directly to Step 2010.

The dialog of Step 2000 first plays a preamble message that corresponds to the topic that was chosen. For example, the message might be: “I have some instructions about how to set up call notes”. The next message provides the information to be provided to the caller for the selected topic.

After the message of Step 2000 is played, there are two possible paths for the remaining dialog. If all information has been given, the dialog proceeds to Step 2015. If the information is lengthy, it is spilt into more than one dialog module, and the dialog proceeds to Step 2005.

Step 2005 is a What Next voice menu module. It is performed after the information of Step 2000 has been played to the caller. This step plays a message that gives the caller the option of rehearing the information given in Step 2000 or of going on. An example message is: “Say repeat that or go on”.

As indicated above, Step 2010 is a second Get Information dialog module, and plays either the second half of information topics presented in Step 2000 or the entire information for topics that are to be played in one piece. For playing the second half of a topic, Step 2010 is performed after the caller has responded “Go on” after Step 2005. When Step 2010 is used to provide all information.

As indicated in FIG. 4B, at any point during Step 2000 or Step 2010, the caller may speak “Stop”. This causes the dialog to branch to Step 2015.

Step 2015 follows Step 2010 and is a second What Next voice menu module. If the caller has entered Step 2015 from Step 2010 and has not said “Stop”, the following message is played: “To hear that again, say Repeat That. Otherwise, . . . . ”. This provides the caller with an opportunity to hear the information from Step 2010 again.

If the caller does not say “Repeat that”, the dialog asks if the caller would like more information about the particular topic selected in Step 1310. If the caller says “Yes”, the dialog returns to Step 1310. If the caller says “No”, the dialog goes to Step 1050, and continues as explained above.

Step 5000 is a voice menu step, performed when the caller says “I'm finished” during Step 1050. Step 5000 plays a first survey question, such as: “Before you go, I just want to ask you two questions about your satisfaction with this service. First, did I give you the information you were looking for?” If the caller says “Yes”, the dialog says “Great” and proceeds to Step 5025. If the caller says “No”, the dialog proceeds to Step 5025. In either case, the response is recorded.

Step 5025 is a voice menu step, performed after Step 5000. Step 5025 plays a second survey question, such as: “And rating your experience using this system on a scale from 1 to 5 with 1 being very dissatisfied and 5 being very satisfied, what's my score?”. The caller's response is recorded and the dialog goes to Step 9100. By analyzing the recorded results of Steps 5000 and 5010, the system can evaluate its effectiveness.

Step 9100 is a good-by message. A message is played such as: Thanks for calling us. Goodbye”. The call is then ended.

The various “Repeat That” messages described above provide the caller with controllable playback, such that the caller may control the pace with which instructions are presented. Also, the division of messages into dialog modules ensures that the caller is not faced with “too much information” at once, and is given adequate opportunity to go back to a previous step or rehear a message of the present step. Each dialog has its own associated timeouts and retries, so that the caller is continually apprised of his or her position in the dialog.

Each of the above-described interactive dialog modules and voice menus includes a “Help” feature. At any time during that dialog module, the caller may say “Help”. The dialog then plays a message as specified by that dialog module. The Help feature is particularly useful during Steps 1050, 1075, and 1310, to assist the caller in identifying a topic of interest when the caller does not know the correct name of the service or product or when the caller wishes to browse topics.

Hardware for Implementation

FIG. 5 illustrates a computer system 500 for implementing the dialog interface of FIGS. 4A and 4B. An IVR Self Service Host process 505 is the main process for the system. It controls and passes tasks to various subsystems, one of which is the HTU process 510. Process 510 is programmed to perform the dialog process described above in connection with FIGS. 4A and 4B. A database 511 stores messages and instructions to be played to callers, as described above. A survey database 512 is used to store survey responses collected during the survey steps (Steps 5000 and 5025).

Claims (20)

What is claimed is:
1. A call handling method, comprising:
responsive to detecting an opening statement of a caller during a call to a service provider, the service provider comprising a plurality of call centers, determining, based on the opening statement, a caller task including an action and an object;
identifying, based on a first business rule model, a first routing destination for calls to a first call center; and
identifying, based on a second business rule model, a second routing destination for calls to a second call center;
wherein routing destinations are selected from: a call center agent, a queue, a self-service speech recognition application, and the Internet.
2. The method of claim 1, wherein the first call center comprises a how-to-use call center, and wherein identifying the first routing destination includes identifying a how-to-use destination in the how-to-use call center, wherein the how-to-use destination includes:
a plurality of dialog modules activated in response to routing decisions;
a set of verbal prompts; and
a plurality of voice recognition entry points.
3. The method of claim 2, wherein the plurality of call centers includes:
a how-to-use call center;
a billing call center;
a caller retention call center; and
an ordering call center.
4. The method of claim 2, wherein the service provider comprises a telephone service provider and wherein the how-to-use call center includes how-to-use information for telephone services provided by the telephone service provider.
5. The method of claim 1, wherein identifying routing destinations includes identifying destinations based upon an input selected from: speech indicating a name of a product, selection input selecting a topic from a menu, and verbal input describing a feature of the product.
6. The method of claim 1, wherein identifying routing destinations includes:
identifying a direct route destination when the opening statements provide sufficient routing information; and
identifying a clarification destination when the opening statements provide insufficient routing information.
7. The method of claim 1, further comprising:
collecting customer persona data during customer visits to the existing service center; and
determining language alternatives based on the persona data.
8. A computer system, comprising computer hardware programmed to perform operations, the operations comprising:
responsive to detecting an opening statement of a caller during a call to a service provider, the service provider comprising a plurality of call centers, determining, based on the opening statement, a caller task including an action and an object;
identifying, based on a first business rule model, a first routing destination for calls to a first call center; and
identifying, based on a second business rule model, a second routing destination for calls to a second call center;
wherein routing destinations are selected from: a call center agent, a queue, a self-service speech recognition application, and the Internet.
9. The computer system of claim 8, wherein the first call center comprises a how-to-use call center, and wherein identifying the first routing destination includes identifying a how-to-use destination in the how-to-use call center, wherein the how-to-use destination includes:
a plurality of dialog modules activated in response to routing decisions;
a set of verbal prompts; and
a plurality of voice recognition entry points.
10. The computer system of claim 9, wherein the plurality of call centers includes:
a how-to-use call center;
a billing call center;
a caller retention call center; and
an ordering call center.
11. The computer system of claim 9, wherein the service provider comprises a telephone service provider and wherein the how-to-use call center includes how-to-use information for telephone services provided by the telephone service provider.
12. The computer system of claim 8, wherein identifying routing destinations includes identifying destinations based upon an input selected from: speech indicating a name of a product, selection input selecting a topic from a menu, and verbal input describing a feature of the product.
13. The computer system of claim 8, wherein identifying routing destinations includes:
identifying a direct route destination when the opening statements provide sufficient routing information; and
identifying a clarification destination when the opening statements provide insufficient routing information.
14. The computer system of claim 8, wherein the operations include:
collecting customer persona data during customer visits to the existing service center; and
determining language alternatives based on the persona data.
15. Computer hardware including stored program operations, performable by a computer system, wherein the program operations, when performed by the computer system, cause the computer system to perform operations, comprising:
responsive to detecting an opening statement of a caller during a call to a service provider, the service provider comprising a plurality of call centers, determining, based on the opening statement, a caller task including an action and an object;
identifying, based on a first business rule model, a first routing destination for calls to a first call center; and
identifying, based on a second business rule model, a second routing destination for calls to a second call center;
wherein routing destinations are selected from: a call center agent, a queue, a self-service speech recognition application, and the Internet.
16. The computer hardware of claim 15, wherein the first call center comprises a how-to-use call center, and wherein identifying the first routing destination includes identifying a how-to-use destination in the how-to-use call center, wherein the how-to-use destination includes:
a plurality of dialog modules activated in response to routing decisions;
a set of verbal prompts; and
a plurality of voice recognition entry points.
17. The computer hardware of claim 16, wherein the plurality of call centers includes:
a how-to-use call center;
a billing call center;
a caller retention call center; and
an ordering call center.
18. The computer hardware of claim 16, wherein the service provider comprises a telephone service provider and wherein the how-to-use call center includes how-to-use information for telephone services provided by the telephone service provider.
19. The computer hardware of claim 15, wherein identifying routing destinations includes identifying destinations based upon an input selected from: speech indicating a name of a product, selection input selecting a topic from a menu, and verbal input describing a feature of the product.
20. The computer hardware of claim 15, wherein the operations include:
collecting customer persona data during customer visits to the existing service center; and
determining language alternatives based on the persona data.
US14312310 2004-05-24 2014-06-23 Method for designing an automated speech recognition (ASR) interface for a customer call center Active US9197752B2 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US10852342 US7460650B2 (en) 2004-05-24 2004-05-24 Method for designing an automated speech recognition (ASR) interface for a customer call center
US12326630 US8315360B2 (en) 2004-05-24 2008-12-02 Method for designing an automated speech recognition (ASR) interface for a customer call center
US13681970 US8761381B2 (en) 2004-05-24 2012-11-20 Method for designing an automated speech recognition (ASR) interface for a customer call center
US14312310 US9197752B2 (en) 2004-05-24 2014-06-23 Method for designing an automated speech recognition (ASR) interface for a customer call center

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14312310 US9197752B2 (en) 2004-05-24 2014-06-23 Method for designing an automated speech recognition (ASR) interface for a customer call center

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US13681970 Continuation US8761381B2 (en) 2004-05-24 2012-11-20 Method for designing an automated speech recognition (ASR) interface for a customer call center

Publications (2)

Publication Number Publication Date
US20140314228A1 true US20140314228A1 (en) 2014-10-23
US9197752B2 true US9197752B2 (en) 2015-11-24

Family

ID=35376318

Family Applications (4)

Application Number Title Priority Date Filing Date
US10852342 Active 2026-05-11 US7460650B2 (en) 2004-05-24 2004-05-24 Method for designing an automated speech recognition (ASR) interface for a customer call center
US12326630 Active 2027-03-12 US8315360B2 (en) 2004-05-24 2008-12-02 Method for designing an automated speech recognition (ASR) interface for a customer call center
US13681970 Active US8761381B2 (en) 2004-05-24 2012-11-20 Method for designing an automated speech recognition (ASR) interface for a customer call center
US14312310 Active US9197752B2 (en) 2004-05-24 2014-06-23 Method for designing an automated speech recognition (ASR) interface for a customer call center

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US10852342 Active 2026-05-11 US7460650B2 (en) 2004-05-24 2004-05-24 Method for designing an automated speech recognition (ASR) interface for a customer call center
US12326630 Active 2027-03-12 US8315360B2 (en) 2004-05-24 2008-12-02 Method for designing an automated speech recognition (ASR) interface for a customer call center
US13681970 Active US8761381B2 (en) 2004-05-24 2012-11-20 Method for designing an automated speech recognition (ASR) interface for a customer call center

Country Status (1)

Country Link
US (4) US7460650B2 (en)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7580837B2 (en) 2004-08-12 2009-08-25 At&T Intellectual Property I, L.P. System and method for targeted tuning module of a speech recognition system
US7043435B2 (en) 2004-09-16 2006-05-09 Sbc Knowledgfe Ventures, L.P. System and method for optimizing prompts for speech-enabled applications
US7242751B2 (en) 2004-12-06 2007-07-10 Sbc Knowledge Ventures, L.P. System and method for speech recognition-enabled automatic call routing
US7751551B2 (en) 2005-01-10 2010-07-06 At&T Intellectual Property I, L.P. System and method for speech-enabled call routing
US7657020B2 (en) 2005-06-03 2010-02-02 At&T Intellectual Property I, Lp Call routing system and method of using the same
US20070067197A1 (en) * 2005-09-16 2007-03-22 Sbc Knowledge Ventures, L.P. Efficiently routing customer inquiries created with a self-service application
US9009046B1 (en) * 2005-09-27 2015-04-14 At&T Intellectual Property Ii, L.P. System and method for disambiguating multiple intents in a natural language dialog system
JP2007114621A (en) * 2005-10-21 2007-05-10 Aruze Corp Conversation controller
US7505951B2 (en) * 2006-05-30 2009-03-17 Motorola, Inc. Hierarchical state machine generation for interaction management using goal specifications
US7797672B2 (en) * 2006-05-30 2010-09-14 Motorola, Inc. Statechart generation using frames
US20080091423A1 (en) * 2006-10-13 2008-04-17 Shourya Roy Generation of domain models from noisy transcriptions
US8605885B1 (en) 2008-10-23 2013-12-10 Next It Corporation Automated assistant for customer service representatives
EP2299440B1 (en) * 2009-09-11 2012-10-31 Vodafone Holding GmbH Method and Device for automatic recognition of given keywords and/or terms within voice data
US9798799B2 (en) * 2012-11-15 2017-10-24 Sri International Vehicle personal assistant that interprets spoken natural language input based upon vehicle context
US10133546B2 (en) 2013-03-14 2018-11-20 Amazon Technologies, Inc. Providing content on multiple devices
US9842584B1 (en) 2013-03-14 2017-12-12 Amazon Technologies, Inc. Providing content on multiple devices
US9201865B2 (en) * 2013-03-15 2015-12-01 Bao Tran Automated assistance for user request that determines semantics by domain, task, and parameter
US9298811B2 (en) * 2013-07-15 2016-03-29 International Business Machines Corporation Automated confirmation and disambiguation modules in voice applications

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5926539A (en) 1997-09-12 1999-07-20 Genesys Telecommunications Laboratories, Inc. Method and apparatus for determining agent availability based on level of uncompleted tasks
US6134530A (en) 1998-04-17 2000-10-17 Andersen Consulting Llp Rule based routing system and method for a virtual sales and service center
US20020032564A1 (en) 2000-04-19 2002-03-14 Farzad Ehsani Phrase-based dialogue modeling with particular application to creating a recognition grammar for a voice-controlled user interface
US6480599B1 (en) 1996-09-04 2002-11-12 Telefonaktiebolaget Lm Ericsson (Publ) Telecommunications system and method for automatic call recognition and distribution
US20020199182A1 (en) * 2001-02-15 2002-12-26 Susan Whitehead Method and apparatus providing convergent solution to end-to end, adaptive business application management
US20020196277A1 (en) * 2000-03-21 2002-12-26 Sbc Properties, L.P. Method and system for automating the creation of customer-centric interfaces
US6584192B1 (en) 1999-12-06 2003-06-24 Genesys Telecommunications Laboratories, Inc. Method and apparatus for skills-based task routing
US20030204404A1 (en) 2002-04-25 2003-10-30 Weldon Phyllis Marie Dyer Systems, methods and computer program products for designing, deploying and managing interactive voice response (IVR) systems
US6823054B1 (en) 2001-03-05 2004-11-23 Verizon Corporate Services Group Inc. Apparatus and method for analyzing an automated response system
US20060165066A1 (en) 2000-01-07 2006-07-27 Aastra Intecom Inc. Customer communication service system

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6480599B1 (en) 1996-09-04 2002-11-12 Telefonaktiebolaget Lm Ericsson (Publ) Telecommunications system and method for automatic call recognition and distribution
US5926539A (en) 1997-09-12 1999-07-20 Genesys Telecommunications Laboratories, Inc. Method and apparatus for determining agent availability based on level of uncompleted tasks
US6134530A (en) 1998-04-17 2000-10-17 Andersen Consulting Llp Rule based routing system and method for a virtual sales and service center
US6584192B1 (en) 1999-12-06 2003-06-24 Genesys Telecommunications Laboratories, Inc. Method and apparatus for skills-based task routing
US20060165066A1 (en) 2000-01-07 2006-07-27 Aastra Intecom Inc. Customer communication service system
US20020196277A1 (en) * 2000-03-21 2002-12-26 Sbc Properties, L.P. Method and system for automating the creation of customer-centric interfaces
US20020032564A1 (en) 2000-04-19 2002-03-14 Farzad Ehsani Phrase-based dialogue modeling with particular application to creating a recognition grammar for a voice-controlled user interface
US20020199182A1 (en) * 2001-02-15 2002-12-26 Susan Whitehead Method and apparatus providing convergent solution to end-to end, adaptive business application management
US6823054B1 (en) 2001-03-05 2004-11-23 Verizon Corporate Services Group Inc. Apparatus and method for analyzing an automated response system
US20030204404A1 (en) 2002-04-25 2003-10-30 Weldon Phyllis Marie Dyer Systems, methods and computer program products for designing, deploying and managing interactive voice response (IVR) systems

Also Published As

Publication number Publication date Type
US20140314228A1 (en) 2014-10-23 application
US20130077770A1 (en) 2013-03-28 application
US20090074158A1 (en) 2009-03-19 application
US20050261902A1 (en) 2005-11-24 application
US8761381B2 (en) 2014-06-24 grant
US8315360B2 (en) 2012-11-20 grant
US7460650B2 (en) 2008-12-02 grant

Similar Documents

Publication Publication Date Title
US6718017B1 (en) System and method for creating and controlling interactive voice response applications
US7995717B2 (en) Method and system for analyzing separated voice data of a telephonic communication between a customer and a contact center by applying a psychological behavioral model thereto
US6807574B1 (en) Method and apparatus for content personalization over a telephone interface
US7076051B2 (en) Promoting caller voice browsing in a hold queue
US6788770B1 (en) Intelligent voice response system with navigator database
US7184540B2 (en) Personality based matching of callers to agents in a communication system
US6757362B1 (en) Personal virtual assistant
US6643622B2 (en) Data retrieval assistance system and method utilizing a speech recognition system and a live operator
US6195426B1 (en) Service providing customized information to queuing customers
US5214689A (en) Interactive transit information system
US7606718B2 (en) Apparatus and method for processing service interactions
US5982857A (en) Voice recording method and system providing context specific storage and retrieval
US5881134A (en) Intelligent call processing platform for home telephone system
US7095842B2 (en) Enabling caller controlled hold queue position adjustment
US6442242B1 (en) Multifunction autoattendant system and method of operation thereof
US7076427B2 (en) Methods and apparatus for audio data monitoring and evaluation using speech recognition
US5355406A (en) Integrated application controlled call processing and messaging system
US6931104B1 (en) Intelligent call processing platform for home telephone system
US6370238B1 (en) System and method for improved user interface in prompting systems
US6069940A (en) Apparatus and method for adding a subject line to voice mail messages
US20060262919A1 (en) Method and system for analyzing separated voice data of a telephonic communication between a customer and a contact center by applying a psychological behavioral model thereto
US6853722B2 (en) System and method for automating customer slamming and cramming complaints
US5283731A (en) Computer-based classified ad system and method
US7197461B1 (en) System and method for voice-enabled input for use in the creation and automatic deployment of personalized, dynamic, and interactive voice services
US6584180B2 (en) Automatic voice response system using voice recognition means and method of the same

Legal Events

Date Code Title Description
AS Assignment

Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., F/K/A SBC KNOW

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUSHEY, ROBERT R.;KNOTT, BENJAMIN A.;MARTIN, JOHN M.;REEL/FRAME:033160/0283

Effective date: 20040519

AS Assignment

Owner name: AT&T KNOWLEDGE VENTURES, L.P., NEVADA

Free format text: CHANGE OF NAME;ASSIGNOR:SBC KNOWLEDGE VENTURES, L.P.;REEL/FRAME:038898/0520

Effective date: 20060224

Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., GEORGIA

Free format text: CHANGE OF NAME;ASSIGNOR:AT&T KNOWLEDGE VENTURES, L.P.;REEL/FRAME:038898/0574

Effective date: 20071001

Owner name: SBC KNOWLEDGE VENTURES, L.P., NEVADA

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED ON REEL 033160 FRAME 0283. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNORS:BUSHEY, ROBERT R.;KNOTT, BENJAMIN A.;MARTIN, JOHN M.;REEL/FRAME:038902/0985

Effective date: 20040519

AS Assignment

Owner name: NUANCE COMMUNICATIONS, INC., MASSACHUSETTS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T INTELLECTUAL PROPERTY I, L.P.;REEL/FRAME:041504/0952

Effective date: 20161214