Patent Description:
The present disclosure generally relates to task assignment systems and, more particularly, to techniques for error handling in a task assignment system with an external pairing system.

A typical pairing system algorithmically assigns tasks arriving at a task assignment system to agents available to handle those tasks. At times, the task assignment system may be in an "L1 state" and have agents available and waiting for assignment to tasks. At other times, the task assignment system may be in an "L2 state" and have tasks waiting in one or more queues for an agent to become available for assignment. At yet other times, the task assignment system may be in an "L3" state and have multiple agents available and multiple tasks waiting for assignment.

Some traditional pairing systems assign tasks to agents ordered based on time of arrival, and agents receive tasks ordered based on the time when those agents became available. This strategy may be referred to as a "first-in, first-out," "FIFO," or "round-robin" strategy. For example, in an L2 environment, when an agent becomes available, the task at the head of the queue would be selected for assignment to the agent.

Some task assignment systems prioritize some types of tasks ahead of other types of tasks. For example, some tasks may be high-priority tasks, while other tasks are low-priority tasks. Under a FIFO strategy, high-priority tasks will be assigned ahead of low-priority tasks.

Other traditional pairing systems may implement a performance-based routing (PBR) strategy for prioritizing higher-performing agents for task assignment. Under PBR, for example, the highest-performing agent among available agents receives the next available task.

"Behavioral Pairing" or "BP" strategies, for assigning tasks to agents, improve upon traditional pairing methods. BP targets balanced utilization of agents while improving overall task assignment system performance potentially beyond what FIFO or PBR methods achieve in practice.

Thus, it may be understood that there may be a need for techniques that enable a task assignment system to use high-performing pairing strategies (e.g., BP strategies) that improve upon traditional pairing strategies.

<CIT> discloses techniques for adapting behavioral pairing to runtime conditions in a task assignment system are disclosed. In one particular embodiment, the techniques may be realized as a method for adapting behavioral pairing to runtime conditions in a task assignment system comprising: determining, by at least one computer processor communicatively coupled to and configured to operate in the task assignment system, at least two pairing models for assigning tasks in the task assignment system; monitoring, by the at least one computer processor, at least one parameter of the task assignment system; and selecting, by the at least one computer processor, one of the at least two pairing models based on a value of the at least one parameter.

<CIT> discloses a task management method and system thereof that enables planning of tasks for task management by autonomous systems, in particular but not exclusively for managing task by recovering from failure for completion of an assigned task and/or increase the likelihood of task completion. The system generates an execution plan based on defined task goals for executing the task and enables continuous management of a plurality of tasks in the case of failure.

Techniques for error handling in a task assignment system with an external pairing system are disclosed. In one particular embodiment, the techniques may be realized as a method for error handling in a task assignment system with an external pairing system comprising transmitting, by at least one computer processor communicatively coupled to and configured to operate in the task assignment system, to the external pairing system over an application programming interface, a request for the external pairing system to select a first pairing between one or more tasks awaiting assignment and one or more agents available for assignment, the first pairing to be selected according to a first pairing strategy; determining, by the at least one computer processor, a timeout window to wait for the external pairing system to provide a response that identifies the first pairing; detecting, by the at least one computer processor, an expiration of the timeout window without receiving the response; and in response to detecting the expiration of the timeout window, accessing, by the at least one computer processor, one or more configuration parameters associated with the external pairing system, the one or more configuration parameters identifying a hidden queue of the task assignment system that is hidden from the external pairing system such that information stored in the hidden queue is not shared with the external pairing system; determining, by the at least one computer processor, that the hidden queue includes one or more second tasks that are designated to be paired by the external pairing system; and in response to determining that the hidden queue includes the one or more second tasks that are designated to be paired by the external pairing system, selecting, by the at least one computer processor, a second pairing between the one or more tasks and the one or more agents, the second pairing being selected according to a second pairing strategy.

Aspects of the invention will be apparent from the appended claim set.

The present disclosure will now be described in more detail with reference to particular embodiments thereof as shown in the accompanying drawings. While the present disclosure is described below with reference to particular embodiments, it should be understood that the present disclosure is not limited thereto. Those of ordinary skill in the art having access to the teachings herein will recognize additional implementations, modifications, and embodiments, as well as other fields of use, which are within the scope of the present disclosure as described herein, and with respect to which the present disclosure may be of significant utility.

To facilitate a fuller understanding of the present disclosure, reference is now made to the accompanying drawings, in which like elements are referenced with like numerals. These drawings should not be construed as limiting the present disclosure, but are intended to be illustrative only.

A typical pairing system algorithmically assigns tasks arriving at a task assignment system to agents available to handle those tasks. At times, the task assignment system may be in an "L1 state" and have agents available and waiting for assignment to tasks. At other times, the task assignment system may be in an "L2 state" and have tasks waiting in one or more queues for an agent to become available for assignment. At yet other times, the task assignment system may be in an "L3" state and have multiple agents available and multiple tasks waiting for assignment. An example of a task assignment system is a contact center system that receives contacts (e.g., telephone calls, internet chat sessions, emails, etc.) to be assigned to agents.

"Behavioral Pairing" or "BP" strategies, for assigning tasks to agents that improve upon traditional pairing methods. BP targets balanced utilization of agents while improving overall task assignment system performance potentially beyond what FIFO or PBR methods achieve in practice. This is a remarkable achievement inasmuch as BP acts on the same tasks and same agents as FIFO or PBR methods, approximately balancing the utilization of agents as FIFO provides, while improving overall task assignment system performance beyond what either FIFO or PBR provides in practice. BP improves performance by assigning agent and task pairs in a fashion that takes into consideration the assignment of potential subsequent agent and task pairs such that, when the benefits of multiple assignments are aggregated, they may exceed those of FIFO and PBR strategies.

Various BP strategies may be used, such as a diagonal model BP strategy or a network flow BP strategy. These task assignment strategies and others are described in detail for a contact center context in, e.g., <CIT>; <CIT>; <CIT>; and <CIT>. BP strategies may be applied in an L1 environment (agent surplus, one task; select among multiple available/idle agents), an L2 environment (task surplus, one available/idle agent; select among multiple tasks in queue), and an L3 environment (multiple agents and multiple tasks; select among pairing permutations).

When a pairing system is integrated into a task assignment system, handling errors that arise in association with implementing the pairing strategy (e.g., failures, outages, misconfigurations, dropped or delayed communications, etc.) may be straightforward given that the task assignment system can readily access information and/or controls used to monitor, detect, and recover from such errors. As explained in detail below, embodiments of the present disclosure relate to techniques for error handling in a task assignment system with an external pairing system, where the ability of the task assignment system to monitor, detect, and/or recover from errors may be more limited.

The description herein describes network elements, computers, and/or components of a system and method for pairing strategies in a task assignment system that may include one or more modules. As used herein, the term "module" may be understood to refer to computing software, firmware, hardware, and/or various combinations thereof. Modules, however, are not to be interpreted as software which is not implemented on hardware, firmware, or recorded on a non-transitory processor readable recordable storage medium (i.e., modules are not software per se). It is noted that the modules are exemplary. The modules may be combined, integrated, separated, and/or duplicated to support various applications. Also, a function described herein as being performed at a particular module may be performed at one or more other modules and/or by one or more other devices instead of or in addition to the function performed at the particular module. Further, the modules may be implemented across multiple devices and/or other components local or remote to one another. Additionally, the modules may be moved from one device and added to another device, and/or may be included in both devices.

<FIG> shows a block diagram of a pairing system <NUM> according to embodiments of the present disclosure. The pairing system <NUM> may be included in a task assignment system (e.g., contact center system) or incorporated in a component or module (e.g., a pairing module) of a task assignment system for helping to assign tasks (e.g., contacts) among various agents.

The pairing system <NUM> may include a task assignment module <NUM> that is configured to pair (e.g., match, assign, route) incoming tasks to available agents. In the example of <FIG>, m tasks 120A-<NUM>m are received over a given period, and n agents 130A-<NUM>n are available during the given period. Each of the m tasks may be assigned to one of the n agents for servicing or other types of task processing. In the example of <FIG>, m and n may be arbitrarily large finite integers greater than or equal to one. In a real-world task assignment system, such as a contact center system, there may be dozens, hundreds, etc. of agents logged into the contact center system to interact with contacts during a shift, and the contact center system may receive dozens, hundreds, thousands, etc. of contacts (e.g., telephone calls, internet chat sessions, emails, etc.) during the shift.

In some embodiments, a task assignment strategy module <NUM> may be communicatively coupled to and/or configured to operate in the pairing system <NUM>. The task assignment strategy module <NUM> may implement one or more task assignment strategies (or "pairing strategies") for assigning individual tasks to individual agents (e.g., pairing contacts with contact center agents). A variety of different task assignment strategies may be devised and implemented by the task assignment strategy module <NUM>. In some embodiments, a FIFO strategy may be implemented in which, for example, the longest-waiting agent receives the next available task (in L1 environments) or the longest-waiting task is assigned to the next available agent (in L2 environments). In other embodiments, a PBR strategy for prioritizing higher-performing agents for task assignment may be implemented. Under PBR, for example, the highest-performing agent among available agents receives the next available task. In yet other embodiments, a BP strategy may be used for optimally assigning tasks to agents using information about either tasks or agents, or both. Various BP strategies may be used, such as a diagonal model BP strategy or a network flow BP strategy. See <CIT>; <CIT>; <CIT>; and <CIT>.

In some aspects, a historical assignment module <NUM> may be communicatively coupled to and/or configured to operate in the pairing system <NUM> via other modules such as the task assignment module <NUM> and/or the task assignment strategy module <NUM>. The historical assignment module <NUM> may be responsible for various functions such as monitoring, storing, retrieving, and/or outputting information about task-agent assignments that have already been made. For example, the historical assignment module <NUM> may monitor the task assignment module <NUM> to collect information about task assignments in a given period. Each record of a historical task assignment may include information such as an agent identifier, a task or task type identifier, offer or offer set identifier, outcome information, or a pairing strategy identifier (i.e., an identifier indicating whether a task assignment was made using a BP strategy, or some other pairing strategy such as a FIFO or PBR pairing strategy).

In some examples, and for some contexts, additional information may be stored. For example, in a call center context, the historical assignment module <NUM> may also store information about the time a call started, the time a call ended, the phone number dialed, and the caller's phone number. For another example, in a dispatch center (e.g., "truck roll") context, the historical assignment module <NUM> may also store information about the time a driver (i.e., field agent) departs from the dispatch center, the route recommended, the route taken, the estimated travel time, the actual travel time, the amount of time spent at the customer site handling the customer's task, etc..

In some examples, the historical assignment module <NUM> may generate a pairing model or a similar computer processor-generated model based on a set of historical assignments for a period of time (e.g., the past week, the past month, the past year, etc.), which may be used by the task assignment strategy module <NUM> to make task assignment recommendations or instructions to the task assignment module <NUM>.

In some examples, a benchmarking module <NUM> may be communicatively coupled to and/or configured to operate in the pairing system <NUM> via other modules such as the task assignment module <NUM> and/or the historical assignment module <NUM>. The benchmarking module <NUM> may benchmark the relative performance of two or more pairing strategies (e.g., FIFO, PBR, BP, etc.) using historical assignment information, which may be received from, for example, the historical assignment module <NUM>. In some embodiments, the benchmarking module <NUM> may perform other functions, such as establishing a benchmarking schedule for cycling among various pairing strategies, tracking cohorts (e.g., base and measurement groups of historical assignments), etc. Benchmarking is described in detail for the contact center context in, e.g., <CIT>.

In some examples, the benchmarking module <NUM> may output or otherwise report or use the relative performance measurements. The relative performance measurements may be used to assess the quality of a pairing strategy to determine, for example, whether a different pairing strategy (or a different pairing model) should be used, or to measure the overall performance (or performance gain) that was achieved within the task assignment system while it was optimized or otherwise configured to use one pairing strategy instead of another.

<FIG> shows a block diagram of a task assignment system <NUM> according to embodiments of the present disclosure. The task assignment system <NUM> may include a central switch <NUM>. The central switch <NUM> may receive incoming tasks <NUM> (e.g., telephone calls, internet chat sessions, emails, etc.) or support outbound connections to contacts via a dialer, a telecommunications network, or other modules (not shown). The central switch <NUM> may include routing hardware and software for helping to route tasks among one or more queues (or subcenters), or to one or more Private Branch Exchange ("PBX") or Automatic Call Distribution (ACD) routing components or other queuing or switching components within the task assignment system <NUM>. The central switch <NUM> may not be necessary if there is only one queue (or subcenter), or if there is only one PBX or ACD routing component in the task assignment system <NUM>.

If more than one queue (or subcenter) is part of the task assignment system <NUM>, each queue may include at least one switch (e.g., switches 280A and 280B). The switches 280A and 280B may be communicatively coupled to the central switch <NUM>. Each switch for each queue may be communicatively coupled to a plurality (or "pool") of agents. Each switch may support a certain number of agents (or "seats") to be logged in at one time. At any given time, a logged-in agent may be available and waiting to be connected to a task, or the logged-in agent may be unavailable for any of a number of reasons, such as being connected to another task, performing certain post-call functions such as logging information about the call, or taking a break. In the example of <FIG>, the central switch <NUM> routes tasks to one of two queues via switch 280A and switch 280B, respectively. Each of the switches 280A and 280B are shown with two agents each. Agents 230A and 230B may be logged into switch 280A, and agents 230C and 230D may be logged into switch 280B.

The task assignment system <NUM> may also be communicatively coupled to an integrated pairing system <NUM>. The pairing system <NUM> may be native to (or built in) the task assignment system <NUM> (i.e., "first-party") or may be a service provided by, for example, a third-party vendor. In the example of <FIG>, the pairing system <NUM> may be communicatively coupled to one or more switches in the switch system of the task assignment system <NUM>, such as central switch <NUM>, switch 280A, and switch 280B. In some embodiments, switches of the task assignment system <NUM> may be communicatively coupled to multiple pairing systems. In some embodiments, the pairing system <NUM> may be embedded within a component of the task assignment system <NUM> (e.g., embedded in or otherwise integrated with a switch). An example of the pairing system <NUM> is the pairing system <NUM>, which is described above.

The pairing system <NUM> may receive information from a switch (e.g., switch 280A) about agents logged into the switch (e.g., agents 230A and 230B) and about incoming tasks <NUM> via another switch (e.g., central switch <NUM>) or, in some embodiments, from a network (e.g., the Internet or a telecommunications network) (not shown). The pairing system <NUM> may process this information to determine which tasks should be paired (e.g., matched, assigned, distributed, routed) with which agents.

For example, in an L1 state, multiple agents may be available and waiting for connection to a task, and a task arrives at the task assignment system <NUM> via a network or the central switch <NUM>. As explained above, without the pairing system <NUM>, a switch will typically automatically distribute the new task to whichever available agent has been waiting the longest amount of time for an agent under a FIFO strategy, or whichever available agent has been determined to be the highest-performing agent under a PBR strategy. With the pairing system <NUM>, contacts and agents may be given scores (e.g., percentiles or percentile ranges/bandwidths) according to a pairing model or other artificial intelligence data model, so that a task may be matched, paired, or otherwise connected to a preferred agent.

In an L2 state, multiple tasks are available and waiting for connection to an agent, and an agent becomes available. These tasks may be queued in a switch such as a PBX or ACD device. Without the pairing system <NUM>, a switch will typically connect the newly available agent to whichever task has been waiting on hold in the queue for the longest amount of time as in a FIFO strategy or a PBR strategy when agent choice is not available. In some task assignment centers, priority queuing may also be incorporated, as previously explained. With the pairing system <NUM> in this L2 scenario, as in the L1 state described above, tasks and agents may be given percentiles (or percentile ranges/bandwidths, etc.) according to, for example, a model, such as an artificial intelligence model, so that an agent becoming available may be matched, paired, or otherwise connected to a preferred task.

In the task assignment system <NUM>, the pairing system <NUM> may switch between pairing strategies and benchmark the relative performance of the task assignment system under each pairing strategy (e.g., by using a benchmarking module such as benchmarking module <NUM> of pairing system <NUM>). The benchmarking results may help to determine which pairing strategy or combination of pairing strategies to use to optimize or improve the overall performance of the task assignment system <NUM>.

Given that the pairing system <NUM> is integrated with-or "internal" to-the task assignment system <NUM>, handling errors that arise in association with implementing the pairing strategy (e.g., failures, outages, misconfigurations, dropped or delayed communications, or various other issues that may interfere with the ability of task assignment system <NUM> to use pairing system <NUM> to select pairings in a timely and accurate manner) may be straightforward given that the task assignment system <NUM> can readily access information and/or controls used to monitor, detect, and recover from such errors. However, in a task assignment system with an external pairing system, error handling (e.g., monitoring, detecting, and/or recovering from errors) may not be as straightforward, as will be described next.

<FIG> shows a block diagram of a task assignment system <NUM> with an external pairing system <NUM> according to embodiments of the present disclosure. In the task assignment system <NUM>, a switch <NUM> may route a plurality of tasks <NUM> to a plurality of agents <NUM>. The switch <NUM> may include routing hardware and software, or to one or more PBX or ACD routing components or other queuing or switching components for helping to route the plurality of tasks <NUM> among the plurality of agents <NUM>.

In the task assignment system <NUM>, an internal pairing system <NUM> may be communicatively coupled to the switch <NUM>. The internal pairing system <NUM> may be native to (or built in) the task assignment system <NUM> (i.e., "first-party") or may be provided by a third-party vendor. Typically, the internal pairing system <NUM> may implement traditional pairing strategies (e.g., FIFO or PBR) or some other pairing strategy that may be proprietary to the task assignment system <NUM>. However, the internal pairing system <NUM> may also be in the form of the pairing system <NUM>. The internal pairing system <NUM> may receive or otherwise retrieve information from the switch <NUM> about the agents <NUM> logged into the switch <NUM> and about the incoming tasks <NUM>.

In the task assignment system <NUM>, the external pairing system <NUM> may be communicatively coupled to the switch <NUM> via an interface <NUM>. The interface <NUM> may isolate the task assignment system <NUM> from the external pairing system <NUM> (e.g., for security purposes), and control information exchanged between the two systems. An example of the interface <NUM> may be a public or a private proprietary application programming interface (API) provided over a network (e.g., the Internet or a telecommunications network) (not shown).

Relative to the internal pairing system <NUM>, the external pairing system <NUM> may have access to less information associated with switch <NUM>, e.g., a limited subset of information that is selected and shared by the switch <NUM>. Similarly, switch <NUM> may have access to less information associated with the external pairing system <NUM> than the internal pairing system <NUM>. Moreover, relative to the internal pairing system <NUM>, the external pairing system <NUM> may have less control over the operation of switch <NUM>, and vice versa. Such information and/or control is generally sufficient for the external pairing system <NUM> to determine the task-agent pairing and convey the determined task-agent pairing to switch <NUM>. The external pairing system <NUM> may be provided by a third-party vendor and may be in the form of the pairing system <NUM> described above. The external pairing system <NUM> may provide a pairing strategy (e.g., BP) that improves the performance of the task assignment system <NUM> when compared to the pairing strategy (or strategies) of the internal pairing system <NUM>. The external pairing system <NUM> may also provide the same or a similar pairing strategy as that of the internal pairing system <NUM>.

In some examples, the external pairing system <NUM> may be configured to assign tasks and/or agents that are associated with one or more skills. Skills generally correspond to classifications of tasks and/or agents based on the subject matter or the field of expertise involved in handling the task. Examples of skills include, but are not limited to, language skills (e.g., Spanish, English, French), sales skills, customer retention skills, technical support skills, etc. The set of skills that the external pairing system <NUM> is configured to handle may be shared with task assignment system <NUM>, e.g., during a policy exchange, in a shared configuration file, or the like. In some embodiments, the task assignment system <NUM> may limit the sharing of information (e.g., information about new tasks and/or agents) with the external pairing system <NUM> to information pertaining to the set of skills that the external pairing system <NUM> is configured to handle. Other information (e.g., information pertaining to skills that the external pairing system <NUM> is not configured to handle) may be hidden from the external pairing system <NUM>.

The task assignment system <NUM> may operate under a shared control, in which the switch <NUM> may send route requests to either or both of the internal pairing system <NUM> and the external pairing system <NUM> to determine which task is to be routed to which agent. The shared control may be desirable, for example, when the internal pairing system <NUM> employs a traditional or proprietary pairing strategy (e.g., FIFO or PBR) that may not be provided by the external pairing system <NUM>, while the external pairing system <NUM> is used to provide a higher-performing pairing strategy (e.g., BP).

When the external pairing system <NUM> includes the same or a similar pairing strategy as that of the internal pairing system <NUM>, the task assignment system <NUM> may operate under full control such that the switch <NUM> sends all route requests to the external pairing system <NUM>. In other words, the external pairing system <NUM> has full control over determining every task-agent pairing. Under full control, at times, the external pairing system <NUM> may simulate/mimic the pairing strategy of the internal pairing system <NUM> (e.g., FIFO or PBR) and, at other times, employ a different pairing strategy (e.g., BP), and send its pairing recommendation to the switch <NUM> over the interface <NUM>. The switch <NUM> may then assign the tasks <NUM> to agents <NUM> based on the pairing recommendation. In some embodiments, shared control and full control may be a preconfigured setting in the task assignment system <NUM>. In other embodiments, the task assignment system <NUM> may switch between shared control and full control automatically during runtime or by receiving input from a task assignment system manager or operator. The task assignment system <NUM> may use a control flag to indicate whether a historical task was assigned by the internal pairing system <NUM> or the external pairing system <NUM>. The task assignment system <NUM> may share the control flag with the external pairing system <NUM> (e.g., for benchmarking purposes) over the interface <NUM>.

Under either shared control or full control, the task assignment system <NUM> may use a second flag-a benchmark flag-to indicate whether a task is an "ON" task or an "OFF" task. An ON task is a task designated to be assigned by the external pairing module <NUM> using a higher-performing pairing strategy (e.g., BP). An OFF task is a task designated to be assigned using a traditional pairing strategy (e.g., FIFO or PBR) by either the internal pairing module <NUM> or the external pairing module <NUM>. When operating in shared control, the task assignment system <NUM> (or the switch <NUM>) may determine which of the tasks <NUM> should be ON or OFF. In full control, the task assignment <NUM> may either mark tasks as ON or OFF prior to sending route requests to the external pairing system <NUM> or send the route requests to the external pairing system <NUM> and allow the external pairing system <NUM> to determine which of the task should be treated as ON or OFF. The determination of the whether a task should be ON or OFF may be based on one or more predetermined schemes or an agreement between the task assignment system <NUM> and the external pairing system <NUM>.

In some examples, the benchmark flag may also be used to indicate that a historical task was paired to an agent by the internal pairing system <NUM> when the task should have been paired by the external pairing system <NUM> (i.e., ON tasks under shared control, or both ON and OFF tasks under full control). In these situations, the benchmark flag may be set to a third value, e.g., "default" instead of "ON" or "OFF"). Historical task assignments flagged as "Default" may be excluded from benchmarking calculations in some embodiments given that such assignments may have been due to unintentional errors or failures in the task assignment system <NUM>.

The task assignment system <NUM> is illustrated as having a single queue with the single switch <NUM> for simplicity. The task assignment system <NUM> could include additional queues with corresponding switches, in which case, either each switch could be communicatively coupled to the internal pairing system <NUM> and the external pairing system <NUM>, or there could be an internal pairing system and an external pairing system for each switch. In some embodiments, one or more queues may be configured as skill queues, each of which are associated with one or more skills. The task assignment system <NUM> may add tasks and/or agents associated with one or more skills to a matching skill queue. Other queues may be configured as general queues that handle any type of task and/or agent.

In some embodiments, one or more queues of the task assignment system <NUM> may be hidden from the external pairing system <NUM>. That is, a limited amount of information, or no information, associated with tasks and/or agents that is stored in a hidden queue may be shared with external pairing system <NUM>. For example, a skill queue may be hidden from external pairing system <NUM> when the one or more skills of the skill queue are incompatible with the one or more skills that the external pairing system <NUM> is configured to handle (e.g., there is no overlap in the respective skill sets). Because the task assignment system does not share information about the skill queue with the external pairing system <NUM>, the external pairing system <NUM> may be unable to select pairing for tasks and/or agents that are stored in the skill queue.

<FIG> shows a flow diagram of an error handling method <NUM> for a task assignment system (e.g., task assignment system <NUM>) with an external pairing system (e.g., external pairing system <NUM>) according to embodiments of the present disclosure.

The error handling method <NUM> may begin at block <NUM>. At block <NUM>, a request for the external pairing system to select a first pairing between one or more tasks awaiting assignment and one or more agents available for assignment (e.g., a pairing request, a routing request, etc.) is transmitted to the external pairing system over an API. In some embodiments, the first pairing is to be selected according to a first pairing strategy implemented by the external pairing system. For example, the first pairing strategy may be the BP strategy, e.g., when the task assignment system is operating in the full control mode, or either the BP strategy or a traditional pairing strategy, such as FIFO or PBR, e.g., when the task assignment system is operating in shared control mode. Various information may be transmitted to the external pairing system to enable the external pairing system to select the first pairing, such as information that identifies the one or more tasks and the one or more agents, control flags, or the like. Under normal conditions, the transmitted request may be received by the external pairing system. However, due to transmission errors (e.g., network faults) or other types of errors, the request may fail to reach the external pairing system.

At block <NUM>, a timeout window to wait for the external pairing system to provide a response that identifies the first pairing is determined. For example, a timer may be set for a predetermined amount of time corresponding to the timeout window upon transmitting the request at block <NUM>. In general, the duration of the timeout window may be selected to provide enough time for the external pairing system to respond under normal conditions (e.g., accounting for routine transmission delays and latency) without timing out. In some examples, the duration of the timeout window may be fixed or flexible. For example, the duration of the timeout window may depend on dynamic network conditions, the location of the external pairing system relative to the task assignment system, the average latency for communications between the task assignment system and the external pairing system, the complexity of the request, or the like.

At block <NUM>, an expiration of the timeout window without receiving the response from the external pairing system is detected. For example, a timer set at block <NUM> may time out before the response is received. The timeout window may expire after an initial duration determined at block <NUM>, or after an extended duration in response to the timeout window being extended during the initial timeout window. For example, the timeout window may be extended when, during the initial timeout window, an extension request that includes an instruction to extend the timeout window is received from the external pairing system. Illustratively, the extension request may be received when the current state of the task assignment system (e.g., the number of permutations between tasks and agents, the environment (L1, L2, or l3), or the like) would result in suboptimal performance of the first pairing strategy. In such cases, the external pairing system may determine to postpone making a pairing selection until the state of the task assignment system develops into the preferred state (e.g., by waiting for more tasks and/or agents to become available, waiting for the environment to develop into an L3 environment, or the like). Illustrative processes for postponing the selection of pairings are described in detail in, e.g., <CIT>. However, the number of extension requests that may be granted and/or the total duration of the extended timeout window may be limited. Accordingly, the timeout window may expire at block <NUM> despite the duration of the timeout window being extended.

When the timeout window lapses without receiving a response from the external pairing system, it is determined that an error or fault occurred. For example, it may be determined that the request or the response encountered an error in transmission, the external pairing system may be experiencing an outage or otherwise be inaccessible, the format of the request or the response may be invalid or incompatible with the API, the external pairing system or the task assignment system may be misconfigured, or the like. When it is determined that an error or fault has occurred, one or more remedial actions may be taken. Illustrative examples of remedial actions can include, but are not limited to, resending the pairing request (e.g., returning to block <NUM>), notifying an operator of the task assignment system and/or the external pairing system that an error has been detected, logging system information to assist with debugging the error, or the like. Moreover, to limit or prevent the formation of a backlog of tasks and/or agents awaiting assignment, the error handling method <NUM> may proceed to block <NUM> for selecting a pairing for the task using the internal pairing system, thereby providing a failover mechanism to address the detected misconfiguration.

At block <NUM>, in response to detecting the expiration of the timeout window, a second pairing between the one or more tasks and the one or more agents is selected. The second pairing may be selected according to a second pairing strategy. For example, the second pairing strategy may be one of FIFO and PBR. The second pairing strategy is implemented by an internal pairing system (e.g., internal pairing system <NUM>), or by a backup external pairing system. By executing the second pairing strategy using the internal pairing system, the formation of a backlog of tasks and/or agents awaiting assignment may be limited or prevented, even when the error associated with the external pairing system remains unresolved. This failover mechanism can be used as the sole remedial action, or it can also be used in conjunction with other remedial actions, used after other remedial actions have been tried but are ineffective, or the like.

In some embodiments, the one or more tasks awaiting assignment may be labeled to indicate which pairing strategy should be used to pair to the task. For example, the label can include a benchmarking flag. Illustratively, an ON task (e.g., a task for which the corresponding label is ON) may designate a task that is to be paired according to the first pairing strategy. An OFF task (e.g., a task for which the corresponding label is OFF) may designate a task that is to be paired according to the second pairing strategy. In full control mode or shared control mode, the external pairing system may assume responsibility for pairing ON tasks with agents. However, in response to the expiration of the timeout window being detected, the task assignment system may transition from a first mode (e.g., the full control mode or the shared control mode) to a second mode (e.g., an error response mode). In the error response mode, the label associated with the one or more tasks (e.g., the ON flag associated with ON tasks) may be overridden. In this manner, the internal pairing system of the task assignment system, rather than the external pairing system, may assume responsibility for pairing ON tasks with agents. In some embodiments, to limit interference with subsequent benchmarking calculations, the label may be changed to a different value (e.g., the benchmarking flag may be set to a "default" flag) to indicate that tasks that are assigned in the error recovery mode should not later be used in the external pairing system's benchmarking calculations, even if they were originally designated as ON tasks.

<FIG> shows a flow diagram of a misconfiguration handling method <NUM> for a task assignment system (e.g., task assignment system <NUM>) with an external pairing system (e.g., external pairing system <NUM>) according to the invention. The misconfiguration handling method <NUM> is performed in conjunction with the error handling method <NUM>. Whereas the error handling method <NUM> provides techniques for detecting and responding to errors in which the external pairing system fails to respond to a pairing request in the expected manner, the misconfiguration handling method <NUM> provides techniques for detecting and responding to errors in which the external pairing system may not even be asked to suggest a pairing. The latter scenario may arise due to, e.g., misconfigurations in which tasks that are designated to be paired by the external pairing system are inadvertently hidden from the external pairing system.

The misconfiguration handling method <NUM> begins at block <NUM>. At block <NUM>, one or more configuration parameters associated with the external pairing system are accessed. The one or more configuration parameters may include information that identifies a hidden queue of the task assignment system that is hidden from the external pairing system. When a queue is a hidden queue, the external pairing system may not be sent updated information about tasks that are stored in or added to the hidden queue, and/or may not be sent requests to select a pairing for tasks that are stored in or added to the hidden queue. In some examples, a queue may be hidden when the external pairing system is associated with one or more first skills, and the queue is a skill queue associated with a second skill that is not among the one or more first skills. Because the respective skill sets are mismatched or incompatible, the external pairing system is not equipped to handle the pairing of tasks or agents in the skill queue, so information associated with the skill queue may be hidden from the external pairing system. In some embodiments, the one or more configuration parameters may be stored in a configuration file. The one or more configuration parameters may be associated with a policy exchange between the task assignment system and the external pairing system, where the policy includes one or more rules for managing interactions between the task assignment system and the external pairing system.

At block <NUM>, it is determined that the hidden queue includes one or more tasks that are designated to be paired by the external pairing system. For example, the one or more tasks may be labeled to indicate that the one or more tasks are to be paired according to a first pairing strategy implemented by the external pairing system (e.g., a task may include an ON flag indicating that the task is an ON task). Accordingly, when the task assignment system is operating in full control mode or shared control mode, the external pairing system assumes responsibility for pairing the one or more tasks according to the first pairing strategy. However, the configuration parameters accessed at block <NUM> indicate that the queue containing the one or more tasks is hidden from the external pairing system. Due to this inconsistency, in the absence of intervention, the one or more tasks may wait in the hidden queue indefinitely. Consequently, detecting that the hidden queue includes tasks designated to be paired by the external pairing system may trigger one or more interventions to be taken. For example, to limit or prevent the formation of a backlog of tasks and/or agents awaiting assignment, the misconfiguration handling method <NUM> may proceed to block <NUM> for selecting a pairing for the task using the internal pairing system, thereby providing a failover mechanism to address the detected misconfiguration.

At block <NUM>, in response to determining that the hidden queue includes one or more tasks that are designated to be paired by the external pairing system, a pairing between the one or more tasks and the one or more agents is selected using an internal pairing system (e.g., internal pairing system <NUM>). In some embodiments, block <NUM> may generally correspond to block <NUM> of error handling method <NUM>. For example, the pairing may be selected according to a second pairing strategy implemented by the internal pairing system that is different from the first strategy implemented by the external pairing system. For example, the second pairing strategy may be one of FIFO and PBR. When the tasks include a label (e.g., an ON flag) that indicates that they are designated to be paired by the external pairing system, the label may be overridden. By executing the second pairing strategy using the internal pairing system, the formation of a backlog of tasks and/or agents awaiting assignment may be limited or prevented, even when the misconfiguration of the task assignment system and/or the external pairing system remains unresolved.

<FIG> shows a flow diagram of a misconfiguration handling method <NUM> for a task assignment system (e.g., task assignment system <NUM>) with an external pairing system (e.g., external pairing system <NUM>) according to embodiments of the present disclosure. Relative to misconfiguration handling method <NUM>, misconfiguration handling <NUM> provides an alternative process for detecting misconfigurations in which a hidden queue includes one or more tasks that are designated to be paired by the external pairing system. This alternative process may be performed in conjunction with, or independently of, misconfiguration handling method <NUM>. Whereas misconfiguration handling method <NUM> detects misconfigurations by analyzing configuration parameters, misconfiguration handling method <NUM> detects misconfigurations using timeout windows, as discussed below.

At block <NUM>, a timeout window to wait for a task to be assigned to an agent is determined, the task being stored in a queue. In some embodiments, a timer may be set for a predetermined amount of time upon adding the task to the queue. Accordingly, the timeout window may correspond to a maximum amount of time that the task can wait in a queue before triggering an intervention from the task assignment system. In general, the duration of the timeout window may be selected to provide enough time for the task to be assigned to an agent under normal conditions (e.g., accounting for routine waiting times) without timing out. In some embodiments, the duration of the timeout window may be fixed or flexible. For example, the duration of the timeout window may depend on the number of tasks in the queue, the number of agents available for assignment, various statistics associated with the average amount of time it takes for tasks to be assigned, the complexity of the task, or the like.

At block <NUM>, an expiration of the timeout window is detected. For example, a timer set at block <NUM> may time out before the task is assigned. The timeout window may expire after an initial duration determined at block <NUM>, or after an extended duration in response to the timeout window being extended during the initial timeout window. For example, the timeout window may be extended when, during the initial timeout window, an extension request that includes an instruction to extend the timeout window is received from the external pairing system. When the timeout window lapses without the task being assigned, it may be determined that an error or fault occurred, or that the task assignment system and/or the external pairing system are misconfigured. For example, it may be determined that the task is designated to be paired by the external pairing system (e.g., the task is an ON task), but the queue that the task was placed into is a hidden queue (e.g., the queue is a skill queue associated with a skill that is not among the skills that the external pairing system is configured to handle). Accordingly, to limit or prevent the formation of a backlog of tasks and/or agents awaiting assignment, the misconfiguration handling method <NUM> may proceed to block <NUM> for selecting a pairing for the task using the internal pairing system, thereby providing a failover mechanism to address the detected misconfiguration.

At block <NUM>, in response to detecting the expiration of the timeout window, a pairing between the one or more tasks and the one or more agents may be selected using an internal pairing system (e.g., internal pairing system <NUM>). In some examples, block <NUM> may generally correspond to block <NUM> of error handling method <NUM>. For example, the pairing may be selected according to a second pairing strategy implemented by the internal pairing system that is different from the first strategy implemented by the external pairing system. For example, the second pairing strategy may be one of FIFO and PBR. When the tasks include a label (e.g., an ON flag) that indicates that they are designated to be paired by the external pairing system, the label may be overridden. By executing the second pairing strategy using the internal pairing system, the formation of a backlog of tasks and/or agents awaiting assignment may be limited or prevented, even when the misconfiguration of the task assignment system and/or the external pairing system remains unresolved.

Although the forgoing description of misconfiguration handling methods <NUM> and <NUM> refers to the pairing of tasks, the techniques are equally applicable to the pairing of agents (e.g., the hidden queue may include agents available for assignment rather than, or in addition to, tasks awaiting assignment).

At this point it should be noted that task assignment in accordance with the present disclosure as described above may involve the processing of input data and the generation of output data to some extent. This input data processing and output data generation may be implemented in hardware or software. For example, specific electronic components may be employed in a behavioral pairing module or similar or related circuitry for implementing the functions associated with task assignment in accordance with the present disclosure as described above. Alternatively, one or more processors operating in accordance with instructions may implement the functions associated with task assignment in accordance with the present disclosure as described above. If such is the case, it is within the scope of the present disclosure that such instructions may be stored on one or more non-transitory processor readable storage media (e.g., a magnetic disk or other storage medium), or transmitted to one or more processors via one or more signals embodied in one or more carrier waves.

Claim 1:
A method for error handling in a task assignment system (<NUM>) with an external pairing system (<NUM>), the method comprising:
transmitting (<NUM>), by at least one computer processor communicatively coupled to and configured to operate in the task assignment system, to the external pairing system over an application programming interface, a request for the external pairing system to select a first pairing between one or more tasks awaiting assignment and one or more agents available for assignment, the first pairing to be selected according to a first pairing strategy;
determining (<NUM>), by the at least one computer processor, a timeout window to wait for the external pairing system to provide a response that identifies the first pairing;
detecting (<NUM>), by the at least one computer processor, an expiration of the timeout window without receiving the response;
in response to detecting the expiration of the timeout window (<NUM>), accessing (<NUM>), by the at least one computer processor, one or more configuration parameters associated with the external pairing system, the one or more configuration parameters identifying a hidden queue of the task assignment system that is hidden from the external pairing system such that information stored in the hidden queue is not shared with the external pairing system;
determining (<NUM>), by the at least one computer processor, that the hidden queue includes one or more second tasks that are designated to be paired by the external pairing system; and
in response to determining that the hidden queue includes the one or more second tasks that are designated to be paired by the external pairing system (<NUM>), selecting (<NUM>), by the at least one computer processor, a second pairing between the one or more tasks and the one or more agents, the second pairing being selected according to a second pairing strategy.