A call center is configured to determine variable rest periods for one or more agents, based at least in part on factors such as call center service state and agent occupancy. The call center service states may include a number of designated service states associated with a particular skill or type of communication supported by one or more agents of the call center. A particular one of the states represents a branded service level, while other states represent over-service and under-service conditions. The rest period determined for one or more of the agents can be used to implement features such as many-to-many work assignment, just-in-time (JIT) delivery of work, next opportunity for service (NOS) indicators, thereby facilitating the processing of communications in the call center.
|
1. A method of processing communications in a call center, the call center providing for a given agent, in addition to scheduled breaks, variable rest periods for the given agent between servicing of communications by that agent, the method comprising the steps of:
determining a rest period for the given agent, based at least in part on one or more of (i) an agent occupancy level and (ii) which of a plurality of designated service states is associated with at least one of a particular skill and a particular type of communication supported by the agent, a set of rest periods being associated with each of the service states and including at least one specified rest period for each of a plurality of agent occupancy levels, a given one of the rest periods thereby being determinable based on agent occupancy level and service state, wherein the plurality of service states comprise at least first, second and third service states corresponding to a first service level, a second service level representative of an over-service condition relative to the first service level, and a third service level representative of an under-service condition relative to the first service level, respectively; and processing the communications in the call center such that communications are not handled by the given agent for at least a portion of the determined rest period.
19. An apparatus for processing communications in a call center, the call center providing for a given agent, in addition to scheduled breaks, variable rest periods for the given agent between servicing of communications by that agent, the apparatus comprising:
a processor operative to determine a rest period for the given agent, based at least in part on one or more of (i) an agent occupancy level and (ii) which of a plurality of designated service states is associated with at least one of a particular skill and a particular type of communication supported by the agent, a set of rest periods being associated with each of the service states and including at least one specified rest period for each of a plurality of agent occupancy levels, a given one of the rest periods thereby being determinable based on agent occupancy level and service state, wherein the plurality of service states comprise at least first, second and third service states corresponding to a first service level, a second service level representative of an over-service condition relative to the first service level, and a third service level representative of an under-service condition relative to the first service level, respectively, such that communications are not handled by the given agent for at least a portion of the determined rest period; and a memory coupled to the processor and operative to store information regarding at least one of the agent occupancy level and the service states.
37. An article of manufacture containing one or more software programs for processing communications in a call center, the call center providing for a given agent, in addition to scheduled breaks, variable rest periods for the given agent between servicing of communications by that agent, wherein the one or more software programs, when executed in a processor, cause the processor to perform the steps of:
determining a rest period for the given agent, based at least in part on one or more of (i) an agent occupancy level and (ii) which of a plurality of designated service states is associated with at least one of a particular skill and a particular type of communication supported by the agent, a set of rest periods being associated with each of the service states and including at least one specified rest period for each of a plurality of agent occupancy levels, a given one of the rest periods thereby being determinable based on agent occupancy level and service state, wherein the plurality of service states comprise at least first, second and third service states corresponding to a first service level, a second service level representative of an over-service condition relative to the first service level, and a third service level representative of an under-service condition relative to the first service level, respectively; and processing the communications in the call center such that communications are not handled by the given agent for at least a portion of the determined rest period.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
9. The method of
10. The method of
11. The method of
12. The method of
13. The method of
14. The method of
15. The method of
16. The method of
17. The method of
18. The method of
20. The apparatus of
21. The apparatus of
22. The apparatus of
23. The apparatus of
24. The apparatus of
25. The apparatus of
26. The apparatus of
27. The apparatus of
28. The apparatus of
29. The apparatus of
30. The apparatus of
31. The apparatus of
32. The apparatus of
33. The apparatus of
34. The apparatus of
35. The apparatus of
36. The apparatus of
|
The invention relates generally to call centers or other call processing systems in which voice calls, e-mails, faxes, voice messages, text messages, Internet service requests or other types of communications are distributed among a number of service agents for handling.
Call centers distribute calls and other types of communications to available service agents in accordance with various predetermined criteria. Existing call centers suffer from a number of drawbacks. For example, as will be described in greater detail below, such centers are generally unable to provide satisfactory techniques for variable rest periods, many-to-many work assignments, just-in-time (JIT) delivery of work, and next opportunity for service (NOS).
With regard to variable rest periods, a call center must be attentive to both the needs of callers and the needs of agents. In some situations, the needs of a caller outweigh the needs of the agent and in other situations the needs of the agent outweigh the needs of the caller. It is therefore necessary that the call center have a convenient way to represent and activate rules that protect an agent from burn-out or heavy workload while also protecting a caller from long wait times.
It is well known that the overall performance of a call center is highly dependent upon the efficiency and effectiveness of the agents. Efficiency and effectiveness are believed to improve in call centers where workload is distributed fairly and situations that create burn-out are minimized. Nonetheless, a typical practice used in conventional call centers is to assign a given available agent to a waiting call, even if the given agent has been carrying a far greater workload than other agents in the same peer group, and even if the call in queue could wait longer and still be considered well served.
Some existing call centers can provide variable agent rest periods using a feature known as "Timed ACW," which puts an agent into an After Call Work (ACW) state for a specified period of time. However, in implementing such a rest period using this feature there is generally no consideration of the current performance conditions of the call center or a particular skill at the time the rest period takes place.
With regard to work assignment, call centers have typically utilized either a one-to-many process or a many-to-one process. In a one-to-many process, a single call arrives and the process chooses among "many" agents currently available to handle that call. In a many-to-one process, a single agent becomes available when many calls are in queue, and the process chooses which one of the "many" calls the agent should take. Existing call centers can evaluate the consequences of each work assignment, taking into account predictions on how the calls not taken from queue will fare or how the various available agents compare in workload so that fairness is taken into account. However, such centers are generally unable to provide a more efficient many-to-many work assignment, i.e., a process in which a set of multiple calls are considered simultaneously for distribution to multiple agents.
With regard to JIT delivery of work, in a call center operating in a distributed work environment, e.g., a business enterprise that includes multiple geographically-dispersed sites, the information and communication elements needed to perform a particular task are often stored or waiting in locations distant from an agent who has been assigned the task. For example, a call assigned to an agent may need to be transferred to the agent from a remote or centralized site and the data associated with the call may need to be retrieved from a remote or centralized server. It is known from the operation of call centers in such distributed environments that significant delays can result when calls and data held in one location are delivered to agents in another location. For example, it may take up to several seconds for an agent to establish the necessary connections and obtain the data required to handle the call. This type of delay is clearly undesirable, and represents a significant loss of productivity.
NOS represents knowledge of upcoming and scheduled availability of agents who are presently on a break or other rest period of defined duration. With regard to NOS, call centers are generally moving from a reactive operation based on historical metrics or measurements to predictive operations based on the ability to predict future events and evaluate consequences of individual operational decisions. Certain call centers now include software enabling the calculation of a predictive outlook for a head call in any queue in order to determine when the call might be handled by an agent other than the one currently available. For example, some call centers use a metric known as Predicted Wait Time (PWT). The PWT measure incorporates a Weighted Advance Time (WAT), which is a predictive outlook on when a call will likely be served by an agent. Although such predictive outlooks can be made more accurate if based on better information regarding agent availability, existing call centers are generally unable to provide such information, and are therefore deficient in terms of NOS capability.
As is apparent from the foregoing, a need exists for improved techniques for providing features such as variable rest periods, many-to-many work assignment, JIT delivery of work, and NOS indicators in a call center.
The invention provides methods and apparatus which improve the processing of calls or other communications in a call center. More particularly, the invention in an illustrative embodiment provides techniques for implementing variable rest periods, many-to-many work assignment,just-in-time (JIT) delivery of work, and next opportunity for service (NOS) indicators.
In accordance with a first aspect of the invention, a call center is configured to determine variable rest periods for one or more agents, based at least in part on factors such as call center service state and agent occupancy. The call center service states may include a number of designated service states associated with a particular skill or type of communication supported by one or more agents of the call center. A particular one of the states represents a branded service level, while other states represent over-service and under-service conditions. For example, the service states may include an over threshold state, a current jeopardy state, a future jeopardy state, a within-range state, an over served state, a queue empty state and an agents idle state, wherein the within range state is representative of the particular service level. The agent occupancy levels may include, e.g., a below target range level, a within range level, and an above target range level.
In an illustrative embodiment, the rest period is determined for the given agent based on both the agent occupancy level and a worst-case one of the service states for one or more skills supported by the agent. More particularly, a different set of rest periods is associated with each of the service states for each of plurality of agent occupancy levels, such that the rest period is determined for the given agent by determining a particular agent occupancy level and a worst-case service state among the service states corresponding to skills supported by the agent. The determined rest period for the given agent provides a precise time of future availability of that agent.
In accordance with a second aspect of the invention, the rest period determined for one or more of the agents can be used to implement a many-to-many work assignment feature in which multiple agents are each considered simultaneously for handling multiple waiting communications.
In accordance with a third aspect of the invention, a JIT delivery of work feature is provided in which the precise time of future availability of the agent as determined based on the rest period is used to schedule at least one event prior to delivery of a particular communication to that agent. Such events may include, e.g., a call selection event, a data retrieval event and a call connection event. These events are scheduled such that data required to process the particular communication is provided to the agent substantially simultaneously with the communication.
In accordance with a fourth aspect of the invention, the precise time of future availability of the agent is used to determine a NOS indicator for each of at least a subset of the skills supported by the agent. Such NOS indicators generated for at least a subset of the plurality of agents associated with the call center may be arranged in a visual display in the form of a time line of NOS indicators for a given skill supported by the agents. Several NOS time lines of this type may be displayed simultaneously, each including NOS indicators for a particular skill supported by at least a subset of the agents. NOS information generated in accordance with the invention may also be made available to call selection and agent selection algorithms.
By providing more accurate information regarding agent availability, the present invention overcomes the above-described drawbacks of conventional call centers, and provides substantially improved processing of calls and other communications. These and other features and advantages of the present invention will become more apparent from the accompanying drawings and the following detailed description.
Although the invention will be illustrated below in conjunction with the processing of calls in an exemplary call center, it is not limited to use with any particular type of call center or communication processing application. For example, the invention is applicable to the processing of incoming communications, outgoing communications or both. The disclosed techniques can be used with automatic call distribution (ACD) systems, telemarketing systems, private-branch exchange (PBX) systems, computer-telephony integration (CTI)-based systems, as well as in combinations of these and other types of call centers. A call center in accordance with the invention may be configured using any type of network infrastructure, such as, e.g., asynchronous transfer mode (ATM), local area networks, wide area networks, Internet Protocol (IP) networks, etc. The term "call center" as used herein is thus intended to include any type of ACD system, telemarketing system or other communication system which processes calls or other service requests, including voice calls, video calls, multimedia calls, e-mail, faxes, text chat or voice messages as well as various portions or combinations of these and other types of communications. The term "call" as used herein is intended to include any of the above-noted types of communications as well as portions or combinations of these and other communications.
The ACD system 101 may be implemented in a manner similar to, for example, the Definity® PBX-based ACD system from Lucent Technologies.
Referring again to
The ACD system 101 further includes a call vector 140. The call vector 140 may be one of a number of different types of stored control programs implemented in system 101. Calls incoming to the call center on lines or trunks 100 are assigned by call vector 140 to different call queues 121-129 based upon the agent skill that they require for proper handling. Agents 106-108 who are available for handling calls are assigned to agent queues 131-139 based upon the skills which they possess. An agent may have multiple skills, and hence may be assigned to multiple agent queues 131-139 simultaneously. Such an agent is referred to herein as a "multi-skill agent." Furthermore, an agent may have different levels of skill expertise (e.g., different skill levels in a multi-level scale or primary (P) and secondary (S) skills), and hence may be assigned to different agent queues 131-139 at different expertise levels.
Call vectoring is described in greater detail in Definity® Communications System Generic 3 Call Vectoring/Expert Agent Selection (EAS) Guide, AT&T Publication No. 555-230-520, Issue Nov. 3, 1993, which is incorporated by reference herein. Skills-based ACD techniques are described in greater detail in, for example, U.S. Pat. No. 5,206,903 issued Apr. 27, 1993 in the name of inventors J. E. Kohler et al. and entitled "Automatic Call Distribution Based on Matching Required Skills with Agents Skills," which is incorporated by reference herein.
Another program executing in ACD system 101 is an agent selector 150. Selector 150 may be implemented in software stored either in the memory 115 of system 101, in a peripheral memory (e.g., a disk, CD-ROM, etc.) of system 101, or in any other type of computer readable medium associated with system 101, and executed by processor 116 or other suitable processing hardware associated with the ACD system 101. Selector 150 in this exemplary embodiment implements conventional techniques for providing an assignment between available calls and available agents. The conventional techniques implemented by selector 150 are well known in the art and will not be further described herein. It should be noted that these functions could be implemented in other elements of the ACD system 101, or using a combination of a number of different elements in such a system.
Further details regarding call processing in a system such as ACD system 101 can be found in, for example, U.S. Pat. No. 5,905,793 issued May 18, 1999 in the name of inventors A. D. Flockhart et al. and entitled "Waiting-Call Selection Based on Anticipated Wait Times," and U.S. Pat. No. 6,192,122 issued Feb. 20, 2001 in the name of inventors A. D. Flockhart et al. and entitled "Call Center Agent Selection that Optimizes Call Wait Times," both of which are incorporated by reference herein.
In accordance with the present invention, the call center of
A first aspect of the invention provides variable rest periods based at least in part on factors such as call center service state and agent occupancy. Variable rest periods in accordance with the invention are determined utilizing a set of rules, with call center service states as a reference in activating the rules. Agents are thus provided with rest breaks in between calls even when calls are in queue in order to improve agent fairness in terms of workload and reduce agent burn-out, which as previously noted can result in less efficient or effective agent performance.
Associated with the flow diagram 200 of
In this example, the set of service states 204 includes an Over Threshold state 211, a Current Jeopardy state 212, a Future Jeopardy state 213, a Within Range state 214, an Over Served state 215, a Queue Empty state 216, and an Agents Idle state 217. Each of the states is associated with a particular display color, in order to facilitate interpretation of the information by a call center manager, agent, etc. More particularly, service states 211 through 217 are associated with the colors red, orange, yellow, green, blue, indigo and violet, respectively.
It should be noted that the particular number and arrangement of service states shown in
A given one of the states in the set of service states 204, i.e., the Within Range state 214, represents a branded range. This branded range may be, e.g., a branded range of wait time that the call center wants to deliver consistently for a particular skill. A more particular example of such a branded range is, e.g., 6 to 20 seconds of wait time for answering an incoming call. Other states in the set of service states 204 represent wait times above the branded range, i.e., under-served conditions, and below the branded range, i.e., over-served conditions. Appropriate rules can be enabled so as to ensure that as many calls as possible are answered within the branded range, to shorten waits that are longer than the branded range, and to minimize the number of calls handled outside of the branded range. The service states may be based on, e.g., a waiting time measure, an average speed of answer (ASA) measure, a percent in service level, or other measures as well as combinations of such measures.
The diagram 200 includes designated sets of service state-based variable rest periods in three different categories of agent occupancy 220. These three categories include a below target range category 222, a within range category 224, and an above target range category 226, each of which may be associated with a particular range of values of a designated agent occupancy metric. Each of the three categories 222, 224 and 226 includes a corresponding set of rest periods 232, 234 and 236, with each of the sets of rest periods including a specified rest period for each of the possible service states 211 through 217.
In this example, the rest periods for the below target range agent occupancy category 222 are all set to 0 seconds, indicating that there are no rest periods when the value of the agent occupancy metric is in this category. The rest periods for the within range agent occupancy category 224 vary in accordance with the service state, e.g., the designated rest periods in this category are 0, 0, 0, 4, 4, 4 and 4 seconds for the service states 211, 212, 213, 214, 215, 216 and 217, respectively. This means that an agent may be given, e.g., a 4 second rest period after completing the current call if the worst-case call center service state for the skills served by that agent is Within Range 214 or better, or a 0 second rest period, i.e., no rest period, if the worst-case call center service state for the skills served by the agent is Future Jeopardy 213 or worse. The rest periods for the above target range agent occupancy category 226 also vary in accordance with the service state, e.g., the designated rest periods in this category are 0, 0,4, 8, 12, 16 and 20 seconds for the service states 211,212, 213, 214, 215, 216 and 217, respectively. This means that an agent may be given, e.g., a 12 second rest period after completing the current call if the worst-case call center service state for the skills served by the agent is Over Served 215, or a 0 second rest period, i.e., no rest period, if the worst-case call center service state for the skills served by the agent is Current Jeopardy 212 or worse.
The variable rest period determination illustrated in
When an agent is granted a rest period as determined in accordance with the above-described rules, the agent may be provided with a notification indicating that such a rest period has been granted and the duration of the rest period. It is possible for the rest period to be curtailed due to a circumstance such as a problematic caller wait time appearing in the interim. In addition, agent breaks, such as those already scheduled in a call center, might be moved forward or appended on to a rest period determined by the above-described rules. These rules can of course also apply to work tasks other than traditional voice calls, such as email, fax, text chat, etc. for which service states are defined and predicted, or simply defined and measured.
It should also be noted that in an alternative embodiment, the rest periods could be determined using only the agent occupancy category, or only the service state of the one or more skills the agent handles. As previously noted, there may be no predictive component in certain applications.
In addition, the above-described rest periods determined for a given skill service state can be further adjusted based on factors such as target occupancy. For example, an adjusted rest period may be computed as the sum of a skill service state rest period and a function of target occupancy in percent, as follows:
In this example, for every 2% over the target occupancy, one additional second is added to the skill service state rest period. Similarly, for every 2% under the target occupancy, one second is removed from the rest period. Numerous other adjustments of this type can be made, based on target occupancy or other factors, as will be apparent to those skilled in the art.
In accordance with a second aspect of the invention, a many-to-many work assignment process is provided. The many-to-many work assignment process implements assignments between many agents and many work assignments, as opposed to the conventional one-to-many or many-to-one processes described previously.
The many-to-many work assignment process of the present invention in an illustrative embodiment determines precisely which agents will become available in the near future so that decisions can be made based on a known pool of agents assigned in various ways to the known body of callers in queue. This precise knowledge regarding when agents are available for the next call may be based at least in part on information relating to variable rest periods granted to those agents in the manner previously described. The process creates a buffered pool of agents by slightly delaying the work assignment decision such that multiple agents can be considered simultaneously for multiple calls.
Examples of the work assignment considerations that can be made in this many-to-many assignment process are the following:
1. Optimum assignment of agents dedicated to particular callers in queue.
2. Optimum use of rare skills held by the agents in the pool.
3. Optimum achievement against branded service targets.
4. Caller treatment changes, including announcements that let callers know that a pre-assigned agent will be with them in X seconds.
5. Better achievement in efforts to create equal and reasonable workloads.
6. Better achievement in efforts to provide a predefined mix of calls to any particular agent.
As a more particular example of the many-to-many work assignment process in accordance with the invention, consider a situation in which a particular set of agents, e.g., Agent 1, Agent 2 and Agent 3, become available in sequential order after designated rest periods. Applying a conventional many-to-one process to this situation, calls queued for service requiring particular skills, e.g., Skill A, Skill B and Skill C, may be assigned such that Agent 1 handles the next call in queue for Skill A, Agent 2 handles the next call in queue for Skill B, and Agent 3 handles the next call in queue for Skill C. Using the many-to-many work assignment process, however, it is possible to consider other factors which may dictate the assignment of a particular agent to a particular call. For example, if Agent 1 is particularly proficient at Skill C and it is known that another agent will be coming available to handle the call queued for Skill A, the many-to-many assignment process may assign the agents to the calls such that Agent 1 handles the next call in queue for Skill C, Agent 2 handles the next call in queue for Skill B, and Agent 3 handles the next call in queue for Skill A. This type of assignment can provide a better utilization of call center resources than the many-to-one process previously described.
Advantageously, a many-to-many work assignment process in accordance with the invention allows for more extensive optimization of call center operations by incorporating information on precisely-known future events pertaining to multiple work items and multiple agents. More particularly, by moving away from the conventional one-to-many or many-to-one approaches with single decisions made in real time to groups of decisions made in quasi-real time, this aspect of the invention allows better alignment of call center operations with various goals.
A third aspect of the present invention relates to just-in-time (JIT) delivery of work within a call center. This aspect of the invention provides a technique which allows work to be delivered to an assigned agent to arrive "just in time" for the agent's availability to work on it, thereby reducing or eliminating the delay incurred by an available agent waiting for the work after the agent becomes available.
The JIT delivery process uses knowledge of an agent's upcoming availability as an event which triggers a series of other events leading up to that availability. The other events in an illustrative embodiment can start with a call selection, to determine what kind of work the agent will do upon becoming available. From this decision, it is known whether a remote call must be delivered to the agent's station and how long that connection may take to establish. The amount of time needed to obtain any data associated with the call can also be determined. The fetching of the data and the connecting of the call can then be scheduled so that their completions approximately coincide with the agent's next known availability.
The knowledge of the agent's upcoming availability may be based at least in part on a known rest period assigned to that agent in accordance with the previously-described variable rest period process, since assigning a rest period of known length creates as a result a known, future availability event. For example, assume that an agent is known to be in a rest period that will end in 10 seconds. The call selection may be scheduled for 6 seconds prior to the end of the rest period, such that call selection executes at 4 seconds into the rest period. Assume then that the call selection assigns a call queued at a remote site to this agent, and the data for this call is also in a remote server. The data retrieval may then be scheduled to take place 5 seconds before the rest period ends, and the call connection may be scheduled to execute 2 seconds before the rest period ends. The call and the data associated with the call then arrive coincident to the end of the agent's rest period.
Advantageously, this aspect of the invention eliminates unnecessary agent delay in cases which include elements such as data retrieval and call connection, by scheduling the retrieval or connection to coincide with the agent's availability.
It will be apparent to those skilled in the art that this technique, like the other call processing techniques described herein, is applicable to call center work tasks other than voice calls.
A fourth aspect of the present invention relates to a technique for providing "next opportunity for service" or NOS, i.e., a known, future point in time at which a work item, such as a call, queued for service could be serviced next. As previously noted, the above-described techniques for providing a rest period of variable length create a known future event of availability. This known future availability can be used to define a NOS. More particularly, any time an agent is in a variable rest period, for each of the skills the agent handles, there is a NOS.
Given that many agents can be in a variable rest period at the same time, an NOS time line can be generated for any skill or type or work in the call center. This knowledge can be incorporated into evaluating the consequences of using an agent for any of the particular skills the agent holds. For example, the NOS time line for a given skill can be used to determine how many opportunities there will be to service a call prior to an pre-defined objective wait time for that type of call. Also, a number of different NOS time lines could be displayed together in a designated arrangement, with appropriate color coding or similar differentiation techniques used to indicate individual agents associated with the time lines.
An NOS in accordance with the invention is generally not considered a guaranteed time at which a particular call will be served, but instead serves as an indication of the next point in time at which the call will be considered for service. However, it could be viewed as a guaranteed time in certain limited circumstances, e.g., if the agent whose rest period is used to derive the NOS is a single-skilled agent and does not become unavailable for another reason in the interim. In addition, the NOS could be reported in real time, perhaps along with a periodically refreshed or reported measure such as Weighted Advance Time (WAT), in order to provide a call center manager with foresight on how calls may be served in the very near future.
It should be understood that the above-described variable rest period, many-to-many work assignment, JIT delivery of work and NOS techniques are not limited to use with voice calls, but are instead more generally applicable to any work tasks that arrive from a customer, e.g., e-mail, fax, text chat, voice over IP, etc., as well as to workflow and/or customer fulfillment generated work tasks that are part of, e.g., a workflow system in which various work tasks dealing with actual or electronic "paperwork," contacts with customers, approvals, etc. that must be completed in order to fulfill a specified customer need.
A call center configured in accordance with the invention may be distributed over multiple sites. For example, the processing operations described above may be performed in a remote or centralized system before a given call or other communication is delivered to an available agent at a particular local site.
The above-described embodiments of the invention are intended to be illustrative only. For example, it should be noted that the exemplary configuration of the call center shown in
In addition, as previously noted, the invention can be applied to a wide variety of communications other than calls, including faxes, e-mails, text chat, voice over IP, etc. It should also be noted that the invention may be implemented in the form of a computer-readable medium or other similar medium containing software which, when executed by a computer or other type of processor, will cause the processor to implement the processing functions described above. For example, the BCMS 110, call vector 140, agent selector 150 and other elements of ACD system 101 may each be implemented at least in part as one or more software programs stored in memory 115 or any other computer readable medium associated with the ACD system 101, and executed by processor 116 or other processing hardware associated with the ACD system 101. A variety of other implementations may also be used to provide communication processing operations in accordance with the invention. These and numerous other alternative embodiments within the scope of the following claims will be apparent to those skilled in the art.
Kohler, Joylee E., Flockhart, Andrew Derek, Mathews, Eugene P., Foster, Robin H., Taylor, John Z.
Patent | Priority | Assignee | Title |
10084918, | May 28 2013 | Mattersight Corporation | Delayed-assignment predictive routing and methods |
10218850, | Mar 14 2013 | Mattersight Corporation | Real-time customer profile based predictive routing |
10375244, | Aug 06 2008 | AVAYA LLC | Premises enabled mobile kiosk, using customers' mobile communication device |
10572879, | Oct 03 2005 | AVAYA LLC | Agent driven media-agnostic work item grouping and sharing over a consult medium |
10819827, | May 29 2018 | System for server scheduling using integer programming | |
10904390, | Jun 30 2020 | Avaya Management L.P. | Method of integrating artificial intelligence systems to dynamically adjust wrap-up time |
11087261, | Mar 14 2008 | DATAINFOCOM USA, INC | Apparatus, system and method for processing, analyzing or displaying data related to performance metrics |
11386382, | Dec 17 2020 | NICE LTD | System and method for determining and utilizing after-call-work factor in contact center quality processes |
6859529, | Apr 12 2000 | UNWIRED BROADBAND, INC | Method and system for self-service scheduling of inbound inquiries |
6895438, | Sep 06 2000 | PAUL ULRICH | Telecommunication-based time-management system and method |
7054434, | Jul 09 2001 | Noble Systems Corporation | System and method for common account based routing of contact records |
7103173, | Jul 09 2001 | Noble Systems Corporation | System and method for preemptive goals based routing of contact records |
7142662, | Jul 11 2000 | Noble Systems Corporation | Method and system for distributing outbound telephone calls |
7158629, | Jul 09 2001 | Noble Systems Corporation | System and method for preemptive goals based routing of contact records |
7184541, | Dec 11 2003 | General Electric Capital Corporation | Method and apparatus for selecting an agent to handle a call |
7239692, | Jul 11 2000 | Noble Systems Corporation | Method and system for distributing outbound telephone calls |
7386850, | Jun 01 2001 | AVAYA Inc | Arrangement for scheduling tasks based on probability of availability of resources at a future point in time |
7421475, | Oct 22 2002 | Dell Products L.P.; Dell Products L P | Method and system for e-mail allocation |
7502460, | Nov 20 2006 | ALVARIA CAYMAN CX | Method and system for distributing outbound telephone calls |
7567653, | Mar 22 2005 | AVAYA LLC | Method by which call centers can vector inbound TTY calls automatically to TTY-enabled resources |
7613289, | Dec 14 2000 | RPX CLEARINGHOUSE LLC | Application based queuing via an H.323/SIP interface |
7620169, | Jun 17 2002 | AVAYA LLC | Waiting but not ready |
7636433, | Dec 02 2005 | AVAYA LLC | Timeline visualization for call center processes |
7657021, | Sep 29 2004 | AVAYA LLC | Method and apparatus for global call queue in a global call center |
7711104, | Mar 31 2004 | AVAYA LLC | Multi-tasking tracking agent |
7715546, | Jul 09 2001 | ALVARIA CAYMAN CX | System and method for updating contact records |
7729490, | Feb 12 2004 | AVAYA LLC | Post-termination contact management |
7734032, | Mar 31 2004 | AVAYA LLC | Contact center and method for tracking and acting on one and done customer contacts |
7747705, | May 08 2007 | AVAYA LLC | Method to make a discussion forum or RSS feed a source for customer contact into a multimedia contact center that is capable of handling emails |
7752230, | Oct 06 2005 | AVAYA LLC | Data extensibility using external database tables |
7770175, | Sep 26 2003 | AVAYA LLC | Method and apparatus for load balancing work on a network of servers based on the probability of being serviced within a service time goal |
7779042, | Aug 08 2005 | AVAYA LLC | Deferred control of surrogate key generation in a distributed processing architecture |
7787609, | Oct 06 2005 | AVAYA LLC | Prioritized service delivery based on presence and availability of interruptible enterprise resources with skills |
7809127, | May 26 2005 | AVAYA Inc | Method for discovering problem agent behaviors |
7817796, | Apr 27 2005 | AVAYA LLC | Coordinating work assignments for contact center agents |
7822587, | Oct 03 2005 | AVAYA Inc | Hybrid database architecture for both maintaining and relaxing type 2 data entity behavior |
7835514, | Sep 18 2006 | AVAYA LLC | Provide a graceful transfer out of active wait treatment |
7844504, | Apr 27 2000 | AVAYA LLC | Routing based on the contents of a shopping cart |
7881450, | Sep 15 2005 | ARLINGTON TECHNOLOGIES, LLC | Answer on hold notification |
7885401, | Mar 29 2004 | AVAYA LLC | Method and apparatus to forecast the availability of a resource |
7936867, | Aug 15 2006 | AVAYA LLC | Multi-service request within a contact center |
7949121, | Sep 27 2004 | AVAYA LLC | Method and apparatus for the simultaneous delivery of multiple contacts to an agent |
7949123, | Sep 28 2004 | AVAYA Inc | Wait time predictor for long shelf-life work |
7953219, | Jul 19 2001 | NICE LTD | Method apparatus and system for capturing and analyzing interaction based content |
7953859, | Mar 31 2004 | AVAYA LLC | Data model of participation in multi-channel and multi-party contacts |
7962356, | Jun 01 2005 | InVision Software AG | Staff scheduling |
8000989, | Mar 31 2004 | AVAYA Inc | Using true value in routing work items to resources |
8036371, | Dec 05 2005 | AVAYA LLC | Utilizing small group call center agents to improve productivity without impacting service level targets |
8050199, | Sep 30 2003 | ARLINGTON TECHNOLOGIES, LLC | Endpoint registration with local back-off in a call processing system |
8065618, | Aug 18 2003 | SAP SE | Customization of an interaction center manager's graphical dashboard |
8073129, | Oct 03 2005 | AVAYA LLC | Work item relation awareness for agents during routing engine driven sub-optimal work assignments |
8094804, | Sep 26 2003 | AVAYA LLC | Method and apparatus for assessing the status of work waiting for service |
8116237, | Sep 26 2008 | AVAYA LLC | Clearing house for publish/subscribe of status data from distributed telecommunications systems |
8116446, | Oct 03 2005 | AVAYA LLC | Agent driven work item awareness for tuning routing engine work-assignment algorithms |
8175258, | Mar 12 2001 | ALVARIA CAYMAN CX | System and method for common account based routing of contact records |
8204884, | Jul 14 2004 | Nice Systems Ltd. | Method, apparatus and system for capturing and analyzing interaction based content |
8234141, | Sep 27 2004 | AVAYA LLC | Dynamic work assignment strategies based on multiple aspects of agent proficiency |
8238541, | Jan 31 2006 | AVAYA LLC | Intent based skill-set classification for accurate, automatic determination of agent skills |
8306212, | Feb 19 2010 | AVAYA LLC | Time-based work assignments in automated contact distribution |
8332249, | Jul 07 2003 | INCONTACT, INC | System and method for integrated supply chain and contact center management |
8345857, | Sep 26 2008 | General Motors LLC | Method for reducing non-value added time between calls serviced at a call center |
8385532, | May 12 2008 | AVAYA LLC | Real-time detective |
8385533, | Sep 21 2009 | AVAYA LLC | Bidding work assignment on conference/subscribe RTP clearing house |
8391463, | Sep 01 2006 | AVAYA LLC | Method and apparatus for identifying related contacts |
8411843, | Oct 04 2005 | ServiceNow, Inc | Next agent available notification |
8442197, | Mar 30 2006 | ARLINGTON TECHNOLOGIES, LLC | Telephone-based user interface for participating simultaneously in more than one teleconference |
8457300, | Feb 12 2004 | AVAYA LLC | Instant message contact management in a contact center |
8503663, | Jun 30 2005 | GENESYS CLOUD SERVICES, INC | System and method for agent queue activation in a contact center |
8504534, | Sep 26 2007 | AVAYA LLC | Database structures and administration techniques for generalized localization of database items |
8565386, | Sep 29 2009 | ARLINGTON TECHNOLOGIES, LLC | Automatic configuration of soft phones that are usable in conjunction with special-purpose endpoints |
8577015, | Sep 16 2005 | AVAYA LLC | Method and apparatus for the automated delivery of notifications to contacts based on predicted work prioritization |
8577706, | Jul 07 2003 | INCONTACT, INC | Method for agent scheduling for revenue and service channels in a skills-based routing environment |
8578396, | Aug 08 2005 | Avaya Inc. | Deferred control of surrogate key generation in a distributed processing architecture |
8612272, | Jun 05 2006 | INCONTACT, INC | System and method for skills-based staffing and scheduling |
8621011, | May 12 2009 | AVAYA LLC | Treatment of web feeds as work assignment in a contact center |
8644491, | Aug 21 2009 | AVAYA LLC | Mechanism for multisite service state description |
8675860, | Feb 16 2012 | AVAYA LLC | Training optimizer for contact center agents |
8731177, | Mar 31 2004 | AVAYA LLC | Data model of participation in multi-channel and multi-party contacts |
8737173, | Feb 24 2006 | AVAYA LLC | Date and time dimensions for contact center reporting in arbitrary international time zones |
8751274, | Sep 26 2003 | AVAYA LLC | Method and apparatus for assessing the status of work waiting for service |
8767944, | Jan 03 2007 | AVAYA LLC | Mechanism for status and control communication over SIP using CODEC tunneling |
8811597, | Sep 07 2006 | AVAYA LLC | Contact center performance prediction |
8831206, | May 12 2008 | AVAYA Inc | Automated, data-based mechanism to detect evolution of employee skills |
8855292, | Sep 08 2006 | AVAYA LLC | Agent-enabled queue bypass to agent |
8856182, | Jan 25 2008 | Avaya Inc. | Report database dependency tracing through business intelligence metadata |
8867733, | Mar 14 2013 | Mattersight Corporation | Real-time predictive routing |
8873739, | Feb 12 2004 | AVAYA LLC | Instant message contact management in a contact center |
8891747, | Sep 26 2003 | AVAYA LLC | Method and apparatus for assessing the status of work waiting for service |
8938063, | Sep 07 2006 | AVAYA LLC | Contact center service monitoring and correcting |
8964958, | May 20 2009 | AVAYA LLC | Grid-based contact center |
8971520, | Oct 27 2006 | Answer Financial Inc. | Method for optimizing skill assignment in call center agent applications |
9025761, | Sep 26 2003 | AVAYA LLC | Method and apparatus for assessing the status of work waiting for service |
9083804, | May 28 2013 | Mattersight Corporation | Optimized predictive routing and methods |
9106748, | May 28 2013 | Mattersight Corporation | Optimized predictive routing and methods |
9137372, | Mar 14 2013 | Mattersight Corporation | Real-time predictive routing |
9137373, | Mar 14 2013 | Mattersight Corporation | Real-time predictive routing |
9398157, | May 28 2013 | Mattersight Corporation | Optimized predictive routing and methods |
9516069, | Nov 17 2009 | ARLINGTON TECHNOLOGIES, LLC | Packet headers as a trigger for automatic activation of special-purpose softphone applications |
9544433, | Jan 08 2009 | GENESYS CLOUD SERVICES, INC | Managing interactive communications campaigns using a hold queue |
9565312, | Mar 14 2013 | Mattersight Corporation | Real-time predictive routing |
9667795, | May 28 2013 | Mattersight Corporation | Dynamic occupancy predictive routing and methods |
9680993, | Jan 08 2009 | GENESYS CLOUD SERVICES, INC | Managing interactive communications campaigns with reduced customer-to-agent connection latency |
9848085, | May 28 2013 | Mattersight Corporation | Customer satisfaction-based predictive routing and methods |
9936075, | Mar 14 2013 | Mattersight Corporation | Adaptive occupancy real-time predictive routing |
RE44979, | Jul 09 2001 | ALVARIA CAYMAN CX | System and method for common account based routing of contact records |
RE46420, | Jul 11 2000 | ALVARIA CAYMAN CX | Method and system for distributing outbound telephone calls |
RE46467, | Jul 11 2000 | Noble Systems Corporation | Method and system for distributing outbound telephone calls |
RE46478, | Jul 11 2000 | Noble Systems Corporation | System and method for preemptive goals based routing of contact records |
RE49905, | Jun 30 2020 | Avaya Management L.P. | Method of integrating artificial intelligence systems to dynamically adjust wrap-up time |
Patent | Priority | Assignee | Title |
5206903, | Dec 26 1990 | AVAYA Inc | Automatic call distribution based on matching required skills with agents skills |
5905793, | Mar 07 1997 | AVAYA Inc | Waiting-call selection based on anticipated wait times |
6044355, | Jul 09 1997 | IEX Corporation | Skills-based scheduling for telephone call centers |
6278978, | Apr 07 1998 | CREDIT SUISSE AS ADMINISTRATIVE AGENT | Agent scheduling system and method having improved post-processing step |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Dec 15 1999 | Avaya Technology Corp. | (assignment on the face of the patent) | / | |||
Jan 13 2000 | FOSTER, ROBIN H | Lucent Technologies Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 010637 | /0982 | |
Jan 20 2000 | FLOCKHART, ANDREW DEREK | Lucent Technologies Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 010637 | /0982 | |
Jan 24 2000 | KOHLER, JOYLEE E | Lucent Technologies Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 010637 | /0982 | |
Feb 09 2000 | MATHEWS, EUGENE P | Lucent Technologies Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 010637 | /0982 | |
Feb 21 2000 | TAYLOR, JOHN Z | Lucent Technologies Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 010637 | /0982 | |
Sep 29 2000 | Lucent Technologies Inc | Avaya Technology Corp | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 012707 | /0562 | |
Apr 05 2002 | Avaya Technology Corp | BANK OF NEW YORK, THE | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 012816 | /0088 | |
Oct 04 2005 | Avaya Technology Corp | Avaya Technology LLC | CONVERSION FROM CORP TO LLC | 022071 | /0420 | |
Oct 26 2007 | VPNET TECHNOLOGIES, INC | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020156 | /0149 | |
Oct 26 2007 | VPNET TECHNOLOGIES, INC | CITICORP USA, INC , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020166 | /0705 | |
Oct 26 2007 | OCTEL COMMUNICATIONS LLC | CITICORP USA, INC , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020166 | /0705 | |
Oct 26 2007 | Avaya Technology LLC | CITICORP USA, INC , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020166 | /0705 | |
Oct 26 2007 | Avaya, Inc | CITICORP USA, INC , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020166 | /0705 | |
Oct 26 2007 | OCTEL COMMUNICATIONS LLC | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020156 | /0149 | |
Oct 26 2007 | Avaya Technology LLC | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020156 | /0149 | |
Oct 26 2007 | Avaya, Inc | CITIBANK, N A , AS ADMINISTRATIVE AGENT | SECURITY AGREEMENT | 020156 | /0149 | |
Jun 25 2008 | Avaya Technology LLC | AVAYA Inc | REASSIGNMENT | 021158 | /0310 | |
Feb 11 2011 | AVAYA INC , A DELAWARE CORPORATION | BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE | SECURITY AGREEMENT | 025863 | /0535 | |
Mar 07 2013 | Avaya, Inc | BANK OF NEW YORK MELLON TRUST COMPANY, N A , THE | SECURITY AGREEMENT | 030083 | /0639 | |
Nov 28 2017 | THE BANK OF NEW YORK MELLON TRUST COMPANY, N A | AVAYA Inc | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 030083 0639 | 045012 | /0666 | |
Nov 28 2017 | The Bank of New York | AVAYA INC FORMERLY KNOWN AS AVAYA TECHNOLOGY CORP | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 012816 0088 | 044892 | /0158 | |
Nov 28 2017 | THE BANK OF NEW YORK MELLON TRUST, NA | AVAYA Inc | BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL FRAME 025863 0535 | 044892 | /0001 | |
Dec 15 2017 | CITICORP USA, INC | Avaya, Inc | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 | |
Dec 15 2017 | CITICORP USA, INC | Avaya Technology, LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 | |
Dec 15 2017 | CITICORP USA, INC | OCTEL COMMUNICATIONS LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 | |
Dec 15 2017 | CITICORP USA, INC | VPNET TECHNOLOGIES, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 | |
Dec 15 2017 | CITICORP USA, INC | SIERRA HOLDINGS CORP | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 045032 | /0213 |
Date | Maintenance Fee Events |
Oct 20 2006 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Oct 14 2010 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Dec 19 2014 | REM: Maintenance Fee Reminder Mailed. |
May 13 2015 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
Date | Maintenance Schedule |
May 13 2006 | 4 years fee payment window open |
Nov 13 2006 | 6 months grace period start (w surcharge) |
May 13 2007 | patent expiry (for year 4) |
May 13 2009 | 2 years to revive unintentionally abandoned end. (for year 4) |
May 13 2010 | 8 years fee payment window open |
Nov 13 2010 | 6 months grace period start (w surcharge) |
May 13 2011 | patent expiry (for year 8) |
May 13 2013 | 2 years to revive unintentionally abandoned end. (for year 8) |
May 13 2014 | 12 years fee payment window open |
Nov 13 2014 | 6 months grace period start (w surcharge) |
May 13 2015 | patent expiry (for year 12) |
May 13 2017 | 2 years to revive unintentionally abandoned end. (for year 12) |