|Title of Invention||
A METHOD FOR IDENTIFYING TARGET BEHAVIOR IN A CONTACT CENTER
|Abstract||A contact center is provided that includes a plurality of agents for servicing incoming contacts and a target behavior indentification module operble to (i) process a set of events to yield a corresponding measure; (ii) compare the measure to a plurality of rule sets, each of the rule sets corresponding to a different type of target behavior; and (iii) when the measure is defined by the a selected rule set, associate the measure with a type of target behavior corresponding to the selected rule set.|
|Full Text||FORM 2
THE PATENTS ACT, 1970 (39 of 1970)
(See Section 10; rule 13)
METHOD FOR DISCOVERING PROBLEM AGENT BEHAVIORS
Avaya Technology Corp. 211 Mount Airy Road
Basking Ridge New Jersey 07920
USA Nationality: a US corporation
The following specification particularly describes
the nature of this invention and the manner in which it is to be performed
CROSS REFERENCE TO RELATED APPLICATION
This application claims the benefits under 35 U.S.C. § 119 of U.S. Provisional Patent Application Serial No. 60/685,258, filed May 26, 2005, of the same title and to the same inventors, which is incorporated herein by this reference.
Cross reference is made to U.S. Patent Application Serial No. 10/815,556, filed March 31, 2004, entitled "USING AGENT PATTERNS FOR PREDICTIVE AGENT ASSIGNMENTS", and Serial No. 10/861,193, filed June 3,2004, entitled "DATA MODEL OF PARTICIPATION IN MULTI-CHANNEL AND MULTI-PARTY CONTACTS", each of which is incorporated herein by this reference.
The present invention is directed generally to contact center administration and specifically to monitoring agent performance.
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
becomes aware of the contact until the contact is connected to an agent are customer-specifiable (z.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.
The primary objective of contact center management, including call-distribution algorithms, is to ultimately maximize contact center performance and profitability. An ongoing challenge in contact center administration is monitoring of agent behaviors to optimize the use of contact center resources and maximize agent performance and profitably. Agents can take many actions to "beat the system" or skew contact center statistics to "hide" deviant agent performance. Such problem agents are distinguished from poorly performing agents because they try to take advantage of the system to benefit themselves. Problem agents may behave in such a way that their metrics indicate that they are high performing agents when in fact they are not. For instance, an agent can have a long contact during which he or she is chit-chatting and follow that contact with a short contact during which the agent fails properly to service the customer so that the average duration of the two contacts falls within contact center targets. Because deviant behaviors are often varied and infrequent, they are hard to detect and correct It is even
Current products for monitoring and reporting on contact center performance are generally unable to isolate problem behaviors and identify contextual patterns. Current contact center reporting products monitor and report on the performance of agents. Generally, these are summary statistics, such as how many contacts were handled, average handle time, and result codes. Call Management System or CMS™ by Avaya, Inc., reports on a few problem behaviors in isolation. These behaviors include transfers, redirects from time out, disconnects from hold, long hold, aux time, direct time, conferences, contacts of less than a determined time or "short contacts", contacts of greater than a determined time or "long contacts", long alerts, and long wrap-ups. Nice Analyzer™ allows one to do ad-hoc queries to search for events, such as abandons from hold. The products fail to provide a systematic method for discovering beneficial or problem behaviors, reporting on combinations of problems, facilitating an understanding of what might be happening around the behavior that is contributing to it, and allowing the administrator to identify the behavior by type of contact being handled, e.g., inbound vs. outbound, direct vs. ACD delivered, and internal vs. external.
These and other needs are addressed by the various embodiments and configurations of the present invention. The present invention is directed generally to the identification, analysis, and/or tracking of target behavior in a contact center. In one embodiment, a method is provided that includes the steps of:
corresponding to a different type of target behavior; and
(c) when the measure matches the selected rule set, associating the measure with a type of target behavior corresponding to the selected rule set As used herein, a "measure" refers to a set of events having a defined relationship.
In another embodiment, the set of events includes a number of causally related events occurring at different times, and each rule set describes filters relative to a number of dimensions.
Using real-time, historic and/or detailed reports, the method can identify and focus on positive and negative (or problem) agent behaviors. The measures being tracked are commonly not focused on overall performance but rather to specific occurrences of identified problem behaviors. For example, target behaviors include long contact, short contact, long alert, long initiate, long preview, long wrap up, short wrap up, transfer from, transfer in, blind transfer, transfer to a same routing point and/or queue, conference, redirect due to agent rejection, redirect due to time out, cancel due to agent rejection, cancel due to time out, agent release first, disconnect from hold, long hold, hold time, short aux, aux time, aux working time, aux non-working time, wrap up time, direct time, internal time, variation in active time, and variation in wrap up time. As will be appreciated, a "contact" can be a communication over any medium, such as voice, email, chat, fax, etc., and "aux" or auxiliary refers to work items that are not directly related to servicing contacts.
logout, login-then-aux, repeated conference or transfer to the same person, and short and long contacts side-by-side.
The behaviors may be either contact-related or time-based. In either case, problem behavior is typically identified by a number or duration of instances of the behavior exceeding a predetermined or business determined threshold.
The present invention can provide the ability to identify target behaviors impacting the business, and allow managers to stop or reward the behavior. In particular, the invention can provide a systematic method for discovering problem behaviors, reporting on combinations of problems, facilitating an understanding of what might be happening around the behavior that is contributing to it, and allowing the administrator to identify the behavior by type of contact being handled, e.g., inbound vs. outbound, direct vs. ACD delivered, and internal vs. external. The benefits of identifying problem behaviors can be substantial. Problem behaviors can cause the loss of customers, represent the misuse of company resources by agents performing unauthorized activities or actions, and lower moral of those engaging in or observing the behaviors. Moreover, problem behaviors are often an early warning sign of dissatisfaction and agent turnover.
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
As used herein, "at least one", "one or more", and "and/or" are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions "at least one of A, B and C", "at least one of A, B, or C", "one or more of A, B, and C", "one or more of A, B, or C" and "A, B, and/or C" means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
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 block diagram depicting an embodiment of the target behavior identification module;
Fig. 4 is a block diagram of the relationships of various target behavior reports;
Fig. 5 depicts a work handling problem behaviors - summary report;
Fig. 6 depicts a duration-based problem behaviors - summary report;
Fig. 7 depicts a work handling problem behaviors - trend report;
Fig. 8 is a duration-based problem behaviors - trend report;
Fig. 9 is an agent problem behaviors - summary report;
Fig. 10 is a flowchart depicting operation of the target behavior identification module; and
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 processing, 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) communication devices 134-1 to N (such as computer work stations or personal computers), and/or circuit-switched (second) communication 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 call software,
Public Switch Communication Network or PSTN 154 and via link(s) 152 to the second communication 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 communications 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 a Basic Call Management System™ or BCMS 224 and a Call Management System™ or CMS 228 that gathers call records and contact-center statistics for use in generating contact-center reports. CMS and BCMS and any other reporting system, such as Operational Analyst™ 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 communication devices. Illustratively, the switch and/or server can be a modified form of the subscriber-premises equipment disclosed in U.S. Patents 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
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 communication 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
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 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. Patents 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 communication devices 134-1, 134-N are packet-switched and can include, for example, EP 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, packet-based traditional computer telephony adjuncts, and any other communication device.
extensions Extl,... 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 communication device endpoints serviced by the switch/server, and the switch/server can direct incoming calls to and receive outgoing calls from these extensions in a conventional manner. The second communication devices can include, for example, wired and wireless telephones, PDAs, H.320 video phones and conferencing units, voice messaging and response units, traditional computer telephony adjuncts, and any other communication device.
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 communication devices, i.e., the invention may be implemented with any desired type of transport medium as well as combinations of different types of transport channels. 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 communication device 174 via a gateway 178, and the circuit-switched network 154 with an external second communication device 180. These communication devices are referred to as "external" in that they are not directly supported as communication device endpoints by the switch or server. The communication devices 174 and 180 are an example of devices more generally referred to herein as "external endpoints."
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, El/Tl, and analog line or trunk.
It should be emphasized that the configuration of the switch, server, user communication 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 communications 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 communications 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 communication device 134,138 associated with a selected agent. The server 110 distributes and connects these contacts to communication devices of available agents based on the predetermined criteria noted above. When the central server 110 forwards a voice contact to an agent, the central server 110 also forwards customer-related information from databases 114 to the agent's computer work station for previewing and/or viewing (such as by a pop-up display) to permit the agent to better serve the customer. The agents process the contacts sent to them by the central server 110.
(e.g., disk, CD ROM, etc.) or some other computer-readable medium of the center 100. The module 232 identifies and analyzes specific occurrences of identified target behaviors. The target behaviors may be behaviors that are considered by administration to be either beneficial or detrimental to contact center efficiency and profitability.
In one configuration, problem behaviors are tracked, identified, and/or analyzed by the module 232, by contact type and/or distribution method. Exemplary problem behaviors include the following:
1. long contacts or contacts in which the selected agent's active time spent communicating is greater than a specified time threshold;
2. short contacts or contacts in which the selected agent!s active time spent communicating is less than a specified time threshold;
3. long alert or contacts in which the selected agent's alerting time was more than a specified time threshold;
4. long initiate or contacts in which the selected agent's time to dial the customer or otherwise initiating the contact was more than a specified time threshold;
5. long preview or contacts in which the selected agent's time to preview the work item or contact was more than a specified time threshold;
6. long wrap ups or contacts in which the selected agent's time to wrap up the contact was more than a specified time threshold;
7. short wrap ups or contacts in which the selected agent's time to wrap up the contact was less than a specified time threshold;
9. transfers in or contacts (such as from friends or acquaintances) that were successfully transferred to the selected agent;
10. blind transfers or contacts that were transferred to the selected agent prior to the far end or transferee accepting the transfer;
11. transfers to the same routing point or queue or contacts that were transferred by the selected agent back to the same routing point or queue that delivered the contact (e.g., with the hope of another selected agent being selecting to service the contact);
12. conferences or contacts to which the selected agent was a party and that had three or more simultaneous parties active at some point during the contact;
13. redirects or inbound contacts that were rejected by the selected agent after alerting started;
14. redirects due to time out or inbound contacts that were alerting to the
selected agent and were redirected because they were not accepted within a time out period;
15. cancels or outbound contacts that were rejected by the selected agent before the far end accepted or answered the contact;
16. cancels due to time out or outbound contacts that were dropped because the far end did not accept the contact within the time out period;
17. agent releases first or contacts dropped by the selected agent with the customer being the last active party;
19. long holds or contacts that stayed on hold longer than a specified time threshold;
20. hold time or the sum of time intervals that contacts were put on hold by the selected agent;
21. short aux occurs when the selected agent stays in the aux (or auxiliary) state shorter than a specified time threshold;
22. aux time or the sum of all time intervals that the selected agent was in the aux state;
23. aux working time or the sum of all time intervals an selected agent was in aux states that are designated as working;
24. aux non-working time or the sum of all time intervals that the selected agent was in aux states that are designated as nonworking;
25. wrap up time or the sum of all time intervals that the selected agent was in the wrap-up state;
26. direct time or the sum of all time intervals that the selected agent was active on a contact distributed directly to the selected agent (i.e., not queued);
27. internal time or the sum of all time intervals in which the selected agent was active on a contact where all parties are internal to the system (i.e., have an interval address);
next state is unstaffed (e.g., dumps a contact prior to break);
29. short contact-then-logout occurs when the selected agent has a contact whose active time and/or wrap-up time is less than a specified time threshold and the agent's next state is unstaffed (e.g., dumps a contact prior to break leaving);
30. login-then-aux occurs when the selected agent first logs in and immediately goes to the aux state (e.g., logs in but not ready to work);
31. short and long contacts side-by-side occurs when the agent manipulates contact durations to maintain a desired average serviced contact duration;
32. variation in active time occurs when across multiple contacts the selected agent has too little (less than a determined time threshold) or too much (in excess of a determined time threshold) variation in active time; and
33. variation in wrap-up time occurs when across multiple contacts the selected agent has too little (less than a determined time threshold) or too much (in excess of a determined time threshold) variation in wrap-up time.
34. Use of specific phrases in interacting with a customer (determined through content analysis or service observing).
In another configuration, beneficial behaviors are tracked, identified, and/or analyzed by the module 232, by contact type and/or distribution method. Exemplary beneficial behaviors include contacts, one-and-done, alerts, initiates, previews, wrap-ups, hold times having a duration within a specified time range (e.g., having a duration greater
As will be appreciated, what is a problem behavior and what is a beneficial behavior frequently depends on the application. In different applications, the same behavior may be viewed in differing ways. Moreover, it is to be appreciated that the above lists of behaviors is not exhaustive. Other behaviors will be identified by those of ordinary skill in the art that are either problematic or beneficial.
The module 232 notifies contact center managers, in real time or periodically and using agent state and/or performance or problem behavior specific reports, when a selected agent has exhibited one or more of the target behaviors over a selected time period, such as one day or shift. Based on that notification, the module permits managers to drill down to a historical summary report to determine if a single target behavior or combination of target behaviors needs to be addressed or otherwise brought to the agent's attention. The same report can be used to review over a date range, such as a month, the total number of occurrences for or instances of each target behavior. From there, the manager can drill down and view data for each occurrence of a target behavior or can further refine the view by selecting only inbound or outbound contacts, direct or ACD distributed contacts, and/or interval or external contacts. Finally, the manager can further drill down to view a detailed trace for the agent or customer experience around the time the problem behavior occurred
Fig. 3 depicts the target behavior identification module 232 according to an embodiment of the present invention. The module 232 includes an event processor 300 to convert events 304 into measures 308, a filtering agent 312 to compare measures 308
of a selected type of target behavior to identify target behavior instances 324.
The module 232 preferably employs dimensional as opposed to relational modeling. As will be appreciated, dimensional modeling divides the world into measurements and context. Measurements are typically numeric and taken repeatedly. Numeric measurements are facts. Facts are surrounded by mostly textual context. Facts are very specific, well-defined numeric attributes and are collected in fact tables. The context surrounding facts is open-ended and verbose. Dimensions are selected groupings of context. Events are an occurrence or happening. Exemplary dimensions include work item (e.g., type, class, etc.), customer (e.g., identity, class, etc.), agent (e.g., identity, skills, etc.), routing (e.g., how work item was processed/routed, routing destination, etc.), class (e.g., inbound, outbound, internal, external, etc.), time (e.g., time stamp (date and time) of when an event occurred), state (e.g., state of agent, state of customer, state of work item, etc.), exit reason (e.g., reason for state change, etc.), and delivery method (e.g., direct, distributed, etc.) and/or an action involving one or more of the foregoing, such as arrival of a work item, agent state change, and the like. An event is typically associated with (structured) context. For example, events are typically associated with and/or are instances of the foregoing dimensions. A measure refers to a set of events having a defined relationship. Generally, an event is a point in time while a measxire is a temporal duration or a count of event occurrences.
Examples of dimensions and measures are as follows: for problem behaviors one and two above, the dimensions are agent, agent state (active), date and time and the
dimensional measure is the altering time; for problem behavior four, the dimensions are agent, agent state (dialing), date and time and the dimensional measure is time spent dialing; for problem behavior five, the dimensions are agent, agent state (previewing), date and time and the dimensional measure is the time spent previewing the work item; for problem behavior six, the dimensions are agent, agent state (wrap-up), date, and time and the dimensional measure is the time spent wrapping up the contact; and so on.
The event processor 300 applies defined rules to group sets of dimensional events into dimensional measures. The operation of the processor 300 is a modified form of the event processing engine in CMS™ by Avaya Inc. The processor 300 is sensitive to the context associated with an event; thus, it can associate subsequent events of similar or related dimensionality.
The filtering agent 312 compares defined templates or rule sets against dimensional measures with a matching dimensional measure being considered to be an instance of a possible target behavior of a type defined by the matching template. The templates are user configurable. Templates commonly specify what dimensional measures are of interest and/or what the values (e.g., count and/or temporal duration) of the dimensional measures should be. Examples of templates are set forth above in problem behaviors 1-33. The reason that the matching dimensional event is considered to be a "possible" target behavior instance is that the dimensional event could have an innocent or acceptable explanation. The precise reason(s) for the occurrence of the
The threshold filter 320 determines whether or not a possible target behavior instance has a requisite level of significance warranting further investigation and determination by the target behavior monitor 328 (or contact center administrator/manager). This may be done either by comparing a total duration of all of the instances of a selected type of possible target behavior for a set of dimensions (e.g., over a selected time period interval) against a selected total duration threshold for that time interval or a count of the number of instances of a selected type of possible target behavior over a selected time interval against a selected count threshold for that time interval. When the selected threshold is exceeded, the possible target behavior instance is considered to be a target behavior instance warranting further investigation and determination by the target behavior monitor 328. When the selected threshold is not exceeded, the possible target behavior instance is not considered to be a target behavior instance warranting further investigation by the target behavior monitor 328.
As will be appreciated, differing types of target behavior can have differing thresholds. Some types of target behavior are considered generally to be more problematical or beneficial than others. Other types of target behavior are considered to more problematical or beneficial during particular time periods than others, e.g., during the busy hour, or with respect to particular types of work items than others, e.g., gold vs. bronze class. The differing levels of significance can be reflected by suitable adjustments to the thresholds. Thus, a first type of target behavior can have a first threshold under a
As can be seen from Fig. 3, differing types of information are stored during operation of the module 232. The (raw) dimensional events 304 are stored in a first database 332. The dimensional measures 300 are stored in a second database 340.
When a type of target behavior is considered to be significant, the target behavior monitor 328 may drill down or across, using context such as agent, routing point, date/time, state, etc., to greater detail to determine a potential cause or reason for the type of target behavior. The detail, for example, may be agent timeline(s) (e.g., a series of agent state changes as a function of time) and work item timeline(s) (e.g., a series of work item state changes as a function of time) that include dimensional events stored in dimensional event storage 336.
The operation of the module 232 will now be discussed with reference to Fig. 10.
In box 1000, one or more dimensional events 304 arrives from the other components of the contact center, such as server 110, switch 130, and other servers 126.
In decision diamond 1004, the dimensional event processor 300 determines whether the end of the monitored time interval has arrived (i.e., whether the monitored time interval is over). If so, the processor 300, in step 1008, archives the received dimensional event(s), and, in step 1012, zeros out the various variables and awaits the arrival of a selected number of dimensional events in box 1000. If the interval is not over, the module 232 processes the events 304 into dimensional measures 308 and proceeds to step 1016.
dimensional measure 308 does not match a template, the module 232 awaits the arrival of the next dimensional event(s) in box 1000. When the selected dimensional measure 308 matches a template, an indicator is associated with the dimensional measure 308 data structures. The indicator typically identifies the type of target behavior corresponding to the matching template. The agent 312, in step 1024, updates the data structures accordingly.
In decision diamond 1028, the threshold filter 320 selects a threshold corresponding to the type of matching target behavior and determines whether the threshold is exceeded. As noted, the threshold may be either a count of the number of or a total duration identified instances of the target behavior over the selected time interval. If the threshold is not exceeded, the module 232 awaits the arrival of a selected number of dimensional events in box 1000. If the threshold is exceeded, the threshold filter 320, in step 1032, updates the formatting of data structures associated with the matching target behavior type and notifies the target behavior monitor 328. The formatting refers to the formatting of one or more fields in a notification or pertinent report. The formatting can be a font type or color or a color display for the field. For example, the field may show blank, yellow or red based on whether any one metric in the set of metrics associated with each light has exceeded a first or second threshold value. If any metric in the set exceeds the upper threshold for that metric, the light for the set displays red. If not and any metric exceeds the lower threshold, the light will be yellow. If not threshold is exceeded the light is blank.
Fig. 4 shows various example reports and their relationships. As can be seen from Fig. 4, the work handling problem behaviors summary report (Fig. 5) and duration-based problem behaviors summary report (Fig. 6) are the higher level reports and correspond to target behaviors for the entire contact center. Both reports list all of the agents. More detailed reports are Fig. 7 (which shows historic trends (or counts) for a selected type of work handling problem behavior), Fig. 8 (which shows historic trends (or durations) for duration-based problem behaviors), and Fig. 9 (which shows a per-agent summary of the count or duration, as appropriate, of all types of problem behaviors).
Fig. 5 tracks, for all of the agents, the counted problem behaviors, namely long contacts (item 1 above), short contacts (item 2 above), long wrap-ups (item 5 above), transfers (item 7 above), transfers to the same routing point (item 9 above), redirects (item 11 above), agent disconnects first (item 15 above), on-hold disconnects (item 16 above), and long on holds (item 17 above). In any problem behavior field, further, more detailed reports may be accessed by right clicking on the field corresponding to the selected agent and behavior type. For example, by right clicking on short contacts for agent 1 a further table known as problem contact - details (not shown) may be accessed. The row "Agent" totals each of the columns,
Fig. 6 tracks, for all of the agents, the duration-based problem behaviors, namely the durations over a selected time interval of short aux (item 19 above), short wrap-ups (item 6 above), nonworking aux duration (item 22 above), working aux duration (item 21 above), wrap-up duration (item 23 above), direct active duration (item 24 above), intemal
outbound, and internal). In any problem behavior field, further, more detailed reports may be accessed by right clicking on the field corresponding to the selected agent and behavior type. For example, by right clicking on short aux for agent 1 a further table known as agent aux duration - details (not shown) may be accessed. The row "Summary" totals each of the columns.
Fig. 7, which is accessible by left clicking on the field of Fig. 5 corresponding to the selected agent and type of work handling problem behavior, shows historic trends by delivery method (distributed and direct) and contact type (inbound, outbound, and internal). In each field, the count of the number of instances of the selected problem behavior (which is shown as long contacts) for the selected agent (which is shown as agent 1) over each selected time interval (in left column) is provided.
Fig. 8, which is accessible by left clicking on the field of Fig. 6 corresponding to the selected agent and type of problem behavior, shows historic trends by for each type of duration-based problem behavior. In each field, the total duration of the instances of the listed problem behaviors for the selected agent (which is shown as agent 1) over each selected time interval (in left column) is provided. The row "Summary" totals each of the columns.
Fig. 9, which is accessible by right clicking on the selected agent field of Figs. 5-8 in the left column, shows a summary of all problem behaviors, whether significant or not, during the selected time interval for the selected agent. As noted above, right clicking on a selected field provides a more detailed table for the selected variables. For example,
totals each of the columns, and the "Inbound", "Outbound", and "Internal" columns under "Delivery Method" total the pertinent items in each row. For example, "Inbound" under "Delivery Method" is the sum of "Inbound" under "Distributed" and "Inbound" under "Direct".
Fig. 11 shows the interrelationships of the various reports.
The monitor 328 starts out with a group problem behavior summary table (either the table of Figs. 5 or 6). In decision diamond 1104, the monitor 328 determines if there are any group (or agent-wide) problem behaviors identified as being significant. If so, the monitor 328 can view the group trend 1108 for the identified and selected significant problem behavior using either Figs. 7 or 8 and the group problem behavior specific details 1112 by right clicking on the selected field in either the group problem summary or trend reports. Itthere is no group problem behavior of interest, the monitor 328 in decision diamond 1116 determines if there is agent-specific problem behaviors identified as being significant. If so, the monitor 328 can view the selected agents problem behaviors summary table (Fig. 9) and/or trend table (Figs. 7 or 8) (not shown). After identifying the problem area in step 1124, the monitor can drill down to specific details for the identified problem behavior by right clicking on the appropriate fields. In decision diamond 1132, the monitor determines if further details are required to ascertain the cause or reason of the problem behavior. If so, the monitor can drill down to an appropriate agent or contact state detail report 1136 to examine surrounding context (or other surrounding dimensional events). For example, if the selected problem behavior is
the agent's state immediately after the short contact to determine if the agent went on break or left for the day immediately after the problem behavior occurred. In another example, if a short contact occurred, the monitor can examine the immediately preceding event to determine if it was a long contact. If the problem behavior is aux time, the monitor can look at immediately preceding events to determine if the agent logged in and immediately went into the aux state (e.g., to get coffee).
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.
In another alternative embodiment, the module 232 prefilters events based on a set of rules followed by template matching. Prefiltering, for example, can group consecutive events or dimensions into related sets. For example, when a selected event is the dumping of a call a rule could require the next agent state to be associated with the event to determine if the call was dumped because the agent went on break or logged out. In a further example, when the selected event is a short or long call the rule could require
In other embodiments, the target behavior identification module 232 is implemented as depicted for target behaviors that are real-time in nature and/or as an application that queries a database and applies the rule sets to the data returned from the database filtered according to rules for behavior that are not real-time in nature (e.g., one might have different thresholds for an hour, day, week, month, etc., to identify a target behavior over different length time periods).
In another embodiment, information identifying target behaviors is stored in a separate data structure that combines disparate transactional data and rule sets into one structure for reporting and/or analysis of target behaviors.
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,
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 disclosxire. 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.
|Indian Patent Application Number||910/CHE/2006|
|PG Journal Number||5/2010|
|Date of Filing||26-May-2006|
|Name of Patentee||AVAYA TECHNOLOGY CORP.|
|Applicant Address||211 Mount Airy Road, Basking Ridge, New Jersey 07920, USA|
|PCT International Classification Number||G06F|
|PCT International Application Number||N/A|
|PCT International Filing date|