US20100172485A1 - Systems and methods for determining allocations for distributed multi-site contact centers - Google Patents
Systems and methods for determining allocations for distributed multi-site contact centers Download PDFInfo
- Publication number
- US20100172485A1 US20100172485A1 US12/725,127 US72512710A US2010172485A1 US 20100172485 A1 US20100172485 A1 US 20100172485A1 US 72512710 A US72512710 A US 72512710A US 2010172485 A1 US2010172485 A1 US 2010172485A1
- Authority
- US
- United States
- Prior art keywords
- contact center
- sub
- distributed
- centers
- events
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1021—Server selection for load balancing based on client or server locations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- 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
- 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
Definitions
- the present invention is generally related to contact center allocation of resources.
- Telephone call center resource allocation and scheduling is an example of a problem with a large number of variables. Variables include contact volume at a particular time of day, available staff, skills of various staff members, call type (e.g., new order call and customer service call), and number of call queues, where a call queue may be assigned a particular call type.
- call type e.g., new order call and customer service call
- number of call queues where a call queue may be assigned a particular call type.
- a basic goal of call center scheduling is to minimize the cost of agents available to answer calls while maximizing service.
- call center scheduling is performed by forecasting incoming contact volumes and estimating average talk times for each time period based on past history and other measures. These values are then correlated to produce a schedule.
- many schedules need to be evaluated.
- a multi-contact call center may handle telephone, email, web callback, web chat, fax, and voice over internet protocol. Therefore, in addition to variation in the types of calls (e.g., service call, order call), modern contact centers have the complication of variation in contact media. The variation in contact media adds complexity to the agent scheduling process.
- multiple geographically distributed call centers may be owned by a single organization, or calls may be distributed to multiple locations depending on whether a contact is for technical support, sales, etc.
- an exemplary embodiment of such a method comprises: creating a workload forecast, such as contact volume and average handle, resolution, interaction and/or order/purchase fulfillment time, of events for a specified time frame, such as hours, days, week, months, quarters and/or years, as if the geographically distributed sites were co-located, performing discrete event-based simulation to assign the events to the contact center resource(s) as if at least a portion of the total contact center resources were co-located, and determining recommended allocations of the contact center resources among the geographically distributed sites based on a relative distribution of events expected, forecasted, simulated or assigned to contact center resources at each of the geographically distributed sites.
- requirements can further include other operational constraints of the sites, including, for example, network bandwidth.
- An exemplary embodiment of a system for allocating contact/support center resources such as agents, servers, computers, databases, recorders (including, among others, TDM, VoIP and/or wireless recorders), administrative staff, customer services personnel, supervisors, managers, marketers, cross-sellers, supplies and other logistical resources involved in the operations of point of contact centers, including contact or customer support centers, back office or support centers, retailing and banking centers, comprises: a forecasting system configured to create a workload forecast, such as volume, peak time, low time, average volume, static and dynamic volume, including requirements per hour (including minutes and seconds), day, week, month, quarter and/or year, with such requirement including, for example, voice, messenger chat, email, and direct contact channels of communication, and average handle, resolution and/or transactional time forecast of events for a specified or predetermined time frame, schedule and/or campaign, as if the geographically distributed resources or sites were co-located, a simulation system configured to perform discrete event-based simulation to assign the events to the resource(s) (for example, contact center agents)
- FIG. 1 is a schematic diagram illustrating an exemplary embodiment of a system for distributing events, such as contact/support center events, according to recommended allocations of resources, such as contact center agents.
- FIG. 2 is a schematic diagram illustrating an embodiment of a computer-implemented system that can be used for determining recommended allocations of resources, such as contact center agents, utilized in FIG. 1 .
- FIG. 3 is a flowchart illustrating functionality (or method steps) that can be performed by an embodiment of a system according to FIG. 2 to create recommended allocations of resources, such as contact center agents, for use in the system of FIG. 1 .
- FIG. 4 is a diagram illustrating a distributed campaign according to FIG. 3 .
- FIG. 5 is a diagram illustrating a sub-campaign from FIG. 4 .
- FIG. 6 is a flowchart illustrating determination of recommended allocations by the system in FIG. 2 .
- FIG. 7 is a flowchart illustrating the multi-scheduling algorithm of FIG. 6 .
- FIG. 8 is a flowchart illustrating the calculation of sub-campaign allocations of FIG. 6 .
- FIG. 9 is a flowchart illustrating the discrete event-based simulation of FIG. 8 .
- the allocation of resources can be achieved using discrete event-based simulations that perform allocations on multiple distributed sites as if the resources were not distributed.
- Recommended allocations are based on a relative distribution, e.g. percentages, of events, such as customer calls, inquiries, purchases and other transactional and operational events, for each site in accordance with the resource to which the simulation assigned the events.
- the systems and methods of the present invention can be deployed or utilized in allocating contact/support center resources, such as agents, servers, computers, databases, recorders (including, among others, TDM, VoIP and/or wireless recorders), administrative staff, customer services personnel, supervisors, managers, marketers, cross-sellers, supplies and other logistical resources involved in the operations of point of contact centers, including contact or customer support centers, back office or support centers, retailing and banking centers.
- contact/support center resources such as agents, servers, computers, databases, recorders (including, among others, TDM, VoIP and/or wireless recorders), administrative staff, customer services personnel, supervisors, managers, marketers, cross-sellers, supplies and other logistical resources involved in the operations of point of contact centers, including contact or customer support centers, back office or support centers, retailing and banking centers.
- An ideal system for distributing events to multiple sites would be a system that could analyze every available site for any available resource located at any of the available sites. After location of an available resource, such a system would route the event to that resource regardless of that resource's geographical location.
- the contact center is a virtual center, the system would distribute events as if the contact center were one large contact center. Such efficiency, however, is difficult to attain.
- contact centers operate on preset allocations of events for a particular time frame. The equipment costs for analyzing all available sites and routing events accordingly can be very expensive. By comparison, equipment costs for routing defined percentages of events is currently preferable. With preset allocations, a distributed site essentially operates as an independent site that knows what volume of events to expect and, thus, is able to schedule staffing, and other resources, accordingly.
- the disclosed systems for determining allocations for distributed multi-site contact centers provide recommended allocations of contact center resources, such as agents, based on simulations that utilize virtual contact centers.
- Statistical information based on existing work flow management (WFM) data are used to create a workload forecast of events for contact volume data and average handle times.
- a contact volume forecast is the number of events forecast for a certain time interval.
- An average handle time forecast is the response time required per event.
- randomly distributed contact arrival events are created based on the WFM data.
- a discrete event-based simulation then routes the events to available agents as if they were assigned to a non-distributed or virtual contact center. Recommended allocations for the various sites are then calculated based on the agents to which the events were assigned.
- FIG. 1 is a schematic diagram illustrating an exemplary embodiment of a system for distributing events according to recommended allocations of resources, such as contact center agents.
- the system 100 comprises one or more customer premises 102 .
- the customer premise 102 includes, for example but not limited to, telephones, cellular phones and computing devices.
- Customer premises 102 communicate with a network 106 (e.g., PSTN and/or cellular) that communicates with a contact center 110 .
- the contact center 110 is shown connected through a network 112 (e.g., local area network (LAN) or wide area network (WAN) or virtual private network (VPN)) to various sub-centers 114 , 116 and 118 .
- LAN local area network
- WAN wide area network
- VPN virtual private network
- Each sub-center 114 , 116 and 118 has multiple contact center agents 120 , 122 , 124 , 126 , 128 , 130 , 132 , 134 and 136 . It should be noted that the number of sub-centers 114 , 116 and 118 , may vary according to the requirements of the contact center 110 . Typically, there will be at least two sites (sub-centers). Of course, the number of contact center agents 120 et al., will also vary according to the recommended allocations for each sub-center 114 , 116 , 118 . Hereafter, unless two different contact center agents are discussed, references to a generic contact center agent or to generic contact center agents will refer to contact center agent 120 .
- contact center agents 120 could just as likely be servers, computers, databases, recorders (including, among others, TDM, VoIp and/or wireless recorders), administrative staff, customer services personnel, supervisors, managers, marketers, cross-sellers, supplies and other logistical resources involved in the operations of point of contact centers, including contact or customer support centers, back office or support centers, retailing and banking centers.
- recorders including, among others, TDM, VoIp and/or wireless recorders
- a contact center agent 120 utilizes computing devices (not shown) such as, for instance, desktop computers (PCs) or Macintosh computers that can, if necessary, be connected to communication devices, such as a headset, microphones, and headphones, among others.
- computing devices such as, for instance, desktop computers (PCs) or Macintosh computers that can, if necessary, be connected to communication devices, such as a headset, microphones, and headphones, among others.
- FIG. 2 is a schematic diagram illustrating an exemplary embodiment of a computer-implemented allocation system 111 that can be used for determining recommended allocations of contact center agents 120 .
- the allocation system 111 could be located in the contact center 110 or at a location connected to the contact center via a network such as the network 112 or the Internet, among others.
- the allocation system 111 includes a processing device 138 , memory 140 , user interface devices 148 , input/output devices (I/O) 150 and networking devices 152 , each of which is connected to local interface 146 .
- the local interface can include, for example but not limited to, one or more buses or other wired or wireless connections.
- the local interface may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, the local interface may include address, control, and/or data connections to enable appropriate communications among aforementioned components.
- the processor may be a hardware device for executing software, particularly software stored in memory.
- the processing device 138 can be any custom made or commercially available processor, a central processing unit (CPU) or an auxiliary processor among several processors associated with the allocation system 111 , a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing software instructions.
- suitable commercially available microprocessors are as follows: a PA-RISC series microprocessor from Hewlett-Packard® Company, an 80 ⁇ 86 or Pentium® series microprocessor from Intel® Corporation, a PowerPC® microprocessor from IBM®, a Sparc® microprocessor from Sun Microsystems®, Inc, or a 68xxx series microprocessor from Motorola® Corporation.
- the memory can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, the memory may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory (as well as various other components) can have a distributed architecture, where various components are situated remote from one another, but can be accessed by the processing device 138 . Additionally, memory 140 can also include an operating system 142 , as well as instructions associated with various subsystems, such as a multi-site allocation recommendation system 144 .
- the software in memory 140 may include one or more separate programs, each of which includes an ordered listing of executable instructions for implementing logical functions.
- suitable commercially available operating systems is as follows: (a) a Windows® operating system available from Microsoft® Corporation; (b) a Netware® operating system available from Novell®, Inc.; (c) a Macintosh® operating system available from Apple® Computer, Inc.; (d) a UNIX operating system, which is available for purchase from many vendors, such as the Hewlett-Packard® Company, Sun Microsystems®, Inc., and AT&T® Corporation; (e) a LINUX operating system, which is freeware that is readily available on the Internet 100; (f) a run time Vxworks® operating system from WindRiver® Systems, Inc.; or (g) an appliance-based operating system, such as that implemented in handheld computers or personal data assistants (PDAs) (e.g., PalmOS® available from Palm® Computing, Inc.,
- PDAs personal data assistants
- a system component embodied as software may also be construed as a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed.
- the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the memory 140 , so as to operate properly in connection with the operating system 142 .
- the processing device 138 When the allocation system 111 is in operation, the processing device 138 is configured to execute software stored within the memory 140 , to communicate data to and from the memory 140 , and to generally control operations of the allocation system 111 pursuant to the software.
- Software in memory 140 in whole or in part, is read by the processing device 138 , perhaps buffered, and then executed.
- the allocation system 111 accesses WFM data from a WFM database 154 through I/O device 150 .
- Multi-site allocation recommendations 144 are determined and made available to the contact center 110 through a networking device 152 .
- FIG. 3 is a flowchart illustrating functionality associated with the embodiment of the system of FIG. 2 .
- the functionality depicted in FIG. 3 is associated with the multi-site allocation recommendations system 144 .
- the functionality begins by assimilating WFM data 160 from forecasted call volume data 156 and other site data 158 . Examples of other site data would include employees, work schedules, time off preferences, event type priorities, etc.
- the WFM data could be retrieved from a WFM database 154 (see FIG. 2 ) and processed by the processing device 138 (see FIG. 2 ) for use in the multi-site allocation recommendations system 144 .
- Forecasted contact volume data 156 is made up of a contact volume for some period of time and an average interaction time forecast.
- a contact volume forecast could be the reception of 25 customer support calls over a 15 minute window from 9:00 A.M. to 9:15 A.M.
- the time window could, of course be adjusted to suit the particular circumstance and/or other requirements.
- Average interaction time forecast could be that an average sales call requires two minutes and forty-five seconds of contact center agent 120 support.
- different type events would require different levels of interaction time and/or follow-up time that could also be included in the forecast.
- the contact volume and average interaction time forecast is an attempt to forecast the total incoming contact volume and the total time required to handle that contact volume at the top level, being the distributed centralized level.
- the WFM history available enables the allocation system 111 to forecast the incoming workload that must be distributed to the available sub-centers 114 , 116 and 118 .
- Block 162 shows the creation of distributed queues, sub-queues and distributed campaigns.
- a distributed campaign is an entire operation, while a distributed queue includes events related to that operation.
- a distributed campaign could have more than one distributed queue.
- sub-campaigns are created for each distributed campaign.
- Sub-campaigns are a portion of the entire operation including sub-queues and employees.
- Sub-queues are derived from a distributed queue and are a stream of events routed to a particular sub-center. An event from the sub-queue is distributed to the employees or agents available to handle that event.
- the sub-queues, skills, organizations and employees are linked to that sub-campaign.
- the multi-site algorithm is applied in block 168 .
- Sub-campaigns comprise various sub-queues as input streams of events to a sub-center and the contact center agents assigned to that sub-center.
- the queues overlap with the campaigns based on agent availability and capability.
- FIG. 4 illustrates an example of a distributed campaign such as created in block 162 .
- One or more distributed queues 170 , 172 stream into the contact center 110 .
- a distributed queue 170 , 172 is a centralized incoming stream of events coming into the contact center 110 to be distributed to some sub-center 114 , 116 , 118 .
- the event could be a phone call, voice over internet protocol or email, among others.
- FIG. 4 shows events distributed to sub-center 114 through sub-queues 174 , 176 . Likewise events are shown distributed to sub-center 116 through sub-queues 178 , 180 and events are shown distributed to sub-center 118 through sub-queue 182 .
- distributed queue 170 could include phone calls for customer support and the contact center agents 120 specializing in customer support might be located at sub-center 114 and at sub-center 116 .
- the customer support events would be routed through sub-queue 174 to sub-center 114 and through sub-queue 178 to sub-center 116 .
- the customer support events might be directed toward different types of support issues, for example installation issues and technical support issues.
- the sub-queues could be directed toward specific types of events. Installation issues could be routed through sub-queue 174 to sub-center 114 and sub-queue 178 to sub-center 116 .
- a contact center agent 120 at each sub-center would receive events related to their specific skill-set.
- a contact center agent 120 could have multiple skill-sets such that a single contact center agent 120 could handle events related to both installation issues and technical support issues in this example.
- distributed queue 172 could include phone calls for sales and the contact center agent(s) 120 specializing in sales might be located at sub-center 118 . The sales events would be routed through sub-queue 182 to sub-center 118 .
- FIG. 5 illustrates a sub-campaign as created in block 164 .
- One or more sub-queues 174 , 176 stream into the sub-center 114 .
- a sub-queue 174 , 176 is a centralized incoming stream of events coming into the sub-center 114 to be distributed to contact center agents 120 , 122 and 124 .
- the number of contact center agents 120 varies with each contact center in accordance with actual and recommended allocations.
- FIG. 5 shows events 184 , 186 distributed to contact center agent 120 .
- events 188 are shown distributed to contact center agent 122 and events 190 , 192 are shown distributed to contact center agent 124 .
- a sub-center 114 can receive different streams of events, for example, from sub-queue 174 and sub queue 176 , and a contact center agent 120 can receive events from a single sub-queue 174 or from multiple sub-queues 174 , 176 .
- event 184 to contact center agent 120 could derive from sub-queue 174 while event 186 could derive from sub-queue 176 .
- FIG. 6 is a flowchart illustrating an exemplary process for determination of recommended allocations by the allocation system 111 in FIG. 2 . Specifically, the functionality depicted in FIG. 6 provides greater detail of the flowchart in FIG. 3 associated with the multi-site allocation recommendations system 144 .
- distributed queues sub-queues and distributed campaigns are created.
- sub-campaigns are created for each distributed campaign.
- the sub-queues, skills, organizations and employees are linked to that sub-campaign.
- the WFM data 160 is used to create contact volume, average interaction time forecasts and service goals in block 194 for the distributed campaign.
- the forecast is for total incoming event volume and the total time it will take to handle that event volume at the distributed centralized level.
- the goal is to forecast the workload that is coming in to the contact center 110 and that must be distributed to the sub-centers 114 , 116 , 118 .
- the forecast is processed as if the distributed campaign were a virtual (non-distributed) campaign. A non-distributed or virtual campaign assumes that all contact center agent(s) 120 are in one location.
- the next step 196 determines whether schedules have been set in each sub-campaign.
- a multi-site scheduling program is executed in block 198 (see FIG. 7 ). Otherwise, if scheduling is already set, then the sub-campaign allocations are calculated in block 200 (see FIG. 8 ) as if all contact center agents 120 are in a virtual environment. This allocation assumes that an event could be routed to any available contact center agent 120 regardless of the actual sub-center 114 , 116 and 118 in which that contact center agent 120 is actually located.
- a discrete event-based simulation is performed to achieve allocations. Many simulations can be performed and then averaged together.
- the results are then analyzed in block 202 to determine to which sub-center the events were routed according to which contact center agents 120 received the event.
- the results could signify that for a certain time period, a particular percentage of calls were routed to the contact center agent(s) 120 at sub-center 114 . For example, if 17 % of events go to sub-center 114 , 38 % of events go to sub-center 116 and the remaining events go to sub-center 118 , then it would be recommended that sub-center 114 will receive 17 % of the routed events and should staff accordingly.
- FIG. 7 is a flowchart illustrating an embodiment of a multi-scheduling algorithm such as used in block 198 of FIG. 6 .
- the multi-scheduling algorithm is performed such as when there is no schedule available for the contact center agents 120 .
- a sub-center schedule, or partial schedule, is used if available.
- the multi-scheduling algorithm begins at block 204 by treating contact center agent(s) 120 as suitably skilled for the distributed queue if they are skilled for any sub-queue of the distributed queue.
- the forecasts for contact volume, average interaction times and service goals are set to apply directly to the distributed queue instead of to any sub-queue.
- the contact center agents 120 are scheduled using algorithms for non-multi-site operations applied to the distributed queue while also meeting contact center agent 120 work rules, time-off requirements and other preferences.
- the scheduling system operates as if all contact center agents 120 are available at one site, or a virtual center.
- the resulting schedule is the schedule that would be available in a virtual center. That schedule is then applied to the sub-centers for determining the recommended allocations.
- contact center systems may also account for scheduled training of contact center agents 120 .
- additional WFM capability may include a learning component that allows a contact center manager to develop training lessons for and assign lessons to contact center agents 120 .
- the learning component provides automated training processes by identifying, scheduling, and delivering online learning directly to contact center agent 120 desktops.
- the lesson content can include recorded interactions, which can be used to create a library of best practices for training agents and other personnel. Using actual interactions, a contact center 110 can develop E-learning content specific to the organization.
- these training lessons can include assessments to help track and measure agent performance, skill acquisition, and knowledge retention.
- the learning component can also deliver targeted learning sessions over a network, using e-mail, or a hyperlink to a Web site, or directly to the agent desktop.
- Supervisors can select the appropriate training sessions from a library of courseware or create sessions themselves using a contact editing feature. Then supervisors can assign course material and monitor completion automatically.
- the multi-site scheduling algorithm When creating a schedule for a multi-site contact center 110 , the multi-site scheduling algorithm will include training events, in addition to shift assignments, breaks and other preferences. Thus, scheduling for multiple sites also includes the scheduling of training events for the individual agents at the individual sites. If the learning sessions are pre-scheduled, then the multi-site scheduling algorithm and/or the discrete event-based simulation will take the learning sessions into account as training events. Alternatively, the training events could be considered along with other events in the discrete event-based simulation discussed in greater detail below.
- integrated workforce optimization platforms can also integrate other capabilities in support of a greater customer service strategy: (1) Quality Monitoring/Call Recording—voice of the customer; the complete customer experience across multimedia touch points; (2) Workforce Management—strategic forecasting and scheduling that drives efficiency and adherence, aids in planning, and helps facilitate optimum staffing and service levels; (3) Performance Management—key performance indicators (KPIs) and scorecards that analyze and help identify synergies, opportunities and improvement areas; (4) e-Learning—training, new information and protocol disseminated to staff, leveraging best practice customer interactions and delivering learning to support development; and/or (5) Analytics—deliver insights from customer interactions to drive business performance.
- KPIs key performance indicators
- Analytics delivery insights from customer interactions to drive business performance.
- contact center agent 120 allocations could be compared against actual event distribution to determine whether the allocations were satisfactory.
- Other integration points with workforce optimization capabilities may also be useful in context of the allocation and scheduling of contact center agents.
- FIG. 8 is a flowchart illustrating an embodiment of the calculation of sub-campaign allocations of FIG. 6 .
- the sub-campaign allocation algorithm 200 preferably is performed once the contact center agents' 120 schedule is set. If there is no schedule, then the sub-campaign allocation algorithm 200 is run after the multi-site scheduling algorithm.
- the sub-campaign allocation algorithm 200 begins at block 210 by treating contact center agents 120 as suitably skilled for the distributed queue if they are skilled for any sub-queue of the distributed queue.
- the forecasts for contact volume, average interaction times and service goals are set to apply directly to the distributed queue instead of to any sub-queue.
- a discrete event-based simulation (discussed in greater detail below) is performed on the pseudo-virtual campaign. Events are routed to available contact center agents 120 as if they are in the same location. In block 216 , allocation recommendations are made for each sub-campaign of a distributed queue and time interval.
- training events may also be included along with events during the calculation of sub-campaign allocations. Training events, or learning sessions, may be included along with other qualifications limiting the availability of the contact center agents 120 .
- FIG. 9 is a flowchart illustrating an embodiment of a discrete event-based simulation 214 as in FIG. 8 .
- Multiple WFM data input parameters are available for the discrete event-based simulation 214 .
- Block 220 shows that parameters related to the contact center agent 120 , such as agent skills and agent schedules, are input. Additionally, for each distributed queue, the contact volume and average interaction time forecast are also available as inputs.
- Block 222 shows that randomly distributed event arrival times are created based on the contact volume and average interaction times.
- the contact volume and average interaction time forecast indicates that between 8:00 A.M. and 9:00 A.M. the contact center 110 expects to receive ten events that are expected to require two minutes on average, then a random distribution will be created for the events during that time interval.
- Block 224 shows that contact center agent 120 schedule events are created for changes in the contact center agent 120 availability. Schedule events for a contact center agent 120 could correspond to arrival, meeting, lunch breaks and departure, among others. A contact center agent 120 changing from one status to another is considered an agent schedule event.
- Block 226 shows that for each event, the discrete event-based simulation 214 determines whether it is a contact arrival event or an agent schedule event. For the arrival of an event, as shown in block 230 , the event is routed to a contact center agent 120 . The discrete event-based simulation 214 finds an unoccupied contact center agent 120 , routes the event to the contact center agent 120 and marks the contact center agent 120 occupied for the duration of the event. When an event is processed, the discrete event-based simulation 214 records to which contact center agent 120 the event was routed. For an agent schedule event, as shown in block 228 , the discrete event-based simulation 214 changes the contact center agent's 120 availability status from one state to another. The contact center agent's 120 status could be as simple as available state versus unavailable state. Of course, other states could also be set dependent upon contact center requirements.
- the discrete event-based simulation 214 continues until all events are processed. After all events are processed, the allocations are analyzed to determine what percentage of events went to contact center agents 120 of the respective sub-centers. Even though the discrete event-based simulation 214 performed the simulation as if all contact center agents 120 were present in a non-distributed contact center, the percentage distribution is calculated based on the contact center to which the contact center agents 120 are assigned. Multiple passes of the discrete event-based simulation 214 can be performed to determine average percentages of event distribution. The average distribution can then be used for recommended allocations to the various sub-centers as shown in block 232 .
- the discrete event-based simulation 214 treats the allocation of events as if the sub-centers, and thus the contact center agents 120 are not distributed.
- the various sub-centers may keep the recommended allocation as provided by the allocation system 111 and adjust staff for the sub-campaign according to the percentage of events expected during the time accounted for by the simulation. Additionally, the sub-center may adjust the staffing and re-execute the allocation system 111 for new recommendations based on the adjusted staffing. Any change to the forecast or to the contact center agents 120 will affect the recommended allocations since the allocation system 111 treats the distributed campaign as one contact center. An iterative process of creating recommended allocations and then sub-centers adjusting the forecast and/or agents allows convergence to an optimal staffing.
- each block can be interpreted to represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
- the functions noted in the blocks may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
- any of the executable instructions can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
- a “computer-readable medium” can be any means that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device.
- the computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device.
- the computer-readable medium could include a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), and a portable compact disc read-only memory (CDROM) (optical).
- the scope of the certain embodiments of this disclosure can include embodying the functionality described in logic embodied in hardware or software-configured mediums.
Abstract
Description
- This application is a continuation of co-pending U.S. utility application having Ser. No. 11/385,499 filed on Mar. 21, 2006, all of which is entirely incorporated herein by reference.
- The present invention is generally related to contact center allocation of resources.
- Resource allocation and planning, including the generation of schedules for employees, is a complex problem for enterprises. Telephone call center resource allocation and scheduling is an example of a problem with a large number of variables. Variables include contact volume at a particular time of day, available staff, skills of various staff members, call type (e.g., new order call and customer service call), and number of call queues, where a call queue may be assigned a particular call type. A basic goal of call center scheduling is to minimize the cost of agents available to answer calls while maximizing service.
- Traditionally, call center scheduling is performed by forecasting incoming contact volumes and estimating average talk times for each time period based on past history and other measures. These values are then correlated to produce a schedule. However, due to the number of variables that may affect the suitability of a schedule, many schedules need to be evaluated.
- Recently, call centers have evolved into “contact centers” in which the agent's contact with the customer can be through many contact media. For example, a multi-contact call center may handle telephone, email, web callback, web chat, fax, and voice over internet protocol. Therefore, in addition to variation in the types of calls (e.g., service call, order call), modern contact centers have the complication of variation in contact media. The variation in contact media adds complexity to the agent scheduling process.
- Additional complexity results when multiple sites are involved. That is, multiple geographically distributed call centers may be owned by a single organization, or calls may be distributed to multiple locations depending on whether a contact is for technical support, sales, etc.
- Systems and methods for allocating resources, e.g., contact center agents, among geographically distributed sites are provided. In this regard, an exemplary embodiment of such a method comprises: creating a workload forecast, such as contact volume and average handle, resolution, interaction and/or order/purchase fulfillment time, of events for a specified time frame, such as hours, days, week, months, quarters and/or years, as if the geographically distributed sites were co-located, performing discrete event-based simulation to assign the events to the contact center resource(s) as if at least a portion of the total contact center resources were co-located, and determining recommended allocations of the contact center resources among the geographically distributed sites based on a relative distribution of events expected, forecasted, simulated or assigned to contact center resources at each of the geographically distributed sites. In addition to time, requirements can further include other operational constraints of the sites, including, for example, network bandwidth.
- An exemplary embodiment of a system for allocating contact/support center resources, such as agents, servers, computers, databases, recorders (including, among others, TDM, VoIP and/or wireless recorders), administrative staff, customer services personnel, supervisors, managers, marketers, cross-sellers, supplies and other logistical resources involved in the operations of point of contact centers, including contact or customer support centers, back office or support centers, retailing and banking centers, comprises: a forecasting system configured to create a workload forecast, such as volume, peak time, low time, average volume, static and dynamic volume, including requirements per hour (including minutes and seconds), day, week, month, quarter and/or year, with such requirement including, for example, voice, messenger chat, email, and direct contact channels of communication, and average handle, resolution and/or transactional time forecast of events for a specified or predetermined time frame, schedule and/or campaign, as if the geographically distributed resources or sites were co-located, a simulation system configured to perform discrete event-based simulation to assign the events to the resource(s) (for example, contact center agents) as if the resource were co-located, and an analysis system configured to determine recommended allocations of resources among the geographically distributed sites based on a relative distribution of events expected, forecasted or simulated for the center and/or assigned to resource(s) at each of the geographically distributed sites
- Other systems, methods, features, and advantages of the present invention will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.
- Many aspects of the invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views. While several embodiments are described in connection with these drawings, there is no intent to limit the disclosure to the embodiment or embodiments disclosed herein. On the contrary, the intent is to cover all alternatives, modifications and equivalents.
-
FIG. 1 is a schematic diagram illustrating an exemplary embodiment of a system for distributing events, such as contact/support center events, according to recommended allocations of resources, such as contact center agents. -
FIG. 2 is a schematic diagram illustrating an embodiment of a computer-implemented system that can be used for determining recommended allocations of resources, such as contact center agents, utilized inFIG. 1 . -
FIG. 3 is a flowchart illustrating functionality (or method steps) that can be performed by an embodiment of a system according toFIG. 2 to create recommended allocations of resources, such as contact center agents, for use in the system ofFIG. 1 . -
FIG. 4 is a diagram illustrating a distributed campaign according toFIG. 3 . -
FIG. 5 is a diagram illustrating a sub-campaign fromFIG. 4 . -
FIG. 6 is a flowchart illustrating determination of recommended allocations by the system inFIG. 2 . -
FIG. 7 is a flowchart illustrating the multi-scheduling algorithm ofFIG. 6 . -
FIG. 8 is a flowchart illustrating the calculation of sub-campaign allocations ofFIG. 6 . -
FIG. 9 is a flowchart illustrating the discrete event-based simulation ofFIG. 8 . - Disclosed herein are systems and methods for determining recommendations for the allocation of resources, such as call center agents, retailers or bankers. In particular, the allocation of resources can be achieved using discrete event-based simulations that perform allocations on multiple distributed sites as if the resources were not distributed. Recommended allocations are based on a relative distribution, e.g. percentages, of events, such as customer calls, inquiries, purchases and other transactional and operational events, for each site in accordance with the resource to which the simulation assigned the events. More generally though, the systems and methods of the present invention can be deployed or utilized in allocating contact/support center resources, such as agents, servers, computers, databases, recorders (including, among others, TDM, VoIP and/or wireless recorders), administrative staff, customer services personnel, supervisors, managers, marketers, cross-sellers, supplies and other logistical resources involved in the operations of point of contact centers, including contact or customer support centers, back office or support centers, retailing and banking centers.
- An ideal system for distributing events to multiple sites would be a system that could analyze every available site for any available resource located at any of the available sites. After location of an available resource, such a system would route the event to that resource regardless of that resource's geographical location. Thus, although the contact center is a virtual center, the system would distribute events as if the contact center were one large contact center. Such efficiency, however, is difficult to attain. Typically, contact centers operate on preset allocations of events for a particular time frame. The equipment costs for analyzing all available sites and routing events accordingly can be very expensive. By comparison, equipment costs for routing defined percentages of events is currently preferable. With preset allocations, a distributed site essentially operates as an independent site that knows what volume of events to expect and, thus, is able to schedule staffing, and other resources, accordingly.
- The disclosed systems for determining allocations for distributed multi-site contact centers provide recommended allocations of contact center resources, such as agents, based on simulations that utilize virtual contact centers. Statistical information based on existing work flow management (WFM) data are used to create a workload forecast of events for contact volume data and average handle times. A contact volume forecast is the number of events forecast for a certain time interval. An average handle time forecast is the response time required per event. In conjunction with agent schedules and other agent rules, randomly distributed contact arrival events are created based on the WFM data. A discrete event-based simulation then routes the events to available agents as if they were assigned to a non-distributed or virtual contact center. Recommended allocations for the various sites are then calculated based on the agents to which the events were assigned.
- Exemplary systems are first discussed with reference to the figures. Although these systems are described in detail, they are provided for purposes of illustration only and various modifications are feasible. After the exemplary systems have been described, examples of recommended allocations are provided to explain the manner in which the scheduling and allocation of the call center agents can be achieved.
- Referring now in more detail to the figures,
FIG. 1 is a schematic diagram illustrating an exemplary embodiment of a system for distributing events according to recommended allocations of resources, such as contact center agents. Thesystem 100 comprises one ormore customer premises 102. Thecustomer premise 102 includes, for example but not limited to, telephones, cellular phones and computing devices.Customer premises 102 communicate with a network 106 (e.g., PSTN and/or cellular) that communicates with acontact center 110. InFIG. 1 thecontact center 110 is shown connected through a network 112 (e.g., local area network (LAN) or wide area network (WAN) or virtual private network (VPN)) tovarious sub-centers contact center agents sub-centers contact center 110. Typically, there will be at least two sites (sub-centers). Of course, the number ofcontact center agents 120 et al., will also vary according to the recommended allocations for each sub-center 114, 116, 118. Hereafter, unless two different contact center agents are discussed, references to a generic contact center agent or to generic contact center agents will refer to contactcenter agent 120. Also, for purposes of illustration, the discussion to follow focuses on the allocation ofcontact center agents 120, though the contact center resources could just as likely be servers, computers, databases, recorders (including, among others, TDM, VoIp and/or wireless recorders), administrative staff, customer services personnel, supervisors, managers, marketers, cross-sellers, supplies and other logistical resources involved in the operations of point of contact centers, including contact or customer support centers, back office or support centers, retailing and banking centers. - Events, such as a
call 104, to customer support are placed from acustomer premise 102 through thenetwork 106 to thecontact center 110. The customer initiates the event with no regard as to where thecontact center agent 120 is actually located. The event is routed to the next availablecontact center agent 120 by thecontact center 110 in accordance with recommended allocations provided to thecontact center 110 from anallocation system 111. Acontact center agent 120 utilizes computing devices (not shown) such as, for instance, desktop computers (PCs) or Macintosh computers that can, if necessary, be connected to communication devices, such as a headset, microphones, and headphones, among others. -
FIG. 2 is a schematic diagram illustrating an exemplary embodiment of a computer-implementedallocation system 111 that can be used for determining recommended allocations ofcontact center agents 120. It should be noted that theallocation system 111 could be located in thecontact center 110 or at a location connected to the contact center via a network such as thenetwork 112 or the Internet, among others. Generally, theallocation system 111 includes aprocessing device 138,memory 140,user interface devices 148, input/output devices (I/O) 150 andnetworking devices 152, each of which is connected tolocal interface 146. The local interface can include, for example but not limited to, one or more buses or other wired or wireless connections. The local interface may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, the local interface may include address, control, and/or data connections to enable appropriate communications among aforementioned components. The processor may be a hardware device for executing software, particularly software stored in memory. - The
processing device 138 can be any custom made or commercially available processor, a central processing unit (CPU) or an auxiliary processor among several processors associated with theallocation system 111, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing software instructions. Examples of suitable commercially available microprocessors are as follows: a PA-RISC series microprocessor from Hewlett-Packard® Company, an 80×86 or Pentium® series microprocessor from Intel® Corporation, a PowerPC® microprocessor from IBM®, a Sparc® microprocessor from Sun Microsystems®, Inc, or a 68xxx series microprocessor from Motorola® Corporation. - The memory can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, the memory may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory (as well as various other components) can have a distributed architecture, where various components are situated remote from one another, but can be accessed by the
processing device 138. Additionally,memory 140 can also include anoperating system 142, as well as instructions associated with various subsystems, such as a multi-siteallocation recommendation system 144. - The software in
memory 140 may include one or more separate programs, each of which includes an ordered listing of executable instructions for implementing logical functions. In this regard, a non-exhaustive list of examples of suitable commercially available operating systems is as follows: (a) a Windows® operating system available from Microsoft® Corporation; (b) a Netware® operating system available from Novell®, Inc.; (c) a Macintosh® operating system available from Apple® Computer, Inc.; (d) a UNIX operating system, which is available for purchase from many vendors, such as the Hewlett-Packard® Company, Sun Microsystems®, Inc., and AT&T® Corporation; (e) a LINUX operating system, which is freeware that is readily available on theInternet 100; (f) a run time Vxworks® operating system from WindRiver® Systems, Inc.; or (g) an appliance-based operating system, such as that implemented in handheld computers or personal data assistants (PDAs) (e.g., PalmOS® available from Palm® Computing, Inc., and Windows CE® available from Microsoft® Corporation). Theoperating system 142 can be configured to control the execution of other computer programs and provides scheduling, input-communication control, file and data management, memory management, and communication control and/or related services. - A system component embodied as software may also be construed as a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed. When constructed as a source program, the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the
memory 140, so as to operate properly in connection with theoperating system 142. - When the
allocation system 111 is in operation, theprocessing device 138 is configured to execute software stored within thememory 140, to communicate data to and from thememory 140, and to generally control operations of theallocation system 111 pursuant to the software. Software inmemory 140, in whole or in part, is read by theprocessing device 138, perhaps buffered, and then executed. Theallocation system 111 accesses WFM data from aWFM database 154 through I/O device 150.Multi-site allocation recommendations 144 are determined and made available to thecontact center 110 through anetworking device 152. -
FIG. 3 is a flowchart illustrating functionality associated with the embodiment of the system ofFIG. 2 . Specifically, the functionality depicted inFIG. 3 is associated with the multi-siteallocation recommendations system 144. In this regard, the functionality begins by assimilatingWFM data 160 from forecastedcall volume data 156 andother site data 158. Examples of other site data would include employees, work schedules, time off preferences, event type priorities, etc. The WFM data could be retrieved from a WFM database 154 (seeFIG. 2 ) and processed by the processing device 138 (seeFIG. 2 ) for use in the multi-siteallocation recommendations system 144. Forecastedcontact volume data 156 is made up of a contact volume for some period of time and an average interaction time forecast. As a non-limiting example, a contact volume forecast could be the reception of 25 customer support calls over a 15 minute window from 9:00 A.M. to 9:15 A.M. The time window could, of course be adjusted to suit the particular circumstance and/or other requirements. Average interaction time forecast, as a non-limiting example, could be that an average sales call requires two minutes and forty-five seconds ofcontact center agent 120 support. Of course, different type events would require different levels of interaction time and/or follow-up time that could also be included in the forecast. The contact volume and average interaction time forecast is an attempt to forecast the total incoming contact volume and the total time required to handle that contact volume at the top level, being the distributed centralized level. The WFM history available enables theallocation system 111 to forecast the incoming workload that must be distributed to theavailable sub-centers -
Block 162 shows the creation of distributed queues, sub-queues and distributed campaigns. A distributed campaign is an entire operation, while a distributed queue includes events related to that operation. A distributed campaign could have more than one distributed queue. As a non-limiting example, when a distributed campaign involves a particular product, a distributed queue could entail a stream of events related to that product. Inblock 164, sub-campaigns are created for each distributed campaign. Sub-campaigns are a portion of the entire operation including sub-queues and employees. Sub-queues are derived from a distributed queue and are a stream of events routed to a particular sub-center. An event from the sub-queue is distributed to the employees or agents available to handle that event. Inblock 166, for each sub-campaign, the sub-queues, skills, organizations and employees are linked to that sub-campaign. Finally, the multi-site algorithm is applied inblock 168. - Within a distributed campaign, events are routed from a distributed queue through sub-queues to various sub-centers and then to individual agents. Sub-campaigns comprise various sub-queues as input streams of events to a sub-center and the contact center agents assigned to that sub-center. The queues overlap with the campaigns based on agent availability and capability.
-
FIG. 4 illustrates an example of a distributed campaign such as created inblock 162. One or more distributedqueues contact center 110. A distributedqueue contact center 110 to be distributed to some sub-center 114, 116, 118. The event could be a phone call, voice over internet protocol or email, among others. -
FIG. 4 shows events distributed to sub-center 114 throughsub-queues sub-queues sub-queue 182. - As a non-limiting example, distributed
queue 170 could include phone calls for customer support and thecontact center agents 120 specializing in customer support might be located atsub-center 114 and atsub-center 116. The customer support events would be routed throughsub-queue 174 to sub-center 114 and throughsub-queue 178 tosub-center 116. Further, the customer support events might be directed toward different types of support issues, for example installation issues and technical support issues. The sub-queues could be directed toward specific types of events. Installation issues could be routed throughsub-queue 174 to sub-center 114 and sub-queue 178 tosub-center 116. Technical support issues could be routed throughsub-queue 176 to sub-center 114 and sub-queue 180 tosub-center 116. Acontact center agent 120 at each sub-center would receive events related to their specific skill-set. Notably, acontact center agent 120 could have multiple skill-sets such that a singlecontact center agent 120 could handle events related to both installation issues and technical support issues in this example. Additionally, distributedqueue 172 could include phone calls for sales and the contact center agent(s) 120 specializing in sales might be located atsub-center 118. The sales events would be routed throughsub-queue 182 tosub-center 118. -
FIG. 5 illustrates a sub-campaign as created inblock 164. One or more sub-queues 174, 176 stream into the sub-center 114. Similarly, at least one sub-queue streams into each sub-center. A sub-queue 174, 176 is a centralized incoming stream of events coming into the sub-center 114 to be distributed to contactcenter agents contact center agents 120 varies with each contact center in accordance with actual and recommended allocations.FIG. 5 showsevents center agent 120. Likewiseevents 188 are shown distributed to contactcenter agent 122 andevents center agent 124. Notably, a sub-center 114 can receive different streams of events, for example, fromsub-queue 174 andsub queue 176, and acontact center agent 120 can receive events from asingle sub-queue 174 or frommultiple sub-queues event 184 to contactcenter agent 120 could derive from sub-queue 174 whileevent 186 could derive fromsub-queue 176. -
FIG. 6 is a flowchart illustrating an exemplary process for determination of recommended allocations by theallocation system 111 inFIG. 2 . Specifically, the functionality depicted inFIG. 6 provides greater detail of the flowchart inFIG. 3 associated with the multi-siteallocation recommendations system 144. Inblock 162 distributed queues, sub-queues and distributed campaigns are created. Inblock 164, sub-campaigns are created for each distributed campaign. Inblock 166, for each sub-campaign, the sub-queues, skills, organizations and employees are linked to that sub-campaign. - Next, a multi-site algorithm is applied to the distributed campaign using a virtual contact center. The
WFM data 160 is used to create contact volume, average interaction time forecasts and service goals inblock 194 for the distributed campaign. The forecast is for total incoming event volume and the total time it will take to handle that event volume at the distributed centralized level. The goal is to forecast the workload that is coming in to thecontact center 110 and that must be distributed to the sub-centers 114, 116, 118. The forecast is processed as if the distributed campaign were a virtual (non-distributed) campaign. A non-distributed or virtual campaign assumes that all contact center agent(s) 120 are in one location. Thenext step 196 determines whether schedules have been set in each sub-campaign. If the contact center agent(s) 120 in a sub-campaign have not been assigned schedules, then a multi-site scheduling program is executed in block 198 (seeFIG. 7 ). Otherwise, if scheduling is already set, then the sub-campaign allocations are calculated in block 200 (seeFIG. 8 ) as if allcontact center agents 120 are in a virtual environment. This allocation assumes that an event could be routed to any availablecontact center agent 120 regardless of theactual sub-center contact center agent 120 is actually located. - A discrete event-based simulation is performed to achieve allocations. Many simulations can be performed and then averaged together. The results are then analyzed in
block 202 to determine to which sub-center the events were routed according to whichcontact center agents 120 received the event. The results could signify that for a certain time period, a particular percentage of calls were routed to the contact center agent(s) 120 atsub-center 114. For example, if 17% of events go tosub-center 114, 38% of events go tosub-center 116 and the remaining events go tosub-center 118, then it would be recommended thatsub-center 114 will receive 17% of the routed events and should staff accordingly. -
FIG. 7 is a flowchart illustrating an embodiment of a multi-scheduling algorithm such as used inblock 198 ofFIG. 6 . The multi-scheduling algorithm is performed such as when there is no schedule available for thecontact center agents 120. A sub-center schedule, or partial schedule, is used if available. The multi-scheduling algorithm begins atblock 204 by treating contact center agent(s) 120 as suitably skilled for the distributed queue if they are skilled for any sub-queue of the distributed queue. For example, inblock 206, the forecasts for contact volume, average interaction times and service goals are set to apply directly to the distributed queue instead of to any sub-queue. Finally, inblock 208, thecontact center agents 120 are scheduled using algorithms for non-multi-site operations applied to the distributed queue while also meetingcontact center agent 120 work rules, time-off requirements and other preferences. The scheduling system operates as if allcontact center agents 120 are available at one site, or a virtual center. The resulting schedule is the schedule that would be available in a virtual center. That schedule is then applied to the sub-centers for determining the recommended allocations. - In an alternative embodiment, contact center systems may also account for scheduled training of
contact center agents 120. In the system 100 (seeFIG. 1 ), additional WFM capability may include a learning component that allows a contact center manager to develop training lessons for and assign lessons to contactcenter agents 120. The learning component provides automated training processes by identifying, scheduling, and delivering online learning directly to contactcenter agent 120 desktops. The lesson content can include recorded interactions, which can be used to create a library of best practices for training agents and other personnel. Using actual interactions, acontact center 110 can develop E-learning content specific to the organization. In an enhancement, these training lessons can include assessments to help track and measure agent performance, skill acquisition, and knowledge retention. - The learning component can also deliver targeted learning sessions over a network, using e-mail, or a hyperlink to a Web site, or directly to the agent desktop. Supervisors can select the appropriate training sessions from a library of courseware or create sessions themselves using a contact editing feature. Then supervisors can assign course material and monitor completion automatically.
- When creating a schedule for a
multi-site contact center 110, the multi-site scheduling algorithm will include training events, in addition to shift assignments, breaks and other preferences. Thus, scheduling for multiple sites also includes the scheduling of training events for the individual agents at the individual sites. If the learning sessions are pre-scheduled, then the multi-site scheduling algorithm and/or the discrete event-based simulation will take the learning sessions into account as training events. Alternatively, the training events could be considered along with other events in the discrete event-based simulation discussed in greater detail below. - In addition to scheduled training of
contact center agents 120, integrated workforce optimization platforms can also integrate other capabilities in support of a greater customer service strategy: (1) Quality Monitoring/Call Recording—voice of the customer; the complete customer experience across multimedia touch points; (2) Workforce Management—strategic forecasting and scheduling that drives efficiency and adherence, aids in planning, and helps facilitate optimum staffing and service levels; (3) Performance Management—key performance indicators (KPIs) and scorecards that analyze and help identify synergies, opportunities and improvement areas; (4) e-Learning—training, new information and protocol disseminated to staff, leveraging best practice customer interactions and delivering learning to support development; and/or (5) Analytics—deliver insights from customer interactions to drive business performance. These five segments can become part of an interwoven and interoperable solution, enabling contact centers to transition from reactive cost centers to proactive, information-rich departments that deliver strategic value to the organization. Workforce optimization is discussed in greater detail in the U.S. Patent Application entitled “Systems and Methods for Workforce Optimization,” filed Feb. 22, 2006, and assigned application Ser. No. 11/359,356, which is entirely incorporated herein by reference. - In a non-limiting example of integration with other workforce optimization capabilities,
contact center agent 120 allocations could be compared against actual event distribution to determine whether the allocations were satisfactory. Other integration points with workforce optimization capabilities may also be useful in context of the allocation and scheduling of contact center agents. -
FIG. 8 is a flowchart illustrating an embodiment of the calculation of sub-campaign allocations ofFIG. 6 . Thesub-campaign allocation algorithm 200 preferably is performed once the contact center agents' 120 schedule is set. If there is no schedule, then thesub-campaign allocation algorithm 200 is run after the multi-site scheduling algorithm. Thesub-campaign allocation algorithm 200 begins atblock 210 by treatingcontact center agents 120 as suitably skilled for the distributed queue if they are skilled for any sub-queue of the distributed queue. Inblock 212, the forecasts for contact volume, average interaction times and service goals are set to apply directly to the distributed queue instead of to any sub-queue. Inblock 214, a discrete event-based simulation (discussed in greater detail below) is performed on the pseudo-virtual campaign. Events are routed to availablecontact center agents 120 as if they are in the same location. Inblock 216, allocation recommendations are made for each sub-campaign of a distributed queue and time interval. - In an alternative embodiment, training events may also be included along with events during the calculation of sub-campaign allocations. Training events, or learning sessions, may be included along with other qualifications limiting the availability of the
contact center agents 120. -
FIG. 9 is a flowchart illustrating an embodiment of a discrete event-basedsimulation 214 as inFIG. 8 . Multiple WFM data input parameters are available for the discrete event-basedsimulation 214.Block 220 shows that parameters related to thecontact center agent 120, such as agent skills and agent schedules, are input. Additionally, for each distributed queue, the contact volume and average interaction time forecast are also available as inputs.Block 222 shows that randomly distributed event arrival times are created based on the contact volume and average interaction times. - As a non-limiting example, if the contact volume and average interaction time forecast indicates that between 8:00 A.M. and 9:00 A.M. the
contact center 110 expects to receive ten events that are expected to require two minutes on average, then a random distribution will be created for the events during that time interval. -
Block 224 shows thatcontact center agent 120 schedule events are created for changes in thecontact center agent 120 availability. Schedule events for acontact center agent 120 could correspond to arrival, meeting, lunch breaks and departure, among others. Acontact center agent 120 changing from one status to another is considered an agent schedule event. -
Block 226 shows that for each event, the discrete event-basedsimulation 214 determines whether it is a contact arrival event or an agent schedule event. For the arrival of an event, as shown inblock 230, the event is routed to acontact center agent 120. The discrete event-basedsimulation 214 finds an unoccupiedcontact center agent 120, routes the event to thecontact center agent 120 and marks thecontact center agent 120 occupied for the duration of the event. When an event is processed, the discrete event-basedsimulation 214 records to whichcontact center agent 120 the event was routed. For an agent schedule event, as shown inblock 228, the discrete event-basedsimulation 214 changes the contact center agent's 120 availability status from one state to another. The contact center agent's 120 status could be as simple as available state versus unavailable state. Of course, other states could also be set dependent upon contact center requirements. - The discrete event-based
simulation 214 continues until all events are processed. After all events are processed, the allocations are analyzed to determine what percentage of events went tocontact center agents 120 of the respective sub-centers. Even though the discrete event-basedsimulation 214 performed the simulation as if allcontact center agents 120 were present in a non-distributed contact center, the percentage distribution is calculated based on the contact center to which thecontact center agents 120 are assigned. Multiple passes of the discrete event-basedsimulation 214 can be performed to determine average percentages of event distribution. The average distribution can then be used for recommended allocations to the various sub-centers as shown inblock 232. - It should be noted that many available simulators are well known in the art and could be utilized to perform the discrete event-based
simulation 214. The emphasis is on the simulation rather than the simulator itself. The discrete event-basedsimulation 214 treats the allocation of events as if the sub-centers, and thus thecontact center agents 120 are not distributed. - The various sub-centers may keep the recommended allocation as provided by the
allocation system 111 and adjust staff for the sub-campaign according to the percentage of events expected during the time accounted for by the simulation. Additionally, the sub-center may adjust the staffing and re-execute theallocation system 111 for new recommendations based on the adjusted staffing. Any change to the forecast or to thecontact center agents 120 will affect the recommended allocations since theallocation system 111 treats the distributed campaign as one contact center. An iterative process of creating recommended allocations and then sub-centers adjusting the forecast and/or agents allows convergence to an optimal staffing. - It should be noted that the flowcharts included herein show the architecture, functionality and/or operation of implementations that may be configured using software. In this regard, each block can be interpreted to represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
- It should be noted that any of the executable instructions, such as those depicted functionally in the accompanying flowcharts, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium could include a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), and a portable compact disc read-only memory (CDROM) (optical). In addition, the scope of the certain embodiments of this disclosure can include embodying the functionality described in logic embodied in hardware or software-configured mediums.
- It should be emphasized that the above-described embodiments are merely possible examples of implementations, merely set forth for a clear understanding of the principles of this disclosure. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/725,127 US20100172485A1 (en) | 2006-03-21 | 2010-03-16 | Systems and methods for determining allocations for distributed multi-site contact centers |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/385,499 US7734783B1 (en) | 2006-03-21 | 2006-03-21 | Systems and methods for determining allocations for distributed multi-site contact centers |
US12/725,127 US20100172485A1 (en) | 2006-03-21 | 2010-03-16 | Systems and methods for determining allocations for distributed multi-site contact centers |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/385,499 Continuation US7734783B1 (en) | 2006-03-21 | 2006-03-21 | Systems and methods for determining allocations for distributed multi-site contact centers |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100172485A1 true US20100172485A1 (en) | 2010-07-08 |
Family
ID=42227025
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/385,499 Active 2029-01-31 US7734783B1 (en) | 2006-03-21 | 2006-03-21 | Systems and methods for determining allocations for distributed multi-site contact centers |
US12/725,127 Abandoned US20100172485A1 (en) | 2006-03-21 | 2010-03-16 | Systems and methods for determining allocations for distributed multi-site contact centers |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/385,499 Active 2029-01-31 US7734783B1 (en) | 2006-03-21 | 2006-03-21 | Systems and methods for determining allocations for distributed multi-site contact centers |
Country Status (1)
Country | Link |
---|---|
US (2) | US7734783B1 (en) |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100027767A1 (en) * | 2008-07-30 | 2010-02-04 | At&T Intellectual Property I, L.P. | Transparent voice registration and verification method and system |
US20100215169A1 (en) * | 2009-02-25 | 2010-08-26 | Herbert Willi Artur Ristock | Virtualization of One or More Sets of Physical Contact Center Resources for Use by One or More Virtual Contact Centers |
US20120087486A1 (en) * | 2010-10-09 | 2012-04-12 | Jose Luis Beltran Guerrero | Call center resource allocation |
US8391466B1 (en) * | 2012-07-24 | 2013-03-05 | Noble Systems Corporation | Generating communication forecasts and schedules based on multiple outbound campaigns |
US20140108022A1 (en) * | 2012-10-12 | 2014-04-17 | American Well Systems | Brokerage System Employing Minimal Criteria Matching and Availability Queuing |
WO2014085760A1 (en) * | 2012-11-29 | 2014-06-05 | Genesys Telecommunications Laboratories, Inc. | Workload distribution with resource awareness |
WO2015143408A1 (en) * | 2014-03-20 | 2015-09-24 | Genesys Telecommunications Laboratories, Inc. | Local survivability in a distributed contact center environment |
US9426291B1 (en) | 2015-10-16 | 2016-08-23 | Noble Systems Corporation | Forecasting and scheduling campaigns involving sending outbound communications that generate inbound communications |
US9538010B2 (en) | 2008-12-19 | 2017-01-03 | Genesys Telecommunications Laboratories, Inc. | Method and system for integrating an interaction management system with a business rules management system |
US9542936B2 (en) | 2012-12-29 | 2017-01-10 | Genesys Telecommunications Laboratories, Inc. | Fast out-of-vocabulary search in automatic speech recognition systems |
US9588830B2 (en) | 2014-03-20 | 2017-03-07 | Genesys Telecommunications Laboratories, Inc. | Local survivability in a distributed contact center environment |
US9774739B2 (en) | 2014-03-20 | 2017-09-26 | Genesys Telecommunications Laboratories, Inc. | Resource sharing in a peer-to-peer network of contact center nodes |
US9787840B1 (en) | 2015-06-11 | 2017-10-10 | Noble Systems Corporation | Forecasting and scheduling campaigns involving different channels of communication |
US9912816B2 (en) | 2012-11-29 | 2018-03-06 | Genesys Telecommunications Laboratories, Inc. | Workload distribution with resource awareness |
US9992336B2 (en) | 2009-07-13 | 2018-06-05 | Genesys Telecommunications Laboratories, Inc. | System for analyzing interactions and reporting analytic results to human operated and system interfaces in real time |
CN108287750A (en) * | 2012-09-12 | 2018-07-17 | 格林伊登美国控股有限责任公司 | System and method for the dynamic elasticity for providing liaison centre's resource |
US20180374176A1 (en) * | 2017-06-26 | 2018-12-27 | Datalign Ltd | Automated government resource allocation |
US10462299B2 (en) * | 2014-09-23 | 2019-10-29 | Interactive Intelligence Group, Inc. | Method and system for creating contact center models |
US10691692B2 (en) | 2016-04-29 | 2020-06-23 | Fujitsu Limited | Computer-implemented method of executing a query in a network of data centres |
US20220101220A1 (en) * | 2020-09-30 | 2022-03-31 | Genesys Telecommunications Laboratories, Inc. | Method and system for dynamic adaptive routing of deferrable work in a contact center |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8015042B2 (en) * | 2001-04-02 | 2011-09-06 | Verint Americas Inc. | Methods for long-range contact center staff planning utilizing discrete event simulation |
US8949443B2 (en) * | 2003-06-11 | 2015-02-03 | Canon Kabushiki Kaisha | Communication apparatus, control method, and computer-usable medium for selecting a network for data transmission |
US8300798B1 (en) * | 2006-04-03 | 2012-10-30 | Wai Wu | Intelligent communication routing system and method |
US8560369B2 (en) * | 2007-11-01 | 2013-10-15 | Red Hat, Inc. | Systems and methods for technical support based on a flock structure |
US10282701B2 (en) * | 2007-11-20 | 2019-05-07 | Red Hat, Inc. | Web-based technical issue assignments based on technical support groups having handled a highest number of technical requests |
US20090168991A1 (en) * | 2007-12-27 | 2009-07-02 | Stanislav Zgardovski | Method and System for Dynamic Tracking and Assignment of Agent Resources within a Contact Center |
US9141942B2 (en) | 2012-09-05 | 2015-09-22 | International Business Machines Corporation | Event scheduler based on real-time analytics and business rules |
US10148592B1 (en) * | 2015-06-29 | 2018-12-04 | Amazon Technologies, Inc. | Prioritization-based scaling of computing resources |
US11126936B2 (en) * | 2016-09-09 | 2021-09-21 | Jaime Job Consulting, Inc. | System and method for the automated generation of financial and resource forecasting data for events |
KR102610537B1 (en) | 2016-11-10 | 2023-12-06 | 삼성전자주식회사 | Solid state drive device and storage system having the same |
US20180288226A1 (en) * | 2017-04-03 | 2018-10-04 | Avaya Inc. | High performance distributed computer work assignment engine |
US10320625B1 (en) * | 2018-08-21 | 2019-06-11 | Capital One Services, Llc | Managing service deployment in a cloud computing environment |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6493446B1 (en) * | 1999-05-13 | 2002-12-10 | Willow Csn Incorporated | Call center posting program |
US20040062380A1 (en) * | 2002-09-26 | 2004-04-01 | Delaney Paul J. | Contact center management |
US6952732B2 (en) * | 2001-04-30 | 2005-10-04 | Blue Pumpkin Software, Inc. | Method and apparatus for multi-contact scheduling |
US7085728B2 (en) * | 2001-07-31 | 2006-08-01 | Iex Corporation | Method for forecasting and managing multimedia contracts |
US7095841B2 (en) * | 2002-03-29 | 2006-08-22 | Avaya Technology Corp. | Queued task/queued resource state forecaster |
US7155399B2 (en) * | 2001-04-03 | 2006-12-26 | Witness Systems, Inc. | System and method for complex schedule generation |
US7406171B2 (en) * | 2003-12-19 | 2008-07-29 | At&T Delaware Intellectual Property, Inc. | Agent scheduler incorporating agent profiles |
US7660407B2 (en) * | 2006-06-27 | 2010-02-09 | Verint Americas Inc. | Systems and methods for scheduling contact center agents |
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 |
Family Cites Families (163)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3594919A (en) | 1969-09-23 | 1971-07-27 | Economy Co | Tutoring devices |
US3705271A (en) | 1971-03-26 | 1972-12-05 | Economy Co | Audio tutoring device including recording capability |
US4510351A (en) | 1982-10-28 | 1985-04-09 | At&T Bell Laboratories | ACD Management information system |
US4684349A (en) | 1984-02-15 | 1987-08-04 | Frank Ferguson | Audio-visual teaching system and method |
US4763353A (en) | 1986-02-14 | 1988-08-09 | American Telephone And Telegraph Company | Terminal based adjunct call manager for a communication system |
US4694483A (en) | 1986-06-02 | 1987-09-15 | Innings Telecom Inc. | Computerized system for routing incoming telephone calls to a plurality of agent positions |
US5008926A (en) | 1986-07-17 | 1991-04-16 | Efrat Future Technology Ltd. | Message management system |
US4924488A (en) | 1987-07-28 | 1990-05-08 | Enforcement Support Incorporated | Multiline computerized telephone monitoring system |
US4815120A (en) | 1987-07-28 | 1989-03-21 | Enforcement Support Incorporated | Computerized telephone monitoring system |
US5101402A (en) | 1988-05-24 | 1992-03-31 | Digital Equipment Corporation | Apparatus and method for realtime monitoring of network sessions in a local area network |
US4953159A (en) | 1989-01-03 | 1990-08-28 | American Telephone And Telegraph Company | Audiographics conferencing arrangement |
US5117225A (en) | 1989-05-01 | 1992-05-26 | Summit Micro Design | Computer display screen monitoring system |
US5016272A (en) | 1989-06-16 | 1991-05-14 | Stubbs James R | Home video system |
US5195086A (en) | 1990-04-12 | 1993-03-16 | At&T Bell Laboratories | Multiple call control method in a multimedia conferencing system |
US5311422A (en) | 1990-06-28 | 1994-05-10 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | General purpose architecture for intelligent computer-aided training |
US5388252A (en) | 1990-09-07 | 1995-02-07 | Eastman Kodak Company | System for transparent monitoring of processors in a network with display of screen images at a remote station for diagnosis by technical support personnel |
US5113430A (en) | 1990-10-01 | 1992-05-12 | United States Advanced Network, Inc. | Enhanced wide area audio response network |
JPH05507396A (en) | 1990-11-20 | 1993-10-21 | テロケント コミュニケーションズ コーポレーション | call processing system |
US5241625A (en) | 1990-11-27 | 1993-08-31 | Farallon Computing, Inc. | Screen image sharing among heterogeneous computers |
US5239460A (en) | 1991-01-03 | 1993-08-24 | At&T Bell Laboratories | Arrangement for motivating telemarketing agents |
US5475625A (en) | 1991-01-16 | 1995-12-12 | Siemens Nixdorf Informationssysteme Aktiengesellschaft | Method and arrangement for monitoring computer manipulations |
US5381470A (en) | 1991-05-28 | 1995-01-10 | Davox Corporation | Supervisory management center with parameter testing and alerts |
US5210789A (en) | 1991-06-28 | 1993-05-11 | International Telecharge, Inc. | Interactive telephone operator terminal |
US5315711A (en) | 1991-11-01 | 1994-05-24 | Unisys Corporation | Method and apparatus for remotely and centrally controlling a plurality of host processors |
US5267865A (en) | 1992-02-11 | 1993-12-07 | John R. Lee | Interactive computer aided natural learning method and apparatus |
JPH0612288A (en) | 1992-06-29 | 1994-01-21 | Hitachi Ltd | Information processing system and monitoring method therefor |
GB2270581A (en) | 1992-09-15 | 1994-03-16 | Ibm | Computer workstation |
JPH0772999A (en) | 1992-10-20 | 1995-03-17 | Hewlett Packard Co <Hp> | Method and apparatus for monitoring of display screen event in screen-corresponding software application tool |
US5499291A (en) | 1993-01-14 | 1996-03-12 | At&T Corp. | Arrangement for automating call-center agent-schedule-notification and schedule-adherence functions |
EP0644510B1 (en) | 1993-09-22 | 1999-08-18 | Teknekron Infoswitch Corporation | Telecommunications system monitoring |
US5689641A (en) | 1993-10-01 | 1997-11-18 | Vicor, Inc. | Multimedia collaboration system arrangement for routing compressed AV signal through a participant site without decompressing the AV signal |
US5347306A (en) | 1993-12-17 | 1994-09-13 | Mitsubishi Electric Research Laboratories, Inc. | Animated electronic meeting place |
US5396371A (en) | 1993-12-21 | 1995-03-07 | Dictaphone Corporation | Endless loop voice data storage and retrievable apparatus and method thereof |
US5572652A (en) | 1994-04-04 | 1996-11-05 | The United States Of America As Represented By The Secretary Of The Navy | System and method for monitoring and controlling one or more computer sites |
US5918214A (en) | 1996-10-25 | 1999-06-29 | Ipf, Inc. | System and method for finding product and service related information on the internet |
US5597312A (en) | 1994-05-04 | 1997-01-28 | U S West Technologies, Inc. | Intelligent tutoring method and system |
US5465286A (en) | 1994-05-24 | 1995-11-07 | Executone Information Systems, Inc. | Apparatus for supervising an automatic call distribution telephone system |
US5784452A (en) | 1994-06-01 | 1998-07-21 | Davox Corporation | Telephony call center with agent work groups |
US5590171A (en) | 1994-07-07 | 1996-12-31 | Bellsouth Corporation | Method and apparatus for communications monitoring |
US6130668A (en) | 1994-07-25 | 2000-10-10 | Apple Computer, Inc. | Supervisory control system for networked multimedia workstations that provides simultaneous observation of multiple remote workstations |
US5619183A (en) | 1994-09-12 | 1997-04-08 | Richard C. Ziegra | Video audio data remote system |
US5982857A (en) | 1994-10-17 | 1999-11-09 | Apropros Technology | Voice recording method and system providing context specific storage and retrieval |
US6244758B1 (en) | 1994-11-15 | 2001-06-12 | Absolute Software Corp. | Apparatus and method for monitoring electronic devices via a global network |
US6091712A (en) | 1994-12-23 | 2000-07-18 | Applied Digital Access, Inc. | Method and apparatus for storing and retrieving performance data collected by a network interface unit |
US5742670A (en) | 1995-01-09 | 1998-04-21 | Ncr Corporation | Passive telephone monitor to control collaborative systems |
US5696906A (en) | 1995-03-09 | 1997-12-09 | Continental Cablevision, Inc. | Telecommunicaion user account management system and method |
ATE330416T1 (en) | 1995-04-24 | 2006-07-15 | Ibm | METHOD AND APPARATUS FOR SKILL-BASED ROUTING IN A CALL CENTER |
US5721842A (en) | 1995-08-25 | 1998-02-24 | Apex Pc Solutions, Inc. | Interconnection system for viewing and controlling remotely connected computers with on-screen video overlay for controlling of the interconnection switch |
US5748499A (en) | 1995-09-19 | 1998-05-05 | Sony Corporation | Computer graphics data recording and playback system with a VCR-based graphic user interface |
US5884032A (en) | 1995-09-25 | 1999-03-16 | The New Brunswick Telephone Company, Limited | System for coordinating communications via customer contact channel changing system using call centre for setting up the call between customer and an available help agent |
US6122668A (en) | 1995-11-02 | 2000-09-19 | Starlight Networks | Synchronization of audio and video signals in a live multicast in a LAN |
US5717879A (en) | 1995-11-03 | 1998-02-10 | Xerox Corporation | System for the capture and replay of temporal data representing collaborative activities |
US5778182A (en) | 1995-11-07 | 1998-07-07 | At&T Corp. | Usage management system |
US6052454A (en) | 1996-01-16 | 2000-04-18 | Global Tel*Link Corp. | Telephone apparatus with recording of phone conversations on massive storage |
US5826014A (en) | 1996-02-06 | 1998-10-20 | Network Engineering Software | Firewall system for protecting network elements connected to a public network |
US6225993B1 (en) | 1996-04-22 | 2001-05-01 | Sun Microsystems, Inc. | Video on demand applet method and apparatus for inclusion of motion video in multimedia documents |
US5727950A (en) | 1996-05-22 | 1998-03-17 | Netsage Corporation | Agent based instruction system and method |
US6018619A (en) | 1996-05-24 | 2000-01-25 | Microsoft Corporation | Method, system and apparatus for client-side usage tracking of information server systems |
US20030144900A1 (en) | 2002-01-28 | 2003-07-31 | Whitmer Michael L. | Method and system for improving enterprise performance |
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 |
US5907680A (en) | 1996-06-24 | 1999-05-25 | Sun Microsystems, Inc. | Client-side, server-side and collaborative spell check of URL's |
US5862330A (en) | 1996-07-16 | 1999-01-19 | Lucent Technologies Inc. | Technique for obtaining and exchanging information on wolrd wide web |
US6157808A (en) | 1996-07-17 | 2000-12-05 | Gpu, Inc. | Computerized employee certification and training system |
US5809247A (en) | 1996-07-22 | 1998-09-15 | Intel Corporation | Method and apparatus for guided touring of internet/intranet websites |
US5933811A (en) | 1996-08-20 | 1999-08-03 | Paul D. Angles | System and method for delivering customized advertisements within interactive communication systems |
US6014134A (en) | 1996-08-23 | 2000-01-11 | U S West, Inc. | Network-based intelligent tutoring system |
US5923746A (en) | 1996-09-18 | 1999-07-13 | Rockwell International Corp. | Call recording system and method for use with a telephonic switch |
DK0934581T3 (en) | 1996-09-25 | 2003-03-24 | Sylvan Learning Systems Inc | System for automated testing and electronic dissemination of curriculum and student administration |
GB9620082D0 (en) | 1996-09-26 | 1996-11-13 | Eyretel Ltd | Signal monitoring apparatus |
US5944791A (en) | 1996-10-04 | 1999-08-31 | Contigo Software Llc | Collaborative web browser |
US5809250A (en) | 1996-10-23 | 1998-09-15 | Intel Corporation | Methods for creating and sharing replayable modules representive of Web browsing session |
US6487195B1 (en) | 1996-10-23 | 2002-11-26 | Ncr Corporation | Collaborative network navigation synchronization mechanism |
US6039575A (en) | 1996-10-24 | 2000-03-21 | National Education Corporation | Interactive learning system with pretest |
US5948061A (en) | 1996-10-29 | 1999-09-07 | Double Click, Inc. | Method of delivery, targeting, and measuring advertising over networks |
US5990852A (en) | 1996-10-31 | 1999-11-23 | Fujitsu Limited | Display screen duplication system and method |
US5864772A (en) | 1996-12-23 | 1999-01-26 | Schlumberger Technology Corporation | Apparatus, system and method to transmit and display acquired well data in near real time at a remote location |
US5903641A (en) * | 1997-01-28 | 1999-05-11 | Lucent Technologies Inc. | Automatic dynamic changing of agents' call-handling assignments |
US5917489A (en) | 1997-01-31 | 1999-06-29 | Microsoft Corporation | System and method for creating, editing, and distributing rules for processing electronic messages |
US6560328B1 (en) | 1997-04-03 | 2003-05-06 | Genesys Telecommunications Laboratories, Inc. | Voice extensions in a call-in center employing virtual restructuring for computer telephony integrated functionality |
US5978648A (en) | 1997-03-06 | 1999-11-02 | Forte Systems, Inc. | Interactive multimedia performance assessment system and process for use by students, educators and administrators |
US6301573B1 (en) | 1997-03-21 | 2001-10-09 | Knowlagent, Inc. | Recurrent training system |
US5796952A (en) | 1997-03-21 | 1998-08-18 | Dot Com Development, Inc. | Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database |
US6078894A (en) | 1997-03-28 | 2000-06-20 | Clawson; Jeffrey J. | Method and system for evaluating the performance of emergency medical dispatchers |
US6578077B1 (en) | 1997-05-27 | 2003-06-10 | Novell, Inc. | Traffic monitoring tool for bandwidth management |
US6171109B1 (en) | 1997-06-18 | 2001-01-09 | Adin Research, Inc. | Method for generating a multi-strata model and an intellectual information processing device |
US6282548B1 (en) | 1997-06-21 | 2001-08-28 | Alexa Internet | Automatically generate and displaying metadata as supplemental information concurrently with the web page, there being no link between web page and metadata |
ID24894A (en) | 1997-06-25 | 2000-08-31 | Samsung Electronics Co Ltd Cs | METHOD AND APPARATUS FOR THREE-OTO DEVELOPMENTS A HOME NETWORK |
US6014647A (en) | 1997-07-08 | 2000-01-11 | Nizzari; Marcia M. | Customer interaction tracking |
US5958016A (en) | 1997-07-13 | 1999-09-28 | Bell Atlantic Network Services, Inc. | Internet-web link for access to intelligent network service control |
US6076099A (en) | 1997-09-09 | 2000-06-13 | Chen; Thomas C. H. | Method for configurable intelligent-agent-based wireless communication system |
US5964836A (en) | 1997-09-11 | 1999-10-12 | International Business Machines Corporation | Apparatus, methods and computer program products for managing web-page-embedded sessions with a host-based application |
US5991373A (en) | 1997-09-15 | 1999-11-23 | Teknekron Infoswitch Corporation | Reproduction of a voice and video session |
US7225249B1 (en) * | 1997-09-26 | 2007-05-29 | Mci, Llc | Integrated systems for providing communications network management services and interactive generating invoice documents |
US6035332A (en) | 1997-10-06 | 2000-03-07 | Ncr Corporation | Method for monitoring user interactions with web pages from web server using data and command lists for maintaining information visited and issued by participants |
US6418471B1 (en) | 1997-10-06 | 2002-07-09 | Ncr Corporation | Method for recording and reproducing the browsing activities of an individual web browser |
US6546405B2 (en) | 1997-10-23 | 2003-04-08 | Microsoft Corporation | Annotating temporally-dimensioned multimedia content |
US6351467B1 (en) | 1997-10-27 | 2002-02-26 | Hughes Electronics Corporation | System and method for multicasting multimedia content |
US6009429A (en) | 1997-11-13 | 1999-12-28 | International Business Machines Corporation | HTML guided web tour |
US5987466A (en) | 1997-11-25 | 1999-11-16 | International Business Machines Corporation | Presenting web pages with discrete, browser-controlled complexity levels |
US6286046B1 (en) | 1997-12-22 | 2001-09-04 | International Business Machines Corporation | Method of recording and measuring e-business sessions on the world wide web |
US6005932A (en) | 1997-12-24 | 1999-12-21 | Rockwell Semiconductor Systems Inc. | Dynamic schedule profiler for ACD |
US6195679B1 (en) | 1998-01-06 | 2001-02-27 | Netscape Communications Corporation | Browsing session recording playback and editing system for generating user defined paths and allowing users to mark the priority of items in the paths |
JP3371791B2 (en) | 1998-01-29 | 2003-01-27 | ヤマハ株式会社 | Music training system and music training device, and recording medium on which music training program is recorded |
US6151622A (en) | 1998-02-02 | 2000-11-21 | International Business Machines Corp. | Method and system for portably enabling view synchronization over the world-wide web using frame hierarchies |
US6144991A (en) | 1998-02-19 | 2000-11-07 | Telcordia Technologies, Inc. | System and method for managing interactions between users in a browser-based telecommunications network |
US6138139A (en) | 1998-10-29 | 2000-10-24 | Genesys Telecommunications Laboraties, Inc. | Method and apparatus for supporting diverse interaction paths within a multimedia communication center |
US6230197B1 (en) | 1998-09-11 | 2001-05-08 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for rules-based storage and retrieval of multimedia interactions within a communication center |
US6038544A (en) | 1998-02-26 | 2000-03-14 | Teknekron Infoswitch Corporation | System and method for determining the performance of a user responding to a call |
US20010043697A1 (en) | 1998-05-11 | 2001-11-22 | Patrick M. Cox | Monitoring of and remote access to call center activity |
US6154771A (en) | 1998-06-01 | 2000-11-28 | Mediastra, Inc. | Real-time receipt, decompression and play of compressed streaming video/hypervideo; with thumbnail display of past scenes and with replay, hyperlinking and/or recording permissively intiated retrospectively |
US6347374B1 (en) | 1998-06-05 | 2002-02-12 | Intrusion.Com, Inc. | Event detection |
CN1139254C (en) | 1998-06-26 | 2004-02-18 | 通用仪器公司 | Terminal for composing and presenting MPEG-4 video programs |
US6286030B1 (en) | 1998-07-10 | 2001-09-04 | Sap Aktiengesellschaft | Systems and methods for recording and visually recreating sessions in a client-server environment |
US6122665A (en) | 1998-08-26 | 2000-09-19 | Sts Software System Ltd. | Communication management system for computer network-based telephones |
FR2782875B1 (en) | 1998-08-27 | 2000-11-03 | France Telecom | TELEPHONE DEVICE FOR PRISON |
US6493758B1 (en) | 1998-09-08 | 2002-12-10 | Microsoft Corporation | Offline viewing of internet content with a mobile device |
US6353851B1 (en) | 1998-12-28 | 2002-03-05 | Lucent Technologies Inc. | Method and apparatus for sharing asymmetric information and services in simultaneously viewed documents on a communication system |
US6411989B1 (en) | 1998-12-28 | 2002-06-25 | Lucent Technologies Inc. | Apparatus and method for sharing information in simultaneously viewed documents on a communication system |
US6360250B1 (en) | 1998-12-28 | 2002-03-19 | Lucent Technologies Inc. | Apparatus and method for sharing information in simultaneously viewed documents on a communication system |
US6236977B1 (en) | 1999-01-04 | 2001-05-22 | Realty One, Inc. | Computer implemented marketing system |
US6301462B1 (en) | 1999-01-15 | 2001-10-09 | Unext. Com | Online collaborative apprenticeship |
US6606657B1 (en) | 1999-06-22 | 2003-08-12 | Comverse, Ltd. | System and method for processing and presenting internet usage information |
US6288753B1 (en) | 1999-07-07 | 2001-09-11 | Corrugated Services Corp. | System and method for live interactive distance learning |
US6289340B1 (en) | 1999-08-03 | 2001-09-11 | Ixmatch, Inc. | Consultant matching system and method for selecting candidates from a candidate pool by adjusting skill values |
US6665644B1 (en) | 1999-08-10 | 2003-12-16 | International Business Machines Corporation | Conversational data mining |
US6772396B1 (en) | 1999-10-07 | 2004-08-03 | Microsoft Corporation | Content distribution system for network environments |
US6823384B1 (en) | 1999-10-15 | 2004-11-23 | James Wilson | Methods and apparatus for securely collecting customer service agent data in a multi-tenant environment |
US6792575B1 (en) | 1999-10-21 | 2004-09-14 | Equilibrium Technologies | Automated processing and delivery of media to web servers |
US6901438B1 (en) | 1999-11-12 | 2005-05-31 | Bmc Software | System selects a best-fit form or URL in an originating web page as a target URL for replaying a predefined path through the internet |
US6535909B1 (en) | 1999-11-18 | 2003-03-18 | Contigo Software, Inc. | System and method for record and playback of collaborative Web browsing session |
US6674447B1 (en) | 1999-12-06 | 2004-01-06 | Oridus, Inc. | Method and apparatus for automatically recording snapshots of a computer screen during a computer session for later playback |
US7613695B1 (en) | 1999-12-06 | 2009-11-03 | Reed Elsevier Inc. | Relationship management system that provides an indication of users having a relationship with a specified contact |
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 |
IL141002A0 (en) | 2000-01-24 | 2002-02-10 | Comverse Infosys Inc | Open storage portal apparatus and method to access contact center information |
US6724887B1 (en) | 2000-01-24 | 2004-04-20 | Verint Systems, Inc. | Method and system for analyzing customer communications with a contact center |
US6810414B1 (en) | 2000-02-04 | 2004-10-26 | Dennis A. Brittain | System and methods for easy-to-use periodic network data capture engine with automatic target data location, extraction and storage |
US6970829B1 (en) * | 2000-02-14 | 2005-11-29 | Iex Corporation | Method and system for skills-based planning and scheduling in a workforce contact center environment |
US6542602B1 (en) | 2000-02-14 | 2003-04-01 | Nice Systems Ltd. | Telephone call monitoring system |
US6775377B2 (en) | 2001-09-10 | 2004-08-10 | Knowlagent, Inc. | Method and system for delivery of individualized training to call center agents |
US6324282B1 (en) | 2000-03-02 | 2001-11-27 | Knowlagent, Inc. | Method and system for delivery of individualized training to call center agents |
AU2001245426A1 (en) | 2000-03-03 | 2001-09-17 | Lawrence R. Jones | Picture communications system and associated network services |
US6683633B2 (en) | 2000-03-20 | 2004-01-27 | Incontext Enterprises, Inc. | Method and system for accessing information |
US6697858B1 (en) | 2000-08-14 | 2004-02-24 | Telephony@Work | Call center |
EP1189161A1 (en) | 2000-09-13 | 2002-03-20 | iMediation, S.A. | A method and system for managing network-based partner relationships |
US7287071B2 (en) | 2000-09-28 | 2007-10-23 | Vignette Corporation | Transaction management system |
US20020065911A1 (en) | 2000-10-03 | 2002-05-30 | Von Klopp Ana H. | HTTP transaction monitor with edit and replay capacity |
AU2002235147A1 (en) | 2000-11-30 | 2002-06-11 | Webtone Technologies, Inc. | Web session collaboration |
AU2002230735A1 (en) | 2000-12-11 | 2002-06-24 | Phlair, Inc. | System and method for detecting and reporting online activity using real-time content-based network monitoring |
US20020143925A1 (en) | 2000-12-29 | 2002-10-03 | Ncr Corporation | Identifying web-log data representing a single user session |
US7054933B2 (en) * | 2001-03-19 | 2006-05-30 | Polycom, Inc. | Self-tuning statistical resource allocation for multipoint network events |
US7506047B2 (en) | 2001-03-30 | 2009-03-17 | Bmc Software, Inc. | Synthetic transaction monitor with replay capability |
US6944660B2 (en) | 2001-05-04 | 2005-09-13 | Hewlett-Packard Development Company, L.P. | System and method for monitoring browser event activities |
US7110525B1 (en) * | 2001-06-25 | 2006-09-19 | Toby Heller | Agent training sensitive call routing system |
US20040100507A1 (en) | 2001-08-24 | 2004-05-27 | Omri Hayner | System and method for capturing browser sessions and user actions |
US6738456B2 (en) | 2001-09-07 | 2004-05-18 | Ronco Communications And Electronics, Inc. | School observation and supervisory system |
US6870916B2 (en) | 2001-09-14 | 2005-03-22 | Lucent Technologies Inc. | Targeted and intelligent multimedia conference establishment services |
US20030079020A1 (en) | 2001-10-23 | 2003-04-24 | Christophe Gourraud | Method, system and service provider for IP media program transfer-and-viewing-on-demand |
US6965886B2 (en) | 2001-11-01 | 2005-11-15 | Actimize Ltd. | System and method for analyzing and utilizing data, by executing complex analytical models in real time |
US6801618B2 (en) | 2002-02-08 | 2004-10-05 | Etalk Corporation | System and method for implementing recording plans using a session manager |
US7451207B2 (en) * | 2002-06-28 | 2008-11-11 | Intel Corporation | Predictive provisioning of media resources |
US20050283393A1 (en) * | 2003-11-20 | 2005-12-22 | New England 800 Company D/B/A Taction | System and method for event-based forecasting |
US20050138560A1 (en) | 2003-12-18 | 2005-06-23 | Kuo-Chun Lee | Method and apparatus for broadcasting live personal performances over the internet |
-
2006
- 2006-03-21 US US11/385,499 patent/US7734783B1/en active Active
-
2010
- 2010-03-16 US US12/725,127 patent/US20100172485A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6493446B1 (en) * | 1999-05-13 | 2002-12-10 | Willow Csn Incorporated | Call center posting program |
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 |
US7085728B2 (en) * | 2001-07-31 | 2006-08-01 | Iex Corporation | Method for forecasting and managing multimedia contracts |
US7095841B2 (en) * | 2002-03-29 | 2006-08-22 | Avaya Technology Corp. | Queued task/queued resource state forecaster |
US20040062380A1 (en) * | 2002-09-26 | 2004-04-01 | Delaney Paul J. | Contact center management |
US7406171B2 (en) * | 2003-12-19 | 2008-07-29 | At&T Delaware Intellectual Property, Inc. | Agent scheduler incorporating agent profiles |
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 |
US7660407B2 (en) * | 2006-06-27 | 2010-02-09 | Verint Americas Inc. | Systems and methods for scheduling contact center agents |
Cited By (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9369577B2 (en) | 2008-07-30 | 2016-06-14 | Interactions Llc | Transparent voice registration and verification method and system |
US8077836B2 (en) * | 2008-07-30 | 2011-12-13 | At&T Intellectual Property, I, L.P. | Transparent voice registration and verification method and system |
US20100027767A1 (en) * | 2008-07-30 | 2010-02-04 | At&T Intellectual Property I, L.P. | Transparent voice registration and verification method and system |
US8406382B2 (en) | 2008-07-30 | 2013-03-26 | At&T Intellectual Property I, L.P. | Transparent voice registration and verification method and system |
US8913720B2 (en) | 2008-07-30 | 2014-12-16 | At&T Intellectual Property, L.P. | Transparent voice registration and verification method and system |
US9924038B2 (en) | 2008-12-19 | 2018-03-20 | Genesys Telecommunications Laboratories, Inc. | Method and system for integrating an interaction management system with a business rules management system |
US9538010B2 (en) | 2008-12-19 | 2017-01-03 | Genesys Telecommunications Laboratories, Inc. | Method and system for integrating an interaction management system with a business rules management system |
US10250750B2 (en) | 2008-12-19 | 2019-04-02 | Genesys Telecommunications Laboratories, Inc. | Method and system for integrating an interaction management system with a business rules management system |
US20100215169A1 (en) * | 2009-02-25 | 2010-08-26 | Herbert Willi Artur Ristock | Virtualization of One or More Sets of Physical Contact Center Resources for Use by One or More Virtual Contact Centers |
US8085693B2 (en) * | 2009-02-25 | 2011-12-27 | Genesys Telecommunications Laboratories, Inc | Virtualization of one or more sets of physical contact center resources for use by one or more virtual contact centers |
US9992336B2 (en) | 2009-07-13 | 2018-06-05 | Genesys Telecommunications Laboratories, Inc. | System for analyzing interactions and reporting analytic results to human operated and system interfaces in real time |
US20120087486A1 (en) * | 2010-10-09 | 2012-04-12 | Jose Luis Beltran Guerrero | Call center resource allocation |
US8396204B2 (en) * | 2010-10-09 | 2013-03-12 | Hewlett-Packard Development Company, L.P. | Call center resource allocation |
US8391466B1 (en) * | 2012-07-24 | 2013-03-05 | Noble Systems Corporation | Generating communication forecasts and schedules based on multiple outbound campaigns |
CN108287750A (en) * | 2012-09-12 | 2018-07-17 | 格林伊登美国控股有限责任公司 | System and method for the dynamic elasticity for providing liaison centre's resource |
US20140108022A1 (en) * | 2012-10-12 | 2014-04-17 | American Well Systems | Brokerage System Employing Minimal Criteria Matching and Availability Queuing |
US10298766B2 (en) | 2012-11-29 | 2019-05-21 | Genesys Telecommunications Laboratories, Inc. | Workload distribution with resource awareness |
WO2014085760A1 (en) * | 2012-11-29 | 2014-06-05 | Genesys Telecommunications Laboratories, Inc. | Workload distribution with resource awareness |
US9912816B2 (en) | 2012-11-29 | 2018-03-06 | Genesys Telecommunications Laboratories, Inc. | Workload distribution with resource awareness |
US9542936B2 (en) | 2012-12-29 | 2017-01-10 | Genesys Telecommunications Laboratories, Inc. | Fast out-of-vocabulary search in automatic speech recognition systems |
US10290301B2 (en) | 2012-12-29 | 2019-05-14 | Genesys Telecommunications Laboratories, Inc. | Fast out-of-vocabulary search in automatic speech recognition systems |
US10567587B2 (en) | 2014-03-20 | 2020-02-18 | Genesys Telecommunications Laboratories, Inc. | Resource sharing in a peer-to-peer network of contact center nodes |
US9774739B2 (en) | 2014-03-20 | 2017-09-26 | Genesys Telecommunications Laboratories, Inc. | Resource sharing in a peer-to-peer network of contact center nodes |
US9588830B2 (en) | 2014-03-20 | 2017-03-07 | Genesys Telecommunications Laboratories, Inc. | Local survivability in a distributed contact center environment |
WO2015143408A1 (en) * | 2014-03-20 | 2015-09-24 | Genesys Telecommunications Laboratories, Inc. | Local survivability in a distributed contact center environment |
US10462299B2 (en) * | 2014-09-23 | 2019-10-29 | Interactive Intelligence Group, Inc. | Method and system for creating contact center models |
US9787840B1 (en) | 2015-06-11 | 2017-10-10 | Noble Systems Corporation | Forecasting and scheduling campaigns involving different channels of communication |
US9924040B1 (en) | 2015-06-11 | 2018-03-20 | Noble Systems Corporation | Forecasting and scheduling campaigns involving different channels of communication |
US9600789B1 (en) | 2015-10-16 | 2017-03-21 | Noble Systems Corporation | Forecasting and scheduling campaigns involving sending outbound communications that generate inbound communications |
US9426291B1 (en) | 2015-10-16 | 2016-08-23 | Noble Systems Corporation | Forecasting and scheduling campaigns involving sending outbound communications that generate inbound communications |
US9531881B1 (en) | 2015-10-16 | 2016-12-27 | Noble Systems Corporation | Forecasting and scheduling campaigns involving sending outbound communications that generate inbound communications |
US9736304B1 (en) | 2015-10-16 | 2017-08-15 | Noble Systems Corporation | Forecasting and scheduling campaigns involving sending outbound communications that generate inbound communications |
US10691692B2 (en) | 2016-04-29 | 2020-06-23 | Fujitsu Limited | Computer-implemented method of executing a query in a network of data centres |
US20180374176A1 (en) * | 2017-06-26 | 2018-12-27 | Datalign Ltd | Automated government resource allocation |
US20220101220A1 (en) * | 2020-09-30 | 2022-03-31 | Genesys Telecommunications Laboratories, Inc. | Method and system for dynamic adaptive routing of deferrable work in a contact center |
Also Published As
Publication number | Publication date |
---|---|
US7734783B1 (en) | 2010-06-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7734783B1 (en) | Systems and methods for determining allocations for distributed multi-site contact centers | |
US9020142B2 (en) | System and method for generating forecasts and analysis of contact center behavior for planning purposes | |
US7660406B2 (en) | Systems and methods for integrating outsourcers | |
US8396204B2 (en) | Call center resource allocation | |
US7386113B2 (en) | System and method for integrated resource scheduling and agent work management | |
US7953621B2 (en) | Systems and methods for displaying agent activity exceptions | |
US8705723B2 (en) | Systems and methods for scheduling contact center agents | |
US9589244B2 (en) | Request process optimization and management | |
US20070201679A1 (en) | Method and system for assessing and deploying personnel for roles in a contact center | |
US8873732B2 (en) | Systems and methods for scheduling of outbound agents | |
Fukunaga et al. | Staff scheduling for inbound call and customer contact centers | |
US10037500B2 (en) | System and method for automatic shrinkage forecasting | |
US7899176B1 (en) | Systems and methods for discovering customer center information | |
Wagenaar | Analysis of the Avis Car Rental South Africa Call Centre | |
Wu | Assessing and improving performance for a small contact centre |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:VERINT SYSTEMS INC.;REEL/FRAME:026208/0727 Effective date: 20110429 |
|
AS | Assignment |
Owner name: WITNESS SYSTEMS, INC., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BOURKE, MIKE;FAMA, JASON;JOSEFSBERG, GAL;SIGNING DATES FROM 20060306 TO 20060419;REEL/FRAME:028948/0422 |
|
AS | Assignment |
Owner name: VERINT AMERICAS INC., NEW YORK Free format text: CHANGE OF NAME;ASSIGNOR:WITNESS SYSTEMS, INC.;REEL/FRAME:029970/0012 Effective date: 20070525 |
|
AS | Assignment |
Owner name: VERINT AMERICAS INC., GEORGIA Free format text: CHANGE OF NAME;ASSIGNOR:WITNESS SYSTEMS, INC.;REEL/FRAME:030112/0585 Effective date: 20070525 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: GRANT OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:VERINT AMERICAS INC.;REEL/FRAME:031465/0450 Effective date: 20130918 Owner name: VERINT AMERICAS INC., NEW YORK Free format text: RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT;REEL/FRAME:031448/0373 Effective date: 20130918 Owner name: VERINT VIDEO SOLUTIONS INC., NEW YORK Free format text: RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT;REEL/FRAME:031448/0373 Effective date: 20130918 Owner name: VERINT SYSTEMS INC., NEW YORK Free format text: RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT;REEL/FRAME:031448/0373 Effective date: 20130918 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, DISTRICT OF COLUMBIA Free format text: GRANT OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:VERINT AMERICAS INC.;REEL/FRAME:031465/0450 Effective date: 20130918 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |
|
AS | Assignment |
Owner name: VERINT AMERICAS INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:043066/0473 Effective date: 20170629 |