US20090041212A1 - Interactive Voice Response System With Prioritized Call Monitoring - Google Patents

Interactive Voice Response System With Prioritized Call Monitoring Download PDF

Info

Publication number
US20090041212A1
US20090041212A1 US12/240,905 US24090508A US2009041212A1 US 20090041212 A1 US20090041212 A1 US 20090041212A1 US 24090508 A US24090508 A US 24090508A US 2009041212 A1 US2009041212 A1 US 2009041212A1
Authority
US
United States
Prior art keywords
dialog
human
monitoring
caller
dialog sequence
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.)
Granted
Application number
US12/240,905
Other versions
US8085927B2 (en
Inventor
George William Erhart
Valentine C. Matula
David Joseph Skiba
Glen A. Taylor
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.)
ServiceNow Inc
Original Assignee
Avaya Inc
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
Priority claimed from US11/107,673 external-priority patent/US7471786B2/en
Application filed by Avaya Inc filed Critical Avaya Inc
Priority to US12/240,905 priority Critical patent/US8085927B2/en
Assigned to AVAYA INC. reassignment AVAYA INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TAYLOR, GLEN A., ERHART, GEORGE WILLIAM, MATULA, VALENTINE C., SKIBA, DAVID JOSEPH
Publication of US20090041212A1 publication Critical patent/US20090041212A1/en
Assigned to BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE reassignment BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE SECURITY AGREEMENT Assignors: AVAYA INC., A DELAWARE CORPORATION
Application granted granted Critical
Publication of US8085927B2 publication Critical patent/US8085927B2/en
Assigned to BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE reassignment BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE SECURITY AGREEMENT Assignors: AVAYA, INC.
Assigned to CITIBANK, N.A., AS ADMINISTRATIVE AGENT reassignment CITIBANK, N.A., AS ADMINISTRATIVE AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AVAYA INC., AVAYA INTEGRATED CABINET SOLUTIONS INC., OCTEL COMMUNICATIONS CORPORATION, VPNET TECHNOLOGIES, INC.
Assigned to AVAYA INC. reassignment AVAYA INC. BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535 Assignors: THE BANK OF NEW YORK MELLON TRUST, NA
Assigned to AVAYA INC. reassignment AVAYA INC. BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Assignors: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Assigned to OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION), AVAYA INC., AVAYA INTEGRATED CABINET SOLUTIONS INC., VPNET TECHNOLOGIES, INC. reassignment OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION) BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Assignors: CITIBANK, N.A.
Assigned to GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT reassignment GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AVAYA INC., AVAYA INTEGRATED CABINET SOLUTIONS LLC, OCTEL COMMUNICATIONS LLC, VPNET TECHNOLOGIES, INC., ZANG, INC.
Assigned to CITIBANK, N.A., AS COLLATERAL AGENT reassignment CITIBANK, N.A., AS COLLATERAL AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AVAYA INC., AVAYA INTEGRATED CABINET SOLUTIONS LLC, OCTEL COMMUNICATIONS LLC, VPNET TECHNOLOGIES, INC., ZANG, INC.
Assigned to AVAYA INC. reassignment AVAYA INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: CITIBANK, N.A.
Assigned to AVAYA INC. reassignment AVAYA INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: GOLDMAN SACHS BANK USA
Assigned to SERVICENOW, INC. reassignment SERVICENOW, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AVAYA INC.
Assigned to AVAYA INTEGRATED CABINET SOLUTIONS LLC, AVAYA HOLDINGS CORP., AVAYA MANAGEMENT L.P., AVAYA INC. reassignment AVAYA INTEGRATED CABINET SOLUTIONS LLC RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Assignors: CITIBANK, N.A., AS COLLATERAL AGENT
Assigned to AVAYA MANAGEMENT L.P., HYPERQUALITY, INC., AVAYA INC., CAAS TECHNOLOGIES, LLC, OCTEL COMMUNICATIONS LLC, VPNET TECHNOLOGIES, INC., INTELLISIST, INC., HYPERQUALITY II, LLC, AVAYA INTEGRATED CABINET SOLUTIONS LLC, ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.) reassignment AVAYA MANAGEMENT L.P. RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Assignors: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
Active legal-status Critical Current
Adjusted expiration legal-status Critical

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/42221Conversation recording systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/22Arrangements for supervision, monitoring or testing
    • H04M3/2281Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls
    • 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/5166Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing in combination with interactive voice response systems or voice portals, e.g. as front-ends
    • 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
    • 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 or time announcements
    • H04M3/493Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals

Definitions

  • the present invention relates to telecommunications in general, and, more particularly, to an interactive voice response system that enables partial human monitoring of calls.
  • a call center is a place where calls from users, such as customers, are handled in support of an organization's activities.
  • Organizations that provide a call center such as companies that offer a service or a product, do so to provide assistance and information to customers of the service or product.
  • a call center typically comprises an interactive voice response (IVR) system that enables a caller to obtain information without any human involvement, or to speak to a person known as a service agent.
  • IVR interactive voice response
  • an interactive voice response (IVR) system presents a hierarchy of menus to a caller, and enables the caller to input information to navigate the menus (e.g., entering alphanumeric information via a telephone keypad, selecting a menu option by saying the number associated with the option, etc.).
  • An interactive voice response (IVR) system is advantageous economically because it enables a call center to accommodate callers with fewer service agents.
  • FIG. 1 depicts telecommunications system 100 in accordance with the prior art.
  • Telecommunications system 100 comprises telecommunications terminal 102 , telecommunications network 103 , and call center 104 , interconnected as shown.
  • telecommunications terminal 102 e.g., a telephone, a browser-enabled client, etc.
  • telecommunications network 103 e.g., the Public Switched Telephone Network [PSTN], the Internet, etc.
  • PSTN Public Switched Telephone Network
  • user 101 uses telecommunications terminal 102 to place a voice telephone call to call center 104 .
  • user 101 might initiate a text-based instant messaging (IM) session, or might activate a “push-to-talk” button on a website that is associated with call center 104 , etc.
  • IM instant messaging
  • FIG. 2 depicts the salient elements of call center 104 , in accordance with the prior art.
  • Call center 104 comprises data-processing system 205 ; interactive voice response system (IVR) 206 ; telecommunications terminals 207 - 1 through 207 -N, where N is a positive integer; clients 209 - 1 through 209 -N; and application server 210 , interconnected as shown.
  • IVR interactive voice response system
  • Service agent converse with callers via telecommunications terminal 207 , and interact with one or more software applications via client 209 - n (e.g., a personal computer, a “dumb” terminal, etc.), both during a call and between calls.
  • the software applications are client/server or web-based and are hosted on application server 210 , in well-known fashion.
  • Private branch exchange (PBX) 205 receives incoming calls from telecommunications network 103 and directs the calls to interactive voice response (IVR) system 206 or to one of telecommunications terminals 207 .
  • Private branch exchange (PBX) 205 also receives outbound signals from telecommunications terminals 507 and interactive voice response system 506 and transmits the signals on to telecommunications network 103 for delivery to the caller's terminal.
  • Interactive voice response (IVR) system 206 prompts a caller for information and menu selections via synthesized speech, and receives input from the caller (e.g., speech signals, keypad input, etc.) via private branch exchange 205 .
  • Interactive voice response system 206 is also capable of: recording a caller's speech and keypad input during a call; performing automated speech recognition (ASR) on a caller's speech; submitting commands and forwarding caller input to one or more software applications that reside on application server 210 ; and receiving output from these software applications.
  • ASR automated speech recognition
  • Application server 210 hosts one or more web-based or client/server software applications that perform tasks such as customer record maintenance, inventory management, order processing, etc. As described above, these software applications can be accessed by both clients 209 and interactive voice response (IVR) system 206 .
  • IVR interactive voice response
  • the Extensible Markup Language is a specification that enables the creation of customized tags, which in turn enables the definition, transmission, validation, and interpretation of data between two applications, organizations, etc.
  • Voice Extensible Markup Language abbreviated VoiceXML or VXML
  • XML Extensible Markup Language
  • VXML Voice Extensible Markup Language
  • the primary objective of VXML is to bring the advantages of web-based development and content delivery to interactive voice response applications.
  • FIG. 3 depicts an exemplary Voice Extensible Markup Language (VXML) script (also known as a VXML document or page), in accordance with the illustrative embodiment of the present invention.
  • VXML Voice Extensible Markup Language
  • the VXML script when executed by interactive voice response system 206 , prompts the caller for his or her social security number, and then his or her mother's maiden name for security purposes. The script then presents a menu with two options; the first option is for reviewing account balances, and the second option is for performing transactions. Audio content (in particular, synthesized speech) that corresponds to text between the ⁇ prompt> and ⁇ /prompt> tags is generated by interactive voice response system 206 and transmitted to the caller.
  • Audio content in particular, synthesized speech
  • application server 210 In call centers that employ VXML scripts, typically application server 210 initially retrieves a “top-level” script at the beginning of a call, and subsequently, in response to menu selections and information supplied by the caller, application server 210 might retrieve one or more additional VXML scripts during the course of a call (e.g., a script for reviewing account balances, a script for processing transactions, etc.). Alternatively, a single large VXML script or application might be employed for the entire duration of a call.
  • a problem with interactive voice response (IVR) systems is that automated speech recognition (ASR) is typically very accurate for some inputs such as zip code and social security number, but can be much less accurate for others such as name, street address, etc. It would be advantageous, therefore, if a service agent could monitor a call and validate information provided by the caller, correct erroneous information, and so forth. If service agents monitor each call, however, the economic advantage of using an interactive voice response (IVR) system is greatly diminished.
  • ASR automated speech recognition
  • the present invention enables service agents to monitor particular portions of calls that are especially error-prone (e.g., automated speech recognition of an address, etc.), while portions of calls that are not error-prone occur without any human monitoring.
  • an interactive voice response (IVR) system script e.g., a VXML script, etc.
  • IVR interactive voice response
  • the illustrative embodiments of the present invention assign priorities to the instances of the dialog sequences in calls, based on an indication of caller intelligibility during (i) prior dialog sequences in the current call, and (ii) prior calls involving the same caller and/or the same contact identifier (e.g., telephone number, email address, Internet Protocol address, etc.).
  • An indication of caller intelligibility might be based on a variety of criteria, such as the number of times that a caller was required to repeat an input, a property of the caller's speech (e.g., speed, accent, a measure of how well phonemes are enunciated, etc.), how long a service agent spoke with the caller to obtain information, and so forth.
  • a partial ordering is defined that indicates which dialog sequences must occur before other dialog sequences.
  • the partial ordering may enable a first dialog sequence that comes after a second dialog sequence in the script to in fact be executed before the second dialog sequence when it is advantageous to do so. For example, suppose a first dialogue sequence of an interactive voice response (IVR) script asks for the caller's name, and a second dialog sequence that occurs after the first dialogue sequence in the script asks for the caller's telephone number.
  • IVR interactive voice response
  • dialog sequences would be indicated as permissible by the partial ordering.
  • dialog sequences there are some pairs of dialog sequences that should not be reordered in this fashion, as would be indicated by the partial ordering. For example, the options for a second-level menu should not be presented until after the options for a first-level menu have been presented and the caller has input his or her selection for the first-level menu.
  • each dialog sequences that requires human monitoring is recorded and packaged into an agent-review task, which is subsequently sent to an available service agent for review.
  • the agent-review task also contains the automated speech recognition (ASR) for the dialog sequence, thus enabling the service agent to check for any errors and make any necessary corrections.
  • ASR automated speech recognition
  • both illustrative embodiments enable a call center to function with fewer service agents.
  • An illustrative embodiment comprises: selecting a dialog sequence from a non-empty set S of dialog sequences, wherein each of the dialog sequences has a human-monitoring requirement; and executing the dialog sequence during a call that involves a caller and an interactive voice response system; wherein the selection of the dialog sequence is based on: (i) the human-monitoring requirements, (ii) the availability of one or more service agents, and (iii) an indication of the intelligibility of the caller in one or more prior dialog sequences of the call.
  • FIG. 1 depicts telecommunications system 100 in accordance with the prior art.
  • FIG. 4 depicts telecommunications system 400 in accordance with the illustrative embodiments of the present invention.
  • FIG. 5 depicts the salient elements of call center 404 , as shown in FIG. 4 , in accordance with the illustrative embodiments of the present invention.
  • FIG. 7 depicts a detailed flowchart of task 650 , as shown in FIG. 6 , in accordance with the first illustrative embodiment of the present invention.
  • FIG. 8 depicts a flowchart of the salient tasks involved in processing an interactive voice response script, in accordance with the second illustrative embodiment of the present invention.
  • FIG. 9 depicts a detailed flowchart of task 840 , as shown in FIG. 8 , in accordance with the second illustrative embodiment of the present invention.
  • FIG. 10 depicts an event loop for the salient tasks involved in delivering agent-review tasks to service agents, in accordance with the second illustrative embodiment of the present invention.
  • FIG. 11 depicts an event loop for the salient tasks involved in handling messages from service agents who process agent-review tasks, in accordance with the second illustrative embodiment of the present invention.
  • call is defined as an interactive communication involving one or more telecommunications terminal users.
  • a call might be a traditional voice telephone call, an instant messaging (IM) session, a video conference, etc.
  • IM instant messaging
  • contact identifier is defined as a string of symbols that is associated with a participant of a call (e.g., a telephone number, an email address, an Internet Protocol address, etc.).
  • FIG. 4 depicts telecommunications system 400 in accordance with the illustrative embodiments of the present invention.
  • Telecommunications system 400 comprises telecommunications terminal 102 and telecommunications network 103 of the prior art, and call center 404 , interconnected as shown.
  • FIG. 5 depicts the salient elements of call center 404 , in accordance with the illustrative embodiments of the present invention.
  • Call center 404 comprises private branch exchange (PBX) 505 ; interactive voice response system (IVR) 506 ; telecommunications terminals 507 - 1 through 507 -N, where N is a positive integer; clients 509 - 1 through 509 -N; application server 510 ; and database 511 , interconnected as shown.
  • PBX private branch exchange
  • IVR interactive voice response system
  • Application server 510 has the same capabilities as application server 210 of the prior art, and is also capable of storing and retrieving data to and from database 511 , and of performing additional tasks as described below and with respect to FIGS. 6 through 10 .
  • Private branch exchange (PBX) 505 is similar to PBX 205 of the prior art and interacts with telecommunications network 103 , interactive voice response system (IVR) 506 , and telecommunications terminals 507 - 1 through 507 -N as described above for PBX 205 .
  • IVR interactive voice response system
  • Private branch exchange (PBX) 505 has the same capabilities as PBX 205 of the prior art.
  • Telecommunications terminals 507 - 1 through 507 -N are have the same capabilities as telecommunications terminals 207 - 1 through 207 -N of the prior art.
  • Clients 508 - 1 through 508 -N have the same capabilities as clients 208 - 1 through 208 -N of the prior art.
  • Interactive voice response (IVR) system 506 has the same capabilities as IVR system 206 of the prior art, and is also capable of receiving commands from application server 510 to start and stop recording of a call while the call is in progress, and of storing and retrieving data to and from database 511 .
  • Database 511 is a database that is capable of receiving data from IVR system 506 and application server 510 , and of storing and organizing the data in a manner that enables efficient retrieval.
  • database 511 is capable of storing indications of caller intelligibility for calls and for individual dialog sequences of calls.
  • an indication of caller intelligibility might be based on a variety of criteria, such as the number of times that a caller was required to repeat an input, a property of the caller's speech (e.g., speed, accent, a measure of how well phonemes are enunciated, etc.), how long a service agent spoke with the caller to obtain information, and so forth.
  • database 404 is a relational database; however, it will be clear to those skilled in the art, after reading this disclosure, how to make use other embodiments of the present invention in which database 404 is some other type of database (e.g., an object-oriented database, a hierarchical database, etc.).
  • database 404 is some other type of database (e.g., an object-oriented database, a hierarchical database, etc.).
  • FIG. 6 depicts a flowchart of the salient tasks involved in processing an interactive voice response script, in accordance with the first illustrative embodiment of the present invention.
  • application server 510 retrieves an appropriate IVR script (e.g., a VXML script, etc.) during a call C, in well-known fashion.
  • an appropriate IVR script e.g., a VXML script, etc.
  • a dialog sequence is a portion of a IVR script that is independent of any other portions of the IVR script.
  • the script might be divided into the following three dialog sequences: a first dialog sequence that comprises greeting the caller, asking for his or her social security number, and validating the social security number against a database; a second dialog sequence that comprises asking the caller for his or her mother's maiden name and validating the name against a database; and a third dialog sequence that comprises presenting the options of the menu and obtaining the caller's selection. It will be clear to those skilled in the art how to parse a IVR script and divide the script into a set of dialog sequences.
  • application server 510 defines a partial ordering on the dialog sequences of set S.
  • the partial ordering means that either: a first dialog sequence might temporally come before a second dialog sequence (i.e., the first dialog sequence is a predecessor of the second dialog sequence); the second dialog sequence is a predecessor of the first dialog sequence; or they are temporally unrelated (i.e., either the first can come before the second, or the second can come before the first).
  • a partial ordering over set S is a relation R ⁇ S ⁇ S such that:
  • application server 510 assigns or generates human-monitoring requirements for the dialog sequences of set S.
  • a human-monitoring requirement might be a simple Boolean value that indicates whether a dialog sequence requires any human monitoring, while in some other embodiments a human-monitoring requirement might be a numeric value that indicates the degree to which a dialog sequence requires human monitoring, or yet some other data type.
  • human-monitoring requirements can be assigned manually or generated automatically, and can be based on empirical data (e.g., the error rate of a particular dialog sequence or of a particular class of dialog sequences, etc.), or on heuristics that take into account the length of a dialog sequence, the kind of input requested from the caller in a dialog sequence, and so forth.
  • empirical data e.g., the error rate of a particular dialog sequence or of a particular class of dialog sequences, etc.
  • heuristics that take into account the length of a dialog sequence, the kind of input requested from the caller in a dialog sequence, and so forth.
  • application server 510 selects a dialog sequence d from set S based on:
  • the selected dialog sequence d is removed from set S.
  • application server 510 checks whether dialog sequence d requires human monitoring. As will be appreciated by those skilled in the art, in some embodiments this might be accomplished by checking whether a Boolean value associated with dialog sequence d is true, while in some other embodiments this might be accomplished by checking whether a numeric value is non-zero. If dialog sequence d requires human monitoring, execution proceeds to task 665 ; otherwise execution continues at task 680 .
  • application server 510 checks what fraction of service agents are available. If the fraction is above a threshold, execution continues at task 680 . Otherwise, application server 510 consults database 411 and determines a priority for human-monitoring based on one or more indications of caller intelligibility during (i) prior dialog sequences in the current call C, and/or (ii) prior calls involving the same caller and/or the same contact identifier (e.g., telephone number, email address, Internet Protocol address, etc.). If the priority is not above a threshold, execution continues at task 680 , otherwise execution continues at task 670 .
  • a priority for human-monitoring based on one or more indications of caller intelligibility during (i) prior dialog sequences in the current call C, and/or (ii) prior calls involving the same caller and/or the same contact identifier (e.g., telephone number, email address, Internet Protocol address, etc.).
  • the identity of the caller might be known via a login procedure or a customer number that the caller inputs, while in some other embodiments, no such explicit identification of the caller might be available, in which case the contact identifier might be used as a good but imperfect proxy for the caller's identity.
  • IVR interactive voice response
  • stall phrase e.g., “One moment please”, etc.
  • filling e.g., “Are you still at address 123 Maple Lane?”, “As a valued customer, can we take a moment to ask about some questions about your last on-line order experience?”, etc.
  • private branch exchange 505 bridges an available service agent into call C, in well-known fashion.
  • the service agent's client 509 enables the service agent to validate information provided during the dialog sequence, correct the information, and so forth.
  • the service agent might receive a visual representation of the dialog sequence at respective client 509 , either in addition to or in lieu of audio bridging (as disclosed, for example, in U.S. patent application Ser. No. 10/874,791, incorporated by reference).
  • interactive voice response (IVR) system 506 executes dialog sequence d for call C, in well-known fashion.
  • private branch exchange 505 drops the service agent from call C, in well-known fashion.
  • service agent's client 509 also closes the visual representation and the interface for validating and correcting information.
  • the dialog sequence is executed without monitoring by an agent, and a recording of the dialog sequence is subsequently sent to an available service agent for review, as described below and with respect to the second illustrative embodiment.
  • interactive voice response (IVR) system 506 executes dialog sequence d for call C, in well-known fashion.
  • application server 510 stores in database 511 an indication of caller intelligibility for the dialog sequence d, along with the identity of the caller and/or contact identifier.
  • the indication of caller intelligibility might be based on a variety of criteria, such as the number of times that a caller was required to repeat an input, a property of the caller's speech (e.g., speed, accent, a measure of how well phonemes are enunciated, etc.), how long a service agent spoke with the caller to obtain information, and so forth.
  • application server 510 checks whether set S is empty. If so, the method of FIG. 6 terminates; otherwise execution continues back at task 650 .
  • FIG. 7 depicts a detailed flowchart of task 650 in accordance with the first illustrative embodiment of the present invention.
  • variable T is initialized to the set of dialog sequences in S that have no predecessor.
  • set T contains the dialog sequences of S that do not require another dialog sequence of S to occur beforehand, and thus are candidates for execution by interactive voice response (IVR) system 506 .
  • IVR interactive voice response
  • application server 510 checks whether there is an available service agent. If not, execution proceeds to task 730 ; otherwise, execution continues at task 740 .
  • application server 510 selects a dialog sequence from set T that has the least human-monitoring requirement (e.g., the smallest numerical value, a requirement of false, etc.) After task 730 , task 650 is completed and execution proceeds to task 655 .
  • the least human-monitoring requirement e.g., the smallest numerical value, a requirement of false, etc.
  • application server 510 checks whether all the dialog sequences of set T have identical human-monitoring requirements. If not, execution proceeds to task 750 ; otherwise, execution continues at task 760 .
  • application server 510 selects a dialog sequence from set T that does not have the least human-monitoring requirement.
  • any dialog sequence that does not have the least human-monitoring requirement might be selected, while some other embodiments might employ a heuristic for selecting a dialog sequence, perhaps based on the lengths of the dialog sequences, the estimated time until a service agent is available, etc.
  • task 650 is completed and execution proceeds to task 655 .
  • application server 510 selects any dialog sequence from set T.
  • a dialog sequence might be selected arbitrarily, while some other embodiments might employ a heuristic for selecting a dialog sequence.
  • task 650 is completed and execution proceeds to task 655 .
  • FIG. 8 depicts a flowchart of the salient tasks involved in processing an interactive voice response script, in accordance with the second illustrative embodiment of the present invention.
  • application server 510 retrieves an appropriate IVR script during a call C, in well-known fashion.
  • application server 510 identifies the dialog sequences of the IVR script. It will be clear to those skilled in the art how to parse a IVR script and identify its constituent dialog sequences.
  • application server 510 assigns or generates human-monitoring requirements for the dialog sequences, as described above and with respect to task 640 .
  • IVR interactive voice response
  • FIG. 9 depicts a detailed flowchart of task 840 , in accordance with the second illustrative embodiment of the present invention.
  • application server 510 checks whether the current position in the script (initially, the first line of the script) is the beginning of a dialog sequence that requires human monitoring. If so, execution proceeds to task 920 ; otherwise, execution continues at task 930 .
  • application server 510 sends a signal to interactive voice response (IVR) system 506 to start recording of the dialog sequence.
  • IVR interactive voice response
  • application server 510 checks whether the current position in the script is the end of a dialog sequence that requires human monitoring. If so, execution proceeds to task 940 ; otherwise, execution continues at task 970 .
  • application server 510 sends a signal to interactive voice response (IVR) system 506 to stop recording of the dialog sequence.
  • IVR interactive voice response
  • application server 510 creates an agent-review task comprising: (i) a recording of the just-completed dialog sequence, and (ii) the result of IVR system 506 's automatic speech recognition for the just-completed dialog sequence.
  • application server 510 adds the agent-review task to a queue for delivery to an available service agent. After task 960 , execution continues at task 980 .
  • interactive voice response (IVR) system 506 executes the current command of the script, in well-known fashion.
  • application server 510 checks whether the end of the script has been reached. If so, the method of FIG. 9 terminates; otherwise execution continues at task 990 .
  • application server 510 advances the current position in the script to the next command, and execution continues back at task 910 .
  • FIG. 10 depicts an event loop for the salient tasks involved in delivering agent-review tasks to service agents, in accordance with the second illustrative embodiment of the present invention.
  • the event loop waits until both (i) the agent-review task queue is non-empty, and (ii) there are one or more available service agents.
  • an agent-review task is removed from the front of the queue and sent to an available service agent, in well-known fashion. After task 1020 , execution continues back at task 1010 .
  • FIG. 11 depicts an event loop for the salient tasks involved in handling messages from service agents who process agent-review tasks, in accordance with the second illustrative embodiment of the present invention.
  • an agent-review message is received from a service agent A, in well-known fashion.
  • Task 1120 checks whether the message contains a request to intervene in the call. If so, execution continues at task 1130 , otherwise execution proceeds to task 1140 .
  • private branch exchange 505 bridges service agent A into the call, in well-known fashion. After task 1130 , execution continues back at task 1110 .
  • Task 1140 checks whether the message contains a request for one or more new dialog sequences from the call. If so, execution continues at task 1150 , otherwise execution proceeds to task 1170 .
  • interactive voice response (IVR) system 506 retrieves recordings of the requested dialog sequences, in well-known fashion.
  • agent-review tasks that correspond to the recordings are created and sent to service agent A. After task 1160 , execution continues back at task 1110 .
  • the message contains an approval by the service agent and, optionally, an indication of which caller inputs, if any, were modified by the service agent.
  • the message is logged in well-known fashion, and execution continues back at task 1110 .
  • a combination of the first and second illustrative embodiments is possible in which a dialog sequence that requires human monitoring is monitored in real-time when a service agent is available, as in the first illustrative embodiment, and when no service agent is available, an agent-review task is created, as in the second illustrative embodiment.

Abstract

The present invention enables service agents in a call center to monitor portions of calls that are especially error-prone (e.g., automated speech recognition of an address, etc.), while portions of calls that are not error-prone occur without any human monitoring. An interactive voice response (IVR) system script (e.g., a VXML script, etc.) is divided into a plurality of independent dialog sequences, each of which is assigned a human-monitoring requirement that indicates whether (and optionally, to what degree) the dialog sequence requires monitoring by a service agent. In addition, instances of the dialog sequences in calls are prioritized based on an indication of caller intelligibility during (i) prior dialog sequences in the current call, and (ii) prior calls involving the same caller and/or the same contact identifier (e.g., telephone number, email address, Internet Protocol address, etc.).

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation-in-part of U.S. patent application Ser. No. 11/107,673, filed 15 Apr. 2005 (now pending), entitled “Interactive Voice Response System With Partial Human Monitoring” (Attorney Docket: 630-119us), which is incorporated by reference.
  • FIELD OF THE INVENTION
  • The present invention relates to telecommunications in general, and, more particularly, to an interactive voice response system that enables partial human monitoring of calls.
  • BACKGROUND OF THE INVENTION
  • A call center is a place where calls from users, such as customers, are handled in support of an organization's activities. Organizations that provide a call center, such as companies that offer a service or a product, do so to provide assistance and information to customers of the service or product. A call center typically comprises an interactive voice response (IVR) system that enables a caller to obtain information without any human involvement, or to speak to a person known as a service agent. Typically an interactive voice response (IVR) system presents a hierarchy of menus to a caller, and enables the caller to input information to navigate the menus (e.g., entering alphanumeric information via a telephone keypad, selecting a menu option by saying the number associated with the option, etc.). An interactive voice response (IVR) system is advantageous economically because it enables a call center to accommodate callers with fewer service agents.
  • FIG. 1 depicts telecommunications system 100 in accordance with the prior art. Telecommunications system 100 comprises telecommunications terminal 102, telecommunications network 103, and call center 104, interconnected as shown.
  • User 101 uses telecommunications terminal 102 (e.g., a telephone, a browser-enabled client, etc.) to place a call to call center 104 via telecommunications network 103 (e.g., the Public Switched Telephone Network [PSTN], the Internet, etc.). Typically user 101 uses telecommunications terminal 102 to place a voice telephone call to call center 104. In some instances, however, user 101 might initiate a text-based instant messaging (IM) session, or might activate a “push-to-talk” button on a website that is associated with call center 104, etc.
  • FIG. 2 depicts the salient elements of call center 104, in accordance with the prior art. Call center 104 comprises data-processing system 205; interactive voice response system (IVR) 206; telecommunications terminals 207-1 through 207-N, where N is a positive integer; clients 209-1 through 209-N; and application server 210, interconnected as shown.
  • As shown in FIG. 2, each telecommunications terminal 207-n (e.g., a telephone, etc.), for n=1 through N, is associated with a respective service agent 208-n. Service agent converse with callers via telecommunications terminal 207, and interact with one or more software applications via client 209-n (e.g., a personal computer, a “dumb” terminal, etc.), both during a call and between calls. The software applications are client/server or web-based and are hosted on application server 210, in well-known fashion.
  • Private branch exchange (PBX) 205 receives incoming calls from telecommunications network 103 and directs the calls to interactive voice response (IVR) system 206 or to one of telecommunications terminals 207. Private branch exchange (PBX) 205 also receives outbound signals from telecommunications terminals 507 and interactive voice response system 506 and transmits the signals on to telecommunications network 103 for delivery to the caller's terminal.
  • Interactive voice response (IVR) system 206 prompts a caller for information and menu selections via synthesized speech, and receives input from the caller (e.g., speech signals, keypad input, etc.) via private branch exchange 205. Interactive voice response system 206 is also capable of: recording a caller's speech and keypad input during a call; performing automated speech recognition (ASR) on a caller's speech; submitting commands and forwarding caller input to one or more software applications that reside on application server 210; and receiving output from these software applications.
  • Application server 210 hosts one or more web-based or client/server software applications that perform tasks such as customer record maintenance, inventory management, order processing, etc. As described above, these software applications can be accessed by both clients 209 and interactive voice response (IVR) system 206.
  • The Extensible Markup Language, abbreviated XML, is a specification that enables the creation of customized tags, which in turn enables the definition, transmission, validation, and interpretation of data between two applications, organizations, etc. Voice Extensible Markup Language (abbreviated VoiceXML or VXML) is an application of the Extensible Markup Language (XML) that enables dialogs featuring synthesized speech, digitized audio, recognition of spoken and keyed input, recording of spoken input, and telephony. The primary objective of VXML is to bring the advantages of web-based development and content delivery to interactive voice response applications.
  • FIG. 3 depicts an exemplary Voice Extensible Markup Language (VXML) script (also known as a VXML document or page), in accordance with the illustrative embodiment of the present invention. The VXML script, when executed by interactive voice response system 206, prompts the caller for his or her social security number, and then his or her mother's maiden name for security purposes. The script then presents a menu with two options; the first option is for reviewing account balances, and the second option is for performing transactions. Audio content (in particular, synthesized speech) that corresponds to text between the <prompt> and </prompt> tags is generated by interactive voice response system 206 and transmitted to the caller.
  • In call centers that employ VXML scripts, typically application server 210 initially retrieves a “top-level” script at the beginning of a call, and subsequently, in response to menu selections and information supplied by the caller, application server 210 might retrieve one or more additional VXML scripts during the course of a call (e.g., a script for reviewing account balances, a script for processing transactions, etc.). Alternatively, a single large VXML script or application might be employed for the entire duration of a call.
  • SUMMARY OF THE INVENTION
  • A problem with interactive voice response (IVR) systems is that automated speech recognition (ASR) is typically very accurate for some inputs such as zip code and social security number, but can be much less accurate for others such as name, street address, etc. It would be advantageous, therefore, if a service agent could monitor a call and validate information provided by the caller, correct erroneous information, and so forth. If service agents monitor each call, however, the economic advantage of using an interactive voice response (IVR) system is greatly diminished.
  • The present invention enables service agents to monitor particular portions of calls that are especially error-prone (e.g., automated speech recognition of an address, etc.), while portions of calls that are not error-prone occur without any human monitoring. In particular, an interactive voice response (IVR) system script (e.g., a VXML script, etc.) is divided into a plurality of independent dialog sequences, each of which is assigned a human-monitoring requirement that indicates whether (and optionally, to what degree) the dialog sequence requires monitoring by a service agent in order to achieve a desired level of performance. Moreover, the illustrative embodiments of the present invention assign priorities to the instances of the dialog sequences in calls, based on an indication of caller intelligibility during (i) prior dialog sequences in the current call, and (ii) prior calls involving the same caller and/or the same contact identifier (e.g., telephone number, email address, Internet Protocol address, etc.). An indication of caller intelligibility might be based on a variety of criteria, such as the number of times that a caller was required to repeat an input, a property of the caller's speech (e.g., speed, accent, a measure of how well phonemes are enunciated, etc.), how long a service agent spoke with the caller to obtain information, and so forth.
  • In the first illustrative embodiment of the present invention, a partial ordering is defined that indicates which dialog sequences must occur before other dialog sequences. The partial ordering may enable a first dialog sequence that comes after a second dialog sequence in the script to in fact be executed before the second dialog sequence when it is advantageous to do so. For example, suppose a first dialogue sequence of an interactive voice response (IVR) script asks for the caller's name, and a second dialog sequence that occurs after the first dialogue sequence in the script asks for the caller's telephone number. If no service agent is available when the interactive voice response (IVR) system is ready to execute the first dialog sequence, it would be advantageous to first execute the second dialog sequence (which typically does not require human monitoring) because a service agent might subsequently become available to monitor the first dialog sequence (which does require human monitoring). Such a reordering of the dialog sequences would be indicated as permissible by the partial ordering. As will be clear to those skilled in the art, there are some pairs of dialog sequences that should not be reordered in this fashion, as would be indicated by the partial ordering. For example, the options for a second-level menu should not be presented until after the options for a first-level menu have been presented and the caller has input his or her selection for the first-level menu.
  • In the second illustrative embodiment of the present invention, each dialog sequences that requires human monitoring is recorded and packaged into an agent-review task, which is subsequently sent to an available service agent for review. The agent-review task also contains the automated speech recognition (ASR) for the dialog sequence, thus enabling the service agent to check for any errors and make any necessary corrections.
  • By enabling service agents to monitor or review only the error-prone portions of calls, and by prioritizing calls based on an indication of prior caller intelligibility, both illustrative embodiments enable a call center to function with fewer service agents.
  • An illustrative embodiment comprises: selecting a dialog sequence from a non-empty set S of dialog sequences, wherein each of the dialog sequences has a human-monitoring requirement; and executing the dialog sequence during a call that involves a caller and an interactive voice response system; wherein the selection of the dialog sequence is based on: (i) the human-monitoring requirements, (ii) the availability of one or more service agents, and (iii) an indication of the intelligibility of the caller in one or more prior dialog sequences of the call.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 depicts telecommunications system 100 in accordance with the prior art.
  • FIG. 2 depicts the salient elements of call center 104, as shown in FIG. 1, in accordance with the prior art.
  • FIG. 3 depicts an exemplary Voice Extensible Markup Language (VXML) document, in accordance with the prior art.
  • FIG. 4 depicts telecommunications system 400 in accordance with the illustrative embodiments of the present invention.
  • FIG. 5 depicts the salient elements of call center 404, as shown in FIG. 4, in accordance with the illustrative embodiments of the present invention.
  • FIG. 6 depicts a flowchart of the salient tasks involved in processing an interactive voice response script, in accordance with the first illustrative embodiment of the present invention.
  • FIG. 7 depicts a detailed flowchart of task 650, as shown in FIG. 6, in accordance with the first illustrative embodiment of the present invention.
  • FIG. 8 depicts a flowchart of the salient tasks involved in processing an interactive voice response script, in accordance with the second illustrative embodiment of the present invention.
  • FIG. 9 depicts a detailed flowchart of task 840, as shown in FIG. 8, in accordance with the second illustrative embodiment of the present invention.
  • FIG. 10 depicts an event loop for the salient tasks involved in delivering agent-review tasks to service agents, in accordance with the second illustrative embodiment of the present invention.
  • FIG. 11 depicts an event loop for the salient tasks involved in handling messages from service agents who process agent-review tasks, in accordance with the second illustrative embodiment of the present invention.
  • DETAILED DESCRIPTION
  • The terms appearing below are given the following definitions for use in this Description and the appended Claims.
  • For the purposes of the specification and claims, the term “call” is defined as an interactive communication involving one or more telecommunications terminal users. A call might be a traditional voice telephone call, an instant messaging (IM) session, a video conference, etc.
  • For the purposes of the specification and claims, the term “contact identifier” is defined as a string of symbols that is associated with a participant of a call (e.g., a telephone number, an email address, an Internet Protocol address, etc.).
  • FIG. 4 depicts telecommunications system 400 in accordance with the illustrative embodiments of the present invention. Telecommunications system 400 comprises telecommunications terminal 102 and telecommunications network 103 of the prior art, and call center 404, interconnected as shown.
  • FIG. 5 depicts the salient elements of call center 404, in accordance with the illustrative embodiments of the present invention. Call center 404 comprises private branch exchange (PBX) 505; interactive voice response system (IVR) 506; telecommunications terminals 507-1 through 507-N, where N is a positive integer; clients 509-1 through 509-N; application server 510; and database 511, interconnected as shown.
  • Application server 510 has the same capabilities as application server 210 of the prior art, and is also capable of storing and retrieving data to and from database 511, and of performing additional tasks as described below and with respect to FIGS. 6 through 10. Private branch exchange (PBX) 505 is similar to PBX 205 of the prior art and interacts with telecommunications network 103, interactive voice response system (IVR) 506, and telecommunications terminals 507-1 through 507-N as described above for PBX 205.
  • Private branch exchange (PBX) 505 has the same capabilities as PBX 205 of the prior art.
  • Telecommunications terminals 507-1 through 507-N are have the same capabilities as telecommunications terminals 207-1 through 207-N of the prior art.
  • Clients 508-1 through 508-N have the same capabilities as clients 208-1 through 208-N of the prior art.
  • Interactive voice response (IVR) system 506 has the same capabilities as IVR system 206 of the prior art, and is also capable of receiving commands from application server 510 to start and stop recording of a call while the call is in progress, and of storing and retrieving data to and from database 511.
  • Database 511 is a database that is capable of receiving data from IVR system 506 and application server 510, and of storing and organizing the data in a manner that enables efficient retrieval. In particular, database 511 is capable of storing indications of caller intelligibility for calls and for individual dialog sequences of calls. As will be appreciated by those skilled in the art, an indication of caller intelligibility might be based on a variety of criteria, such as the number of times that a caller was required to repeat an input, a property of the caller's speech (e.g., speed, accent, a measure of how well phonemes are enunciated, etc.), how long a service agent spoke with the caller to obtain information, and so forth.
  • In accordance with the illustrative embodiment, database 404 is a relational database; however, it will be clear to those skilled in the art, after reading this disclosure, how to make use other embodiments of the present invention in which database 404 is some other type of database (e.g., an object-oriented database, a hierarchical database, etc.).
  • FIG. 6 depicts a flowchart of the salient tasks involved in processing an interactive voice response script, in accordance with the first illustrative embodiment of the present invention.
  • At task 610, application server 510 retrieves an appropriate IVR script (e.g., a VXML script, etc.) during a call C, in well-known fashion.
  • At task 620, application server 510 generates a set S of dialog sequences from the IVR script. A dialog sequence is a portion of a IVR script that is independent of any other portions of the IVR script. For example, in the IVR script of FIG. 3, the script might be divided into the following three dialog sequences: a first dialog sequence that comprises greeting the caller, asking for his or her social security number, and validating the social security number against a database; a second dialog sequence that comprises asking the caller for his or her mother's maiden name and validating the name against a database; and a third dialog sequence that comprises presenting the options of the menu and obtaining the caller's selection. It will be clear to those skilled in the art how to parse a IVR script and divide the script into a set of dialog sequences.
  • At task 630, application server 510 defines a partial ordering on the dialog sequences of set S. Intuitively, the partial ordering means that either: a first dialog sequence might temporally come before a second dialog sequence (i.e., the first dialog sequence is a predecessor of the second dialog sequence); the second dialog sequence is a predecessor of the first dialog sequence; or they are temporally unrelated (i.e., either the first can come before the second, or the second can come before the first). Formally, a partial ordering over set S is a relation R∈S×S such that:
    • (i) ∀x∈R:(x,x)∉R,
    • (ii) ∀x,y∈S where x≠y, at most one of (x,y) and (y,x)∈R, and
    • (iii) (x,y)∈R and (y,z)∈R
      Figure US20090041212A1-20090212-P00001
      (x,z)∈R.
      As is well-known in the art, a variety of data structures such as a tree or directed acyclic graph can be used to represent a partial order on a set of elements. In the case of set S, each node in a tree or graph would represent one of the dialog sequences of S. It will be clear to those skilled in the art how to define a partial ordering on, and build a corresponding data structure for, the dialog sequences of a IVR script based on the contents and structure of the script.
  • At task 640, application server 510 assigns or generates human-monitoring requirements for the dialog sequences of set S. As will be appreciated by those skilled in the art, in some embodiments a human-monitoring requirement might be a simple Boolean value that indicates whether a dialog sequence requires any human monitoring, while in some other embodiments a human-monitoring requirement might be a numeric value that indicates the degree to which a dialog sequence requires human monitoring, or yet some other data type. As will further be appreciated by those skilled in the art, human-monitoring requirements can be assigned manually or generated automatically, and can be based on empirical data (e.g., the error rate of a particular dialog sequence or of a particular class of dialog sequences, etc.), or on heuristics that take into account the length of a dialog sequence, the kind of input requested from the caller in a dialog sequence, and so forth.
  • At task 650, application server 510 selects a dialog sequence d from set S based on:
    • (i) the partial ordering defined at task 630,
    • (ii) the human-monitoring requirements of dialog sequences in S, and
    • (iii) the availability of one or more service agents.
      Task 650 is described in detail below and with respect to FIG. 7.
  • At task 655, the selected dialog sequence d is removed from set S.
  • At task 660 application server 510 checks whether dialog sequence d requires human monitoring. As will be appreciated by those skilled in the art, in some embodiments this might be accomplished by checking whether a Boolean value associated with dialog sequence d is true, while in some other embodiments this might be accomplished by checking whether a numeric value is non-zero. If dialog sequence d requires human monitoring, execution proceeds to task 665; otherwise execution continues at task 680.
  • At task 665 application server 510 checks what fraction of service agents are available. If the fraction is above a threshold, execution continues at task 680. Otherwise, application server 510 consults database 411 and determines a priority for human-monitoring based on one or more indications of caller intelligibility during (i) prior dialog sequences in the current call C, and/or (ii) prior calls involving the same caller and/or the same contact identifier (e.g., telephone number, email address, Internet Protocol address, etc.). If the priority is not above a threshold, execution continues at task 680, otherwise execution continues at task 670.
  • As will be appreciated by those skilled in the art, in some embodiments the identity of the caller might be known via a login procedure or a customer number that the caller inputs, while in some other embodiments, no such explicit identification of the caller might be available, in which case the contact identifier might be used as a good but imperfect proxy for the caller's identity.
  • At task 670, if no service agent is available, then execution of the method waits until a service agent is available. In some embodiments, interactive voice response (IVR) system 506 might output to the caller a “stall phrase” (e.g., “One moment please”, etc.) or a “filler” dialogue sequence (e.g., “Are you still at address 123 Maple Lane?”, “As a valued customer, can we take a moment to ask about some questions about your last on-line order experience?”, etc.) in order to avoid the appearance of a dropped call or system crash.
  • At task 671, private branch exchange 505 bridges an available service agent into call C, in well-known fashion. In some embodiments of the present invention, the service agent's client 509 enables the service agent to validate information provided during the dialog sequence, correct the information, and so forth. Furthermore, in some embodiments, the service agent might receive a visual representation of the dialog sequence at respective client 509, either in addition to or in lieu of audio bridging (as disclosed, for example, in U.S. patent application Ser. No. 10/874,791, incorporated by reference).
  • At task 672, interactive voice response (IVR) system 506 executes dialog sequence d for call C, in well-known fashion.
  • At task 673, private branch exchange 505 drops the service agent from call C, in well-known fashion. As appropriate, service agent's client 509 also closes the visual representation and the interface for validating and correcting information. After task 673 is completed, execution continues at task 685.
  • As will be appreciated by those skilled in the art, in some variations of the first illustrative embodiment, instead of waiting for an available service agent, the dialog sequence is executed without monitoring by an agent, and a recording of the dialog sequence is subsequently sent to an available service agent for review, as described below and with respect to the second illustrative embodiment.
  • At task 680, interactive voice response (IVR) system 506 executes dialog sequence d for call C, in well-known fashion.
  • At task 685, application server 510 stores in database 511 an indication of caller intelligibility for the dialog sequence d, along with the identity of the caller and/or contact identifier. As described above, the indication of caller intelligibility might be based on a variety of criteria, such as the number of times that a caller was required to repeat an input, a property of the caller's speech (e.g., speed, accent, a measure of how well phonemes are enunciated, etc.), how long a service agent spoke with the caller to obtain information, and so forth.
  • At task 690, application server 510 checks whether set S is empty. If so, the method of FIG. 6 terminates; otherwise execution continues back at task 650.
  • FIG. 7 depicts a detailed flowchart of task 650 in accordance with the first illustrative embodiment of the present invention.
  • At task 710, variable T is initialized to the set of dialog sequences in S that have no predecessor. In other words, set T contains the dialog sequences of S that do not require another dialog sequence of S to occur beforehand, and thus are candidates for execution by interactive voice response (IVR) system 506.
  • At task 720, application server 510 checks whether there is an available service agent. If not, execution proceeds to task 730; otherwise, execution continues at task 740.
  • At task 730, application server 510 selects a dialog sequence from set T that has the least human-monitoring requirement (e.g., the smallest numerical value, a requirement of false, etc.) After task 730, task 650 is completed and execution proceeds to task 655.
  • At task 740, application server 510 checks whether all the dialog sequences of set T have identical human-monitoring requirements. If not, execution proceeds to task 750; otherwise, execution continues at task 760.
  • At task 750, application server 510 selects a dialog sequence from set T that does not have the least human-monitoring requirement. As will be appreciated by those skilled in the art, in some embodiments any dialog sequence that does not have the least human-monitoring requirement might be selected, while some other embodiments might employ a heuristic for selecting a dialog sequence, perhaps based on the lengths of the dialog sequences, the estimated time until a service agent is available, etc. After task 750, task 650 is completed and execution proceeds to task 655.
  • At task 760, application server 510 selects any dialog sequence from set T. As in task 750, in some embodiments a dialog sequence might be selected arbitrarily, while some other embodiments might employ a heuristic for selecting a dialog sequence. After task 760, task 650 is completed and execution proceeds to task 655.
  • FIG. 8 depicts a flowchart of the salient tasks involved in processing an interactive voice response script, in accordance with the second illustrative embodiment of the present invention.
  • At task 810, application server 510 retrieves an appropriate IVR script during a call C, in well-known fashion.
  • At task 820, application server 510 identifies the dialog sequences of the IVR script. It will be clear to those skilled in the art how to parse a IVR script and identify its constituent dialog sequences.
  • At task 830, application server 510 assigns or generates human-monitoring requirements for the dialog sequences, as described above and with respect to task 640.
  • At task 840, interactive voice response (IVR) system 506 executes the IVR script for call C. Task 840 is described in detail below and with respect to FIG. 9.
  • FIG. 9 depicts a detailed flowchart of task 840, in accordance with the second illustrative embodiment of the present invention.
  • At task 910, application server 510 checks whether the current position in the script (initially, the first line of the script) is the beginning of a dialog sequence that requires human monitoring. If so, execution proceeds to task 920; otherwise, execution continues at task 930.
  • At task 920, application server 510 sends a signal to interactive voice response (IVR) system 506 to start recording of the dialog sequence. After task 920, execution continues at task 980.
  • At task 930, application server 510 checks whether the current position in the script is the end of a dialog sequence that requires human monitoring. If so, execution proceeds to task 940; otherwise, execution continues at task 970.
  • At task 940, application server 510 sends a signal to interactive voice response (IVR) system 506 to stop recording of the dialog sequence.
  • At task 950, application server 510 creates an agent-review task comprising: (i) a recording of the just-completed dialog sequence, and (ii) the result of IVR system 506's automatic speech recognition for the just-completed dialog sequence.
  • At task 960, application server 510 adds the agent-review task to a queue for delivery to an available service agent. After task 960, execution continues at task 980.
  • At task 970, interactive voice response (IVR) system 506 executes the current command of the script, in well-known fashion.
  • At task 980, application server 510 checks whether the end of the script has been reached. If so, the method of FIG. 9 terminates; otherwise execution continues at task 990.
  • At task 990, application server 510 advances the current position in the script to the next command, and execution continues back at task 910.
  • FIG. 10 depicts an event loop for the salient tasks involved in delivering agent-review tasks to service agents, in accordance with the second illustrative embodiment of the present invention.
  • At task 1010, the event loop waits until both (i) the agent-review task queue is non-empty, and (ii) there are one or more available service agents.
  • At task 1020, an agent-review task is removed from the front of the queue and sent to an available service agent, in well-known fashion. After task 1020, execution continues back at task 1010.
  • FIG. 11 depicts an event loop for the salient tasks involved in handling messages from service agents who process agent-review tasks, in accordance with the second illustrative embodiment of the present invention.
  • At task 1110, an agent-review message is received from a service agent A, in well-known fashion.
  • Task 1120 checks whether the message contains a request to intervene in the call. If so, execution continues at task 1130, otherwise execution proceeds to task 1140.
  • At task 1130, private branch exchange 505 bridges service agent A into the call, in well-known fashion. After task 1130, execution continues back at task 1110.
  • Task 1140 checks whether the message contains a request for one or more new dialog sequences from the call. If so, execution continues at task 1150, otherwise execution proceeds to task 1170.
  • At task 1150, interactive voice response (IVR) system 506 retrieves recordings of the requested dialog sequences, in well-known fashion.
  • At task 1160, agent-review tasks that correspond to the recordings are created and sent to service agent A. After task 1160, execution continues back at task 1110.
  • If task 1170 is reached, the message contains an approval by the service agent and, optionally, an indication of which caller inputs, if any, were modified by the service agent. The message is logged in well-known fashion, and execution continues back at task 1110.
  • As described above with respect to task 673, a combination of the first and second illustrative embodiments is possible in which a dialog sequence that requires human monitoring is monitored in real-time when a service agent is available, as in the first illustrative embodiment, and when no service agent is available, an agent-review task is created, as in the second illustrative embodiment.
  • It is to be understood that the disclosure teaches just one example of the illustrative embodiment and that many variations of the invention can easily be devised by those skilled in the art after reading this disclosure and that the scope of the present invention is to be determined by the following claims.
  • The following claims are presented for examination:

Claims (20)

1. A method comprising:
selecting a dialog sequence from a non-empty set S of dialog sequences, wherein each of said dialog sequences has a human-monitoring requirement; and
executing said dialog sequence during a call that involves a caller and an interactive voice response system;
wherein the selection of said dialog sequence is based on:
(i) said human-monitoring requirements,
(ii) the availability of one or more service agents, and
(iii) an indication of the intelligibility of said caller in one or more prior dialog sequences of said call.
2. The method of claim 1 wherein when none of said service agents is available, the selected dialog sequence has the least human-monitoring requirement.
3. The method of claim 1 wherein when one or more of said service agents is available and when two or more of said human-monitoring requirements are different, the selected dialog sequence does not have the least human-monitoring requirement.
4. The method of claim 1 wherein the selection of said dialog sequence is also based on a partial ordering on said set S.
5. The method of claim 4 wherein when none of said service agents is available, the selected dialog sequence
(i) is a member of set T={d∈S|d has no predecessors}, and
(ii) has the least human-monitoring requirement in set T.
6. The method of claim 4 wherein when one or more of said service agents is available, the selected dialog sequence
(i) is a member of set T={d∈S|d has no predecessors}, and
(ii) does not have the least human-monitoring requirement in set T when set T has two or more dialog sequences with different human-monitoring requirements.
7. The method of claim 1 wherein the selection of said dialog sequence is also based on: (iv) an indication of the intelligibility of said caller in one or more prior calls involving said caller.
8. A method comprising:
selecting a dialog sequence from a non-empty set S of dialog sequences, wherein each of said dialog sequences has a human-monitoring requirement; and
executing said dialog sequence during a call that involves a caller and an interactive voice response system;
wherein the selection of said dialog sequence is based on:
(i) said human-monitoring requirements,
(ii) the availability of one or more service agents, and
(iii) an indication of the intelligibility of said caller in one or more prior calls involving said caller.
9. The method of claim 8 wherein when none of said service agents is available, the selected dialog sequence has the least human-monitoring requirement.
10. The method of claim 8 wherein when one or more of said service agents is available and when two or more of said human-monitoring requirements are different, the selected dialog sequence does not have the least human-monitoring requirement.
11. The method of claim 8 wherein the selection of said dialog sequence is also based on a partial ordering on said set S.
12. The method of claim 11 wherein when none of said service agents is available, the selected dialog sequence
(i) is a member of set T={d∈S|d has no predecessors}, and
(ii) has the least human-monitoring requirement in set T.
13. The method of claim 11 wherein when one or more of said service agents is available, the selected dialog sequence
(i) is a member of set T={d∈S|d has no predecessors}, and
(ii) does not have the least human-monitoring requirement in set T when set T has two or more dialog sequences with different human-monitoring requirements.
14. The method of claim 8 further comprising, when said dialog sequence requires human monitoring, generating an agent-review task that comprises one or both of:
(i) a recording of said call during said dialog sequence, and
(ii) an output of automated speech recognition.
15. A method comprising:
selecting a dialog sequence from a non-empty set S of dialog sequences, wherein each of said dialog sequences has a human-monitoring requirement; and
executing said dialog sequence during a call that involves:
(i) a caller associated with a contact identifier I, and
(ii) an interactive voice response system;
wherein the selection of said dialog sequence is based on:
(i) said human-monitoring requirements,
(ii) the availability of one or more service agents, and
(iii) an indication of caller intelligibility in a prior call involving said interactive voice response system and said contact identifier I.
16. The method of claim 15 wherein the selection of said dialog sequence is also based on: (iv) an indication of the intelligibility of said caller in one or more prior dialog sequences of said call.
17. The method of claim 15 wherein when none of said service agents is available, the selected dialog sequence has the least human-monitoring requirement.
18. The method of claim 15 wherein when one or more of said service agents is available and when two or more of said human-monitoring requirements are different, the selected dialog sequence does not have the least human-monitoring requirement.
19. The method of claim 15 wherein the selection of said dialog sequence is also based on a partial ordering on said set S; and wherein when none of said service agents is available, the selected dialog sequence
(i) is a member of set T={d∈S|d has no predecessors}, and
(ii) has the least human-monitoring requirement in set T.
20. The method of claim 15 wherein the selection of said dialog sequence is also based on a partial ordering on said set S; and wherein when one or more of said service agents is available, the selected dialog sequence
(i) is a member of set T={d∈S|d has no predecessors}, and
(ii) does not have the least human-monitoring requirement in set T when set T has two or more dialog sequences with different human-monitoring requirements.
US12/240,905 2005-04-15 2008-09-29 Interactive voice response system with prioritized call monitoring Active 2027-04-05 US8085927B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/240,905 US8085927B2 (en) 2005-04-15 2008-09-29 Interactive voice response system with prioritized call monitoring

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/107,673 US7471786B2 (en) 2005-04-15 2005-04-15 Interactive voice response system with partial human monitoring
US12/240,905 US8085927B2 (en) 2005-04-15 2008-09-29 Interactive voice response system with prioritized call monitoring

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/107,673 Continuation-In-Part US7471786B2 (en) 2005-04-15 2005-04-15 Interactive voice response system with partial human monitoring

Publications (2)

Publication Number Publication Date
US20090041212A1 true US20090041212A1 (en) 2009-02-12
US8085927B2 US8085927B2 (en) 2011-12-27

Family

ID=40346533

Family Applications (1)

Application Number Title Priority Date Filing Date
US12/240,905 Active 2027-04-05 US8085927B2 (en) 2005-04-15 2008-09-29 Interactive voice response system with prioritized call monitoring

Country Status (1)

Country Link
US (1) US8085927B2 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110313767A1 (en) * 2010-06-18 2011-12-22 At&T Intellectual Property I, L.P. System and method for data intensive local inference
US20170185945A1 (en) * 2015-12-29 2017-06-29 Avaya Inc. Dynamic interaction pacing
US10339930B2 (en) * 2016-09-06 2019-07-02 Toyota Jidosha Kabushiki Kaisha Voice interaction apparatus and automatic interaction method using voice interaction apparatus
US11244697B2 (en) * 2018-03-21 2022-02-08 Pixart Imaging Inc. Artificial intelligence voice interaction method, computer program product, and near-end electronic device thereof

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9338295B2 (en) 2013-09-27 2016-05-10 At&T Intellectual Property I, L.P. Dynamic modification of automated communication systems
US11032416B2 (en) 2019-01-25 2021-06-08 American TEL-A Systems, Inc. Intelligent speech-enabled scripting
CN110572521A (en) * 2019-09-20 2019-12-13 中国银行股份有限公司 Voice broadcasting method and device

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6047060A (en) * 1998-02-20 2000-04-04 Genesys Telecommunications Laboratories, Inc. Method and apparatus for enabling full interactive monitoring of calls to and from a call-in center
US6259785B1 (en) * 1998-08-17 2001-07-10 Siemens Information And Communication Networks, Inc. System and method for dynamically altering digital voice mixing location in ACD silent monitoring
US6487277B2 (en) * 1997-09-19 2002-11-26 Siemens Information And Communication Networks, Inc. Apparatus and method for improving the user interface of integrated voice response systems
US20030053615A1 (en) * 2000-12-19 2003-03-20 Gregory Anderson Methods and apparatus for automated monitoring and action taking based on decision support mechanism
US20030212558A1 (en) * 2002-05-07 2003-11-13 Matula Valentine C. Method and apparatus for distributed interactive voice processing
US6907119B2 (en) * 2001-03-08 2005-06-14 Qwest Communications International, Inc. Automated business directory assistance
US20070121893A1 (en) * 2005-11-29 2007-05-31 Cisco Technology, Inc. Optimal call speed for call center agents
US7305070B2 (en) * 2002-01-30 2007-12-04 At&T Labs, Inc. Sequential presentation of long instructions in an interactive voice response system
US7660715B1 (en) * 2004-01-12 2010-02-09 Avaya Inc. Transparent monitoring and intervention to improve automatic adaptation of speech models

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6487277B2 (en) * 1997-09-19 2002-11-26 Siemens Information And Communication Networks, Inc. Apparatus and method for improving the user interface of integrated voice response systems
US6047060A (en) * 1998-02-20 2000-04-04 Genesys Telecommunications Laboratories, Inc. Method and apparatus for enabling full interactive monitoring of calls to and from a call-in center
US6259785B1 (en) * 1998-08-17 2001-07-10 Siemens Information And Communication Networks, Inc. System and method for dynamically altering digital voice mixing location in ACD silent monitoring
US20030053615A1 (en) * 2000-12-19 2003-03-20 Gregory Anderson Methods and apparatus for automated monitoring and action taking based on decision support mechanism
US6907119B2 (en) * 2001-03-08 2005-06-14 Qwest Communications International, Inc. Automated business directory assistance
US7305070B2 (en) * 2002-01-30 2007-12-04 At&T Labs, Inc. Sequential presentation of long instructions in an interactive voice response system
US20030212558A1 (en) * 2002-05-07 2003-11-13 Matula Valentine C. Method and apparatus for distributed interactive voice processing
US7660715B1 (en) * 2004-01-12 2010-02-09 Avaya Inc. Transparent monitoring and intervention to improve automatic adaptation of speech models
US20070121893A1 (en) * 2005-11-29 2007-05-31 Cisco Technology, Inc. Optimal call speed for call center agents

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110313767A1 (en) * 2010-06-18 2011-12-22 At&T Intellectual Property I, L.P. System and method for data intensive local inference
US8442827B2 (en) * 2010-06-18 2013-05-14 At&T Intellectual Property I, L.P. System and method for customized voice response
US9343063B2 (en) 2010-06-18 2016-05-17 At&T Intellectual Property I, L.P. System and method for customized voice response
US20160240191A1 (en) * 2010-06-18 2016-08-18 At&T Intellectual Property I, Lp System and method for customized voice response
US10192547B2 (en) * 2010-06-18 2019-01-29 At&T Intellectual Property I, L.P. System and method for customized voice response
US20170185945A1 (en) * 2015-12-29 2017-06-29 Avaya Inc. Dynamic interaction pacing
US10339930B2 (en) * 2016-09-06 2019-07-02 Toyota Jidosha Kabushiki Kaisha Voice interaction apparatus and automatic interaction method using voice interaction apparatus
US11244697B2 (en) * 2018-03-21 2022-02-08 Pixart Imaging Inc. Artificial intelligence voice interaction method, computer program product, and near-end electronic device thereof

Also Published As

Publication number Publication date
US8085927B2 (en) 2011-12-27

Similar Documents

Publication Publication Date Title
US7471786B2 (en) Interactive voice response system with partial human monitoring
US9992336B2 (en) System for analyzing interactions and reporting analytic results to human operated and system interfaces in real time
US7242752B2 (en) Behavioral adaptation engine for discerning behavioral characteristics of callers interacting with an VXML-compliant voice application
US8090086B2 (en) VoiceXML and rule engine based switchboard for interactive voice response (IVR) services
EP2056578B1 (en) Providing a multi-modal communications infrastructure for automated call centre operation
US9699315B2 (en) Computer-implemented system and method for processing caller responses
US8085927B2 (en) Interactive voice response system with prioritized call monitoring
EP1486054B1 (en) System and method for providing a message-based communications infrastructure for automated call center operation
US7609829B2 (en) Multi-platform capable inference engine and universal grammar language adapter for intelligent voice application execution
US9654631B2 (en) Automatic language selection for interactive voice response system
US20040086095A1 (en) Voice message based applets
WO2008137327A1 (en) Automated attendant grammar tuning
CN109417583B (en) System and method for transcribing audio signal into text in real time
US20080256200A1 (en) Computer application text messaging input and output
RU2763691C1 (en) System and method for automating the processing of voice calls of customers to the support services of a company
CN111901486A (en) Voice call processing method and device and electronic equipment
WO2023196363A1 (en) Modular technologies for servicing telephony systems

Legal Events

Date Code Title Description
AS Assignment

Owner name: AVAYA INC., NEW JERSEY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ERHART, GEORGE WILLIAM;MATULA, VALENTINE C.;SKIBA, DAVID JOSEPH;AND OTHERS;REEL/FRAME:021831/0131;SIGNING DATES FROM 20081009 TO 20081014

Owner name: AVAYA INC., NEW JERSEY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ERHART, GEORGE WILLIAM;MATULA, VALENTINE C.;SKIBA, DAVID JOSEPH;AND OTHERS;SIGNING DATES FROM 20081009 TO 20081014;REEL/FRAME:021831/0131

AS Assignment

Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLAT

Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535

Effective date: 20110211

Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE, PENNSYLVANIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535

Effective date: 20110211

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE, PENNSYLVANIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:030083/0639

Effective date: 20130307

Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE,

Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:030083/0639

Effective date: 20130307

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT, NEW YORK

Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS INC.;OCTEL COMMUNICATIONS CORPORATION;AND OTHERS;REEL/FRAME:041576/0001

Effective date: 20170124

AS Assignment

Owner name: OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION), CALIFORNIA

Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531

Effective date: 20171128

Owner name: AVAYA INTEGRATED CABINET SOLUTIONS INC., CALIFORNIA

Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531

Effective date: 20171128

Owner name: AVAYA INC., CALIFORNIA

Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST, NA;REEL/FRAME:044892/0001

Effective date: 20171128

Owner name: OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL

Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531

Effective date: 20171128

Owner name: AVAYA INC., CALIFORNIA

Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531

Effective date: 20171128

Owner name: VPNET TECHNOLOGIES, INC., CALIFORNIA

Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531

Effective date: 20171128

Owner name: AVAYA INTEGRATED CABINET SOLUTIONS INC., CALIFORNI

Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531

Effective date: 20171128

Owner name: AVAYA INC., CALIFORNIA

Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:045012/0666

Effective date: 20171128

AS Assignment

Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW YORK

Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:045034/0001

Effective date: 20171215

Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW Y

Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:045034/0001

Effective date: 20171215

AS Assignment

Owner name: CITIBANK, N.A., AS COLLATERAL AGENT, NEW YORK

Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:045124/0026

Effective date: 20171215

AS Assignment

Owner name: AVAYA INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044974/0619

Effective date: 20180214

Owner name: AVAYA INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:GOLDMAN SACHS BANK USA;REEL/FRAME:044974/0715

Effective date: 20180214

AS Assignment

Owner name: SERVICENOW, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AVAYA INC.;REEL/FRAME:045006/0301

Effective date: 20180214

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8

AS Assignment

Owner name: AVAYA INTEGRATED CABINET SOLUTIONS LLC, NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001

Effective date: 20230403

Owner name: AVAYA MANAGEMENT L.P., NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001

Effective date: 20230403

Owner name: AVAYA INC., NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001

Effective date: 20230403

Owner name: AVAYA HOLDINGS CORP., NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063457/0001

Effective date: 20230403

AS Assignment

Owner name: AVAYA MANAGEMENT L.P., NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

Owner name: CAAS TECHNOLOGIES, LLC, NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

Owner name: HYPERQUALITY II, LLC, NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

Owner name: HYPERQUALITY, INC., NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

Owner name: ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.), NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

Owner name: VPNET TECHNOLOGIES, INC., NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

Owner name: OCTEL COMMUNICATIONS LLC, NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

Owner name: AVAYA INTEGRATED CABINET SOLUTIONS LLC, NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

Owner name: INTELLISIST, INC., NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

Owner name: AVAYA INC., NEW JERSEY

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063779/0622

Effective date: 20230501

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12