Pacing in knowledge worker engagement
A method for mapping ready agents to incoming transactions has steps for (a) placing incoming transactions in a first queue managed by software executing from a machine-readable medium on a computerized appliance; (b) issuing a determined number of invitations in a period of time to agents known to be available to consider an invitation to interact with an incoming transaction; (c) placing identification of ready agents, who have accepted an invitation to interact, in a second queue managed by the software; (d) mapping transactions from the first queue to agents from the second queue; (e) monitoring changes in state of both the first and the second queues in the time period; and (f) adjusting determined number of invitations in step (b) in a manner to drive a chosen system performance metric toward a desired target value.
1. A method for mapping contact center agents to incoming transactions, the method comprising:
storing, by a processor, data for incoming transactions in a first data structure;
issuing, by the processor, a preset number of invitations for a first period having a predetermined duration of time to contact center agents identified to be available for being queued, along with a plurality of other agents, to interact with an incoming transaction from among the incoming transactions;
identifying, by the processor, one or more of the contact center agents accepting the invitation for being queued;
storing, by the processor, identification data of the one or more agents identified as accepting the invitation for being queued, in a second data structure;
mapping, by the processor, one of the transactions associated with the data in the first data structure to one of the one or more agents identified via the identification data in the second data structure;
transmitting, by the processor, a signal to a switch for routing the one of the transactions to an electronic device associated with the mapped agent;
removing, by the processor, the identification data of the mapped agent from the second data structure;
monitoring, by the processor, changes in both the first and the second data structures during the first period having the predetermined duration of time;
calculating, by the processor, a probability value for any given one of the contact center agents to accept a future invitation during a second period having the predetermined duration of time;
adjusting, by the processor, the preset number of invitations for driving a system performance metric toward a desired target value based in part on the probability value for the any given one of the contact center agents to accept the future invitation during the second period and based in part on the changes in both the first and the second data structures during the first period; and
after adjusting the preset number of invitations, issuing, by the processor, the preset number of invitations for the second period having the predetermined duration of time.
2. The method of claim 1 , wherein the system performance metric is the difference between the number of one or more agents identified as accepting the invitation to interact and the number of incoming transactions having stored data in the first data structure, and the desired value is zero.
3. The method of claim 2 , wherein an algorithm determines the number of invitations to issue, and the algorithm incorporates a known average rate of transactions received in the particular period of time.
4. The method of claim 2 , wherein an algorithm determines the number of invitation to issue, and operates without a prior knowledge of an average rate of transactions received in the particular period of time.
5. The method of claim 2 , wherein the system performance metric is a rate of transactions abandoned in the particular period of time, and an algorithm determines the number of invitations to issue to maintain an average rate of transactions abandoned at a preselected value.
6. The method of claim 1 , wherein the particular period of time is a fixed, repeating period.
7. The method of claim 1 , wherein the particular period of time is determined by occurrence of one or more system events.
8. The method of claim 1 , further comprising removing the data associated with the mapped transaction from the first data structure.
9. A system for mapping contact center agents to incoming transactions, the system comprising:
a switch configured to receive a plurality of communications for routing to one or more communication devices;
a processor; and
a memory, wherein the memory has stored thereon instructions that, when executed by the processor, cause the processor to:
store data for incoming transactions in a first data structure;
issue a preset number of invitations for a first period having a predetermined duration of time to contact center agents identified to be available for being queued, along with a plurality of other agents, to interact with an incoming transaction from among the incoming interactings;
identify one or more of the contact center agents accepting the invitation for being queued;
store identification data of the one or more agents identified as accepting the invitation, for being queued, in a second data structure;
map one of the transactions associated with the data in the first data structure to one of the one or more agents identified via the identification data in the second data structure;
transmit a signal to the switch for routing the one of the transactions to an electronic device associated with the mapped agent;
remove the identification data of the mapped agent from the second data structure;
monitor changes in both the first and the second data structures during the first period having the predetermined duration of time;
calculate a probability value for any given one of the contact center agents to accept a future invitation during a second period having the predetermined duration of time;
adjust the preset number of invitations for driving a system performance metric toward a desired target value based in part on the probability value for the any given one of the contact center agents to accept the future invitation during the second period and based in part on the changes in both the first and the second data structures during the first period; and
after adjusting the preset number of invitations, issue the preset number of invitations for a second period having the predetermined duration of time.
10. The system of claim 9 , wherein the system performance metric is the difference between the number of one or more agents identified as accepting the invitation to interact and the number of incoming transactions having stored data in the first data structure, and the desired value is zero.
11. The system of claim 10 , wherein an algorithm determines the number of invitations to issue, and the algorithm incorporates a known average rate of transactions received in the particular period of time.
12. The system of claim 10 , wherein an algorithm determines the number of invitation to issue, and operates without a prior knowledge of an average rate of transactions received in the particular period of time.
13. The system of claim 9 , wherein the system performance metric is an average rate of transactions abandoned in the particular period of time, and an algorithm determines the number of invitations to issue to maintain the average rate of transactions abandoned at a preselected value.
14. The system of claim 9 , wherein the particular period of time is a fixed, repeating period.
15. The system of claim 9 , wherein the particular period of time is determined by occurrence of one or more system events.
16. The system of claim 9 , wherein the executed instructions stored on the memory further cause the processor to remove the data associated with the mapped transaction from the first data structure.
17. The method of claim 1 , wherein the system performance metric comprises an amount of idle time for agents whose identification data is stored in the second data structure.
18. The system of claim 9 , wherein the system performance metric comprises an amount of idle time for agents whose identification data is stored in the second data structure.