CA2109274C - Arrangement for automating call-center agent-schedule-notification and schedule-adherence functions - Google Patents
Arrangement for automating call-center agent-schedule-notification and schedule-adherence functionsInfo
- Publication number
- CA2109274C CA2109274C CA002109274A CA2109274A CA2109274C CA 2109274 C CA2109274 C CA 2109274C CA 002109274 A CA002109274 A CA 002109274A CA 2109274 A CA2109274 A CA 2109274A CA 2109274 C CA2109274 C CA 2109274C
- Authority
- CA
- Canada
- Prior art keywords
- agent
- call center
- communicating
- corresponding terminal
- schedule
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0062—Provisions for network management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/38—Displays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/40—Aspects of automatic or semi-automatic exchanges related to call centers
- H04M2203/402—Agent or workforce management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5175—Call or contact centers supervision arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/60—Semi-automatic systems, i.e. in which the numerical selection of the outgoing line is under the control of an operator
- H04M3/62—Keyboard equipment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13516—Indexing scheme relating to selecting arrangements in general and for multiplex systems agents or brokers - user, terminal etc., also OSI agent/managers
Abstract
A call-management system (14) for a call center (FIG. 1) having a plurality of terminals (12) staffed by agents (13) includes a program-implemented arrangement (24) for communicating each agent's schedule to the agent via the agent's corresponding terminal and for monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal, thereby relieving a supervisor (19) of having to perform these functions. Other programs (25-27) that enable the supervisor to automatically communicate with the agents via their terminals are also included in the call-management system.
Description
210927;1 ARRANGEMENT FOR AUTOMATING CALL-CENTER
AGENT-SCHEDULE-NOTIFICATION AND
SCHEDULE-ADHERENCE FUNCTIONS
Technical Field 5This invendon relates to call-center operations.
Back~round of the Invention Call centers, such as e.-lefgellcy-services dispatch centers, telemarketing sales centers, customer-service centers, and other automatic call-distribution centers, employ large numbers of human agents to place and/or answer calls. For proper, 10 efficient, and smooth center operadon, work schedules must be developed for agents, the schedules must be communicated to the agents, and the agents' adherence to the schedules must be monitored. Presently, some or all of these activides are done manually, by center supervisors. This is slow, inefficient, and consumes an inordinate amount of the supervisors' time which could be better-spent on other 15 acdvities.
Call centers are typically low-margin, high-volume operations, and therefore even small improvements in efficiency can have a significant effect on the centers' commercial viability. Realizing this, suppliers of call-center systems have automated some of these activities to make them more efficient and to unload the20 supervisors of their burden. Thus, call-management s~sle-lls, which monitor call-center activity and issue reports thereon to the supervisor, have been introduced.
Also introduced have been schedllling systems, which generate agent schedules based upon the reports generated by the call-management ~y~ s. While these advances have considerably improved the efficiency of call-center operations, further 25 advances continue to be sought.
Summary of the Invention This invention is directed to meeting these and other needs of the prior art. I have recognized that a significant hindrance to the efficiency of call-center operations is the fact that the tasks of communicating agent schedules to the agents 30 and of monitoring the agents' adherence to these schedules continue to be performed by human call-center supervisors in largely a manual manner. Therefore, according to the invention, there is provided an arrangement which automates these functions.
Specifically according to the invention, there is provided an arrangement which communicates with the agents via their telecommunication terminals to advise them 35 of their schedules and to monitor their adherence thereto. Illustratively, the arrangement is incorporated into the call-management system of the call-center, in 21~927~
order to share therewith, and thereby avoid unnecess~y duplication of, the call-management system's existing capabilities.
According to an illustrative embodiment of the invention, in a call center that has a plurality of teleco~ -ications terminals staffed by agents, each 5 event of an agent's schedule which includes predetermined events -- such as breaks -- scheduled for predetermined times is co.~ nicated at its scheduled time to the agent via that agent's corresponding terminal. Then the agent's performance of the col~nullicated event at the scheduled time is lllonilor~,d via the agent's input -- such as pressing of the appr~pliate key -- into that agent's corresponding terminal.
10 Preferably, this functionality is obtained by means of execution of stored programs in a call-management system of the call center. Also preferably, other programs that facilitate cGmmullications between a call center supeIvisor and the agents are likewise stored and executed in the call-management system.
The invention frees the call center supervisor from having to 15 colllll~unicate schedules and schedule events to agents and from monitoring the agents' adherence to the schedules. It automatizes these functions, making theirperformance more exact and efficient. It provides the supervisor with a capability to co..-,.-~lnic~te with the agents through their terminals. And when implemented as programs executing in the call center's call-management system, the invention is20 easy and in~nsi~e to implement and to retrofit, adds no additional hardware to the call center, and advantageously makes use of capabilities already provided by the call-management center so as to avoid their duplication.
These and other advantages and features of the invention will become more al)pale.l~ from the following description of an illustrative embodiment of the 25 invention taken together with the drawing.
Brief Description of the Drawin~
FIG. 1 is a block diagram of an automatic call-distribution (ACD) system that includes an illustrative embodiment of the invention;
FIG. 2 is a flow diagram of an agent schedule-notification and 30 schedule-adherence-monitoring program of a CMS system of the ACD system of FIG. l;
FIG. 3 is a flow diagram of an agent-move program of the CMS system of the ACD system of FIG. l;
FIG. 4 is a flow diagram of an agent-disable program of the CMS
35 system of the ACD system of FIG. l; and 210g27~
-FIG. S is a flow diagram of an agent-messa~ing program of the CMS
system of the ACD system of FIG. 1.
Detailed Description FIG. 1 shows an automatic call~istribution (ACD) system having a 5 conventional architecture. It comprises an ACD private branch exchange (PBX) 10, such as an AT&T DEFINITY~ G1 or G2 execudng conventional AT&T ACD
software. PBX 10 is connected to the outside world, e.g., the public telephony network, by a plurality of trunks 11. PBX 10 serves a plurality of ACD agent terminals 12 staffed by ACD agents 13. PBX 10 is connected to each terminal 12 by 10 a digital link 16, such as an ISDN or an AT&T DCP link, which carries both voice and data commllnications. Also connected to PBX 10 is a call-management system (CMS) 14, such as an AT&T CMS. The connection is via a control co,--"~lnicationslink 17, such as an AT&T DCIU or ASAI link. An a-lmini~tration terminal 18 is connected to CMS 14. An ACD system supervisor 19 interfaces with CMS 14 via 15 terminal 18.
CMS 14 is a computer-implemented system. It comprises a processor 20 executing programs out of a memory 21. Included among the programs in memory 21 are conventional CMS programs 22, optionally a conventional scheduler (SCH.) 23, and -- according to the invention -- a schedule notification and 20 adherence monitoring program 24 and other agent-interaction programs 25-27.
Programs 24-27 are diagramed in FIGS. 2-5, respectively.
Illustratively, CMS 14 runs a copy of program 24 of FIG. 2 as a separate process for each agent 13. Execution of a program 24 is invoked in response to receiving the schedule of an agent 13, either from supervisor 19 via a~lmini~trative 25 terminal 14 or from scheduler 23, at step 200. Executing program 24 records, for example in the form of scheduled in~l.upl~ or wakeup calls, the action points of this schedule, such as starting time, break times, and quitting times, at step 204.
Program 24 then check whether the corresponding agent 13 is due to start, at step 208, and if not, program 24 returns to step 208. Alternatively, the check of 30 step 208 is replaced by a wakeup call or interrupt at the agent's starting time.
If it is determined at step 208 that agent 13 is due to start, program 24 queries CMS programs 22 whether they have a record of agent 13 having logged in yet, at step 212. If not, program 24 checks whether agent 13 is more than a predetermined number (Y) of minutes overdue, at step 216. If not, program 24 35 returns to step 212; if so, program 24 causes CMS programs 22 to generate an exception reporting that agent 13 is overdue, at step 220, and then returns to 21~271 step 212, If and when agent 13 is found at step 212 to have logged in, program 24 sends a request to PBX 10 via CMS programs 22 to place agent 13 in work mode, atstep 222. Program 24 then checks whether agent 13 is due to quit, at step 224, and if 5 not, checks whether agent 13 is due to break, at step 228. If agent 13 is not scheduled to break, program 24 returns to step 224. Alternatively, the check of each step 224 and 228 is replaced by a wakeup call or interrupt at the quitting and break times, respectively.
When agent 13 is determined to be due to go on break at step 228, 10 program 24 requests PBX 10 via CMS programs 22 to place agent 13 in non-work mode after completion of any call which agent 13 is presently handling, at step 232.
Program 24 then queries CMS programs 22 to determine whether agent 13 has yet been placed in non-work mode, at step 236, and if not, program 24 returns to step 236. Alternatively, the check of step 236 is replaced by a wakeup call or 15 inte,lu~l issued by CMS programs 22 upon agent 13 being placed in non-work mode.
When agent 13 is determined at step 236 to have been placed in non-work mode, prograrn 24 checks with CMS programs 22 to determine if the agent split of which agent 13 is a part is presently overloaded with work, at step 240. If so, 20 program 24 sends a display message to agent 13, via CMS programs 22, PBX 10, and display 30 of that agent's terminal 12, informing agent 13 that his or her break has been delayed by a predetermined number (X) of minutes~ at step 244.
Program 24 then requests PBX 10 via CMS program 22 to place agent 13 back in work mode, at step 248, and also adjusts the recorded break schedule for agent 13 to 25 reflect the new scheduled break time, at step 252. Program 24 then returns to step 224.
Returning to step 240, if it is there determined that the agent's split is not overloaded, program 24 sends a voice and/or display message to agent 13, viaCMS programs 22 and PBX 10, that the agent's break has begun. The message is 30 either displayed to agent 13 on display 30 of his or her terminal 12 or voiced to agent 13 via his or her headphone 32. Program 24 then checks whether agent 13 isdue back from break, at step 260, and if not, program 24 returns to step 260.
Alternatively, the check of step 260 is replaced by a wakeup call or an interrupt issued when the scheduled break period expires.
When agent 13 is found at step 260 to be due back from break, program 24 sends a display message to agent 13 via CMS programs 22 and PBX 10 informing him or her that the break is over, at step 264. Program 24 further causes PBX 10 via CMS prograrns 22 to send a tone to speaker 31 of agent terminal 12 to5 alert agent 13 to the incoming display mess~ge, at step 268. Program 24 then checks with CMS programs 22 to determine whether agent 13 has returned from break, at step 272. Illustratively, program 24 checks whether CMS programs 22 have received an indication that an aux-work button has been depressed on that agent's terminal 12 which cancels a previous activation of the aux-work feature. If it is 10 determined at step 272 that agent 13 has not returned to work, program 24 determines whether agent 13 is more than a predete....i.led number (Y) of minutes overdue, at step 276. If not, program 24 retums to step 272; if so, program 24 causes CMS programs 22 to generate an exception to record this fact, at step 280, and then returns to step 272.
If and when it is determined at step 272 that agent 13 has returned to work, program 24 requests PBX 10 via CMS programs 22 to place agent 13 back in work mode, at step 284. Program 24 then returns to step 224.
When it is determined at step 224 that agent 13 is due to quit, program 24 requests PBX 10 to place agent 13 in non-work mode upon completion of any call presently being handled by agent 13, at step 288. Program 24 then queries CMS programs 22 to determine whether agent 13 has yet been placed in non-work mode, at step 292, and if not, program 24 returns to step 292.
Alternatively, the check at step 292 is replaced by a wakeup call or in~ell upt issued by CMS programs 22 upon agent 13 being placed in non-work mode.
When agent 13 is detected at step 292 to have been placed in non-work mode, program 24 causes a display message to be sent to terminal 12 of agent 13 informing him or her that it is quitting time; at step 296. Program 24 then exists execution, at step 299.
When a need arises to move an agent 13 from one ACD agent split to another, program 25 of FIG. 3 is executed. Program 25 is invoked in response to supervisor 19 entering, via ~lmini~tration terrnin~l 14, the conditions upon theoccurrence of which one or more agents 13 should be moved from one split (A) to another split (B) and how many (C) agents 13 should be moved. Program 25 receives these conditions, at step 300, and begins to monitor output of CMS
programs 22 to determine if these conditions are met, at step 304. When it determines that the conditions have been met, program 25 sends a message via CMS
210~27~
-programs 22 to PBX 10 requesting it to log C agents 13 out of split A at the completion of any calls presently being handled by those agents 13, at step 308. It then monitors CMS programs 22 to obtain the identity of the C agents 13 which PBX 10 has logged out of split A at step 312. When it determines, at step 316, that it 5 has the identity of C agents 13, program 25 causes a visual message to be sent to each one of those agents 13 informing them that they are being moved to split B, at step 320. Program 25 then requests PBX 10 to log those C agents 13 into split B, at step 324, and exits execution, at step 328.
Program 26 of FIG. 4 is invoked when supervisor 19 decides that certain 10 exceptions to proper operation should disable any offending agent 13 from h~nclling calls. Supervisor 19 enters, via terminal 14, the condi~ions that define which, and how many, exceptions should disable an agent 13. Program 26 receives these conditions, at step 300, and begins to monitor the output of CMS programs 22 foroccull-,nce of these conditions, at step 404. When it determines that the conditions 15 have been met by an agent 13, program 26 requests PBX 10 to place the offending agent 13 in non-work mode following completion of any call presently being handled by offending agent 13, at step 408. When the offending agent 13 has beenplaced in non-work mode, as determined at step 412, program 26 sends a visual message to offending agent 13, at step 416, informing him or her of the fact that he 20 or she has been disabled. Optionally, the mess~ge also informs offending agent 13 of the exceptions which caused the disablement, and directs offending agent 13 to report to supervisor 19. Program 26 then returns to step 404.
Program 27 of FIG. S is executed when supervisor 19 unconditionally wishes to send a message to one or more agents 13. Supervisor 19 inputs the 25 message on terminal 14, identifies the one or more agents 13 to whom it should be sent, and specifies the time at which it should be sent. In response to receiving this input, at step 500, program 27 begins to monitor real time for occurrence of thesending time, at step 504. Alternatively to the check of step 504, program 27 isissued a wakeup call at the sending time. When the sending time occurs, program 27 30 sends a request to PBX 10 to place the designated one or more agents 13 in non-work mode at completion of any calls presently being h~ndled by those agents 13, at step 508. When all designated agents 13 have been placed in non-work mode, as determined at step 512, program 27 sends the supervisor's message in visual form to display 30 of terminals 12 of the designated agents 13, at step 516. Program 27 then 35 exits execution, at step 520.
210927 1 ;
-Of course, it should be understcod that various changes and modifications to the illustrative embodiment described above will be apparent tothose skilled in the art. For example, these flow charts of the figures are only a representation of an illustrative implementation; an actual implementation in a CMS
5 architecture or another multi-tasked programming env~ mel-t may be different.
Such changes and modifications can be made without departing from the spirit andthe scope of the invention and without dimini~hing its attendant advantages. It is therefore intended that all such changes and modifications be covered by the following claims.
AGENT-SCHEDULE-NOTIFICATION AND
SCHEDULE-ADHERENCE FUNCTIONS
Technical Field 5This invendon relates to call-center operations.
Back~round of the Invention Call centers, such as e.-lefgellcy-services dispatch centers, telemarketing sales centers, customer-service centers, and other automatic call-distribution centers, employ large numbers of human agents to place and/or answer calls. For proper, 10 efficient, and smooth center operadon, work schedules must be developed for agents, the schedules must be communicated to the agents, and the agents' adherence to the schedules must be monitored. Presently, some or all of these activides are done manually, by center supervisors. This is slow, inefficient, and consumes an inordinate amount of the supervisors' time which could be better-spent on other 15 acdvities.
Call centers are typically low-margin, high-volume operations, and therefore even small improvements in efficiency can have a significant effect on the centers' commercial viability. Realizing this, suppliers of call-center systems have automated some of these activities to make them more efficient and to unload the20 supervisors of their burden. Thus, call-management s~sle-lls, which monitor call-center activity and issue reports thereon to the supervisor, have been introduced.
Also introduced have been schedllling systems, which generate agent schedules based upon the reports generated by the call-management ~y~ s. While these advances have considerably improved the efficiency of call-center operations, further 25 advances continue to be sought.
Summary of the Invention This invention is directed to meeting these and other needs of the prior art. I have recognized that a significant hindrance to the efficiency of call-center operations is the fact that the tasks of communicating agent schedules to the agents 30 and of monitoring the agents' adherence to these schedules continue to be performed by human call-center supervisors in largely a manual manner. Therefore, according to the invention, there is provided an arrangement which automates these functions.
Specifically according to the invention, there is provided an arrangement which communicates with the agents via their telecommunication terminals to advise them 35 of their schedules and to monitor their adherence thereto. Illustratively, the arrangement is incorporated into the call-management system of the call-center, in 21~927~
order to share therewith, and thereby avoid unnecess~y duplication of, the call-management system's existing capabilities.
According to an illustrative embodiment of the invention, in a call center that has a plurality of teleco~ -ications terminals staffed by agents, each 5 event of an agent's schedule which includes predetermined events -- such as breaks -- scheduled for predetermined times is co.~ nicated at its scheduled time to the agent via that agent's corresponding terminal. Then the agent's performance of the col~nullicated event at the scheduled time is lllonilor~,d via the agent's input -- such as pressing of the appr~pliate key -- into that agent's corresponding terminal.
10 Preferably, this functionality is obtained by means of execution of stored programs in a call-management system of the call center. Also preferably, other programs that facilitate cGmmullications between a call center supeIvisor and the agents are likewise stored and executed in the call-management system.
The invention frees the call center supervisor from having to 15 colllll~unicate schedules and schedule events to agents and from monitoring the agents' adherence to the schedules. It automatizes these functions, making theirperformance more exact and efficient. It provides the supervisor with a capability to co..-,.-~lnic~te with the agents through their terminals. And when implemented as programs executing in the call center's call-management system, the invention is20 easy and in~nsi~e to implement and to retrofit, adds no additional hardware to the call center, and advantageously makes use of capabilities already provided by the call-management center so as to avoid their duplication.
These and other advantages and features of the invention will become more al)pale.l~ from the following description of an illustrative embodiment of the 25 invention taken together with the drawing.
Brief Description of the Drawin~
FIG. 1 is a block diagram of an automatic call-distribution (ACD) system that includes an illustrative embodiment of the invention;
FIG. 2 is a flow diagram of an agent schedule-notification and 30 schedule-adherence-monitoring program of a CMS system of the ACD system of FIG. l;
FIG. 3 is a flow diagram of an agent-move program of the CMS system of the ACD system of FIG. l;
FIG. 4 is a flow diagram of an agent-disable program of the CMS
35 system of the ACD system of FIG. l; and 210g27~
-FIG. S is a flow diagram of an agent-messa~ing program of the CMS
system of the ACD system of FIG. 1.
Detailed Description FIG. 1 shows an automatic call~istribution (ACD) system having a 5 conventional architecture. It comprises an ACD private branch exchange (PBX) 10, such as an AT&T DEFINITY~ G1 or G2 execudng conventional AT&T ACD
software. PBX 10 is connected to the outside world, e.g., the public telephony network, by a plurality of trunks 11. PBX 10 serves a plurality of ACD agent terminals 12 staffed by ACD agents 13. PBX 10 is connected to each terminal 12 by 10 a digital link 16, such as an ISDN or an AT&T DCP link, which carries both voice and data commllnications. Also connected to PBX 10 is a call-management system (CMS) 14, such as an AT&T CMS. The connection is via a control co,--"~lnicationslink 17, such as an AT&T DCIU or ASAI link. An a-lmini~tration terminal 18 is connected to CMS 14. An ACD system supervisor 19 interfaces with CMS 14 via 15 terminal 18.
CMS 14 is a computer-implemented system. It comprises a processor 20 executing programs out of a memory 21. Included among the programs in memory 21 are conventional CMS programs 22, optionally a conventional scheduler (SCH.) 23, and -- according to the invention -- a schedule notification and 20 adherence monitoring program 24 and other agent-interaction programs 25-27.
Programs 24-27 are diagramed in FIGS. 2-5, respectively.
Illustratively, CMS 14 runs a copy of program 24 of FIG. 2 as a separate process for each agent 13. Execution of a program 24 is invoked in response to receiving the schedule of an agent 13, either from supervisor 19 via a~lmini~trative 25 terminal 14 or from scheduler 23, at step 200. Executing program 24 records, for example in the form of scheduled in~l.upl~ or wakeup calls, the action points of this schedule, such as starting time, break times, and quitting times, at step 204.
Program 24 then check whether the corresponding agent 13 is due to start, at step 208, and if not, program 24 returns to step 208. Alternatively, the check of 30 step 208 is replaced by a wakeup call or interrupt at the agent's starting time.
If it is determined at step 208 that agent 13 is due to start, program 24 queries CMS programs 22 whether they have a record of agent 13 having logged in yet, at step 212. If not, program 24 checks whether agent 13 is more than a predetermined number (Y) of minutes overdue, at step 216. If not, program 24 35 returns to step 212; if so, program 24 causes CMS programs 22 to generate an exception reporting that agent 13 is overdue, at step 220, and then returns to 21~271 step 212, If and when agent 13 is found at step 212 to have logged in, program 24 sends a request to PBX 10 via CMS programs 22 to place agent 13 in work mode, atstep 222. Program 24 then checks whether agent 13 is due to quit, at step 224, and if 5 not, checks whether agent 13 is due to break, at step 228. If agent 13 is not scheduled to break, program 24 returns to step 224. Alternatively, the check of each step 224 and 228 is replaced by a wakeup call or interrupt at the quitting and break times, respectively.
When agent 13 is determined to be due to go on break at step 228, 10 program 24 requests PBX 10 via CMS programs 22 to place agent 13 in non-work mode after completion of any call which agent 13 is presently handling, at step 232.
Program 24 then queries CMS programs 22 to determine whether agent 13 has yet been placed in non-work mode, at step 236, and if not, program 24 returns to step 236. Alternatively, the check of step 236 is replaced by a wakeup call or 15 inte,lu~l issued by CMS programs 22 upon agent 13 being placed in non-work mode.
When agent 13 is determined at step 236 to have been placed in non-work mode, prograrn 24 checks with CMS programs 22 to determine if the agent split of which agent 13 is a part is presently overloaded with work, at step 240. If so, 20 program 24 sends a display message to agent 13, via CMS programs 22, PBX 10, and display 30 of that agent's terminal 12, informing agent 13 that his or her break has been delayed by a predetermined number (X) of minutes~ at step 244.
Program 24 then requests PBX 10 via CMS program 22 to place agent 13 back in work mode, at step 248, and also adjusts the recorded break schedule for agent 13 to 25 reflect the new scheduled break time, at step 252. Program 24 then returns to step 224.
Returning to step 240, if it is there determined that the agent's split is not overloaded, program 24 sends a voice and/or display message to agent 13, viaCMS programs 22 and PBX 10, that the agent's break has begun. The message is 30 either displayed to agent 13 on display 30 of his or her terminal 12 or voiced to agent 13 via his or her headphone 32. Program 24 then checks whether agent 13 isdue back from break, at step 260, and if not, program 24 returns to step 260.
Alternatively, the check of step 260 is replaced by a wakeup call or an interrupt issued when the scheduled break period expires.
When agent 13 is found at step 260 to be due back from break, program 24 sends a display message to agent 13 via CMS programs 22 and PBX 10 informing him or her that the break is over, at step 264. Program 24 further causes PBX 10 via CMS prograrns 22 to send a tone to speaker 31 of agent terminal 12 to5 alert agent 13 to the incoming display mess~ge, at step 268. Program 24 then checks with CMS programs 22 to determine whether agent 13 has returned from break, at step 272. Illustratively, program 24 checks whether CMS programs 22 have received an indication that an aux-work button has been depressed on that agent's terminal 12 which cancels a previous activation of the aux-work feature. If it is 10 determined at step 272 that agent 13 has not returned to work, program 24 determines whether agent 13 is more than a predete....i.led number (Y) of minutes overdue, at step 276. If not, program 24 retums to step 272; if so, program 24 causes CMS programs 22 to generate an exception to record this fact, at step 280, and then returns to step 272.
If and when it is determined at step 272 that agent 13 has returned to work, program 24 requests PBX 10 via CMS programs 22 to place agent 13 back in work mode, at step 284. Program 24 then returns to step 224.
When it is determined at step 224 that agent 13 is due to quit, program 24 requests PBX 10 to place agent 13 in non-work mode upon completion of any call presently being handled by agent 13, at step 288. Program 24 then queries CMS programs 22 to determine whether agent 13 has yet been placed in non-work mode, at step 292, and if not, program 24 returns to step 292.
Alternatively, the check at step 292 is replaced by a wakeup call or in~ell upt issued by CMS programs 22 upon agent 13 being placed in non-work mode.
When agent 13 is detected at step 292 to have been placed in non-work mode, program 24 causes a display message to be sent to terminal 12 of agent 13 informing him or her that it is quitting time; at step 296. Program 24 then exists execution, at step 299.
When a need arises to move an agent 13 from one ACD agent split to another, program 25 of FIG. 3 is executed. Program 25 is invoked in response to supervisor 19 entering, via ~lmini~tration terrnin~l 14, the conditions upon theoccurrence of which one or more agents 13 should be moved from one split (A) to another split (B) and how many (C) agents 13 should be moved. Program 25 receives these conditions, at step 300, and begins to monitor output of CMS
programs 22 to determine if these conditions are met, at step 304. When it determines that the conditions have been met, program 25 sends a message via CMS
210~27~
-programs 22 to PBX 10 requesting it to log C agents 13 out of split A at the completion of any calls presently being handled by those agents 13, at step 308. It then monitors CMS programs 22 to obtain the identity of the C agents 13 which PBX 10 has logged out of split A at step 312. When it determines, at step 316, that it 5 has the identity of C agents 13, program 25 causes a visual message to be sent to each one of those agents 13 informing them that they are being moved to split B, at step 320. Program 25 then requests PBX 10 to log those C agents 13 into split B, at step 324, and exits execution, at step 328.
Program 26 of FIG. 4 is invoked when supervisor 19 decides that certain 10 exceptions to proper operation should disable any offending agent 13 from h~nclling calls. Supervisor 19 enters, via terminal 14, the condi~ions that define which, and how many, exceptions should disable an agent 13. Program 26 receives these conditions, at step 300, and begins to monitor the output of CMS programs 22 foroccull-,nce of these conditions, at step 404. When it determines that the conditions 15 have been met by an agent 13, program 26 requests PBX 10 to place the offending agent 13 in non-work mode following completion of any call presently being handled by offending agent 13, at step 408. When the offending agent 13 has beenplaced in non-work mode, as determined at step 412, program 26 sends a visual message to offending agent 13, at step 416, informing him or her of the fact that he 20 or she has been disabled. Optionally, the mess~ge also informs offending agent 13 of the exceptions which caused the disablement, and directs offending agent 13 to report to supervisor 19. Program 26 then returns to step 404.
Program 27 of FIG. S is executed when supervisor 19 unconditionally wishes to send a message to one or more agents 13. Supervisor 19 inputs the 25 message on terminal 14, identifies the one or more agents 13 to whom it should be sent, and specifies the time at which it should be sent. In response to receiving this input, at step 500, program 27 begins to monitor real time for occurrence of thesending time, at step 504. Alternatively to the check of step 504, program 27 isissued a wakeup call at the sending time. When the sending time occurs, program 27 30 sends a request to PBX 10 to place the designated one or more agents 13 in non-work mode at completion of any calls presently being h~ndled by those agents 13, at step 508. When all designated agents 13 have been placed in non-work mode, as determined at step 512, program 27 sends the supervisor's message in visual form to display 30 of terminals 12 of the designated agents 13, at step 516. Program 27 then 35 exits execution, at step 520.
210927 1 ;
-Of course, it should be understcod that various changes and modifications to the illustrative embodiment described above will be apparent tothose skilled in the art. For example, these flow charts of the figures are only a representation of an illustrative implementation; an actual implementation in a CMS
5 architecture or another multi-tasked programming env~ mel-t may be different.
Such changes and modifications can be made without departing from the spirit andthe scope of the invention and without dimini~hing its attendant advantages. It is therefore intended that all such changes and modifications be covered by the following claims.
Claims (26)
1. An arrangement for a call center having a plurality of telecommunications terminals staffed by agents, comprising:
means responsive to an agent's schedule which includes predetermined events scheduled for predetermined times, for communicating each said event at its scheduled time to the agent via the agent's corresponding terminal; and means cooperative with the communicating means, for monitoring the agent's performance of the communicated event at the scheduled time via the agent's input into the agent's corresponding terminal.
means responsive to an agent's schedule which includes predetermined events scheduled for predetermined times, for communicating each said event at its scheduled time to the agent via the agent's corresponding terminal; and means cooperative with the communicating means, for monitoring the agent's performance of the communicated event at the scheduled time via the agent's input into the agent's corresponding terminal.
2. The arrangement of claim 1 implemented in a call-management system of the call center.
3. The arrangement of claim 1 for a call center having a processor-implemented call management system, wherein:
the communicating means and the monitoring means both comprise a program stored for execution on the call management system processor.
the communicating means and the monitoring means both comprise a program stored for execution on the call management system processor.
4. The arrangement of claim 1 wherein:
the means for communicating each said event comprise means for causing at least one of an audio signal generator and a visual signal generator of the agent's corresponding terminal to generate at least one of an audio signal and a visual signal, respectively, to alert the agent to occurrence of the scheduled time for each said event.
the means for communicating each said event comprise means for causing at least one of an audio signal generator and a visual signal generator of the agent's corresponding terminal to generate at least one of an audio signal and a visual signal, respectively, to alert the agent to occurrence of the scheduled time for each said event.
5. The arrangement of claim 1 wherein:
the means for communicating each said event comprise means for sending a display message indicating each said event at its scheduled time to a display of the agent's corresponding terminal.
the means for communicating each said event comprise means for sending a display message indicating each said event at its scheduled time to a display of the agent's corresponding terminal.
6. The arrangement of claim 5 wherein:
the means for communicating each said event further comprise means for causing a speaker of the agent's corresponding terminal to produce an auditory signal when the display message is displayed on the display of the terminal.
the means for communicating each said event further comprise means for causing a speaker of the agent's corresponding terminal to produce an auditory signal when the display message is displayed on the display of the terminal.
7. The arrangement of claim 1 wherein:
the means for communicating each said event comprise:
means for selectively causing the call center to place the agent in a non-work state substantially at the scheduled time.
the means for communicating each said event comprise:
means for selectively causing the call center to place the agent in a non-work state substantially at the scheduled time.
8. The arrangement of claim 1 wherein:
the means for monitoring comprise means responsive to detection of the agent's performance of the communicated event for selectively causing the call center to place the agent in a work state.
the means for monitoring comprise means responsive to detection of the agent's performance of the communicated event for selectively causing the call center to place the agent in a work state.
9. The arrangement of claim 1 wherein:
the means for monitoring comprise means responsive to detection of the agent's failure to perform the communicated event substantially at the scheduled time for causing the call center to register an exception against the agent.
the means for monitoring comprise means responsive to detection of the agent's failure to perform the communicated event substantially at the scheduled time for causing the call center to register an exception against the agent.
10. An arrangement for a call center having a plurality of telecommunications terminal staffed by agents, comprising:
means for communicating an agent's schedule to the agent via the agent's corresponding terminal;
means cooperative with the communicating means, for monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal; and means responsive to receipt of a message and an identification of at least one agent intended to receive the message, for sending the received message to the identified at least one agent via the identified at least one agent's corresponding terminal.
means for communicating an agent's schedule to the agent via the agent's corresponding terminal;
means cooperative with the communicating means, for monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal; and means responsive to receipt of a message and an identification of at least one agent intended to receive the message, for sending the received message to the identified at least one agent via the identified at least one agent's corresponding terminal.
11. An arrangement for a call center having a plurality of telecommunications terminals staffed by agents, comprising:
means for communicating an agent's schedule to the agent via the agent's corresponding terminal;
means cooperative with the communicating means, for monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal;
means responsive to receipt of criteria for moving an agent from one agent split to another, for monitoring the call center for occurrence of the received criteria;
and means responsive to detection of occurrence of the received criteria, for moving an agent from the one split to the other split.
means for communicating an agent's schedule to the agent via the agent's corresponding terminal;
means cooperative with the communicating means, for monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal;
means responsive to receipt of criteria for moving an agent from one agent split to another, for monitoring the call center for occurrence of the received criteria;
and means responsive to detection of occurrence of the received criteria, for moving an agent from the one split to the other split.
12. An arrangement for a call center having a plurality of telecommunications terminals staffed by agents, comprising:
means for communicating an agent's schedule to the agent via the agent's corresponding terminal;
means cooperative with the communicating means, for monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal;
means responsive to detection of the agent's failure to adhere to the communicated schedule, for causing the call center to register an exception against the agent;
means responsive to receipt of information characterizing exceptions meriting disablement of an agent, for monitoring the call center for registration of the characterized exceptions; and means responsive to detection of registration of the characterized exceptions, for causing the call center to place in a non-work state an agent against whom the characterized exceptions were registered.
means for communicating an agent's schedule to the agent via the agent's corresponding terminal;
means cooperative with the communicating means, for monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal;
means responsive to detection of the agent's failure to adhere to the communicated schedule, for causing the call center to register an exception against the agent;
means responsive to receipt of information characterizing exceptions meriting disablement of an agent, for monitoring the call center for registration of the characterized exceptions; and means responsive to detection of registration of the characterized exceptions, for causing the call center to place in a non-work state an agent against whom the characterized exceptions were registered.
13. An arrangement for a call center having a plurality of telecommunications terminals staffed by agents, comprising:
means responsive to an agent's schedule which includes predetermined breaks scheduled for predetermined times, for determining at each scheduled break time whether an agent split to which the agent belongs is overloaded with work;
means responsive to a first determination at an individual predetermined time that the agent split is overloaded, for rescheduling the corresponding break to another time;
means responsive to said first determination for sending a message to the agent via a display of the agent's corresponding terminal that the break has been rescheduled;
means responsive to a second determination at an individual predetermined time that the agent split is not overloaded, for causing the call center to place the agent in a non-work state;
means responsive to the second determination for sending a message to the agent via the display informing the agent to go on break;
means responsive to the second determination and to expiration of a predetermined break period following the individual predetermined time, for sending a message to the agent via the display informing the agent to go off break;
means responsive to detection, from the agent's input on the agent's corresponding terminal, that the agent has gone off break within a predetermined time period following expiration of the predetermined break period, for causing the call center to place the agent in a work state; and means responsive to detection, from lack of the agent's said input on the agent's corresponding terminal, that the agent has not gone off break within thepredetermined time period following expiration of the predetermined break period, for causing the call center to register an exception against the agent.
means responsive to an agent's schedule which includes predetermined breaks scheduled for predetermined times, for determining at each scheduled break time whether an agent split to which the agent belongs is overloaded with work;
means responsive to a first determination at an individual predetermined time that the agent split is overloaded, for rescheduling the corresponding break to another time;
means responsive to said first determination for sending a message to the agent via a display of the agent's corresponding terminal that the break has been rescheduled;
means responsive to a second determination at an individual predetermined time that the agent split is not overloaded, for causing the call center to place the agent in a non-work state;
means responsive to the second determination for sending a message to the agent via the display informing the agent to go on break;
means responsive to the second determination and to expiration of a predetermined break period following the individual predetermined time, for sending a message to the agent via the display informing the agent to go off break;
means responsive to detection, from the agent's input on the agent's corresponding terminal, that the agent has gone off break within a predetermined time period following expiration of the predetermined break period, for causing the call center to place the agent in a work state; and means responsive to detection, from lack of the agent's said input on the agent's corresponding terminal, that the agent has not gone off break within thepredetermined time period following expiration of the predetermined break period, for causing the call center to register an exception against the agent.
14. A method of communicating with agents in a call center having a plurality of telecommunications terminals staffed by the agents, comprising the steps of:
in response to an agent's schedule which includes predetermined events scheduled for predetermined times, communicating each said event at its scheduled time to the agent via the agent's corresponding terminal; and monitoring the agent's performance of the communicated event at the scheduled time via the agent's input into the agent's corresponding terminal.
in response to an agent's schedule which includes predetermined events scheduled for predetermined times, communicating each said event at its scheduled time to the agent via the agent's corresponding terminal; and monitoring the agent's performance of the communicated event at the scheduled time via the agent's input into the agent's corresponding terminal.
15. The method of claim 14 wherein:
the step of communicating comprises the step of communicating the agent's schedule to the agent from a call-management system of the call center; and the step of monitoring comprises the step of monitoring the agent's adherence to the communicated schedule at the call-management system.
the step of communicating comprises the step of communicating the agent's schedule to the agent from a call-management system of the call center; and the step of monitoring comprises the step of monitoring the agent's adherence to the communicated schedule at the call-management system.
16. The method of claim 14 in a call center having a processor-implemented call management system, wherein:
the step of communicating comprises the step of executing a stored program on the call-management system processor to communicate each said event at its scheduled time to the agent; and the step of monitoring comprises the step of executing a stored program on the call management system processor to monitor the agent's performance of the communicated event at the scheduled time.
the step of communicating comprises the step of executing a stored program on the call-management system processor to communicate each said event at its scheduled time to the agent; and the step of monitoring comprises the step of executing a stored program on the call management system processor to monitor the agent's performance of the communicated event at the scheduled time.
17. The method of claim 14 wherein:
the step of communicating each said event comprises the step of causing at least one of an audio signal generator and a visual signal generator of the agent's corresponding terminal to generate at least one of an audio signal and a visual signal, respectively, to alert the agent to occurrence of the scheduled time for each said event.
the step of communicating each said event comprises the step of causing at least one of an audio signal generator and a visual signal generator of the agent's corresponding terminal to generate at least one of an audio signal and a visual signal, respectively, to alert the agent to occurrence of the scheduled time for each said event.
18. The method of claim 14 wherein:
the step of communicating each said event comprises the step of sending a display message indicating each said event at its scheduled time to a display of the agent's corresponding terminal.
the step of communicating each said event comprises the step of sending a display message indicating each said event at its scheduled time to a display of the agent's corresponding terminal.
19. The method of claim 18 wherein:
the step of communicating each said event further comprises the step of causing a speaker of the agent's corresponding terminal to produce an auditory signal when the display message is displayed on the display of the terminal.
the step of communicating each said event further comprises the step of causing a speaker of the agent's corresponding terminal to produce an auditory signal when the display message is displayed on the display of the terminal.
20. The method of claim 14 wherein:
the step of communicating each said event comprises the step of selectively causing the call center to place the agent in a non-work state substantially at the scheduled time.
the step of communicating each said event comprises the step of selectively causing the call center to place the agent in a non-work state substantially at the scheduled time.
21. The method of claim 14 wherein:
the step of monitoring comprises the step of in response to detection of the agent's performance of the communicated event, selectively causing the call center to place the agent in a work state.
the step of monitoring comprises the step of in response to detection of the agent's performance of the communicated event, selectively causing the call center to place the agent in a work state.
22. The method of claim 14 wherein:
the step of monitoring comprises the step of in response to detection of the agent's failure to perform the communicated event substantially at the scheduled time, causing the call center to register an exception against the agent.
the step of monitoring comprises the step of in response to detection of the agent's failure to perform the communicated event substantially at the scheduled time, causing the call center to register an exception against the agent.
23. A method of communicating with agents in a call center having a plurality of telecommunications terminals staffed by the agents, comprising the steps of:
communicating an agent's schedule to the agent via the agent's corresponding terminal;
monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal; and in response to receipt of a message and an identification of at least one agent intended to receive the message, sending the received message to the identified at least one agent via the identified at least one agent's corresponding terminal.
communicating an agent's schedule to the agent via the agent's corresponding terminal;
monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal; and in response to receipt of a message and an identification of at least one agent intended to receive the message, sending the received message to the identified at least one agent via the identified at least one agent's corresponding terminal.
24. A method of communicating with agents in a call center having a plurality of telecommunications terminals staffed by the agents, comprising the steps of:
communicating an agent's schedule to the agent via the agent's corresponding terminal;
monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal;
in response to receipt of criteria for moving an agent from one agent split to another, monitoring the call center for occurrence of the received criteria; andin response to detection of occurrence of the received criteria, moving an agent from the one split to the other split.
communicating an agent's schedule to the agent via the agent's corresponding terminal;
monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal;
in response to receipt of criteria for moving an agent from one agent split to another, monitoring the call center for occurrence of the received criteria; andin response to detection of occurrence of the received criteria, moving an agent from the one split to the other split.
25. A method of communicating with agents in a call center having a plurality of telecommunications terminals staffed by the agents, comprising the steps of:
communicating an agent's schedule to the agent via the agent's corresponding terminal;
monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal;
is response to detection of the agent's failure to adhere to the communicated schedule, causing the call center to register an exception against the agent;
in response to receipt of information characterizing exceptions meriting disablement of an agent, monitoring the call center for registration of the characterized exceptions; and in response to detection of registration of the characterized exceptions, causing the call center to place in a non-work state an agent against whom the characterized exceptions were registered.
communicating an agent's schedule to the agent via the agent's corresponding terminal;
monitoring the agent's adherence to the communicated schedule via the agent's corresponding terminal;
is response to detection of the agent's failure to adhere to the communicated schedule, causing the call center to register an exception against the agent;
in response to receipt of information characterizing exceptions meriting disablement of an agent, monitoring the call center for registration of the characterized exceptions; and in response to detection of registration of the characterized exceptions, causing the call center to place in a non-work state an agent against whom the characterized exceptions were registered.
26. A method of communicating with agents in a call center having a plurality of telecommunications terminals staffed by the agents, comprising:
in response to an agent's schedule which includes predetermined breaks scheduled for predetermined times, determining at each scheduled break time whether an agent split to which the agent belongs is overloaded with work;
in response to a first determination at an individual predetermined time that the agent split is overloaded, rescheduling the corresponding break to another time;
in response to said first determination, sending a message to the agent via a display of the agent's corresponding terminal that the break has been rescheduled;
in response to a second determination at an individual predetermined time that the agent split is not overloaded, causing the call center to place the agent in a non-work state;
in response to the second determination, sending a message to the agent via the display informing the agent to go on break;
in response to the second determination and to expiration of a predetermined break period following the individual predetermined time, sending a message to the agent via the display informing the agent to go off break;
in response to detection, from the agent's input on the agent's corresponding terminal, that the agent has gone off break within a predetermined time period following expiration of the predetermined break period, causing the call center to place the agent in a work state; and in response to detection, from lack of the agent's said input on the agent's corresponding terminal, that the agent has not gone off break within the predetermined time period following expiration of the predetermined break period, causing the call center to register an exception against the agent.
in response to an agent's schedule which includes predetermined breaks scheduled for predetermined times, determining at each scheduled break time whether an agent split to which the agent belongs is overloaded with work;
in response to a first determination at an individual predetermined time that the agent split is overloaded, rescheduling the corresponding break to another time;
in response to said first determination, sending a message to the agent via a display of the agent's corresponding terminal that the break has been rescheduled;
in response to a second determination at an individual predetermined time that the agent split is not overloaded, causing the call center to place the agent in a non-work state;
in response to the second determination, sending a message to the agent via the display informing the agent to go on break;
in response to the second determination and to expiration of a predetermined break period following the individual predetermined time, sending a message to the agent via the display informing the agent to go off break;
in response to detection, from the agent's input on the agent's corresponding terminal, that the agent has gone off break within a predetermined time period following expiration of the predetermined break period, causing the call center to place the agent in a work state; and in response to detection, from lack of the agent's said input on the agent's corresponding terminal, that the agent has not gone off break within the predetermined time period following expiration of the predetermined break period, causing the call center to register an exception against the agent.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/004,387 US5499291A (en) | 1993-01-14 | 1993-01-14 | Arrangement for automating call-center agent-schedule-notification and schedule-adherence functions |
US004,387 | 1993-01-14 |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2109274A1 CA2109274A1 (en) | 1994-07-15 |
CA2109274C true CA2109274C (en) | 1997-02-04 |
Family
ID=21710554
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002109274A Expired - Fee Related CA2109274C (en) | 1993-01-14 | 1993-10-26 | Arrangement for automating call-center agent-schedule-notification and schedule-adherence functions |
Country Status (5)
Country | Link |
---|---|
US (1) | US5499291A (en) |
EP (1) | EP0606719B1 (en) |
JP (1) | JP2925911B2 (en) |
CA (1) | CA2109274C (en) |
DE (1) | DE69321699T2 (en) |
Families Citing this family (191)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0865723A (en) * | 1994-08-25 | 1996-03-08 | Toshiba Corp | Key telephone system provided with automatic call distribution function |
US5621789A (en) * | 1993-09-01 | 1997-04-15 | Teknekron Infoswitch Corporation | Method and system for integrating a plurality of call center agent performance enhancement modules |
US5946375A (en) * | 1993-09-22 | 1999-08-31 | Teknekron Infoswitch Corporation | Method and system for monitoring call center service representatives |
AU693462B2 (en) * | 1993-09-22 | 1998-07-02 | E-Talk Corporation | Method and system for automatically monitoring the performance quality of call center service representatives |
US5784452A (en) * | 1994-06-01 | 1998-07-21 | Davox Corporation | Telephony call center with agent work groups |
US5546452A (en) | 1995-03-02 | 1996-08-13 | Geotel Communications Corp. | Communications system using a central controller to control at least one network and agent system |
US5815554A (en) * | 1995-05-24 | 1998-09-29 | Burgess; Ken L. | Method and system for indicating operator availability |
US5751795A (en) * | 1995-08-11 | 1998-05-12 | Lucent Technologies Inc. | Broadcasting of information through telephone switching system display messages |
JP3318484B2 (en) * | 1996-04-26 | 2002-08-26 | 富士通株式会社 | Group silent monitor control method |
US8861707B2 (en) * | 1996-05-31 | 2014-10-14 | Verint Americas Inc. | Method and apparatus for simultaneously monitoring computer user screen and telephone activity from a remote location |
US6370574B1 (en) * | 1996-05-31 | 2002-04-09 | Witness Systems, Inc. | Method and apparatus for simultaneously monitoring computer user screen and telephone activity from a remote location |
US5790798A (en) * | 1996-05-31 | 1998-08-04 | Witness Systems, Inc. | Method and apparatus for simultaneously monitoring computer user screen and telephone activity from a remote location |
US5721770A (en) * | 1996-07-02 | 1998-02-24 | Lucent Technologies Inc. | Agent vectoring programmably conditionally assigning agents to various tasks including tasks other than handling of waiting calls |
CA2262598C (en) * | 1996-08-06 | 2003-05-13 | Calvin W. Battle | Automatic call-work director |
US5822400A (en) * | 1996-08-19 | 1998-10-13 | Davox Corporation | Call record scheduling system and method |
US6263049B1 (en) * | 1996-10-10 | 2001-07-17 | Envision Telephony, Inc. | Non-random call center supervisory method and apparatus |
US6009162A (en) * | 1996-10-31 | 1999-12-28 | Lucent Technologies Inc. | Telecommunication feature for exchange of translation information between a computer and a telecommunication switching system |
US6005920A (en) * | 1997-01-03 | 1999-12-21 | Ncr Corporation | Call center with fault resilient server-switch link |
US5903641A (en) * | 1997-01-28 | 1999-05-11 | Lucent Technologies Inc. | Automatic dynamic changing of agents' call-handling assignments |
US6480600B1 (en) | 1997-02-10 | 2002-11-12 | Genesys Telecommunications Laboratories, Inc. | Call and data correspondence in a call-in center employing virtual restructuring for computer telephony integrated functionality |
US7031442B1 (en) | 1997-02-10 | 2006-04-18 | Genesys Telecommunications Laboratories, Inc. | Methods and apparatus for personal routing in computer-simulated telephony |
US6104802A (en) | 1997-02-10 | 2000-08-15 | Genesys Telecommunications Laboratories, Inc. | In-band signaling for routing |
JP4054399B2 (en) * | 1997-03-24 | 2008-02-27 | キヤノン株式会社 | Information processing apparatus and method |
US6782087B1 (en) | 1997-09-19 | 2004-08-24 | Mci Communications Corporation | Desktop telephony application program for a call center agent |
US6466663B1 (en) | 1997-09-30 | 2002-10-15 | Don Ravenscroft | Monitoring system client for a call center |
US6711611B2 (en) | 1998-09-11 | 2004-03-23 | Genesis Telecommunications Laboratories, Inc. | Method and apparatus for data-linking a mobile knowledge worker to home communication-center infrastructure |
US6985943B2 (en) | 1998-09-11 | 2006-01-10 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center |
US6490350B2 (en) | 1997-09-30 | 2002-12-03 | Mci Communications Corporation | Monitoring system for telephony resources in a call center |
USRE46528E1 (en) | 1997-11-14 | 2017-08-29 | Genesys Telecommunications Laboratories, Inc. | Implementation of call-center outbound dialing capability at a telephony network level |
US7907598B2 (en) | 1998-02-17 | 2011-03-15 | Genesys Telecommunication Laboratories, Inc. | Method for implementing and executing communication center routing strategies represented in extensible markup language |
US6332154B2 (en) | 1998-09-11 | 2001-12-18 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for providing media-independent self-help modules within a multimedia communication-center customer interface |
US7318046B1 (en) | 1998-03-05 | 2008-01-08 | American Management Systems, Inc. | Collector's account payment promise option advisory apparatus and method |
US6038542A (en) * | 1998-04-28 | 2000-03-14 | Micron Electronics, Inc. | System for notifying an individual of a previously scheduled event |
US6064976A (en) * | 1998-06-17 | 2000-05-16 | Intel Corporation | Scheduling system |
US6097806A (en) * | 1998-07-13 | 2000-08-01 | Rockwell Semiconductor Systems, Inc. | ACD with multi-lingual agent position |
USRE46153E1 (en) | 1998-09-11 | 2016-09-20 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment |
US6665395B1 (en) * | 1998-12-11 | 2003-12-16 | Avaya Technology Corp. | Automatic call distribution system using computer network-based communication |
US6356632B1 (en) * | 1998-12-31 | 2002-03-12 | Avaya Technology Corp. | Call selection and agent selection in a call center based on agent staffing schedule |
GB2349040B (en) | 1999-04-14 | 2003-09-03 | Mitel Corp | Adaptive feature behaviour |
US6493446B1 (en) | 1999-05-13 | 2002-12-10 | Willow Csn Incorporated | Call center posting program |
US7006994B1 (en) | 1999-07-16 | 2006-02-28 | American Management Systems, Inc. | Automated receivables management system |
US6594470B1 (en) | 1999-10-28 | 2003-07-15 | Nortel Networks Limited | System and method for remote management of call center operations |
US20080059277A1 (en) * | 1999-11-09 | 2008-03-06 | West Corporation | Proposing downtime adjustments to a work schedule |
US20080059278A1 (en) * | 1999-11-09 | 2008-03-06 | West Corporation | Offering uptime adjustments to a work schedule |
US8788308B1 (en) | 2004-03-29 | 2014-07-22 | West Corporation | Employee scheduling and schedule modification method and apparatus |
US20040202308A1 (en) * | 1999-11-16 | 2004-10-14 | Knowlagent, Inc. | Managing the selection of performance interventions in a contact center |
US20060233346A1 (en) * | 1999-11-16 | 2006-10-19 | Knowlagent, Inc. | Method and system for prioritizing performance interventions |
US20050175971A1 (en) * | 1999-11-16 | 2005-08-11 | Knowlagent, Inc., Alpharetta, Ga | Method and system for scheduled delivery of training to call center agents |
US20040202309A1 (en) * | 1999-11-16 | 2004-10-14 | Knowlagent, Inc. | Managing the rate of delivering performance interventions in a contact center |
US7929978B2 (en) | 1999-12-01 | 2011-04-19 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for providing enhanced communication capability for mobile devices on a virtual private network |
US7899180B2 (en) * | 2000-01-13 | 2011-03-01 | Verint Systems Inc. | System and method for analysing communications streams |
GB0000735D0 (en) | 2000-01-13 | 2000-03-08 | Eyretel Ltd | System and method for analysing communication streams |
US6959078B1 (en) * | 2000-01-24 | 2005-10-25 | Verint Systems Inc. | Apparatus and method for monitoring and adapting to environmental factors within a contact center |
US6775377B2 (en) * | 2001-09-10 | 2004-08-10 | Knowlagent, Inc. | Method and system for delivery of individualized training to call center agents |
JP3380519B2 (en) * | 2000-04-11 | 2003-02-24 | 川鉄情報システム株式会社 | Call center business consignment usage fee billing system |
US6956941B1 (en) * | 2000-04-12 | 2005-10-18 | Austin Logistics Incorporated | Method and system for scheduling inbound inquiries |
US7043193B1 (en) * | 2000-05-09 | 2006-05-09 | Knowlagent, Inc. | Versatile resource computer-based training system |
US7502460B2 (en) | 2006-11-20 | 2009-03-10 | Austin Logistics Incorporated | Method and system for distributing outbound telephone calls |
US7142662B2 (en) | 2000-07-11 | 2006-11-28 | Austin Logistics Incorporated | Method and system for distributing outbound telephone calls |
US7103173B2 (en) * | 2001-07-09 | 2006-09-05 | Austin Logistics Incorporated | System and method for preemptive goals based routing of contact records |
US7325190B1 (en) | 2000-10-02 | 2008-01-29 | Boehmer Tiffany D | Interface system and method of building rules and constraints for a resource scheduling system |
JP3585116B2 (en) * | 2000-10-26 | 2004-11-04 | 日本アイ・ビー・エム株式会社 | E-mail distribution system, customer service system, server system, e-mail distribution method |
GB0103381D0 (en) * | 2001-02-12 | 2001-03-28 | Eyretel Ltd | Packet data recording method and system |
US8015042B2 (en) * | 2001-04-02 | 2011-09-06 | Verint Americas Inc. | Methods for long-range contact center staff planning utilizing discrete event simulation |
US7155399B2 (en) | 2001-04-03 | 2006-12-26 | Witness Systems, Inc. | System and method for complex schedule generation |
US6952732B2 (en) | 2001-04-30 | 2005-10-04 | Blue Pumpkin Software, Inc. | Method and apparatus for multi-contact scheduling |
US6959405B2 (en) | 2001-04-18 | 2005-10-25 | Blue Pumpkin Software, Inc. | Method and system for concurrent error identification in resource scheduling |
US7054434B2 (en) * | 2001-07-09 | 2006-05-30 | Austin Logistics Incorporated | System and method for common account based routing of contact records |
US7715546B2 (en) * | 2001-07-09 | 2010-05-11 | Austin Logistics Incorporated | System and method for updating contact records |
US7174010B2 (en) * | 2001-11-05 | 2007-02-06 | Knowlagent, Inc. | System and method for increasing completion of training |
US7415417B2 (en) * | 2002-03-15 | 2008-08-19 | Avaya Technology Corp. | Presence awareness agent |
US7415605B2 (en) * | 2002-05-21 | 2008-08-19 | Bio-Key International, Inc. | Biometric identification network security |
GB0219493D0 (en) | 2002-08-21 | 2002-10-02 | Eyretel Plc | Method and system for communications monitoring |
US7646927B2 (en) * | 2002-09-19 | 2010-01-12 | Ricoh Company, Ltd. | Image processing and display scheme for rendering an image at high speed |
US6934380B2 (en) * | 2003-05-02 | 2005-08-23 | Cisco Technology, Inc. | Method and system for automatic contact distribution utilizing presence detection |
US8065618B2 (en) * | 2003-08-18 | 2011-11-22 | Sap Ag | Customization of an interaction center manager's graphical dashboard |
US7158628B2 (en) * | 2003-08-20 | 2007-01-02 | Knowlagent, Inc. | Method and system for selecting a preferred contact center agent based on agent proficiency and performance and contact center state |
US8094804B2 (en) * | 2003-09-26 | 2012-01-10 | Avaya Inc. | Method and apparatus for assessing the status of work waiting for service |
US8364509B1 (en) | 2003-09-30 | 2013-01-29 | West Corporation | Systems methods, and computer-readable media for gathering, tabulating, and reporting on employee performance |
US9137366B2 (en) * | 2004-03-29 | 2015-09-15 | West Corporation | Maintaining a work schedule |
US7734032B1 (en) | 2004-03-31 | 2010-06-08 | Avaya Inc. | Contact center and method for tracking and acting on one and done customer contacts |
US7953859B1 (en) | 2004-03-31 | 2011-05-31 | Avaya Inc. | Data model of participation in multi-channel and multi-party contacts |
US8000989B1 (en) | 2004-03-31 | 2011-08-16 | Avaya Inc. | Using true value in routing work items to resources |
US8738412B2 (en) * | 2004-07-13 | 2014-05-27 | Avaya Inc. | Method and apparatus for supporting individualized selection rules for resource allocation |
US7949121B1 (en) | 2004-09-27 | 2011-05-24 | Avaya Inc. | Method and apparatus for the simultaneous delivery of multiple contacts to an agent |
US8234141B1 (en) | 2004-09-27 | 2012-07-31 | Avaya Inc. | Dynamic work assignment strategies based on multiple aspects of agent proficiency |
US20060072739A1 (en) * | 2004-10-01 | 2006-04-06 | Knowlagent Inc. | Method and system for assessing and deploying personnel for roles in a contact center |
US20060256953A1 (en) * | 2005-05-12 | 2006-11-16 | Knowlagent, Inc. | Method and system for improving workforce performance in a contact center |
US7809127B2 (en) * | 2005-05-26 | 2010-10-05 | Avaya Inc. | Method for discovering problem agent behaviors |
US8503663B2 (en) * | 2005-06-30 | 2013-08-06 | Interactive Intelligence, Inc. | System and method for agent queue activation in a contact center |
US20070007331A1 (en) * | 2005-07-06 | 2007-01-11 | Verety Llc | Order processing apparatus and method |
US7779042B1 (en) | 2005-08-08 | 2010-08-17 | Avaya Inc. | Deferred control of surrogate key generation in a distributed processing architecture |
US7822587B1 (en) | 2005-10-03 | 2010-10-26 | Avaya Inc. | Hybrid database architecture for both maintaining and relaxing type 2 data entity behavior |
US7787609B1 (en) | 2005-10-06 | 2010-08-31 | Avaya Inc. | Prioritized service delivery based on presence and availability of interruptible enterprise resources with skills |
US7752230B2 (en) * | 2005-10-06 | 2010-07-06 | Avaya Inc. | Data extensibility using external database tables |
US9008075B2 (en) | 2005-12-22 | 2015-04-14 | Genesys Telecommunications Laboratories, Inc. | System and methods for improving interaction routing performance |
US8160233B2 (en) * | 2006-02-22 | 2012-04-17 | Verint Americas Inc. | System and method for detecting and displaying business transactions |
US8108237B2 (en) * | 2006-02-22 | 2012-01-31 | Verint Americas, Inc. | Systems for integrating contact center monitoring, training and scheduling |
US8112298B2 (en) * | 2006-02-22 | 2012-02-07 | Verint Americas, Inc. | Systems and methods for workforce optimization |
US8670552B2 (en) * | 2006-02-22 | 2014-03-11 | Verint Systems, Inc. | System and method for integrated display of multiple types of call agent data |
US8112306B2 (en) * | 2006-02-22 | 2012-02-07 | Verint Americas, Inc. | System and method for facilitating triggers and workflows in workforce optimization |
US20070206767A1 (en) * | 2006-02-22 | 2007-09-06 | Witness Systems, Inc. | System and method for integrated display of recorded interactions and call agent data |
US7853006B1 (en) | 2006-02-22 | 2010-12-14 | Verint Americas Inc. | Systems and methods for scheduling call center agents using quality data and correlation-based discovery |
US8117064B2 (en) * | 2006-02-22 | 2012-02-14 | Verint Americas, Inc. | Systems and methods for workforce optimization and analytics |
US7864946B1 (en) | 2006-02-22 | 2011-01-04 | Verint Americas Inc. | Systems and methods for scheduling call center agents using quality data and correlation-based discovery |
US7734783B1 (en) | 2006-03-21 | 2010-06-08 | Verint Americas Inc. | Systems and methods for determining allocations for distributed multi-site contact centers |
US8126134B1 (en) | 2006-03-30 | 2012-02-28 | Verint Americas, Inc. | Systems and methods for scheduling of outbound agents |
US8442033B2 (en) | 2006-03-31 | 2013-05-14 | Verint Americas, Inc. | Distributed voice over internet protocol recording |
US20070237525A1 (en) * | 2006-03-31 | 2007-10-11 | Witness Systems, Inc. | Systems and methods for modular capturing various communication signals |
US7792278B2 (en) | 2006-03-31 | 2010-09-07 | Verint Americas Inc. | Integration of contact center surveys |
US8594313B2 (en) | 2006-03-31 | 2013-11-26 | Verint Systems, Inc. | Systems and methods for endpoint recording using phones |
US8000465B2 (en) * | 2006-03-31 | 2011-08-16 | Verint Americas, Inc. | Systems and methods for endpoint recording using gateways |
US7826608B1 (en) | 2006-03-31 | 2010-11-02 | Verint Americas Inc. | Systems and methods for calculating workforce staffing statistics |
US8204056B2 (en) | 2006-03-31 | 2012-06-19 | Verint Americas, Inc. | Systems and methods for endpoint recording using a media application server |
US8130938B2 (en) | 2006-03-31 | 2012-03-06 | Verint Americas, Inc. | Systems and methods for endpoint recording using recorders |
US7852994B1 (en) | 2006-03-31 | 2010-12-14 | Verint Americas Inc. | Systems and methods for recording audio |
US7672746B1 (en) | 2006-03-31 | 2010-03-02 | Verint Americas Inc. | Systems and methods for automatic scheduling of a workforce |
US7774854B1 (en) | 2006-03-31 | 2010-08-10 | Verint Americas Inc. | Systems and methods for protecting information |
US7822018B2 (en) * | 2006-03-31 | 2010-10-26 | Verint Americas Inc. | Duplicate media stream |
US8254262B1 (en) | 2006-03-31 | 2012-08-28 | Verint Americas, Inc. | Passive recording and load balancing |
US7995612B2 (en) * | 2006-03-31 | 2011-08-09 | Verint Americas, Inc. | Systems and methods for capturing communication signals [32-bit or 128-bit addresses] |
US7701972B1 (en) | 2006-03-31 | 2010-04-20 | Verint Americas Inc. | Internet protocol analyzing |
US7680264B2 (en) * | 2006-03-31 | 2010-03-16 | Verint Americas Inc. | Systems and methods for endpoint recording using a conference bridge |
US7633930B2 (en) | 2006-03-31 | 2009-12-15 | Verint Americas Inc. | Systems and methods for capturing multimedia communication signals |
US8155275B1 (en) | 2006-04-03 | 2012-04-10 | Verint Americas, Inc. | Systems and methods for managing alarms from recorders |
US20070255611A1 (en) * | 2006-04-26 | 2007-11-01 | Csaba Mezo | Order distributor |
US8331549B2 (en) * | 2006-05-01 | 2012-12-11 | Verint Americas Inc. | System and method for integrated workforce and quality management |
US8396732B1 (en) | 2006-05-08 | 2013-03-12 | Verint Americas Inc. | System and method for integrated workforce and analytics |
US7817795B2 (en) * | 2006-05-10 | 2010-10-19 | Verint Americas, Inc. | Systems and methods for data synchronization in a customer center |
US20070282807A1 (en) * | 2006-05-10 | 2007-12-06 | John Ringelman | Systems and methods for contact center analysis |
US7747745B2 (en) * | 2006-06-16 | 2010-06-29 | Almondnet, Inc. | Media properties selection method and system based on expected profit from profile-based ad delivery |
US7660407B2 (en) | 2006-06-27 | 2010-02-09 | Verint Americas Inc. | Systems and methods for scheduling contact center agents |
US7660406B2 (en) * | 2006-06-27 | 2010-02-09 | Verint Americas Inc. | Systems and methods for integrating outsourcers |
US20070297578A1 (en) * | 2006-06-27 | 2007-12-27 | Witness Systems, Inc. | Hybrid recording of communications |
US7660307B2 (en) * | 2006-06-29 | 2010-02-09 | Verint Americas Inc. | Systems and methods for providing recording as a network service |
US7903568B2 (en) * | 2006-06-29 | 2011-03-08 | Verint Americas Inc. | Systems and methods for providing recording as a network service |
US7966397B2 (en) | 2006-06-30 | 2011-06-21 | Verint Americas Inc. | Distributive data capture |
US8131578B2 (en) * | 2006-06-30 | 2012-03-06 | Verint Americas Inc. | Systems and methods for automatic scheduling of a workforce |
US20080004945A1 (en) * | 2006-06-30 | 2008-01-03 | Joe Watson | Automated scoring of interactions |
US7769176B2 (en) * | 2006-06-30 | 2010-08-03 | Verint Americas Inc. | Systems and methods for a secure recording environment |
US7953621B2 (en) | 2006-06-30 | 2011-05-31 | Verint Americas Inc. | Systems and methods for displaying agent activity exceptions |
US7848524B2 (en) * | 2006-06-30 | 2010-12-07 | Verint Americas Inc. | Systems and methods for a secure recording environment |
US7853800B2 (en) | 2006-06-30 | 2010-12-14 | Verint Americas Inc. | Systems and methods for a secure recording environment |
US7936867B1 (en) | 2006-08-15 | 2011-05-03 | Avaya Inc. | Multi-service request within a contact center |
US8391463B1 (en) | 2006-09-01 | 2013-03-05 | Avaya Inc. | Method and apparatus for identifying related contacts |
US8811597B1 (en) | 2006-09-07 | 2014-08-19 | Avaya Inc. | Contact center performance prediction |
US8938063B1 (en) | 2006-09-07 | 2015-01-20 | Avaya Inc. | Contact center service monitoring and correcting |
US7953750B1 (en) | 2006-09-28 | 2011-05-31 | Verint Americas, Inc. | Systems and methods for storing and searching data in a customer center environment |
US7930314B2 (en) * | 2006-09-28 | 2011-04-19 | Verint Americas Inc. | Systems and methods for storing and searching data in a customer center environment |
US7873156B1 (en) | 2006-09-29 | 2011-01-18 | Verint Americas Inc. | Systems and methods for analyzing contact center interactions |
US8068602B1 (en) | 2006-09-29 | 2011-11-29 | Verint Americas, Inc. | Systems and methods for recording using virtual machines |
US7613290B2 (en) * | 2006-09-29 | 2009-11-03 | Verint Americas Inc. | Recording using proxy servers |
US7899178B2 (en) * | 2006-09-29 | 2011-03-01 | Verint Americas Inc. | Recording invocation of communication sessions |
US7965828B2 (en) | 2006-09-29 | 2011-06-21 | Verint Americas Inc. | Call control presence |
US20080080685A1 (en) * | 2006-09-29 | 2008-04-03 | Witness Systems, Inc. | Systems and Methods for Recording in a Contact Center Environment |
US20080082387A1 (en) * | 2006-09-29 | 2008-04-03 | Swati Tewari | Systems and methods or partial shift swapping |
US8005676B2 (en) * | 2006-09-29 | 2011-08-23 | Verint Americas, Inc. | Speech analysis using statistical learning |
US8645179B2 (en) * | 2006-09-29 | 2014-02-04 | Verint Americas Inc. | Systems and methods of partial shift swapping |
US7570755B2 (en) | 2006-09-29 | 2009-08-04 | Verint Americas Inc. | Routine communication sessions for recording |
US7991613B2 (en) | 2006-09-29 | 2011-08-02 | Verint Americas Inc. | Analyzing audio components and generating text with integrated additional session information |
US8199886B2 (en) * | 2006-09-29 | 2012-06-12 | Verint Americas, Inc. | Call control recording |
US7752043B2 (en) | 2006-09-29 | 2010-07-06 | Verint Americas Inc. | Multi-pass speech analytics |
US7920482B2 (en) | 2006-09-29 | 2011-04-05 | Verint Americas Inc. | Systems and methods for monitoring information corresponding to communication sessions |
US7899176B1 (en) | 2006-09-29 | 2011-03-01 | Verint Americas Inc. | Systems and methods for discovering customer center information |
US8837697B2 (en) * | 2006-09-29 | 2014-09-16 | Verint Americas Inc. | Call control presence and recording |
US7881216B2 (en) * | 2006-09-29 | 2011-02-01 | Verint Systems Inc. | Systems and methods for analyzing communication sessions using fragments |
US7885813B2 (en) * | 2006-09-29 | 2011-02-08 | Verint Systems Inc. | Systems and methods for analyzing communication sessions |
US8130926B2 (en) * | 2006-12-08 | 2012-03-06 | Verint Americas, Inc. | Systems and methods for recording data |
US8130925B2 (en) * | 2006-12-08 | 2012-03-06 | Verint Americas, Inc. | Systems and methods for recording |
US8280011B2 (en) * | 2006-12-08 | 2012-10-02 | Verint Americas, Inc. | Recording in a distributed environment |
US20080137814A1 (en) * | 2006-12-07 | 2008-06-12 | Jamie Richard Williams | Systems and Methods for Replaying Recorded Data |
US20080244686A1 (en) * | 2007-03-27 | 2008-10-02 | Witness Systems, Inc. | Systems and Methods for Enhancing Security of Files |
US8743730B2 (en) * | 2007-03-30 | 2014-06-03 | Verint Americas Inc. | Systems and methods for recording resource association for a communications environment |
US9106737B2 (en) * | 2007-03-30 | 2015-08-11 | Verint Americas, Inc. | Systems and methods for recording resource association for recording |
US8170184B2 (en) | 2007-03-30 | 2012-05-01 | Verint Americas, Inc. | Systems and methods for recording resource association in a recording environment |
US8437465B1 (en) | 2007-03-30 | 2013-05-07 | Verint Americas, Inc. | Systems and methods for capturing communications data |
US20080300955A1 (en) * | 2007-05-30 | 2008-12-04 | Edward Hamilton | System and Method for Multi-Week Scheduling |
US8315901B2 (en) * | 2007-05-30 | 2012-11-20 | Verint Systems Inc. | Systems and methods of automatically scheduling a workforce |
US20080300963A1 (en) * | 2007-05-30 | 2008-12-04 | Krithika Seetharaman | System and Method for Long Term Forecasting |
US8504534B1 (en) | 2007-09-26 | 2013-08-06 | Avaya Inc. | Database structures and administration techniques for generalized localization of database items |
US8079066B1 (en) | 2007-11-20 | 2011-12-13 | West Corporation | Multi-domain login and messaging |
US8856182B2 (en) | 2008-01-25 | 2014-10-07 | Avaya Inc. | Report database dependency tracing through business intelligence metadata |
US8401155B1 (en) | 2008-05-23 | 2013-03-19 | Verint Americas, Inc. | Systems and methods for secure recording in a customer center environment |
US8719016B1 (en) | 2009-04-07 | 2014-05-06 | Verint Americas Inc. | Speech analytics system and system and method for determining structured speech |
IL199115A (en) * | 2009-06-03 | 2013-06-27 | Verint Systems Ltd | Systems and methods for efficient keyword spotting in communication traffic |
US8565386B2 (en) * | 2009-09-29 | 2013-10-22 | Avaya Inc. | Automatic configuration of soft phones that are usable in conjunction with special-purpose endpoints |
US10115065B1 (en) | 2009-10-30 | 2018-10-30 | Verint Americas Inc. | Systems and methods for automatic scheduling of a workforce |
US9516069B2 (en) * | 2009-11-17 | 2016-12-06 | Avaya Inc. | Packet headers as a trigger for automatic activation of special-purpose softphone applications |
US20110191134A1 (en) * | 2010-02-03 | 2011-08-04 | Mukul Jain | Contact offer time for agents supporting contact centers |
US8644489B1 (en) | 2013-03-15 | 2014-02-04 | Noble Systems Corporation | Forced schedule adherence for contact center agents |
US11244317B2 (en) | 2015-11-03 | 2022-02-08 | Mastercard International Incorporated | Systems and methods for feeding a previous case action for a decision of confirming financial transactions |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS58104047U (en) * | 1982-01-07 | 1983-07-15 | 日本電気株式会社 | relay stand |
JPH06101864B2 (en) * | 1986-04-30 | 1994-12-12 | 株式会社東芝 | Mode switching system for relay stations of private branch exchanges |
JPS62255053A (en) * | 1986-04-30 | 1987-11-06 | Toshiba Corp | Process controller |
JPS6376555A (en) * | 1986-09-19 | 1988-04-06 | Nec Corp | Abnormal operation detecting system for telephone exchange operator |
US4807154A (en) * | 1987-01-29 | 1989-02-21 | International Business Machines Corporation | Method for developing automatic replies in an interactive electronic calendaring system |
JPS6458462A (en) * | 1987-08-26 | 1989-03-06 | Hitachi Ltd | Production instruction system |
CH674910A5 (en) * | 1987-11-27 | 1990-07-31 | Francois Joseph Camperio | |
JPH01320517A (en) * | 1988-06-22 | 1989-12-26 | Mitsubishi Electric Corp | Work managing device for display terminal equipment |
US4988209A (en) * | 1988-12-29 | 1991-01-29 | At&T Bell Laboratories | Telephone agent management information system |
JPH0320896A (en) * | 1989-06-19 | 1991-01-29 | Casio Comput Co Ltd | Managing device for person in charge |
JPH0349349A (en) * | 1989-07-17 | 1991-03-04 | Nec Corp | Line holding system |
US5111391A (en) * | 1989-10-05 | 1992-05-05 | Mrs. Fields, Inc. | System and method for making staff schedules as a function of available resources as well as employee skill level, availability and priority |
JPH0463095A (en) * | 1990-06-29 | 1992-02-28 | Fujitsu Ltd | Message processing system for call information processing system |
US5289368A (en) * | 1990-10-12 | 1994-02-22 | Iex Corporation | Force management system user interface |
AU8907691A (en) * | 1990-10-12 | 1992-05-20 | Iex Corporation | Method and system for planning, scheduling and managing personnel |
JPH04253460A (en) * | 1991-01-30 | 1992-09-09 | Nec Corp | Called party schedule display system |
-
1993
- 1993-01-14 US US08/004,387 patent/US5499291A/en not_active Expired - Lifetime
- 1993-10-26 CA CA002109274A patent/CA2109274C/en not_active Expired - Fee Related
- 1993-12-06 EP EP93309759A patent/EP0606719B1/en not_active Expired - Lifetime
- 1993-12-06 DE DE69321699T patent/DE69321699T2/en not_active Expired - Fee Related
-
1994
- 1994-01-11 JP JP6012272A patent/JP2925911B2/en not_active Expired - Fee Related
Also Published As
Publication number | Publication date |
---|---|
EP0606719B1 (en) | 1998-10-21 |
DE69321699D1 (en) | 1998-11-26 |
JPH06261129A (en) | 1994-09-16 |
US5499291A (en) | 1996-03-12 |
EP0606719A1 (en) | 1994-07-20 |
DE69321699T2 (en) | 1999-06-10 |
JP2925911B2 (en) | 1999-07-28 |
CA2109274A1 (en) | 1994-07-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2109274C (en) | Arrangement for automating call-center agent-schedule-notification and schedule-adherence functions | |
US5592543A (en) | Method and system for allocating agent resources to a telephone call campaign | |
US6766012B1 (en) | System and method for allocating agent resources to a telephone call campaign based on agent productivity | |
US5247569A (en) | System and method for controlling outbound and inbound calls in a telephone communication system | |
EP0429770B1 (en) | Switchless automatic call distribution system | |
US5715306A (en) | Automatic call distribution system with user definable logging and method therefor | |
US6751310B1 (en) | System and method for prioritizing telephone call campaigns based on campaign productivity | |
US5274700A (en) | Methods of automatically rerouting an incoming telephone call placed over a network | |
US7050568B2 (en) | Hold queue management | |
US5436967A (en) | Held party call-back arrangement | |
US6128380A (en) | Automatic call distribution and training system | |
US5832059A (en) | Call path system and method for modeling and modifying a call path of a telephone call routed by a telephone switch | |
KR100359586B1 (en) | Automatic call distribution method and apparatus | |
US5511112A (en) | Automated voice system for improving agent efficiency and improving service to parties on hold | |
US5168515A (en) | Switchless automatic call distribution system | |
CA2210710C (en) | Teleworking arrangements | |
US6959079B2 (en) | Telephone call monitoring system | |
US6353667B1 (en) | Minimum interruption cycle time threshold for reserve call center agents | |
US5555297A (en) | Automatic call distributor reporting system and method therefor | |
JPH10504425A (en) | Equipment for monitoring automatic call distribution telephone systems | |
JPH0690284A (en) | Method and system for monitoring of usage of telephone | |
US6574329B2 (en) | Incoming call processing method, incoming call processing apparatus, and computer-readable recording medium having an incoming call processing program recorded thereon | |
Harvey et al. | Call center solutions | |
US5546454A (en) | Automatic call distributor with telephonic call holding system | |
CN111050003A (en) | Operation and maintenance call center system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKLA | Lapsed |