Multi-tasking tracking agent

Abstract

The present invention is directed to a system for tracking a contact center operation. The system includes a tracking agent 232 operable to (a) receive a notification indicating a change in agent focus from a first work item to a second work item; (b) determine whether the first work item involves a communication medium different from the second work item; and (c) when the first work item involves a communication medium different from the second work item, cause termination of a timer with respect to the servicing of the first work item and initiation of a timer with respect to the servicing of the second work item. The first and second work items are concurrently assigned for servicing to the agent.

Description

FIELD OF THE INVENTION

The present invention is directed generally to servicing a contactor in a contact center and specifically to monitoring the performance of contact center resources.

BACKGROUND OF THE INVENTION

Contact centers, such as Automatic Call Distribution or ACD systems, are employed by many enterprises to service customer contacts. A typical contact center includes a switch and/or server to receive and route incoming packet-switched and/or circuit-switched contacts and one or more resources, such as human agents and automated resources (e.g., Interactive Voice Response (IVR) units), to service the incoming contacts. Contact centers distribute contacts, whether inbound or outbound, for servicing to any suitable resource according to predefined criteria. In many existing systems, the criteria for servicing the contact from the moment that the contact center becomes aware of the contact until the contact is connected to an agent are customer-specifiable (i.e., programmable by the operator of the contact center), via a capability called vectoring. Normally in present-day ACDs when the ACD system's controller detects that an agent has become available to handle a contact, the controller identifies all predefined contact-handling skills of the agent (usually in some order of priority) and delivers to the agent the highest-priority oldest contact that matches the agent's highest-priority skill. Generally, the only condition that results in a contact not being delivered to an available agent is that there are no contacts waiting to be handled.

An important factor in administering call distribution algorithms and rewarding agents based on performance is accurate tracking and reporting of agent performance. In monitoring agent performance, two areas are particularly troublesome. First, how should one track the previewing of work that is new or has been deferred while deciding what to do next? As will be appreciated, when an agent previews a work item, he or she is typically provided with a summary or condensed description of one or more work items (which can include, for example, contactor identity, nature or subject of the contact, arrival time, type of media, and intended recipient) and, based on the description, decides whether he or she is qualified or otherwise able to service the contact and/or prepares himself or herself to service the contact. Consideration must be given to performance when scrolling through a list of work items, like email, in a preview mode prior to selecting a work item. Second, how should one track work time when it appears that the agent is working on more than one thing simultaneously? For example, an agent is handling a first contact on a first communication medium (e.g., a live voice contact) for a first customer while at the same time handling a second contact on a second communication medium (e.g., an email or Web chat) for a second customer. More specifically, the agent does not have the first or second contact on hold while intermittently working on or wrapping up the other contact (completing the after call work). It is desirable to track accurately the agent's time for each work item. Inaccurate tracking can lead to nonsensical results, such as showing agents being present for more time than they are actually present and/or showing agent occupancy levels greater than 100%. Such erroneous results can propagate into significant errors in administering the call distribution algorithm. Moreover in some applications, the contact center may wish to discourage multi-tasking due to a concomitant decrease in the quality of service.

While tracking voice contacts is well established and accurate in the industry, the tracking of other channels or communication media (e.g., email, chat) is neither established nor accurate. For example, an agent using Avaya Inc.'s Interaction Center™ can read an entire email or web chat by previewing it and have that time counted as idle time or against another work item. It is only when the agent replies (because it requires explicit input) that accurate accounting for that email or web chat begins. Since it is impossible to know what work item an agent is thinking about without explicit agent input, multi-tasking tracking has not been done effectively. For example, the agent can be listening to a caller while at the same time concentrating on reading an email or web chat.

SUMMARY OF THE INVENTION

These and other needs are addressed by the various embodiments and configurations of the present invention. The invention is directed generally to a contact center that tracks previewing and/or multi-tasking operations for improved contact center efficiency.

In a first embodiment of the present invention, a method for tracking a contact center operation is provided. The method includes the steps:

(a) receiving a notification indicating a change in agent focus from a first work item to a second work item;

(b) determining whether the first work item involves a communication medium different from the communication medium of the second work item; and

(c) when the first work item involves a communication medium different from the communication medium of the second work item, terminating a timer with respect to the servicing of the first work item and initiating a timer with respect to the servicing of the second work item. Because the agent is multi-tasking, the first and second work items are concurrently assigned for servicing to the agent. As will be appreciated, multi-tasking, by its very nature, requires the first and second work items to be carried by different communication media.

The notification commonly indicates that (i) the agent has switched from servicing the first work item, possibly involving a first communication medium, to servicing a second work item, possibly involving a different second communication medium, and/or (ii) the agent has switched from servicing the first work item to previewing of the second work item. The first and second communication media, for example, can each be a set of one or more of circuit-switched voice, packet-switched voice, email, instant messaging, text chat, voice messages, faxes, and scanned documents.

The notification may involve the incidence or occurrence of a cursor marker and/or a voice marker while the agent is servicing the first work item. The cursor marker indicates a cursor location and/or activity. For example, the location of the cursor marker can be in a specific window, and/or the activity of the cursor can be typing, clicking on an icon, idle, and the like. The voice marker indicates an amount and/or type of voice energy being transmitted and/or received by the agent while the agent is servicing the first work item. The amount and type of voice energy can be monitored by known techniques, for example, to identify auto-acknowledge responses, music on hold, active discussion between two endpoints, silence on one or both voice paths, key word recognition, and the like.

In response to the receipt of a notification, the agent's GUI and/or TUI can be returned to a previous configuration associated with the second work item. For example, the change to the GUI can be returning the GUI to a previous configuration, such as displaying of information previously displayed to the agent.

A counter can be used to track the number of times during a selected time period that the agent is engaged in a specified type of activity, such as previewing, and/or the number of times the agent returns to a selected work item.

The present invention can have a number of advantages over the prior art. First, the present invention can permit accurate tracking of multi-tasking and previewing activities. This capability will allow contact center operators to realize significant productivity increases that multi-tasking can enable and permit agents able to engage successfully in multi-tasking to be recognized and rewarded. Second, the present invention can permit contact centers to control selected types of multi-tasking to avoid potential decreases in the quality of customer service.

These and other advantages will be apparent from the disclosure of the invention(s) contained herein.

The above-described embodiments and configurations are neither complete nor exhaustive. As will be appreciated, other embodiments of the invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a contact center according to an embodiment of the present invention;

FIG. 2 is a block diagram of a server according to an embodiment of the present invention;

FIG. 3 is a flow chart depicting an operational embodiment of the multi-tasking tracking agent; and

FIG. 4 is a flow chart depicting an operational embodiment of the database updating agent.

DETAILED DESCRIPTION

The invention will be illustrated below in conjunction with an exemplary communication system. Although well suited for use with, e.g., a system having an ACD or other similar contact processing switch, the invention is not limited to use with any particular type of communication system switch or configuration of system elements. Those skilled in the art will recognize that the disclosed techniques may be used in any communication application in which it is desirable to provide improved contact processing.

FIG. 1 shows an illustrative embodiment of the present invention. A contact center 100 comprises a central server 110, a set of data stores or databases 114 containing contact or customer related information and other information that can enhance the value and efficiency of the contact, and a plurality of servers, namely a voice mail server 118, an Interactive Voice Response unit or IVR 122, and other servers 126, a switch 130, a plurality of working agents operating packet-switched (first) telecommunication devices 134-1 to N (such as computer work stations or personal computers), and/or circuit-switched (second) telecommunication devices 138-1 to M, all interconnected by a local area network LAN (or wide area network WAN) 142. The servers can be connected via optional communication lines 146 to the switch 130. As will be appreciated, the other servers 126 can also include a scanner (which is normally not connected to the switch 130 or Web server), VoIP software, video contact software, voice messaging software, an IP voice server, a fax server, a web server, and an email server) and the like. The switch 130 is connected via a plurality of trunks 150 to the Public Switch Telecommunication Network or PSTN 154 and via link(s) 152 to the second telecommunication devices 138-1 to M. A gateway 158 is positioned between the server 110 and the packet-switched network 162 to process communications passing between the server 110 and the network 162.

The term “switch” or “server” as used herein should be understood to include a PBX, an ACD, an enterprise switch, or other type of telecommunications system switch or server, as well as other types of processor-based communication control devices such as media servers, computers, adjuncts, etc.

Referring to FIG. 2, one possible configuration of the server 110 is depicted. The server 110 is in communication with a plurality of customer communication lines 200a-y (which can be one or more trunks, phone lines, etc.) and agent communication line 204 (which can be a voice-and-data transmission line such as LAN 142 and/or a circuit switched voice line 140). The server 110 can include Avaya Inc.'s Operational Analyst™ or OA 224 with On-Line Analytical Processing or OLAP technology or a Call Management System or CMS 228 that gathers contact records and contact-center statistics for use in generating contact-center reports. OA and CMS will hereinafter be referred to jointly as CMS 228.

The switch 130 and/or server 110 can be any architecture for directing contacts to one or more telecommunication devices. Illustratively, the switch and/or server can be a modified form of the subscriber-premises equipment disclosed in U.S. Pat. Nos. 6,192,122; 6,173,053; 6,163,607; 5,982,873; 5,905,793; 5,828,747; and 5,206,903, all of which are incorporated herein by this reference; Avaya Inc.'s Definity™ Private-Branch Exchange (PBX)-based ACD system; MultiVantage™ PBX, CRM Central 2000 Server™, Communication Manager™, S8300™ media server, and/or Avaya Interaction Center™. Typically, the switch/server is a stored-program-controlled system that conventionally includes interfaces to external communication links, a communications switching fabric, service circuits (e.g., tone generators, announcement circuits, etc.), memory for storing control programs and data, and a processor (i.e., a computer) for executing the stored control programs to control the interfaces and the fabric and to provide automatic contact-distribution functionality. The switch and/or server typically include a network interface card (not shown) to provide services to the serviced telecommunication devices. Other types of known switches and servers are well known in the art and therefore not described in detail herein.

Referring to FIG. 2, included among the data stored in the server 110 is a set of contact queues 208a-n and a separate set of agent queues 212a-n. Each contact queue 208a-n corresponds to a different set of agent skills, as does each agent queue 212a-n. Conventionally, contacts are prioritized and either are enqueued in individual ones of the contact queues 208a-n in their order of priority or are enqueued in different ones of a plurality of contact queues that correspond to a different priority. Likewise, each agent's skills are prioritized according to his or her level of expertise in that skill, and either agents are enqueued in individual ones of agent queues 212a-n in their order of expertise level or are enqueued in different ones of a plurality of agent queues 212a-n that correspond to a skill and each one of which corresponds to a different expertise level. Included among the control programs in the server 110 is a contact vector 216. Contacts incoming to the contact center are assigned by contact vector 216 to different contact queues 208a-n based upon a number of predetermined criteria, including customer identity, customer needs, contact center needs, current contact center queue lengths, customer value, and the agent skill that is required for the proper handling of the contact. Agents who are available for handling contacts are assigned to agent queues 212a-n based upon the skills that they possess. An agent may have multiple skills, and hence may be assigned to multiple agent queues 212a-n simultaneously. Furthermore, an agent may have different levels of skill expertise (e.g., skill levels 1-N in one configuration or merely primary skills and secondary skills in another configuration), and hence may be assigned to different agent queues 212a-n at different expertise levels. Call vectoring, one type of contact routing, is described in DEFINITY Communications System Generic 3 Call Vectoring/Expert Agent Selection (EAS) Guide, AT&T publication no. 555-230-520 (Issue 3, Nov. 1993). Skills-based ACD is described in further detail in U.S. Pat. Nos. 6,173,053 and 5,206,903.

Referring to FIG. 1, the gateway 158 can be Avaya Inc.'s, G700 Media Gateway™ and may be implemented as hardware such as via an adjunct processor (as shown) or as a chip in the server.

The first telecommunication devices 134-1, . . . 134-N are packet-switched and can include, for example, IP hardphones such as the Avaya Inc.'s, 4600 Series IP Phones™, IP softphones such as Avaya Inc.'s, IP Softphone™, Personal Digital Assistants or PDAs, Personal Computers or PCs, laptops, packet-based H.320 video phones and conferencing units, packet-based voice messaging and response units, and packet-based traditional computer telephony adjuncts.

The second telecommunication devices 138-1, . . . 138-M are circuit-switched. Each of the telecommunication devices 138-1, . . . 138-M corresponds to one of a set of internal extensions Ext1, . . . ExtM, respectively. These extensions are referred to herein as “internal” in that they are extensions within the premises that are directly serviced by the switch. More particularly, these extensions correspond to conventional telecommunication device endpoints serviced by the switch/server, and the switch/server can direct incoming contacts to and receive outgoing contacts from these extensions in a conventional manner. The second telecommunication devices can include, for example, wired and wireless telephones, PDAs, H.320 video phones and conferencing units, voice messaging and response units, and traditional computer telephony adjuncts.

It should be noted that the invention does not require any particular type of information transport medium between switch or server and first and second telecommunication devices, i.e., the invention maybe implemented with any desired type of transport medium as well as combinations of different types of transport medium.

The packet-switched network 162 can be any data and/or distributed processing network, such as the Internet. The network 162 typically includes proxies (not shown), registrars (not shown), and routers (not shown) for managing packet flows.

The packet-switched network 162 is in communication with an external first telecommunication device 174 via a gateway 178, and the circuit-switched network 154 with an external second telecommunication device 180. These telecommunication devices are referred to as “external” in that they are not directly supported as telecommunication device endpoints by the switch or server. The telecommunication devices 174 and 180 are an example of devices more generally referred to herein as “external endpoints.”

In a preferred configuration, the server 110, network 162, and first telecommunication devices 134 are Session Initiation Protocol or SIP compatible and can include interfaces for various other protocols such as the Lightweight Directory Access Protocol or LDAP, H.248, H.323, Simple Mail Transfer Protocol or SMTP, IMAP4, ISDN, E1/T1, and analog line or trunk.

It should be emphasized that the configuration of the switch, server, user telecommunication devices, and other elements as shown in FIG. 1 is for purposes of illustration only and should not be construed as limiting the invention to any particular arrangement of elements.

As will be appreciated, the central server 110 is notified via LAN 142 of an incoming contact by the telecommunications component (e.g., switch 130, fax server, email server, web server, and/or other server) receiving the incoming contact. The incoming contact is held by the receiving telecommunications component until the server 110 forwards instructions to the component to forward or route the contact to a specific contact center resource, such as the IVR unit 122, the voice mail server 118, and/or first or second telecommunication device 134, 138 associated with a selected agent. The server 110 distributes and connects these contacts to telecommunication devices of available agents based on the predetermined criteria noted above. When the central server 110 forwards a voice contact (or first work item) to an agent, the central server 110 also forwards customer-related information from databases 114 to the agent's computer work station for viewing (such as by a pop-up display) to permit the agent to better serve the customer. When multi-tasking is desired, the central server 110 can forward a second work item on other media types (e.g., email, instant messaging, text or Web chat, and the like) to be handled simultaneously with the first work item. Depending on the contact center configuration, the central server may forward a list of work items to an available agent to preview before forwarding the contact itself and the data associated therewith to the agent. The agents process the contacts or work items sent to them by the central server 110. This embodiment is particularly suited for a Customer Relationship Management (CRM) environment in which customers are permitted to use any medium to contact a business. In a CRM environment, both real-time and non-real-time contacts must be handled and distributed with equal efficiency and effectiveness.

According to the invention, included among the programs executing on the server 110 are an agent and contact selector 220, multi-tasking tracking agent 232, and database updating agent 236. The selector 220 and tracking agent 232 are stored either in the main memory or in a peripheral memory (e.g., disk, CD ROM, etc.) or some other computer-readable medium of the center 100. The selector 220 and agent 232 collectively effect an assignment between available contacts and available agents in a way that tends to maximize contact center efficiency. The selector 220 uses predefined criteria, particularly the agent profile, in selecting an appropriate agent to service the contact. The tracking agent 232, by a combination of limiting agent work handling operations that cause work tracking ambiguity and by taking advantage of various markers or indicators available from the agents, applications, and affected channels, accurately tracks agent previewing and multi-tasking activities. This information, along with other statistics gathered by the CMS 228, is used by the selector 220 in distributing available work items to available agents. The updating agent 236 is the interface to the database 114 that updates the database records, including agent and customer profiles, in response to update notifications received from other applications, including the tracking agent 232.

The agent and customer profiles are typically maintained and updated by a profile generator (not shown). Upon the completion of handling a contact, the generator collects selected metrics for the contact. These metrics include the skill involved in servicing the contact, the identifier of the servicing agent, the contact duration, the transaction or contact type (e.g., catalog sale, information request, complaint, etc.), the time-of-day, the result (e.g., the type of sale, the number of units sold, revenue generated, service ticket closure or escalation, the information provided, etc.), a self-rating of the servicing agent respecting the agent's proficiency in handling the contact, the rating of the customer of the agent's proficiency in handling the contact, the rating of another party, such as the agent's supervisor or another observer, of how the contact was serviced, whether the agent requested assistance, and whether the agent's training was completed, and stores the information in the database 114, such as CMS 228. The metrics over a selected period of time are typically stored under each profile. Each agent profile typically includes metrics associated with a plurality of contacts serviced by the agent for each agent skill, and each customer profile includes metrics associated with a plurality of contacts by the customer.

Returning again to the tracking agent 232, the tracking agent removes tracking ambiguity, for example, by restricting what can be done by the agent and requiring the agent to take explicit action by activating a work item before beginning to work on the item. The time to service the work item can be accurately monitored by monitoring such actions by the agent. For example, if the agent is not shown the body of the work item until he/she explicitly activates it, then the agent's time spent reading the body of the message will be tracked accurately. In a further example, when the agent is on a voice call (or first work item) and elects to work on a second work item in a different communication medium, such as email, instant message, and Web chat, the voice call is automatically put on hold or the outgoing voice communications channel (or talk path) from the agent to the customer is otherwise blocked or disabled (while permitting the agent to continue to receive voice communications from the customer) when the agent initiates work on the second work item. When the agent wishes to return to the first work item, he or she must remove the call from hold status or otherwise request the outgoing channel to be enabled for outgoing communications from the agent to the customer. The request (such as “line one please”) can be automatically generated when certain types (e.g., keywords) and/or levels of voice energy are provided by the agent for transmission to the customer over the talk path. In that event, the spoken voice energy is buffered until the talk path is reactivated or enabled and thereafter transmitted to the customer.

The tracking agent 232 can assume an agent is working on a second item rather than a first item when the agent spends more than a predetermined time in the second item. In particular, when the agent spends more than a predetermined threshold of time previewing a particular work item the tracking agent would treat that period of time plus any ensuing previewing time as time spent working on the previewed item. This threshold permits the agent to scroll through an email, for instance, and only when the agent stops to read the email does time tracking against the work item being previewed begin.

The tracking agent 232 can further monitor for markers or indicators to identify whether or not the customer is in work mode and what work item the agent is currently servicing. The markers include, for example, a cursor marker, a voice marker, and a video marker (e.g., particular movement).

The cursor marker indicates cursor (window) location and/or activity (e.g., typing, clicking on an icon, selecting a window, etc.). For example, when the cursor is located in a particular window and/or is active in that window the agent 232 can assume that the agent is working on a specific work item associated with the window or is not working (e.g., is in preview mode), depending on the information displayed in the window. Alternatively, engagement on a different work item can be detected implicitly in the application (e.g., receiving a request to preview a work list, movement through a work list, another work item is activated by clicking on an icon or window, or a new unrelated application is brought up by the agent by clicking on an icon).

The voice marker indicates the amount and type of voice energy being transmitted and/or received by the agent. A voice energy detector (not shown), such as a call classifier, can identify, on the one hand, when a particular speaker is engaged actively in a conversation (or the agent is working on the voice call) or, on the other hand, when the particular speaker is on auto-acknowledge (e.g., saying something like “yes”, “ah ha”, “yah”, “no”, “ok”, or “nah” every few seconds) to keep the other person talking, when energy other than voice energy (such as music on hold) is being transmitted/received, and/or when no voice energy is detected on either the outgoing or incoming talk path for a determined time period (or the agent is not working on the voice call). When the voice energy detector detects voice energy from only one party over a selected length of time, the tracking agent 232 may conclude that the agent is not actively servicing the work item associated with the voice communication.

In applications where multi-tasking is to be discouraged, when the agent is servicing a work item the tracking agent can restrict information regarding other work items being displayed to the agent. For example, the subject of the other work item can be omitted from a display of information regarding the work item.

Whenever the tracking agent 232 detects that an agent is engaged on a different work item, the previous work item is automatically stopped from a tracking perspective and tracking starts on the new work item. For example, if an agent is talking with a customer and the agent activates an email by opening it, the call work time ends and the email work time begins. While an agent can only have work time accumulating for one work item at a time, one can track the amount of time an agent spends with more than one work item active (i.e., the amount of time spent multi-tasking). When work time is automatically stopped on an existing work item because the agent engages on a new work item, the existing work item could have additional time tracking of “engaged elsewhere (or non-work-item-specific) time.”

The tracking agent 232 may also automatically alter the agent's Graphical User Interface or GUI and/or Telephone User Interface or TUI when the tracking agent detects a change in work items. For example, when the agent returns again to a voice communication from an email the tracking agent 232 may cause a previously provided display of information associated with the voice communication (e.g., customer profile and/or other context of the particular contact) to be displayed again to the agent. By way of further illustration, the tracking agent 232 in the foregoing example may cause the configuration/control settings of the TUI of the agent to change.

The operation of the tracking agent 232 will now be discussed with reference to FIG. 3.

In step 300, the tracking agent 232 receives a marker notification (or notification of a change of agent focus) from an application in the contact center. As noted, the marker notification typically refers to the incidence of a marker or a command issued by or on behalf of the agent.

In decision diamond 304, the tracking agent 232 determines whether the marker notification is issued in respect of a change by the corresponding agent from a first work item on a first communication medium or set of communication media to a different (second) work item on a different (second) communication medium or set of communication media. For example, when the first work item is a voice communication, the second work item is associated with a nonvoice communication medium, such as email, instant messaging, and Web or text chat. When the first work item is a text communication, the second work item is associated with a voice communication medium, such as a circuit-switched voice call, Voice Over IP or VoIP, and the like. When the marker notification is issued with respect to a change related to the communication medium of the current active work item of the human agent, the tracking agent 232 assumes that the human agent has not changed to a second different work item while the first work item is still active. When the notification does not relate to a different communication medium, the notification is deemed to be insignificant with regard to multi-tasking (but it may still be significant with regard to tracking the agent's time since the agent focus has changed from one contact to another) and the tracking agent 232 returns to step 300 and awaits the next notification. When the notification does relate to a different communication medium, the tracking agent 232 proceeds to decision diamond 308.

In decision diamond 308, the tracking agent 232 determines whether or not the agent that is the subject of the notification is in work mode. The non-work mode is deemed to apply when the agent is performing activities not related directly to a given work item. For example, the preview or work item selection operation is considered to be an activity in the non-work mode except as noted above. The agent can also be idle for a predetermined period of time and be considered to be in the non-work mode. The work mode, conversely, is deemed to apply when the agent is performing activities related directly to a given work item, such as conversing with a customer, preparing to service a work item before receipt of the work item, wrapping up the work item after the contact, and the like.

When the notification is from a marker or activity that is not considered to be the work mode, the tracking agent 232 proceeds to step 312 and causes the updating agent to stop the timer for the currently active work item and start a timer for the non-work mode activity (e.g., preview) and increment a non-work or preview counter, as desired. The counter tracks the number of times over a specified time period that the agent performs a non-work function, such as a preview. The tracking agent 232 then returns to step 300 and awaits the next notification.

When the notification is from a marker or activity that is considered to be the work mode, the tracking agent 232 proceeds to decision diamond 320.

In step 320, the tracking agent 232 issues an update notification to update the agent and work tracking records in the database 114.

Referring now to FIG. 4, the operation of the updating agent 236 will now be discussed.

In step 400 of FIG. 4, the updating agent 232 receives the update notification from the tracking agent 232. In decision diamond 404, the updating agent 232 determines whether the notification involves a newly assigned work item. If so, the updating agent 232 stops a timer for the first work item and starts a timer to track the time that the agent works on the new or second work item. If not, the updating agent 232, in step 412, increments a return counter for the previously assigned work item to indicate the number of times that the agent has returned to the work item. In next step 416, the updating agent 232 stops the timer for the first work item and restarts the timer to continue accumulating time for the agent for servicing the second work item.

Returning again to FIG. 3, the tracking agent 232, after receiving a successful update notification acknowledgment from the updating agent 232, if appropriate, updates the corresponding agent's GUI and/or TUI as described above. The tracking agent 232 then returns to step 300 to await the next marker notification.

A number of variations and modifications of the invention can be used. It would be possible to provide for some features of the invention without providing others.

For example, the server and/or switch can be a software-controlled system including a processing unit (CPU), microprocessor, or other type of digital data processor executing software or an Application-Specific Integrated Circuit (ASIC) as well as various portions or combinations of such elements. The memory may be a random access memory (RAM), a read-only memory (ROM), or combinations of these and other types of electronic memory devices.

The present invention, in various embodiments, includes components, methods, processes, systems and/or apparatus substantially as depicted and described herein, including various embodiments, subcombinations, and subsets thereof. Those of skill in the art will understand how to make and use the present invention after understanding the present disclosure. The present invention, in various embodiments, includes providing devices and processes in the absence of items not depicted and/or described herein or in various embodiments hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and/or reducing cost of implementation.

The foregoing discussion of the invention has been presented for purposes of illustration and description. The foregoing is not intended to limit the invention to the form or forms disclosed herein. In the foregoing Detailed Description for example, various features of the invention are grouped together in one or more embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate preferred embodiment of the invention.

Moreover though the description of the invention has included description of one or more embodiments and certain variations and modifications, other variations and modifications are within the scope of the invention, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter.

Claims

1. A method, comprising: (a) providing a plurality of human agents to service a plurality of work items, the work items being in the form of contacts;(b) selecting, by a processor, a first human agent;(c) while the first human agent is servicing concurrently first and second work items on different communication media and involving different customers, determining, by a processor, a change in focus by the first human agent by at least one of the following indicators: (C1) a cursor location on a display;(C2) a cursor activity on the display;(C3) an amount of voice energy generated by a communication device of the first agent; and(C4) a type of voice energy being received by the agent's communication device, wherein the first work item is a voice call and wherein the determination of step (c) that the first agent had a change in agent focus was made without input from the first agent;(d) in response to detecting a change in agent focus, stopping a first timer of service time on the first work item and initiating a second timer of service time on a second work item, wherein, while the second timer is activated, the agent is speaking with a first customer on the first voice call.

2. The method of claim 1, wherein the at least one indicator is (C1).

3. The method of claim 1, wherein the at least one indicator is (C2).

4. The method of claim 1, wherein the at least one indicator is (C3).

5. A computer readable medium encoded with computer executable instructions operable, when executed by the computer, to perform the steps of claim 1.

6. The method of claim 1, wherein the at least one indicator is (C4).

7. A method, comprising: (a) while an agent is servicing simultaneously first and second work items on different communication media and involving different customers, detecting, by a processor, a change in agent focus by the agent from the first work item to the second work item, wherein the detection of change in agent focus is based on one or more of the following: (i) cursor location on a display,(ii) cursor activity on the display,(iii) an amount of voice energy being transmitted from a communication device of the agent,(iv) a type of voice energy being received by the agent's communication device, and(v) a movement of the agent;(b) in response to detecting the change in agent focus, stopping, by a processor, a first timer of work time on servicing of the first work item and initiating a second timer of work on servicing of the second work item, wherein the first work item is a first voice call and wherein, while the second timer is activated, the agent is speaking with a first customer on the first voice call.

8. The method of claim 7, wherein the change in agent focus is indicated by a marker notification and wherein the notification indicates the occurrence of (i).

9. The method of claim 7, wherein the change in agent focus is indicated by a marker notification and wherein the notification indicates the occurrence of (ii).

10. The method of claim 8, further comprising: (c) in response to the occurrence of (i), causing, automatically, at least one of a Graphical User Interface (GUI) and Telephone User Interface (TUI) of the agent to be returned automatically to a previous configuration associated with the second work item or turned to a different configuration associated with the second work item.

11. The method of claim 10, wherein the at least one of a GUI and TUI is returned to the previous configuration and wherein the previous configuration is a display of information previously displayed to the agent and is related to the second work item.

12. A computer readable medium encoded with computer executable instructions operable, when executed by the computer, to perform the steps of claim 7.

13. The method of claim 7, wherein the change in agent focus is indicated by a marker notification and wherein the notification indicates the occurrence of at least one of (i) and (ii) and further comprising: (c) while the agent is working on the first work item, identifying a cursor location and/or a cursor activity in a display or portion thereof associated with the second work item; and(d) in response, generating the marker notification.

14. The method of claim 7, further comprising: (c) while the agent is working on the first work item and before work on the first work item has been completed, determining that the agent has previewed the second work item for a predetermined time, the first and second work items being concurrently assigned to the first human agent for servicing; and(d) in response, generating the marker notification.

15. The method of claim 7, wherein the change in agent focus is indicated by a marker notification and wherein the notification indicates the occurrence of (iii) and wherein the first work item is a voice call and further comprising: (c) detecting, for a selected length of time, voice energy from only one node over the first communication medium, the only one node being associated with a contactor associated with the first work item;(d) in response, generating the marker notification.

16. The method of claim 7, wherein the change in agent focus is indicated by a marker notification and wherein the notification indicates the occurrence of (iv) and wherein the first work item is a voice call and further comprising: (c) monitoring an amount and/or type of voice energy being transmitted and/or received by the agent while the agent is servicing the first work item;(d) in response, generating the marker notification.

17. The method of claim 7, further comprising: (c) while the agent is working on the first work item, restricting at least one of what can be done and viewed by the agent with respect to the second work item until the agent activates the second work item.

18. The method of claim 7, wherein the change in agent focus is indicated by a marker notification, wherein the change in agent focus is determined based on (v) and further comprising: (c) in response to receipt of the marker notification, at least one of placing, automatically, on hold the voice call and muting, automatically, a talk path of the voice call, the talk path extending from the agent to a customer, whereby the agent can hear the customer but the customer cannot hear the agent.

19. The method of claim 18, wherein the agent, to resume the voice call, must, as appropriate, at least one of remove the call from on-hold status and unmute the talk path.

20. The method of claim 18, further comprising: (d) when at least one of the voice call is removed from on hold status and the talk path is unmuted, returning at least one of a Graphical User Interface (GUI) and a Telephone User Interface (TUI) to a prior configuration associated with the first work item.

21. The method of claim 7, further comprising: tracking an amount of time the agent has had more than one work item active.

22. The method of claim 7, wherein the agent did not indicate the change in agent focus.

23. A system, comprising: a plurality of human agents to service work items;a plurality of queues to receive work items awaiting service; anda processor operable to: (a) while an agent is servicing simultaneously first and second work items on different communication media and involving different customers, detect a change in agent focus by the agent from the first work item to the second work item, wherein the detection of change in agent focus is based on one or more of the following: (i) cursor location on a display,(ii) cursor activity on the display,(iii) an amount of voice energy being transmitted from a communication device of the agent,(iv) a type of voice energy being received by the agent's communication device, and(v) a movement of the agent,wherein the first work item is a first voice call and wherein, while a second timer is activated, the agent is speaking with a first customer on the first voice call; and(b) in response to detecting the change in agent focus, stop a first timer of work time on servicing of the first work item and initiating the second timer of work on servicing of the second work item.

24. The system of claim 23, wherein the change in agent focus is indicated by a marker notification and wherein the notification indicates the occurrence of (i).

25. The system of claim 23, wherein the change in agent focus is indicated by a marker notification and wherein the notification indicates the occurrence of (ii).

26. The system of claim 24, further comprising the operation: (c) in response to the occurrence of (i), cause, automatically, at least one of a Graphical User Interface (GUI) and Telephone User Interface (TUI) of the agent to be returned to a previous configuration associated with the second work item or turned to a different configuration associated with the second work item.

27. The method of claim 26, wherein the at least one of a GUI and TUI is returned to the previous configuration and wherein the previous configuration is a display of information previously displayed to the agent and is related to the second work item.

28. The system of claim 23, wherein the change in agent focus is indicated by a marker notification, wherein the notification indicates the occurrence of at least one of (i) and (ii) and further comprising the operations: (c) while the agent is working on the first work item, identify a cursor location and/or a cursor activity in a display or portion thereof associated with the second work item; and(d) in response, generate the marker notification.

29. The system of claim 23, wherein the change in agent focus is indicated by a marker notification and further comprising the operations: (c) while the agent is working on the first work item, identify a passage of a predetermined time before work on the second work item by the agent is indicated as being completed, the first and second work items being concurrently assigned to the first human agent for servicing; and(d) in response, generate the marker notification.

30. The system of claim 23, wherein the change in agent focus is indicated by a marker notification, wherein the notification indicates the occurrence of (iii) and further comprising the operation: (c) detect, for a selected length of time, voice energy from only one node over the first communication medium, the only one node being associated with a contactor associated with the first work item;(d) in response, generate the marker notification.

31. The system of claim 23, wherein the change in agent focus is indicated by a marker notification, wherein the notification indicates the occurrence of at least one of (iii) and (iv) and further comprising the operation: (c) monitor an amount and/or type of voice energy being transmitted and/or received by the agent while the agent is servicing the first work item;(d) in response, generate the marker notification.

32. The system of claim 23, wherein the change in agent focus is indicated by a marker notification, wherein the notification indicates the occurrence of (v) and further comprising the operation: (c) while the agent is working on the first work item, restrict at least one of what can be done and viewed by the agent with respect to the second work item until the agent activates the second work item.

33. The system of claim 23, further comprising the operation: (c) in response to receipt of the marker notification, at least one of place, automatically, on hold the voice call and mute, automatically, a talk path of the voice call, the talk path extending from the agent to a customer, whereby the agent can hear the customer but the customer cannot hear the agent.

34. The system of claim 33, wherein the agent, to resume the voice call, must, as appropriate, at least one of remove the call from on-hold status and unmute the talk path.

35. The system of claim 33, further comprising the operation: (c) when at least one of the voice call is removed from on hold status and the talk path is unmuted, returning at least one of a Graphical User Interface (GUI) and a Telephone User Interface (TUI) to a prior configuration associated with the first work item.

36. The system of claim 23, wherein the processor tracks an amount of time the agent has had more than one work item active.

37. The system of claim 23, wherein the agent did not indicate the change in agent focus.