US20150146867A1 - System And Method For Determining Customer Hold Times - Google Patents
System And Method For Determining Customer Hold Times Download PDFInfo
- Publication number
- US20150146867A1 US20150146867A1 US14/612,220 US201514612220A US2015146867A1 US 20150146867 A1 US20150146867 A1 US 20150146867A1 US 201514612220 A US201514612220 A US 201514612220A US 2015146867 A1 US2015146867 A1 US 2015146867A1
- Authority
- US
- United States
- Prior art keywords
- caller
- call
- agent
- module
- hold
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5175—Call or contact centers supervision arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/428—Arrangements for placing incoming calls on hold
- H04M3/4285—Notifying, informing or entertaining a held party while on hold, e.g. Music On Hold
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5133—Operator terminal details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
- H04M3/5238—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing with waiting time or load prediction arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/40—Electronic components, circuits, software, systems or apparatus used in telephone systems using speech recognition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42059—Making use of the calling party identifier
- H04M3/42068—Making use of the calling party identifier where the identifier is used to access a profile
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
Definitions
- the present invention relates in general to automated call center operation and, in particular, to a system and method for determining customer hold times.
- call centers or simply, “call centers,” offer a convenient and universally-accessible forum for customer assistance. Most call centers are reachable by telephone, including data network-based telephone, such as Voice-Over-Internet (VoIP), although Web- and email-based customer support are becoming increasingly available.
- VoIP Voice-Over-Internet
- Each customer call is an interactive process.
- the expectation level of callers is generally lower when they are aware that an automated system, rather than a live agent, is providing assistance. Nevertheless, callers still expect expeditious resolution of their concerns and minimizing delay is crucial, even when caller volume is high. Hold times can occur, such as when customers must be placed on hold until an agent becomes available.
- Call centers frequently play recorded music or advertisements to entertain callers while on hold, although callers on hold for a long time may hear the same content played repeatedly.
- call centers can feed live radio or subscription content, such as Muzak®, Fort Mill, S.C., which avoids repetition, but also relinquishes control over the content to a third party.
- live radio or subscription content such as Muzak®, Fort Mill, S.C.
- Hold times usually occur when a caller calls and all agents are busy.
- the waiting times for each on-going caller session can be evaluated to determine hold time.
- Each caller waiting on hold can be evaluated for attributes, such as calling location or area of customer assistance.
- the content played to each caller on hold can be customized to better tailor the call to the caller and to advantageously use the hold time.
- An embodiment provides a system and method for determining customer hold times.
- a database of caller profiles is maintained.
- a call from a caller is received into a call center and assigned to an agent.
- a delay during which the caller is to be placed on hold is identified.
- a hold time for the delay is determined based on a length of a hold queue, a level of busyness of the agent and the caller profile associated with the caller.
- FIG. 1 is a functional block diagram showing an automated call center operational environment.
- FIG. 2 is a functional block diagram showing an automated call center for use in the automated call center operational environment of FIG. 1 .
- FIG. 3 is a process flow diagram showing, by way of example, a typical call sequence, as transacted by the automated call center of FIG. 2 .
- FIG. 4 is a screen diagram showing, by way of example, a view of an agent console for an on-going call session.
- FIG. 5 is a process flow diagram showing a method for managing a dynamic call flow during automated call processing, in accordance with one embodiment.
- FIG. 6 is a block diagram showing, by way of example, caller attributes evaluated during dynamic call flow management.
- FIG. 7 is a block diagram showing, by way of example, customized caller options for managing hold times, in accordance with one embodiment.
- FIG. 1 is a functional block diagram showing an automated call center operational environment 10 .
- a multiplicity of callers call into an automated call center 11 , generally through telephonic means, which can include conventional telephone handsets 13 a - c through Plain Old Telephone Service (POTS) 12 , portable handsets 15 a - c through cellular and satellite telephone service 14 , VoIP clients 17 a - b, and Internet telephony clients 18 a - b, as well as other forms of telephony and voice-based communications.
- POTS Plain Old Telephone Service
- Callers can also “call” or interface into the automated call center 11 using conventional network clients 19 through an internetwork 16 , including the Internet.
- Other types of automated call center access are possible.
- Hold times can occur under various circumstances. For example, multiple callers may call at the same time, thereby flooding the call center 11 . Similarly, one agent may be handling several callers at once and need time to resolve each problem. Other circumstances causing hold times are possible.
- the terms “caller,” “user,” and “customer” are used interchangeably to refer to a caller to the automated call center 11 .
- the terms “agent,” “guide,” and “operator” are used interchangeably to refer to an agent that provides service provisioning for the automated call center 11 .
- “wait” and “hold” may be used interchangeably to refer to the time a caller spends holding for an agent's attention.
- the automated call center 11 is shown as a single point within the automated call center operation environment 10 , the automated call center 11 could include two or more logically interconnected, but physically separate, including geographically removed, call center operations, which collectively provide a unified automated call center. Other automated call center arrangements and configurations are possible.
- FIG. 2 is a functional block diagram showing an automated call center 30 for use in the automated call center operational environment 10 of FIG. 1 .
- the automated call center 30 includes one or more servers 31 , 34 and agent consoles 32 a - c operatively interconnected over an internal network 33 .
- the agent consoles 32 a - c could also be interconnected to the message server 31 over an external network infrastructure 33 , such as the Internet or a non-public enterprise data network.
- the network infrastructure 33 can be either wired or wireless and, in one embodiment, is implemented based on the Transmission Control Protocol/Internet Protocol (TCP/IP) network specification, although other types or combinations of networking implementations are possible. Similarly, other network topologies and arrangements are possible.
- TCP/IP Transmission Control Protocol/Internet Protocol
- a message server 31 provides the primary message-based communications infrastructure for call center operation, such as described in commonly-assigned U.S. Pat. No. 7,292,689, issued Nov. 6, 2007, to Odinak et al., and U.S. Pat. No. 8,170,197, issued May 1, 2012, to Odinak, the disclosures of which are incorporated by reference.
- the message server 31 executes individual threads to process multiple simultaneous calls, which are handled by agents executing agent applications on agent consoles 32 a - c. Hold time can occur, for instance, if the agents become overloaded.
- a telephony interface 35 which is operatively coupled to the message server 31 to provide access to a telephone voice and data network 36 .
- the telephony interface connects to the telephone network 36 over a T-1 carrier line, which can provide up to 24 individual channels of voice or data traffic provided at 64 kilobits (Kbits) per second. Other types of telephone network connections are possible.
- the automated call center 30 also includes a recognition server 34 that interfaces directly to the message server 31 as a top-level or root tier of a speech recognition hierarchy.
- the message server 31 sends streamed audio data for each incoming call to the recognition server 34 , which performs distributed speech recognition, such as described in commonly-assigned U.S. Patent Application Publication No. 2007/0162282, published Jul. 12, 2007, to Odinak; and U.S. Provisional Patent application Ser. No. 60/757,356, filed Jan. 9, 2006, expired, the disclosures of which are incorporated by reference.
- the message server 31 assigns grammar generation and speech recognition to the recognition server 34 .
- the telephony gateway 35 opens a T- 1 carrier device channel for each available T-1 time slot.
- the telephony gateway 35 initiates a new connection to the message server 31 , one connection per T-1 device channel, and the message server 31 , in turn, initiates a corresponding new connection to the recognition server 34 .
- the separate telephony gateway-to-message server and message server-to-main recognizer connections form one concurrent session.
- the telephony gateway 35 sends a call message to the message server 31 .
- the message server 31 then sends a new call message to the recognition server 34 .
- the message server 31 also assigns each new call to one of the agent consoles 32 a - c through dynamic load balancing, such as described in commonly-assigned U.S. Pat. No. 8,023,638, issued Sep. 20, 2011; and U.S. Provisional Patent application Ser. No. 60/838,074, filed Aug. 15, 2006, expired, the disclosures of which are incorporated by reference.
- Each agent console 32 a - c provides the primary means for direct customer interaction by providing service provisioning and related assistance to callers, such as further described below with reference to FIG. 3 .
- each agent console 32 a - c The main purpose of each agent console 32 a - c is to execute one or more agent applications, which display both user and agent messages and provide menus of actions that can be executed in response to agent commands, including script execution and management of variable hold time.
- agent applications execute on each agent console and one or more agent consoles can execute in parallel.
- multiple instances of agent applications can run on a server machine, and can be accessed and, if needed, modified by agents at agent consoles operating as remote terminals.
- Each component including the message server 31 , recognition server 34 , and agent consoles 32 a - c, is implemented as a computer program, procedure or module written as source code in a conventional programming language, such as the C++ programming language, and presented for execution by a computer system as object or byte code.
- the components could be directly implemented in hardware, either as integrated circuitry or burned into read-only or read-rewriteable memory components.
- the various implementations of the source code and object and byte codes can be held on a computer-readable storage medium or embodied on a transmission medium in a carrier wave.
- Callers interface with an agent indirectly, who multitasks through one or more caller sessions via an agent console 32 a - c.
- the callers only perceive an automated calling interface heard, for instance, through their telephone or portable handset and do not actually speak with the agent person-to-person.
- FIG. 3 is a process flow diagram showing, by way of example, a typical call sequence 40 , as transacted by the automated call center 30 of FIG. 2 .
- the form of call processing required may vary by subject matter and other factors, the same overall sequence of caller-to-agent interchanges will loosely apply.
- a caller session starts with an incoming call and continues through to call termination, including any hold times.
- each caller upon calling into the call center 30 , each caller receives an initial greeting and informational message 41 providing a synopsis of caller options, which enable the caller to navigate to a specific topic for assistance or support.
- the caller engages in a customer assistance or support scenario 42 with an agent, which is either a live person or an automated prompt, such as generated by an automated voice response system, to collect information and problem troubleshoot.
- the scenario 42 can be delayed due to agent unavailability, caller volume, and other factors, which require the caller to be placed on hold.
- the interactive call flow and hold time of each call can be adjusted by evaluating caller attributes, such as described below beginning with reference to FIG. 5 .
- caller attributes such as described below beginning with reference to FIG. 5 .
- the order in which information is gathered from a caller, such as identifying the caller's needs or problems, can be dynamically evaluated and controlled, such as further described in commonly-assigned U.S. Pat. No. 8,442,209, issued May 14, 2013; and U.S. Provisional Patent application Ser. No. 60/838,102, filed Aug. 15, 2006, expired, the disclosures of which are incorporated by reference.
- service-provisioning 43 is provided to the caller, either directly during the course of the call or indirectly through a service request dispatch.
- Service provisioning may be stalled as the agent collects information to address the caller's particular needs or is attending to other callers during high call volume, thereby resulting in callers being placed on hold.
- the content heard by the caller can be customized to the caller or situation, as further described below with reference to FIG. 7 .
- the content can include product information, advertising, or location-oriented materials.
- the playback speed can also be adjusted to better suit the length of expected delay.
- wrap-up 44 which provides closure to the call and a departing salutation. Other customer call sequences are feasible.
- the call center 30 can perform post-call processing 45 , such as identifying sound “bites,” that is, speech utterances in each call for analysis and storage in a database 34 .
- the speech utterances can be presented to an agent for review and manipulation, such as ranking or reordering.
- the post-call processing 45 can include performing speech recognition on the speech utterances, identifying speaker characteristics, and marking certain speech utterances and holding prompt selections for later use.
- the call center 30 can also perform in-progress call processing 46 , which operates on a stream of speech utterances copied from on-going calls. The same types of processing operations can be performed as on completed calls, but allows real time call analysis.
- FIG. 4 is a screen diagram showing, by way of example, a view of an agent console 50 for an on-going call session. Multiple call sessions can be simultaneously displayed and managed through the GUI controls.
- the particulars concerning the live call session are obtained by the message server 31 and provided to the agent.
- the session particulars can include, for instance, a caller profile including last hold time, personal prompt, options selections, modifications by the caller 51 , address 52 , contact information 53 , reason for the call 54 , credit card data 55 , and system available options for hold time.
- Other types of session particulars are possible.
- the agent can request a display update by pressing an “Update” control 56 and can review a recording of the caller's spoken responses through intuitive playback controls 57 . Additionally, the agent can transfer the caller to a live agent by pressing a “Transfer to Live Agent” control 58 and can log out by pressing a “Logout” control 59 . Other GUI controls are possible.
- FIG. 5 is a process flow diagram showing a method 70 for managing a dynamic call flow during automated call processing, in accordance with one embodiment.
- a caller interface would ordinarily be modified or adjusted by the agent that is assigned to a call session, the caller interface could also be modified by another agent console or by a server based on known caller attributes and conditions.
- the caller and agent engage in interaction throughout the call session (operation 71 ), such as described above with reference to FIG. 3 .
- the agent can evaluate the caller attributes (operation 72 ) and customize call flow and caller options, including hold time (operation 73 ), as further described below with reference to FIGS. 6 and 7 . Caller interaction, attribute evaluation, hold times, and call flow customization can be repeated as necessary throughout the remainder of the session.
- Caller attributes depend upon both the caller and call characteristics.
- FIG. 6 is a block diagram showing, by way of example; caller attributes 81 evaluated 80 during call.
- Caller-specific attributes can relate to perceived caller idiosyncrasies. Call characteristics exist independently of the caller and can be artifacts of both the physical medium and call timing.
- Caller attributes 81 that relate to the caller specifically include emotion 82 , accent 83 , gender 84 , and age 85 . Unless independently confirmed, for instance, through a questionnaire or database lookup, these caller attributes are perceived based on the subjective impressions of the agent or through automated analysis.
- Physical caller-independent attributes 81 include origin of the call 86 and the call time 87 .
- the caller origin 86 can be determined, for example, through area code or zip code lookup, and the call time 87 is available through automated timestamp.
- Other caller attributes 88 are possible.
- Caller options can vary for different reasons.
- the caller interface can be flexibly managed to improve the caller's experience and to benefit the manufacturer or vendor.
- FIG. 7 is a block diagram showing, by way of example, customized caller options 100 for managing hold times, in accordance with one embodiment.
- Caller options 100 that relate to the current call contest include altering playback speed 102 and selecting context-appropriate content 103 .
- Caller options 100 that relate to the caller include providing location-based content 104 .
- Other caller options 105 are possible.
- the options 100 can be triggered automatically or upon agent request.
- Hold time can be estimated by evaluating the length of the hold queue, the level of busyness of each agent, and upon the profile of the customer, for example, whether the customer is a preferred customer with enhanced service or a new customer. Other hold time estimation factors are possible. Different speeds and lengths of hold time content may be employed as needed to fill the estimated hold time. For example, depending upon the length of the hold queue or the time an agent needs to collect information to accurately and precisely address callers' needs, content may be more or less verbose, or may be shorter or longer.
Abstract
Description
- This U.S. Patent Application is a continuation of U.S. patent application Ser. No. 12/039,558, filed Feb. 28, 2008, pending, which claims priority to U.S. Provisional Patent Application Ser. No. 60/904,296, filed Feb. 28, 2007, the disclosure of which is incorporated by reference.
- The present invention relates in general to automated call center operation and, in particular, to a system and method for determining customer hold times.
- Customer call centers, or simply, “call centers,” offer a convenient and universally-accessible forum for customer assistance. Most call centers are reachable by telephone, including data network-based telephone, such as Voice-Over-Internet (VoIP), although Web- and email-based customer support are becoming increasingly available.
- Each customer call is an interactive process. The expectation level of callers is generally lower when they are aware that an automated system, rather than a live agent, is providing assistance. Nevertheless, callers still expect expeditious resolution of their concerns and minimizing delay is crucial, even when caller volume is high. Hold times can occur, such as when customers must be placed on hold until an agent becomes available. Call centers frequently play recorded music or advertisements to entertain callers while on hold, although callers on hold for a long time may hear the same content played repeatedly. Alternatively, call centers can feed live radio or subscription content, such as Muzak®, Fort Mill, S.C., which avoids repetition, but also relinquishes control over the content to a third party. Thus, recorded and live content only occupy time and seldom take fullest advantage of the opportunity to provide variable length or targeted content to callers while on hold.
- Therefore, there is a need for providing content to call center callers who are waiting on hold that can tailor the content played based on the callers and their customer assistance situations.
- Hold times usually occur when a caller calls and all agents are busy. The waiting times for each on-going caller session can be evaluated to determine hold time. Each caller waiting on hold can be evaluated for attributes, such as calling location or area of customer assistance. The content played to each caller on hold can be customized to better tailor the call to the caller and to advantageously use the hold time.
- An embodiment provides a system and method for determining customer hold times. A database of caller profiles is maintained. A call from a caller is received into a call center and assigned to an agent. A delay during which the caller is to be placed on hold is identified. A hold time for the delay is determined based on a length of a hold queue, a level of busyness of the agent and the caller profile associated with the caller.
- Still other embodiments of the present invention will become readily apparent to those skilled in the art from the following detailed description, wherein is described embodiments of the invention by way of illustrating the best mode contemplated for carrying out the invention. As will be realized, the invention is capable of other and different embodiments and its several details are capable of modifications in various obvious respects, all without departing from the spirit and the scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.
-
FIG. 1 is a functional block diagram showing an automated call center operational environment. -
FIG. 2 is a functional block diagram showing an automated call center for use in the automated call center operational environment ofFIG. 1 . -
FIG. 3 is a process flow diagram showing, by way of example, a typical call sequence, as transacted by the automated call center ofFIG. 2 . -
FIG. 4 is a screen diagram showing, by way of example, a view of an agent console for an on-going call session. -
FIG. 5 is a process flow diagram showing a method for managing a dynamic call flow during automated call processing, in accordance with one embodiment. -
FIG. 6 is a block diagram showing, by way of example, caller attributes evaluated during dynamic call flow management. -
FIG. 7 is a block diagram showing, by way of example, customized caller options for managing hold times, in accordance with one embodiment. - Automated call centers are a form of voice-response system, which rely upon programmed control to guide callers through a machine-generated dialogue for receiving support and problem resolution assistance.
FIG. 1 is a functional block diagram showing an automated call centeroperational environment 10. By way of example, a multiplicity of callers call into anautomated call center 11, generally through telephonic means, which can include conventional telephone handsets 13 a-c through Plain Old Telephone Service (POTS) 12, portable handsets 15 a-c through cellular andsatellite telephone service 14, VoIP clients 17 a-b, and Internet telephony clients 18 a-b, as well as other forms of telephony and voice-based communications. Callers can also “call” or interface into theautomated call center 11 usingconventional network clients 19 through aninternetwork 16, including the Internet. Other types of automated call center access are possible. - Hold times can occur under various circumstances. For example, multiple callers may call at the same time, thereby flooding the
call center 11. Similarly, one agent may be handling several callers at once and need time to resolve each problem. Other circumstances causing hold times are possible. - As used herein, the terms “caller,” “user,” and “customer” are used interchangeably to refer to a caller to the
automated call center 11. Similarly, the terms “agent,” “guide,” and “operator” are used interchangeably to refer to an agent that provides service provisioning for theautomated call center 11. Also, “wait” and “hold” may be used interchangeably to refer to the time a caller spends holding for an agent's attention. Additionally, although theautomated call center 11 is shown as a single point within the automated callcenter operation environment 10, theautomated call center 11 could include two or more logically interconnected, but physically separate, including geographically removed, call center operations, which collectively provide a unified automated call center. Other automated call center arrangements and configurations are possible. - Generally, an automated call center provides a single dial-in source for support and problem resolution assistance for customers seeking direct help from manufacturers and service vendors. Occasionally, the single dial-in source may experience an overflow of calls resulting in delayed response and hold times. However,
automated call centers 11 can also be applied to many other diverse areas of commerce, such as mail order sales and roadside assistance dispatch.FIG. 2 is a functional block diagram showing anautomated call center 30 for use in the automated call centeroperational environment 10 ofFIG. 1 . Theautomated call center 30 includes one ormore servers internal network 33. The agent consoles 32 a-c could also be interconnected to themessage server 31 over anexternal network infrastructure 33, such as the Internet or a non-public enterprise data network. Thenetwork infrastructure 33 can be either wired or wireless and, in one embodiment, is implemented based on the Transmission Control Protocol/Internet Protocol (TCP/IP) network specification, although other types or combinations of networking implementations are possible. Similarly, other network topologies and arrangements are possible. - A
message server 31 provides the primary message-based communications infrastructure for call center operation, such as described in commonly-assigned U.S. Pat. No. 7,292,689, issued Nov. 6, 2007, to Odinak et al., and U.S. Pat. No. 8,170,197, issued May 1, 2012, to Odinak, the disclosures of which are incorporated by reference. During regular operation, themessage server 31 executes individual threads to process multiple simultaneous calls, which are handled by agents executing agent applications on agent consoles 32 a-c. Hold time can occur, for instance, if the agents become overloaded. - Customer calls are received through a
telephony interface 35, which is operatively coupled to themessage server 31 to provide access to a telephone voice anddata network 36. In one embodiment, the telephony interface connects to thetelephone network 36 over a T-1 carrier line, which can provide up to 24 individual channels of voice or data traffic provided at 64 kilobits (Kbits) per second. Other types of telephone network connections are possible. - The
automated call center 30 also includes arecognition server 34 that interfaces directly to themessage server 31 as a top-level or root tier of a speech recognition hierarchy. Themessage server 31 sends streamed audio data for each incoming call to therecognition server 34, which performs distributed speech recognition, such as described in commonly-assigned U.S. Patent Application Publication No. 2007/0162282, published Jul. 12, 2007, to Odinak; and U.S. Provisional Patent application Ser. No. 60/757,356, filed Jan. 9, 2006, expired, the disclosures of which are incorporated by reference. Themessage server 31 assigns grammar generation and speech recognition to therecognition server 34. Upon startup, thetelephony gateway 35 opens a T-1 carrier device channel for each available T-1 time slot. Thetelephony gateway 35 initiates a new connection to themessage server 31, one connection per T-1 device channel, and themessage server 31, in turn, initiates a corresponding new connection to therecognition server 34. - The separate telephony gateway-to-message server and message server-to-main recognizer connections form one concurrent session. When a customer call is answered or connected, the
telephony gateway 35 sends a call message to themessage server 31. Themessage server 31 then sends a new call message to therecognition server 34. - The
message server 31 also assigns each new call to one of the agent consoles 32 a-c through dynamic load balancing, such as described in commonly-assigned U.S. Pat. No. 8,023,638, issued Sep. 20, 2011; and U.S. Provisional Patent application Ser. No. 60/838,074, filed Aug. 15, 2006, expired, the disclosures of which are incorporated by reference. Each agent console 32 a-c provides the primary means for direct customer interaction by providing service provisioning and related assistance to callers, such as further described below with reference toFIG. 3 . - The main purpose of each agent console 32 a-c is to execute one or more agent applications, which display both user and agent messages and provide menus of actions that can be executed in response to agent commands, including script execution and management of variable hold time. One or more agent applications execute on each agent console and one or more agent consoles can execute in parallel. Alternatively, multiple instances of agent applications can run on a server machine, and can be accessed and, if needed, modified by agents at agent consoles operating as remote terminals.
- Each component, including the
message server 31,recognition server 34, and agent consoles 32 a-c, is implemented as a computer program, procedure or module written as source code in a conventional programming language, such as the C++ programming language, and presented for execution by a computer system as object or byte code. Alternatively, the components could be directly implemented in hardware, either as integrated circuitry or burned into read-only or read-rewriteable memory components. The various implementations of the source code and object and byte codes can be held on a computer-readable storage medium or embodied on a transmission medium in a carrier wave. - Callers interface with an agent indirectly, who multitasks through one or more caller sessions via an agent console 32 a-c. The callers only perceive an automated calling interface heard, for instance, through their telephone or portable handset and do not actually speak with the agent person-to-person.
- Calls are processed through a sequence of phases.
FIG. 3 is a process flow diagram showing, by way of example, atypical call sequence 40, as transacted by theautomated call center 30 ofFIG. 2 . Although the form of call processing required may vary by subject matter and other factors, the same overall sequence of caller-to-agent interchanges will loosely apply. - A caller session starts with an incoming call and continues through to call termination, including any hold times. Initially, upon calling into the
call center 30, each caller receives an initial greeting andinformational message 41 providing a synopsis of caller options, which enable the caller to navigate to a specific topic for assistance or support. Following option selection, the caller engages in a customer assistance orsupport scenario 42 with an agent, which is either a live person or an automated prompt, such as generated by an automated voice response system, to collect information and problem troubleshoot. Thescenario 42 can be delayed due to agent unavailability, caller volume, and other factors, which require the caller to be placed on hold. - Throughout each session, the interactive call flow and hold time of each call can be adjusted by evaluating caller attributes, such as described below beginning with reference to
FIG. 5 . In addition, the order in which information is gathered from a caller, such as identifying the caller's needs or problems, can be dynamically evaluated and controlled, such as further described in commonly-assigned U.S. Pat. No. 8,442,209, issued May 14, 2013; and U.S. Provisional Patent application Ser. No. 60/838,102, filed Aug. 15, 2006, expired, the disclosures of which are incorporated by reference. - As required, service-provisioning 43 is provided to the caller, either directly during the course of the call or indirectly through a service request dispatch. Service provisioning may be stalled as the agent collects information to address the caller's particular needs or is attending to other callers during high call volume, thereby resulting in callers being placed on hold. The content heard by the caller can be customized to the caller or situation, as further described below with reference to
FIG. 7 . The content can include product information, advertising, or location-oriented materials. The playback speed can also be adjusted to better suit the length of expected delay. Followingservice provisioning 43, the call ends in wrap-up 44, which provides closure to the call and a departing salutation. Other customer call sequences are feasible. Importantly, however, from the perspective of the caller, the experience appears to be an interaction with an intelligent machine and the caller is aware that the agent is automated, not human. Accordingly, a typical caller will have a more relaxed expectation of agent responsiveness since a machine, and not an actual person, is on the line. - Following call termination, the
call center 30 can performpost-call processing 45, such as identifying sound “bites,” that is, speech utterances in each call for analysis and storage in adatabase 34. The speech utterances can be presented to an agent for review and manipulation, such as ranking or reordering. In addition, thepost-call processing 45 can include performing speech recognition on the speech utterances, identifying speaker characteristics, and marking certain speech utterances and holding prompt selections for later use. In a further embodiment, thecall center 30 can also perform in-progress call processing 46, which operates on a stream of speech utterances copied from on-going calls. The same types of processing operations can be performed as on completed calls, but allows real time call analysis. - Call sessions are displayed on each agent console through a graphical user interface (GUI).
FIG. 4 is a screen diagram showing, by way of example, a view of anagent console 50 for an on-going call session. Multiple call sessions can be simultaneously displayed and managed through the GUI controls. - The particulars concerning the live call session are obtained by the
message server 31 and provided to the agent. The session particulars can include, for instance, a caller profile including last hold time, personal prompt, options selections, modifications by the caller 51,address 52,contact information 53, reason for thecall 54, credit card data 55, and system available options for hold time. Other types of session particulars are possible. - During a session, the agent can request a display update by pressing an “Update”
control 56 and can review a recording of the caller's spoken responses through intuitive playback controls 57. Additionally, the agent can transfer the caller to a live agent by pressing a “Transfer to Live Agent”control 58 and can log out by pressing a “Logout”control 59. Other GUI controls are possible. - Caller sessions, including managed hold times, can be dynamically customized by an agent at any point during a call.
FIG. 5 is a process flow diagram showing amethod 70 for managing a dynamic call flow during automated call processing, in accordance with one embodiment. Although a caller interface would ordinarily be modified or adjusted by the agent that is assigned to a call session, the caller interface could also be modified by another agent console or by a server based on known caller attributes and conditions. Generally, with the exception of hold times, the caller and agent engage in interaction throughout the call session (operation 71), such as described above with reference toFIG. 3 . Throughout the session, the agent, with the assistance of the agent console 32 a-c, ormessage server 31, can evaluate the caller attributes (operation 72) and customize call flow and caller options, including hold time (operation 73), as further described below with reference toFIGS. 6 and 7 . Caller interaction, attribute evaluation, hold times, and call flow customization can be repeated as necessary throughout the remainder of the session. - Caller attributes depend upon both the caller and call characteristics.
FIG. 6 is a block diagram showing, by way of example; caller attributes 81 evaluated 80 during call. Caller-specific attributes can relate to perceived caller idiosyncrasies. Call characteristics exist independently of the caller and can be artifacts of both the physical medium and call timing. - Caller attributes 81 that relate to the caller specifically include
emotion 82,accent 83,gender 84, andage 85. Unless independently confirmed, for instance, through a questionnaire or database lookup, these caller attributes are perceived based on the subjective impressions of the agent or through automated analysis. - Physical caller-
independent attributes 81 include origin of thecall 86 and thecall time 87. Thecaller origin 86 can be determined, for example, through area code or zip code lookup, and thecall time 87 is available through automated timestamp. Other caller attributes 88 are possible. - Caller options can vary for different reasons. The caller interface can be flexibly managed to improve the caller's experience and to benefit the manufacturer or vendor.
FIG. 7 is a block diagram showing, by way of example, customizedcaller options 100 for managing hold times, in accordance with one embodiment.Caller options 100 that relate to the current call contest include alteringplayback speed 102 and selecting context-appropriate content 103.Caller options 100 that relate to the caller include providing location-basedcontent 104.Other caller options 105 are possible. Theoptions 100 can be triggered automatically or upon agent request. - Hold time can be estimated by evaluating the length of the hold queue, the level of busyness of each agent, and upon the profile of the customer, for example, whether the customer is a preferred customer with enhanced service or a new customer. Other hold time estimation factors are possible. Different speeds and lengths of hold time content may be employed as needed to fill the estimated hold time. For example, depending upon the length of the hold queue or the time an agent needs to collect information to accurately and precisely address callers' needs, content may be more or less verbose, or may be shorter or longer.
- While the invention has been particularly shown and described as referenced to the embodiments thereof, those skilled in the art will understand that the foregoing and other changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/612,220 US20150146867A1 (en) | 2007-02-28 | 2015-02-02 | System And Method For Determining Customer Hold Times |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US90429607P | 2007-02-28 | 2007-02-28 | |
US12/039,558 US8948371B2 (en) | 2007-02-28 | 2008-02-28 | System and method for managing hold times during automated call processing |
US14/612,220 US20150146867A1 (en) | 2007-02-28 | 2015-02-02 | System And Method For Determining Customer Hold Times |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/039,558 Continuation US8948371B2 (en) | 2007-02-28 | 2008-02-28 | System and method for managing hold times during automated call processing |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150146867A1 true US20150146867A1 (en) | 2015-05-28 |
Family
ID=39535643
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/039,558 Active 2032-02-12 US8948371B2 (en) | 2007-02-28 | 2008-02-28 | System and method for managing hold times during automated call processing |
US14/612,220 Abandoned US20150146867A1 (en) | 2007-02-28 | 2015-02-02 | System And Method For Determining Customer Hold Times |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/039,558 Active 2032-02-12 US8948371B2 (en) | 2007-02-28 | 2008-02-28 | System and method for managing hold times during automated call processing |
Country Status (2)
Country | Link |
---|---|
US (2) | US8948371B2 (en) |
EP (1) | EP1965577B1 (en) |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7292689B2 (en) * | 2002-03-15 | 2007-11-06 | Intellisist, Inc. | System and method for providing a message-based communications infrastructure for automated call center operation |
US7899178B2 (en) | 2006-09-29 | 2011-03-01 | Verint Americas Inc. | Recording invocation of communication sessions |
EP1965577B1 (en) * | 2007-02-28 | 2014-04-30 | Intellisist, Inc. | System and method for managing hold times during automated call processing |
JP4695614B2 (en) * | 2007-03-02 | 2011-06-08 | 株式会社ドワンゴ | Access management apparatus, access management method, and access management program |
CA2628297A1 (en) * | 2007-04-03 | 2008-10-03 | Intellisist, Inc. | System and method for managing customer queuing |
US9014365B1 (en) * | 2007-06-06 | 2015-04-21 | United Services Automobile Association (Usaa) | Systems and methods for state information exchange |
US9721270B2 (en) * | 2012-05-02 | 2017-08-01 | At&T Intellectual Property I, L.P. | Integrating communications services with personalized social networks |
US9602458B2 (en) | 2013-01-29 | 2017-03-21 | International Business Machines Corporation | Establishing an automatic communications delay based on prevailing activity factors |
US9432324B2 (en) | 2013-01-29 | 2016-08-30 | International Business Machines Corporation | Establishing an automatic communications delay based on social or business network factors |
WO2015024104A1 (en) * | 2013-08-21 | 2015-02-26 | Offen David William | Systems and methods for managing incoming calls |
US10623565B2 (en) * | 2018-02-09 | 2020-04-14 | Afiniti Europe Technologies Limited | Techniques for behavioral pairing in a contact center system |
US10942941B2 (en) * | 2018-11-12 | 2021-03-09 | International Business Machines Corporation | Natural language processor for cognitively generating contextual filler designed to keep users engaged |
CN110719362A (en) * | 2019-09-10 | 2020-01-21 | 北京百度网讯科技有限公司 | Call processing method and device, electronic equipment and storage medium |
US20210117882A1 (en) | 2019-10-16 | 2021-04-22 | Talkdesk, Inc | Systems and methods for workforce management system deployment |
US11736615B2 (en) | 2020-01-16 | 2023-08-22 | Talkdesk, Inc. | Method, apparatus, and computer-readable medium for managing concurrent communications in a networked call center |
US11677875B2 (en) | 2021-07-02 | 2023-06-13 | Talkdesk Inc. | Method and apparatus for automated quality management of communication records |
US11856140B2 (en) | 2022-03-07 | 2023-12-26 | Talkdesk, Inc. | Predictive communications system |
US11736616B1 (en) | 2022-05-27 | 2023-08-22 | Talkdesk, Inc. | Method and apparatus for automatically taking action based on the content of call center communications |
US11943391B1 (en) | 2022-12-13 | 2024-03-26 | Talkdesk, Inc. | Method and apparatus for routing communications within a contact center |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030103617A1 (en) * | 2001-12-03 | 2003-06-05 | Ibm Corporation | Managing caller profiles across multiple call hold centers |
US20040174980A1 (en) * | 2003-03-06 | 2004-09-09 | Sbc Properties, L.P. | System and method for providing customer activities while in queue |
US20060221941A1 (en) * | 2004-11-05 | 2006-10-05 | Konstantin Kishinsky | Voice over internet protocol implemented call center |
US8948371B2 (en) * | 2007-02-28 | 2015-02-03 | Intellisist, Inc. | System and method for managing hold times during automated call processing |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB9723813D0 (en) * | 1997-11-11 | 1998-01-07 | Mitel Corp | Call routing based on caller's mood |
US6798768B1 (en) * | 2000-02-23 | 2004-09-28 | Lucent Technologies Inc. | Multimedia call routing in an IP network |
US7095842B2 (en) * | 2001-12-03 | 2006-08-22 | International Business Machines Corporation | Enabling caller controlled hold queue position adjustment |
US8170197B2 (en) | 2002-03-15 | 2012-05-01 | Intellisist, Inc. | System and method for providing automated call center post-call processing |
US7292689B2 (en) | 2002-03-15 | 2007-11-06 | Intellisist, Inc. | System and method for providing a message-based communications infrastructure for automated call center operation |
US6959080B2 (en) | 2002-09-27 | 2005-10-25 | Rockwell Electronic Commerce Technologies, Llc | Method selecting actions or phases for an agent by analyzing conversation content and emotional inflection |
US7050569B1 (en) | 2003-08-08 | 2006-05-23 | Sprint Spectrum L.P. | Selecting an interactive application to run while a caller is on hold depending on the caller's expected wait time |
US8380484B2 (en) * | 2004-08-10 | 2013-02-19 | International Business Machines Corporation | Method and system of dynamically changing a sentence structure of a message |
US20070025540A1 (en) * | 2005-07-07 | 2007-02-01 | Roger Travis | Call center routing based on talkativeness |
US20070162282A1 (en) | 2006-01-09 | 2007-07-12 | Gilad Odinak | System and method for performing distributed speech recognition |
CA2660907C (en) | 2006-08-15 | 2013-06-11 | Intellisist, Inc. | Balancing agent console load during automated call processing |
EP2057830B1 (en) | 2006-08-15 | 2010-03-24 | Intellisist, Inc. | Processing out-of-order caller responses during automated call processing |
-
2008
- 2008-02-28 EP EP08102101.6A patent/EP1965577B1/en active Active
- 2008-02-28 US US12/039,558 patent/US8948371B2/en active Active
-
2015
- 2015-02-02 US US14/612,220 patent/US20150146867A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030103617A1 (en) * | 2001-12-03 | 2003-06-05 | Ibm Corporation | Managing caller profiles across multiple call hold centers |
US20040174980A1 (en) * | 2003-03-06 | 2004-09-09 | Sbc Properties, L.P. | System and method for providing customer activities while in queue |
US20060221941A1 (en) * | 2004-11-05 | 2006-10-05 | Konstantin Kishinsky | Voice over internet protocol implemented call center |
US8948371B2 (en) * | 2007-02-28 | 2015-02-03 | Intellisist, Inc. | System and method for managing hold times during automated call processing |
Also Published As
Publication number | Publication date |
---|---|
EP1965577A1 (en) | 2008-09-03 |
US20080205620A1 (en) | 2008-08-28 |
EP1965577B1 (en) | 2014-04-30 |
US8948371B2 (en) | 2015-02-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8948371B2 (en) | System and method for managing hold times during automated call processing | |
US8442209B2 (en) | System and method for processing out-of-order caller responses during automated call processing | |
US9386154B2 (en) | System, method and software program for enabling communications between customer service agents and users of communication devices | |
US8494151B2 (en) | System and method for balancing call session assignments on an agent console | |
US6751306B2 (en) | Local on-hold information service with user-controlled personalized menu | |
US7751552B2 (en) | Intelligently routing customer communications | |
US8566419B2 (en) | Systems and methods for enhanced user communications | |
JP2018195315A (en) | Real-time speech feed to agent greeting | |
US20130114801A1 (en) | Customer-controlled recording | |
US9438734B2 (en) | System and method for managing a dynamic call flow during automated call processing | |
GB2420246A (en) | Predetermined greeting or announcement related to caller | |
US20020076032A1 (en) | On-hold information service with caller-controlled personalized menu | |
GB2463358A (en) | Forwarding a telephone call to an agent from a Computer Telephony (CT) server located as Service Provider Equipment (SPE) within a telephone network. | |
US8699697B2 (en) | Providing caller-specific information | |
GB2582401A (en) | Intelligent speech-enabled scripting |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTELLISIST, INC., WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ODINAK, GILAD;WAALKES, ADAM;SIGNING DATES FROM 20070226 TO 20070227;REEL/FRAME:045360/0686 |
|
AS | Assignment |
Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW YORK Free format text: TERM LOAN INTELLECTUAL PROPERTY SECURITY AGREEMENT;ASSIGNOR:INTELLISIST, INC.;REEL/FRAME:046202/0467 Effective date: 20180508 Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW YORK Free format text: TERM LOAN SUPPLEMENT NO. 1;ASSIGNOR:INTELLISIST, INC.;REEL/FRAME:046204/0465 Effective date: 20180508 Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW Y Free format text: TERM LOAN INTELLECTUAL PROPERTY SECURITY AGREEMENT;ASSIGNOR:INTELLISIST, INC.;REEL/FRAME:046202/0467 Effective date: 20180508 Owner name: CITIBANK N.A., AS COLLATERAL AGENT, NEW YORK Free format text: ABL SUPPLEMENT NO. 1;ASSIGNOR:INTELLISIST, INC.;REEL/FRAME:046204/0525 Effective date: 20180508 Owner name: CITIBANK N.A., AS COLLATERAL AGENT, NEW YORK Free format text: ABL INTELLECTUAL PROPERTY SECURITY AGREEMENT;ASSIGNOR:INTELLISIST, INC.;REEL/FRAME:046204/0418 Effective date: 20180508 Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW Y Free format text: TERM LOAN SUPPLEMENT NO. 1;ASSIGNOR:INTELLISIST, INC.;REEL/FRAME:046204/0465 Effective date: 20180508 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: INTELLISIST, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 46204/FRAME 0525;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063456/0001 Effective date: 20230403 Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 46204/FRAME 0525;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063456/0001 Effective date: 20230403 Owner name: AVAYA HOLDINGS CORP., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 46204/FRAME 0525;ASSIGNOR:CITIBANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:063456/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 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 Effective date: 20230501 Owner name: CAAS TECHNOLOGIES, LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 Effective date: 20230501 Owner name: HYPERQUALITY II, LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 Effective date: 20230501 Owner name: HYPERQUALITY, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 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 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 Effective date: 20230501 Owner name: VPNET TECHNOLOGIES, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 Effective date: 20230501 Owner name: OCTEL COMMUNICATIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 Effective date: 20230501 Owner name: AVAYA INTEGRATED CABINET SOLUTIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 Effective date: 20230501 Owner name: INTELLISIST, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 Effective date: 20230501 Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46202/0467);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063695/0145 Effective date: 20230501 Owner name: AVAYA MANAGEMENT L.P., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 Effective date: 20230501 Owner name: CAAS TECHNOLOGIES, LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 Effective date: 20230501 Owner name: HYPERQUALITY II, LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 Effective date: 20230501 Owner name: HYPERQUALITY, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 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 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 Effective date: 20230501 Owner name: VPNET TECHNOLOGIES, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 Effective date: 20230501 Owner name: OCTEL COMMUNICATIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 Effective date: 20230501 Owner name: AVAYA INTEGRATED CABINET SOLUTIONS LLC, NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 Effective date: 20230501 Owner name: INTELLISIST, INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 Effective date: 20230501 Owner name: AVAYA INC., NEW JERSEY Free format text: RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 46204/0465);ASSIGNOR:GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT;REEL/FRAME:063691/0001 Effective date: 20230501 |