US20210117884A1 - Systems and methods for workforce management system deployment - Google Patents
Systems and methods for workforce management system deployment Download PDFInfo
- Publication number
- US20210117884A1 US20210117884A1 US16/656,139 US201916656139A US2021117884A1 US 20210117884 A1 US20210117884 A1 US 20210117884A1 US 201916656139 A US201916656139 A US 201916656139A US 2021117884 A1 US2021117884 A1 US 2021117884A1
- Authority
- US
- United States
- Prior art keywords
- agent
- agents
- contact center
- hours
- application
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- G06F16/909—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
- G06Q10/063114—Status monitoring or status determination for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06312—Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1091—Recording time for administrative or management purposes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
- G06Q10/1097—Task assignment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
- G06Q30/0202—Market predictions or forecasting for commercial activities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5175—Call or contact centers supervision arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
- H04M3/5232—Call distribution algorithms
- H04M3/5233—Operator skill based call distribution
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
- H04M2203/2072—Schedules, e.g. personal calendars
-
- 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
- WFM contact center workforce management
- a system for quickly deploying WFM systems in contact centers is provided.
- a user or administrator can quickly install a WFM application on a deployment server.
- the administrator can provide the WFM application access to the contact center data where the WFM application can import data from the contact center about one or more customers, agents, queues, teams, and any other information or items typically associated with contact centers.
- the imported data may also include presence data about the agents, teams, and customers.
- the WFM application may execute one or more workflows to automatically determine information such as maximum and minimum hours, break patterns, and shift data about the agents and teams. This information can be used by the WFM system to automatically generate forecasts and schedules.
- the WFM deployment systems and methods described herein provide many advantages over the prior art. By leveraging the information that is already part of the contact center used by an entity, WFM systems can be easily and quickly deployed without significant input from an administrator. Accordingly, the WFM deployment systems and applications described herein can save these entities significant time and money.
- a method for configuring an application for a contact center includes: interfacing with a contact center by an application; receiving contact center data from the contact center by the application; receiving a selection of an item of the application to configure by the application; based on the selected item, selecting a workflow corresponding to the selected item by the application; and configuring the item of the application automatically using the selected workflow and the contact center data by the application.
- Embodiments may include some or all of the following features.
- the application may be a WFM application.
- the method may further include: determining a plurality of agents associated with the contact center; and configuring the item of the application automatically using the selected workflow and the contact center data by the application comprises: configuring one or more of a minimum hours for the at least one agent, a break pattern for the at least one agent, and a shift for the at least one agent.
- the method may further include retrieving presence data for each agent from the contact center, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time.
- the method may further include: for the at least one agent of the plurality of agents, determining a location for the agent; retrieving one or more rules that relate to scheduling for the determined location; and for the at least one agent of the plurality of agents, generating the schedule for the at least one agent based on the one or more rules and the minimum hours for the at least one agent.
- Determining a location for the agent may include determining a telephone number associated with the agent and determining the location for the agent based on the telephone number.
- Interfacing with the contact center by the application may include: requesting credentials from a user associated with the contact center; and interfacing with the contact center using the requested credentials.
- a method for configuring a workforce management system for a contact center includes: interfacing with a contact center by a workforce management system; determining a plurality of agents associated with the contact center by the workforce management system; retrieving presence data for each agent from the contact center by the workforce management system, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time; for at least one agent of the plurality of agents, determining a maximum hours for the at least one agent based on the presence data for the agent by the workforce management system; and for the at least one agent of the plurality of agents, generating a schedule for the at least one agent based on the determined maximum hours by the workforce management system.
- Embodiments may include some or all of the following features.
- the method may further include: for the at least one agent of the plurality of agents, determining a location for the at least one agent; retrieving one or more rules that relate to scheduling for the location; and for the at least one agent of the plurality of agents, determining the maximum hours for the at least one agent based on the presence data for the at least one agent and the one or more rules.
- Determining the maximum hours for the at least one agent based on the presence data for the at least one agent may include: inferring, from the presence data, a number of hours worked by the at least one agent for each week of a plurality of weeks; and determining the maximum hours for the at least one agent based on the number of hours worked by the at least one agent for each week of the plurality of weeks.
- the events may include one or more of computer logins, computer logouts, communications, and application activities.
- the method may further include for the at least one agent of the plurality of agents, determining a minimum hours for the at least one agent based on the presence data for the at least one agent.
- the method may further include for the at least one agent of the plurality of agents, generating the schedule for the at least one agent based on the determined maximum hours and the determined minimum hours.
- the method may further include, for the at least one agent of the plurality of agents, determining, based on the presence data, one or more shifts that the at least one agent is available to work, and one or more break patterns associated with the at least one agent.
- the method may further include generating the schedule for the at least one agent based on the determined maximum hours, the determined one or more shifts that the at least one agent is available to work, and the determined one or more break patterns associated with the at least one agent.
- a method for configuring a workforce management system for a contact center includes: interfacing with a contact center by a workforce management system; determining a plurality of agents associated with the contact center by the workforce management system; retrieving presence data for each agent from the contact center by the workforce management system, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time; for at least one agent of the plurality of agents, determining one or more shifts for the at least one agent based on the presence data for the at least one agent by the workforce management system; and for the at least one agent of the plurality of agents, generating a schedule for the at least one agent by the workforce management system based on the determined one or more shifts.
- Embodiments may have some or all of the following features.
- the method may further include: for the at least one agent of the plurality of agents, determining a location for the agent; retrieving one or more rules that relate to scheduling for the location; and for the at least one agent of the plurality of agents, generating the schedule for the at least one agent based on the one or more rules and the determined one or more shifts.
- Determining the one or more shifts for the at least one agent based on the presence data for the at least one agent may include: inferring, from the presence data, times worked by the at least one agent for each week of a plurality of weeks; and determining the one or more shifts for the at least one agent based on the times worked by the at least one agent for each week of the plurality of weeks.
- the events may include one or more of computer logins, computer logouts, communications, and application activities.
- the method may further include, for the at least one agent of the plurality of agents, determining, based on the presence data, maximum hours for the at least one agent, minimum hours for the at least one agent, and a break pattern associated with the at least one agent.
- the method may further include generating the schedule for the at least one agent based on the determined maximum hours, the determined minimum hours, the determined one or more shifts that the at least one agent is available to work, and the determined break pattern associated with the at least one agent.
- Interfacing with the contact center by the workforce management system may include: requesting credentials from a user associated with the contact center; and interfacing with the contact center using the requested credentials.
- a method for configuring a workforce management system for a contact center includes: interfacing with a contact center by a workforce management system; determining a plurality of agents associated with the contact center by the workforce management system; retrieving presence data for each agent from the contact center by the workforce management system, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time; for at least one agent of the plurality of agents, determining a break pattern associated with the at least one agent based on the presence data for the at least one agent by the workforce management system; and for the at least one agent of the plurality of agents, generating a schedule for the at least one agent based on the determined break pattern by the workforce management system.
- Embodiments may include some or all of the following features.
- the method may further include: for the at least one agent of the plurality of agents, determining a location for the agent; retrieving one or more rules that relate to scheduling for the location; and for the at least one agent of the plurality of agents, generating the schedule for the at least one agent based on the one or more rules and the determined break pattern.
- the method may further include: determining the break pattern associated with the at least one agent based on the presence data for the at least one agent comprises: inferring, from the presence data, breaks taken by the at least one agent for each day of a plurality of days; and determining the break pattern for the at least one agent based on the breaks taken by the at least one agent for each day of the plurality of days.
- the events may include one or more of computer logins, computer logouts, communications, and application activities.
- the method may further include, for the at least one agent of the plurality of agents, determining, based on the presence data, maximum hours for the at least one agent, minimum hours for the at least one agent, and one or more shifts that the at least one agent is available to work.
- the method may further include generating the schedule for the at least one agent based on the determined break pattern, the determined minimum hours, the determined maximum hours, and the determined one or more shifts that the at least one agent is available to work.
- Interfacing with the contact center by the workforce management system may include: requesting credentials from a user associated with the contact center; and interfacing with the contact center using the requested credentials.
- FIG. 1 is an illustration of an example system architecture
- FIG. 2 is an illustration of an example environment for installing and configuring a WFM application
- FIG. 3 is an illustration of an example method for configuring a WFM system
- FIG. 4 is an illustration of an example method for automatically configuring items for a WFM application based on data received from a contact center;
- FIGS. 5-7 are illustrations of example methods for automatically configuring a WFM application
- FIG. 8 is an illustration of an example method for automatically configuring a WFM application using workflows and for generating one or more forecasts and schedules;
- FIG. 9 illustrates an example computing device.
- FIG. 1 is an example system architecture 100 , and illustrates example components, functional capabilities and optional modules that may be included in a cloud-based contact center infrastructure solution.
- Customers 110 interact with a contact center 150 using voice, email, text, and web interfaces in order to communicate with the agents 120 through a network 130 and one or more of text or multimedia channels.
- the system that controls the operation of the contact center 150 including the routing and handling of communications between customers 110 and agents 120 for the contact center 150 is referred to herein as the contact routing system 153 .
- the contact routing system 153 could be any of a contact center as a service (CCaS) system, an automated call distributor (ACD) system, or a case system, for example.
- CaS service
- ACD automated call distributor
- the agents 120 may be remote from the contact center 150 and handle communications with customers 110 on behalf of an enterprise.
- the agents 120 may utilize devices, such as but not limited to, work stations, desktop computers, laptops, telephones, a mobile smartphone and/or a tablet.
- customers 110 may communicate using a plurality of devices, including but not limited to, a telephone, a mobile smartphone, a tablet, a laptop, a desktop computer, or other.
- telephone communication may traverse networks such as a public switched telephone networks (PSTN), Voice over Internet Protocol (VoIP) telephony (via the Internet), a Wide Area Network (WAN) or a Large Area Network.
- PSTN public switched telephone networks
- VoIP Voice over Internet Protocol
- WAN Wide Area Network
- Large Area Network The network types are provided by way of example and are not intended to limit types of networks used for communications.
- the agents 120 may be assigned to one or more queues.
- the agents 120 assigned to a queue may handle communications that are placed in the queue by the contact center 150 .
- a communication is received by the contact center 150 , the communication may be placed in a relevant queue, and one of the agents 120 associated with the relevant queue may handle the communication.
- the agents 120 of a contact center 150 may be further organized into one or more teams. Depending on the embodiment, the agents 120 may be organized into teams based on a variety of factors including, but not limited to, skills, location, experience, assigned queues, associated or assigned customers 110 , and shift. Other factors may be used to assign agents 120 to teams.
- WFM systems are used to schedule agents 120 based on workload forecasts. To generate schedules the WFM systems must take into account information such as local employment laws, time and shift preferences of each agent 120 , and the skills of each agent 120 , for example.
- the environment 100 further includes a WFM application 250 that may be used to quickly deploy and configure WFM systems.
- the workings of the application 250 will be described in further detail with respect to FIG. 2 .
- a deployment sever 170 may implement the WFM system for the contact center 150 .
- the WFM system may be implemented on its own deployment server 170 .
- some or all of the contact routing system 153 or the WFM system may be implemented together on the same computer, deployment server 170 , or cloud-computing environment.
- An example deployment server 170 is the computing system 900 illustrated with respect to FIG. 9 .
- the administrator may then cause the WFM application 250 to be installed on the deployment server 170 by an application server 160 .
- the application server 160 may function similar to an “app store” where the administrator of the contact center 150 may view one or more applications (including the application 250 ) that are available for download. After selecting the WFM application 250 , the application server 160 may cause the application 250 to be installed on the deployment server 170 .
- the application 250 may be configured to interface with, and retrieve data from, the contact routing system 153 .
- the contact routing system 153 already includes data that is relevant to the WFM application 250 (e.g., information on agents 120 such as hours worked and schedules, and information on customers 110 such as communications received), it may be desirable to import the data directly from the contact routing system 153 .
- the application may have one or more workflows that can be executed by the administrator to automatically set up and configure the application using the imported data.
- Each workflow may attempt to configure the application from the imported data with as little input from the administrator as possible.
- the administrator may be asked to confirm or accept any proposed configurations or settings suggested by the workflow.
- workflows that infer, for each agent 120 or team of agents 120 , settings for the application 250 such as agent 120 hours, schedules, and work preferences.
- settings for the application 250 such as agent 120 hours, schedules, and work preferences.
- the embodiments described herein are not limited to configuring the WFM applications 250 using data imported from a contact routing system 153 .
- Other sources of data may be used.
- the application 250 may import data from a variety of systems including, but not limited to, customer relationship management systems and document management systems. Other systems may be included.
- FIG. 2 is an illustration of an example environment 200 for installing and configuring a WFM application 250 .
- the environment 200 includes a deployment server 170 , a contact center 150 including a contact routing system 153 , and an administrator 290 .
- each of the contact routing system 153 , deployment server 170 , and administrator 290 may be implemented together or separately by one or more general purpose computing devices such as the computing system 900 illustrated with respect to FIG. 9 .
- the administrator 290 may cause the WFM application 250 to be installed on the deployment server 170 .
- the administrator 290 may allow the WFM application 250 to access the contact routing system 153 .
- the administrator 290 may provide credentials (e.g., login and password) to the WFM application 250 , and the WFM application 250 may use an API to access the contact routing system 153 using the credentials.
- credentials e.g., login and password
- Other methods for accessing a contact routing system 153 (or other data source) may be used.
- the WFM application 250 may initially download contact center data 159 and may begin using the contact center data 159 to configure the WFM application 250 for the administrator 290 .
- the contact center data 159 may include information about the contact center 150 such as information about the agents 120 , teams that the agents 120 are organized into, queues associated with the contact center 150 , contacts 110 associated with the contact center 150 , skills associated with the agents 120 and queues, historical contact data (e.g., historical data for each queue about the volume of contacts, handling times, etc.), and event types.
- the contact center data 159 may further include information such as consistency rules (e.g., rules about whether shifts need to start and stop at the same time), and presence data (e.g., data showing when agents 120 were available to receive communications or interact with customers 110 ). Other information may be included in the contact center data 159 .
- consistency rules e.g., rules about whether shifts need to start and stop at the same time
- presence data e.g., data showing when agents 120 were available to receive communications or interact with customers 110 .
- Other information may be included in the contact center data 159 .
- the WFM application 250 may use some or all of the contact center data 159 to begin setting up the WFM application 250 for the administrator 290 .
- the WFM application 250 may extract all of the agents 120 associated with the contact center 150 and may enter them into the WFM application 250 .
- the WFM application 250 may similarly, extract information such as the customers 110 associated with the contact center 150 , the queues associated with the contact center 150 , and any teams associated with the contact center 150 .
- the WFM application 250 may provide a graphical-user interface (GUI) through which the administrator 290 can review and control what information is imported into the WFM application 250 from the contact center data 159 .
- GUI graphical-user interface
- the WFM application 250 may ask the administrator 290 to confirm each agent 120 , contact 110 , or team that it extracts from the contact center 150 .
- the administrator 290 may also use the GUI to add any additional information to the WFM application 250 including any agents 120 , customers 110 , teams, or queues that the WFM application 250 was unable to extract from the contact center data 159 .
- the administrator 290 would have had to manually add each agent 120 , contact 110 , queue, or team to the WFM application 250 .
- the WFM application 250 described herein may use one or more workflows to infer additional WFM application 250 items or settings to further reduce the amount of time that the administrator 290 may spend configuring the application.
- the WFM application 250 may use workflows to infer or more items such as minimum or maximum hours 171 for agents 120 individually or as a team, shifts 172 that each agent 120 can work individually or as a team, break patterns 173 associated with each agent 120 or team, and start rules 173 for each agent 120 or team. Other items may be inferred and configured by the WFM application 250 using a workflow.
- the WFM application 250 may infer the one or more items from what is referred to herein as presence data 155 .
- the presence data 155 may include a plurality of events associated with each agent 120 or customer 110 , and each event may be associated with a time.
- the events may include logging in or out of a computer, receiving or responding to a communication such as an email or telephone call, and updating a record in an application, for example. Other types of events may be supported.
- the presence data 155 may be received from the contact routing system 153 by the WFM application 250 . Alternatively, or additionally, the presence data 155 may be extracted from the contact center data 159 . The events included in the presence data 155 may be selected by the administrator 290 , for example.
- the events may include sending a communication to the contact center 150 , receiving a communication from the contact center 150 , and interacting with an agent 120 .
- Other types of events may be supported.
- the WFM application 250 may configure various WFM related items on a team-by-team basis. As part of an initial setup procedure, the WFM application 250 may attempt to associate each team with a geographic location. As will be described further below, the location associated with a team (and the agents 120 associated with each team) can be used to determine location-based rules 157 that govern how long agents 120 can work, how many breaks each agent 120 must receive, etc.
- the WFM application 250 may for each team, determine the geographic location associated with the team.
- the WFM application 250 may infer the location of a team using the contact center data 159 .
- the WFM application 250 may determine the location for a team based on the home or work addresses listed for the agents 120 on the team or may determine the location for a team based on the area codes of the phone numbers used by the agents 120 on the team.
- the WFM application 20 may infer the location based on an address associated with the contact center 150 , or an area code of one or more phone numbers associated with the contact center 150 . Any method for inferring the locations of agents 120 or employees may be used.
- the WFM application 250 may present the determined location to the administrator 290 in a GUI.
- the administrator 290 may either confirm the determined location or may provide a different location using the GUI.
- the WFM application 250 may ask the administrator 290 , through the GUI, whether all of the teams of the contact center 150 may be associated with the same location. If the administrator 290 affirms that all of the teams may be associated with the same location, the WFM application 250 may associated each team with the location and stop the workflow. Otherwise, the WFM application 250 may continue the workflow and may determine a location for the next team based on the contact center data 159 .
- the administrator 290 may select another item of the WFM application 250 to configure for a team.
- One example of such an item may be a minimum and maximum working hours 171 for each agent 120 in a team.
- the WFM application 250 may ask the administrator 290 (using the GUI) whether each agent 120 in the team has the same minimum or maximum hours 171 . If the administrator 290 answers affirmatively, the WFM application 250 may request the minimum and maximum hours 171 for the agents 120 in the team from the administrator 290 . The WFM application 250 may then consider a next team of the contact center 150 .
- the WFM application 250 may use a workflow to determine the minimum or maximum hours 171 .
- the WFM application 250 for each agent 120 of the team, may use the presence data 155 to determine the minimum and maximum hours 171 for the agent 120 .
- the WFM application 250 may determine the minimum and maximum weekly hours 171 for an agent 120 by using the presence data 155 to determine events that indicate that the agent 120 was likely working such as computer logins, application usage information, phone usage information, etc. The WFM application 250 may then use the times associated with each determined event to infer, for one or more weeks, the hours that the agent 120 was likely working during the one or more weeks. The maximum and minimum hours 171 for the agent 120 may then be inferred based on the likely hours determined for each of the one or more weeks.
- the WFM application 250 may use the location determined for the team or agent 120 , to determine location-based rules 157 that may apply to an agent 120 . The WFM application 250 may then ensure that the determined maximum or minimum hours 171 comply with the location-based rules 157 .
- the location-based rules 157 may include legal rules related to the maximum number of hours that an agent 120 may work in a day or week, as well as entity or contact center 150 policies about the minimum and maximum number of hours that an agent 120 may work during a day or week. For example, an entity such as a corporation may prefer that an agent 120 not work more than some number of overtime hours per week.
- the entity or contact center 150 policies may be provided by an administrator 290 .
- the WFM application 250 may present the determined maximum and minimum hours 171 for each agent 120 to the administrator 290 through the GUI.
- the administrator 290 may then accept or modify the determined maximum and minimum hours 171 for each agent 120 .
- the maximum and minimum hours 171 for each agent 120 may be used later by the WFM application 250 to generate one or more schedules 255 .
- shifts 172 that each agent 120 for a team can work.
- the contact routing system 153 of the contact center 150 may schedule agents 120 to one or more of a plurality of shifts 172 .
- shifts 172 include a morning shift, an afternoon shift, and a night shift. More or fewer shifts 172 may be used by the contact center 150 .
- the WFM application 250 may ask the administrator 290 (using the GUI) whether each agent 120 in the team works the same shifts 172 . If the administrator 290 answers affirmatively, the WFM application 250 may request the shifts 172 for the agents 120 in the team from the administrator 290 . The WFM application 250 may then consider a next team of the contact center 150 .
- the WFM application 250 may use the presence data 155 to determine the shifts 172 for the agent 120 .
- the WFM application 250 may determine the shifts 172 for an agent 120 by using the presence data 155 to determine events that indicate that the agent 120 was likely working such as computer logins, application usage information, phone usage information, etc. The WFM application 250 may then use the times associated with each determined event to infer, for one or more weeks, the shifts 172 that the agent 120 was likely working during the one or more weeks. The shifts 172 for the agent 120 may then be determined based on the shifts 172 that the agent 120 was likely working for the one or more weeks.
- the WFM application 250 may use the location-based rules 157 to ensure that the determined shifts for each agent 120 comply with all local laws and entity policies.
- the WFM application 250 may present the determined shifts 172 for each agent 120 to the administrator 290 through the GUI.
- the administrator 290 may then accept or modify the determined shifts 172 for each agent 120 .
- start rules 173 for each agent 120 of a team may indicate by how much the time at which the agent 120 begins their work day varies over the week. For example, one agent 120 may start work at the same time every day of the week, while another agent 120 may start at a different time every day of the week.
- the start rule 173 for an agent 120 may generally indicate how flexible an agent 120 is regarding their start time, and therefore may be considered by the WFM application 250 when generating a schedule 255 .
- the WFM application 250 may ask the administrator 290 (using the GUI) whether each agent 120 in the team must start their shift at the same time each day. If the administrator 290 answers affirmatively, the WFM application 250 may request the start time from the administrator 290 . The WFM application 250 may then consider a next team of the contact center 150 .
- the WFM application 250 may use the presence data 155 to determine the variability of the start times for each agent 120 .
- the WFM application 250 may determine the different start times for an agent 120 by using the presence data 155 to determine events that indicate that the agent 120 was likely working. The WFM application 250 may then use the times associated with each determined event to infer, for one or more weeks, the different times that the agent 120 likely started each shift.
- the different times may be used to construct a start rule 173 for the agent 120 .
- the WFM application 250 determines that the start times for an agent 120 varies as much as three hours, then the agent 120 may be associated with a start rule 173 that says that the start time for the agent 120 may be varied by at most three hours.
- the WFM application 250 determines that the start times for an agent 120 does not vary at all, then the agent 120 may be associated with a start rule 173 that says that the start time for the agent 120 may not be varied.
- the WFM application 250 may present the determined start rules 173 for each agent 120 to the administrator 290 through the GUI.
- the administrator 290 may then accept or modify the determined start rules 173 for each agent 120 .
- the break pattern 174 for an agent 120 may be indicators of when, and for how long, the agent 120 typically takes breaks during a workday or shift including longer breaks such as lunch and shorter breaks such as lavatory breaks, etc.
- the WFM application 250 may ask the administrator 290 (using the GUI) whether each agent 120 in the team must have the same break pattern 174 during their shifts. If the administrator 290 answers affirmatively, the WFM application 250 may request the break pattern 174 from the administrator 290 . The WFM application 250 may then consider a next team of the contact center 150 .
- the WFM application 250 may use the presence data 155 to determine the break pattern 174 for each agent 120 .
- the WFM application 250 may use the presence data 155 to determine events that indicate that the agent 120 has taken a break during their shift or workday. These events may include logging out on an application or workstation, or setting a presence indicator to away, for example. The WFM application 250 may then use the times associated with each determined event to infer, for one or more weeks, the different times that the agent 120 likely took breaks. These times may be used to determine a break pattern 174 for the agent 120 . Depending on the embodiment, the WFM application 250 may use the location-based rules 157 to ensure that the determined break pattern 174 for an agent 120 complies with all applicable laws and regulations (e.g., does the agent 120 take enough breaks as required by law), as well as any entity or contact center 150 specific policies.
- all applicable laws and regulations e.g., does the agent 120 take enough breaks as required by law
- the WFM application 250 may present the determined break pattern 174 for each agent 120 to the administrator 290 through the GUI. The administrator 290 may then accept or modify the presented break pattern 174 for each agent 120 .
- the WFM application 250 may further us the contact center data 159 and the presence data 155 to generate one or more forecasts 251 for the contact center 150 .
- a forecast 251 for a contact center 150 may be an estimate or prediction of how busy the contact center 150 will likely be at date or time in the future.
- the WFM application 250 may determine the forecast 251 for the contact center 150 by processing the presence data 155 and contact center data 159 to determine indicators of how busy the contact center 150 was in the past. These indicators can then be used by the WFM application 250 to train a model to predict how busy the contact center 150 will likely be at a future date based on characteristics of the future date like day of the week or proximity to a holiday, for example. Other information may be used to train the model.
- the model may be further trained by comparing forecasts 251 generated by the model with actual observed workload data for the contact center 150 for the same dates (e.g., using machine learning).
- the WFM application 250 may further generate schedules 255 for the contact center 150 (or team) based on the forecasts 251 , and the various items that were inferred for each agent 120 such as maximum and minimum hours 171 , shifts 172 , break patterns 174 , and start rules 173 .
- the WFM application 250 may further consider the location-based rules 157 to ensure that each schedule 255 complies with all laws and regulations as well as entity policies. Any method for scheduling agents 120 may be used.
- the WFM application 250 may present each proposed schedule 255 to the administrator 290 for approval through the GUI.
- the administrator 290 may either approve the proposed schedule 255 , may reject the proposed schedule 255 , or may make one or more changes to the proposed schedule 255 .
- FIG. 3 is an illustration of an example method 300 for configuring a WFM system.
- the method 300 may be performed by the WFM application 250 .
- an administrator 290 may have installed the WFM application 250 , and the method 300 may configure one or more items of the WFM application 250 using contact center data 159 and presence data 155 automatically downloaded from a contact routing system 153 of a contact center 150 .
- an item is selected to configure.
- the item may be a configurable item or setting of the WFM application 250 .
- the configurable items may include minimum or maximum hours 171 , shifts 172 , and break patterns 174 . Other configurable items may be supported. Depending on the embodiment and items, the items may be configurable per agent 120 , per customer 110 , or per team, for example.
- the item may be selected automatically by the WFM application 250 , or may be selected by a user (e.g., administrator 290 ) using a GUI.
- a team is selected.
- the team may be a group of agents 120 and may be selected by the administrator 290 through the GUI. Alternatively, the team may be selected automatically (i.e., without user input) by the WFM application 250 .
- the teams may be teams of the contact center 150 and may have been determined from contact center data 159 downloaded from the contact routing system 153 . Because the teams were determined from the contact center data 159 , the administrator 290 did not have to manually enter the teams (and associated agents 120 ) into the WFM application 250 .
- the WFM application 250 may make the determination by asking the administrator 290 using the GUI.
- an item has a simple configuration may be dependent on the item.
- an item has a simple configuration if all agents 120 associated with the team have the same value or setting for the item. For example, for an item such as maximum hours 171 , the item may have a simple configuration if all agents 120 of the team have the same maximum hours 171 (e.g., 40 ).
- the method 300 may continue at 307 . Else, the method 300 may continue at 309 .
- the item is configured. Because the configuration was determined to be simple, the item may be configured by the WFM application 250 asking the administrator 290 to provide a value for the item (through the GUI). User input including the value may be received from the administrator 290 and may be used by the WFM application 250 to configure the item for all agents 120 associated with the team.
- the administrator 290 may provide the value “40” as the maximum hours 171 for the agents 120 in the team.
- the WFM application 250 may then configure the maximum hours 171 to “40” for all agents 120 in the team.
- automatic configuration of the item is performed.
- the automatic configuration of the item may be performed by the WFM application 250 using one or both of the contact center data 159 or the presence data 155 .
- the item may be configured by, for each agent 120 of the team, inferring the value of the item from the contact center data 159 or the presence data 155 .
- the value may be inferred using a workflow associated with the item.
- the WFM application 250 may analyze the presence data 155 associated with the agent 120 to determine events such as logins and application usage, that may indicate when the agent 120 was likely working. Based on these determined events and their associated times, the WFM application 250 may infer the maximum hours 171 for the agent 120 .
- a user review is performed.
- the user review may be performed by the WFM application 250 .
- the WFM application 250 may display the proposed configuration for the item with respect to each agent 120 in the team to the administrator 290 , and the administrator 290 may approve the configurations, or may provide different values to use for some or all of the proposed item configurations.
- FIG. 4 is an illustration of an example method 400 for automatically configuring items for a WFM application 250 based on data received from a contact routing system 153 .
- the method 400 may be implemented by the WFM application 250 .
- a 410 a contact routing system is interfaced with.
- the WMF application 250 may interface with the contact routing system 153 using credentials provided by the administrator 290 .
- contact center data 159 is received.
- the contact center data 159 may be received by the WFM application 250 from the contact routing system 153 through the interface.
- a selection of an item to configure is received.
- the selection of the item may be received by the WFM application 250 from an administrator 290 through a GUI.
- the GUI may be used by the administrator 290 to configure the WFM application 250 .
- the selected item may be a configurable item associated with the WFM application 250 .
- the configurable items may include start rules 173 , shifts 172 , hours 171 , and break patterns 174 . Other items may be configured.
- the configurable items may be related to agents 120 , teams, or customers 110 associated with the contact center 150 .
- a workflow corresponding to the selected item is selected.
- the workflow may be selected by the WFM application 250 from a plurality of workflows.
- the WFM application 250 may have separate workflows to configure items such as start rules 173 , break patterns 174 , and shifts 172 .
- the selected item is configured automatically using the selected workflow and the contact center data.
- the selected item may be configured by the WFM application 250 .
- the item may be configured also using presence data 155 and one or more location-based rules 157 corresponding to a location of one or more agents 120 , teams, or the contact center 150 .
- FIG. 5 is an illustration of an example method 500 for automatically configuring a WFM application 250 based on data received from a contact routing system 153 of a contact center 150 .
- the method 500 may be implemented by the WFM application 250 .
- a 510 a contact routing system is interfaced with.
- a WFM application 250 may interface with the contact routing system 153 as part of configuring the WFM application 250 .
- an entity or administrator 290 associated with the contact center 150 may have determined to create and configure a WFM management system for the agents 120 and employees of the contact center 150 . Accordingly, the administrator 290 may have caused an instance of the WFM application 250 to be installed on a deployment server 170 .
- the deployment server 170 executing the WFM application 250 may be referred to as the WFM server.
- a plurality of agents associated with the contact center are determined.
- the plurality of agents 120 may be determined by the WFM application 250 from contact center data 159 received from the contact routing system 153 .
- the WFM application 250 may further determine teams associated with the contact center 150 and may determine agents 120 associated with each team.
- the presence data 155 may be received by the WFM application 250 from the contact routing system 153 .
- the presence data 155 for an agent 120 may include a plurality of events, and each event may be associated with a time.
- Example events may include logging in, or out, or a computer or application, using a particular application, setting a presence indicator to present or away, and handling a communication such as a phone call, email, or text message. Other events may be supported.
- the presence data 155 may be part of the contact center data 159 or may be received separately from the contact routing system 153 .
- a maximum and a minimum hours 171 is determined.
- the maximum and minimum hours 171 may be determined by the WFM application 250 using the presence data 155 associated with the at least one agent 120 .
- the maximum hours 171 for an agent 120 may be the maximum hours that the agent 120 is willing to work during some period such as a day, week, month, etc.
- the minimum hours 171 may be the minimum hours that the agent 120 that the agent 120 is willing to work during the period.
- knowing the minimum and maximum hours 171 for each agent 120 is desirable when generating a schedule 255 to ensure that each agent 120 is satisfied with the number of hours that they are assigned.
- FIG. 6 is an illustration of an example method 600 for automatically configuring a WFM application 250 based on data received from contact routing system 153 of a contact center 150 .
- the method 600 may be implemented by the WFM application 250 .
- a 610 a contact routing system is interfaced with.
- a WFM application 250 may interface with the contact routing system as part of configuring the WFM application 250 .
- a plurality of agents associated with the contact center are determined.
- the plurality of agents 120 may be determined by the WFM application 250 from contact center data 159 received from the contact routing system 153 .
- the WFM application 250 may further determine teams associated with the contact center 150 and may determine agents 120 associated with each team.
- presence data associated with each agent is received.
- the presence data 155 may be received by the WFM application 250 from the contact routing system 153 .
- one or more shifts are determined.
- the shifts 172 e.g., morning shift, day shift, or night shift
- the shifts 172 may be determined by the WFM application 250 using the presence data 155 associated with the at least one agent 120 .
- the shifts 172 for an agent 120 may be the shifts 172 that the agent 120 typically worked in the past for the contact center 150 . As may be appreciated, knowing the shifts 172 for each agent 120 is desirable when generating a schedule 255 to ensure that each agent 120 is only scheduled to work during a shift that they are willing to work.
- the WFM application 250 may determine the shifts 172 using the presence data 155 . For example, the WFM application 250 may determine events from the presence data 155 that indicate when the agent 120 was likely working. The WFM application 250 may then determine what shifts of the contact center 150 that the determined events occurred during based on the times associated with the determined events. The shifts with the most associated events may be determined as the shifts 172 for the agent 120 . Other methods may be used.
- FIG. 7 is an illustration of an example method 700 for automatically configuring a WFM application 250 based on data received from a contact routing system 153 of a contact center 150 .
- the method 700 may be implemented by the WFM application 250 .
- a 710 a contact routing system is interfaced with.
- a WFM application 250 may interface with the contact routing system 153 as part of configuring the WFM application 250 .
- a plurality of agents associated with the contact center are determined.
- the plurality of agents 120 may be determined by the WFM application 250 from contact center data 159 received from the contact routing system 153 .
- the WFM application 250 may further determine teams associated with the contact center 150 and may determine agents 120 associated with each team.
- presence data associated with each agent is received.
- the presence data 155 may be received by the WFM application 250 from the contact routing system 153 .
- a break pattern 174 is determined.
- the break pattern 174 may be determined by the WFM application 250 using the presence data 155 associated with the at least one agent 120 .
- the break pattern 174 for an agent 120 may be a data structure that identifies the time and duration of each break taken by the agent 120 during a shift or other period (e.g., day or week). As may be appreciated, the break pattern 174 associated with the agent 120 may be used for generating a schedule 255 so that any breaks that the agent 120 is used to taking are scheduled at their expected times.
- the WFM application 250 may determine the break pattern 174 using the presence data 155 .
- the WFM application 250 may determine events from the presence data 155 that indicate when the agent 120 was likely on break. These events may include logging out of a computer, closing one or more applications or setting a presence indicator to away. The WFM application 250 may then determine the times usually associated with breaks for the agent 120 and may use those times to determine the break pattern 174 for the agent 120 . Other methods may be used.
- the WFM application 250 may determine the minimum and maximum hours 171 for a period using the presence data 155 .
- the WFM application 250 may, for previous periods, determine events from the presence data 155 that indicate when the agent 120 was likely working. These events may include when the agent 120 first logged into their computer during a period, and when the agent 120 last logged out from their computer during the period. Average minimum and maximum hours worked by the agent 120 during the periods may be used as the minimum and maximum hours 171 for the agent 120 . Other methods may be used.
- FIG. 8 is an illustration of an example method 800 for automatically configuring a WFM application 250 using workflows and for generating one or more forecasts and schedules.
- the method 800 may be implemented by the WFM application 250 .
- an application is deployed.
- the application may be a WFM application 250 and may be deployed on a deployment server 170 by an administrator 290 .
- the administrator 290 may have selected the application 260 to deploy from a plurality of applications made available by an application server 160 .
- a contact routing system is interfaced with.
- a WFM application 250 may interface with the contact routing system 153 as part of configuring the WFM application 250 .
- the WFM application 250 may import data from the contact routing system 153 such as contact center data 159 and presence data 155 . Other types of data may be imported from the contact routing system 153 .
- the WFM application 250 may be configured automatically using one or more workflows and the data imported from the contact routing system 153 .
- the items of the WFM application 250 that may be configured using workflows may include teams, locations, queues, event types, historical contact data, agents 120 , minimum and maximum hours 171 , shifts 172 , breaks or break patterns 174 , constancy rules (e.g., start rules 173 ), and agent 120 availability. Other items may be configured.
- the one or more forecast 251 may be generated by the WFM application 250 .
- Each forecast 251 may be an indication of how busy the contact center 150 is likely to be at some future time or period (e.g., day, week, or month).
- the forecast 251 may be generated using historical data about the workload or overall busyness of the contact center 150 during past periods.
- the historical data may be part of the contact data center data 159 , for example. Any method for generating a forecast 251 for a future period based on historical data from past periods may be used.
- the one or more forecasts are validated.
- the one or more forecasts may be validated by the administrator 290 .
- the one or more forecasts 251 may have been provided to the administrator 290 in a GUI. If the administrator 290 is satisfied by the one or more forecasts 251 , the administrator 290 may use the GUI to validate the one or more forecasts.
- one or more schedules are generated.
- the one or more schedules 255 may be generated by the WFM application 250 .
- Each schedule 255 may be generated for one of the generated forecasts 251 according to the items configured for the application 250 at 815 .
- the WFM application 250 may generate each schedule 255 such that sufficient agents 120 are scheduled to handle the workload predicted by the associated forecast 251 while also complying with location-based rules 157 associated with the location determined for the agents 120 or the contact center 150 .
- the WFM application 250 may further generate each schedule 255 to honor items such as start rules 173 , break patterns 174 , hours 171 , and shifts 172 determined by the WFM application 250 for each agents 120 or team.
- the one or more schedules are validated.
- the one or more schedules 835 may be validated by the administrator 290 through the GUI.
- the one or more schedules 255 may be implemented by the contact center 150 .
- FIG. 9 shows an exemplary computing environment in which example embodiments and aspects may be implemented.
- the computing system environment is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality.
- Examples of well-known computing systems, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers, servers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network personal computers (PCs), minicomputers, mainframe computers, embedded systems, distributed computing environments that include any of the above systems or devices, and the like.
- Computer-executable instructions such as program modules, being executed by a computer may be used.
- program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
- Distributed computing environments may be used where tasks are performed by remote processing devices that are linked through a communications network or other data transmission medium.
- program modules and other data may be located in both local and remote computer storage media including memory storage devices.
- an exemplary system for implementing aspects described herein includes a computing device, such as computing device 900 .
- computing device 900 typically includes at least one processing unit 902 and memory 904 .
- memory 904 may be volatile (such as random access memory (RAM)), non-volatile (such as read-only memory (ROM), flash memory, etc.), or some combination of the two.
- RAM random access memory
- ROM read-only memory
- flash memory etc.
- Computing device 900 may have additional features/functionality.
- computing device 900 may include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape.
- additional storage is illustrated in FIG. 9 by removable storage 908 and non-removable storage 910 .
- Computing device 900 typically includes a variety of tangible computer readable media.
- Computer readable media can be any available tangible media that can be accessed by device 900 and includes both volatile and non-volatile media, removable and non-removable media.
- Tangible computer storage media include volatile and non-volatile, and removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
- Memory 904 , removable storage 908 , and non-removable storage 910 are all examples of computer storage media.
- Tangible computer storage media include, but are not limited to, RAM, ROM, electrically erasable program read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 900 . Any such computer storage media may be part of computing device 900 .
- Computing device 900 may contain communications connection(s) 912 that allow the device to communicate with other devices.
- Computing device 900 may also have input device(s) 914 such as a keyboard, mouse, pen, voice input device, touch input device, etc.
- Output device(s) 916 such as a display, speakers, printer, etc. may also be included. All these devices are well known in the art and need not be discussed at length here.
- agent(s) 120 and customers 110 may communicate with each other and with other services over the network 130 .
- a customer calling on telephone handset may connect through the PSTN and terminate on a private branch exchange (PBX).
- PBX private branch exchange
- a video call originating from a tablet may connect through the network 130 terminate on the media server.
- a smartphone may connect via the WAN and terminate on an interactive voice response (IVR)/intelligent virtual agent (IVA) components.
- IVR are self-service voice tools that automate the handling of incoming and outgoing calls. Advanced IVRs use speech recognition technology to enable customers to interact with them by speaking instead of pushing buttons on their phones.
- IVR applications may be used to collect data, schedule callbacks and transfer calls to live agents.
- IVA systems are more advanced and utilize artificial intelligence (AI), machine learning (ML), advanced speech technologies (e.g., natural language understanding (NLU)/natural language processing (NLP)/natural language generation (NLG)) to simulate live and unstructured cognitive conversations for voice, text and digital interactions.
- AI artificial intelligence
- ML machine learning
- NLU natural language understanding
- NLP natural language processing
- NLG natural language generation
- Social media, email, SMS/MMS, IM may communicate with their counterpart's application (not shown) within the contact center 150 .
- the contact center 150 itself be in a single location or may be cloud-based and distributed over a plurality of locations.
- the contact center 150 may include servers, databases, and other components.
- the contact center 150 may include, but is not limited to, a routing server, a SIP server, an outbound server, a reporting/dashboard server, automated call distribution (ACD), a computer telephony integration server (CTI), an email server, an IM server, a social server, a SMS server, and one or more databases for routing, historical information and campaigns.
- the ACD is used by inbound, outbound and blended contact centers to manage the flow of interactions by routing and queuing them to the most appropriate agent.
- software connects the ACD to a servicing application (e.g., customer service, CRM, sales, collections, etc.), and looks up or records information about the caller.
- CTI may display a customer's account information on the agent desktop when an interaction is delivered.
- Campaign management may be performed by an application to design, schedule, execute and manage outbound campaigns. Campaign management systems are also used to analyze campaign effectiveness.
- the routing server may use statistical data from reporting/dashboard information and a routing database to the route SIP request message.
- a response may be sent to the media server directing it to route the interaction to a target agent 120 .
- the routing database may include: customer relationship management (CRM) data; data pertaining to one or more social networks (including, but not limited to network graphs capturing social relationships within relevant social networks, or media updates made by members of relevant social networks); agent skills data; data extracted from third party data sources including cloud-based data sources such as CRM; or any other data that may be useful in making routing decisions.
- CRM customer relationship management
- Real-time communication services include Internet Protocol (IP) telephony, call control, instant messaging (IM)/chat, presence information, real-time video and data sharing.
- Non-real-time applications include voicemail, email, SMS and fax services.
- IP Internet Protocol
- IM instant messaging
- the communications services are delivered over a variety of communications devices, including IP phones, personal computers (PCs), smartphones and tablets.
- Presence provides real-time status information about the availability of each person in the network, as well as their preferred method of communication (e.g., phone, email, chat and video).
- Recording applications may be used to capture and play back audio and screen interactions between customers and agents. Recording systems should capture everything that happens during interactions and what agents do on their desktops.
- Surveying tools may provide the ability to create and deploy post-interaction customer feedback surveys in voice and digital channels.
- the IVR/IVA development environment is leveraged for survey development and deployment rules.
- Reporting/dashboards are tools used to track and manage the performance of agents, teams, departments, systems and processes within the contact center. Reports are presented in narrative, graphical or tabular formats. Reports can be created on a historical or real-time basis, depending on the data collected by the contact center applications. Dashboards typically include widgets, gadgets, gauges, meters, switches, charts and graphs that allow role-based monitoring of agent, queue and contact center performance.
- Unified messaging (UM) applications include various messaging and communications media (voicemail, email, SMS, fax, video, etc.) stored in a common repository and accessed by users via multiple devices through a single unified interface.
- the computing device In the case of program code execution on programmable computers, the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.
- One or more programs may implement or utilize the processes described in connection with the presently disclosed subject matter, e.g., through the use of an application programming interface (API), reusable controls, or the like.
- API application programming interface
- Such programs may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system.
- the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language and it may be combined with hardware implementations.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Game Theory and Decision Science (AREA)
- Data Mining & Analysis (AREA)
- Educational Administration (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Library & Information Science (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
A system for quickly deploying WFM systems in contact centers is provided. A user or administrator can quickly install a WFM application on a deployment server. The administrator can provide the WFM application access to the contact center data where the WFM application can import data from the contact center about one or more customers, agents, queues, teams, and any other items typically associated with contact centers. The imported data may also include presence data about the agents, teams, and customers. Based on the imported data, the WFM application may execute one or more workflows to automatically determine information such as maximum and minimum hours, break patterns, and shift data about the agents and teams.
Description
- This application is a continuation of U.S. patent application Ser. No. 16/654,356 filed on Oct. 16, 2019, entitled “SYSTEMS AND METHODS FOR WORKFORCE MANAGEMENT SYSTEM DEPLOYMENT.” The contents of which are hereby incorporated by reference.
- The initial deployment and configuration of a contact center workforce management (WFM) system is a typically time-consuming processes often taking weeks or months. In particular, parameters must be configured to represent external conditions of work to be done, the employees who are expected to do the work, and rules for how the employees can be scheduled to do the work. The inability of WFM systems to configure these items quickly and automatically leads to a large amount of work for WFM administrators to collect, interpret, and input the necessary information.
- A system for quickly deploying WFM systems in contact centers is provided. A user or administrator can quickly install a WFM application on a deployment server. The administrator can provide the WFM application access to the contact center data where the WFM application can import data from the contact center about one or more customers, agents, queues, teams, and any other information or items typically associated with contact centers. The imported data may also include presence data about the agents, teams, and customers. Based on the imported data, the WFM application may execute one or more workflows to automatically determine information such as maximum and minimum hours, break patterns, and shift data about the agents and teams. This information can be used by the WFM system to automatically generate forecasts and schedules.
- As may be appreciated, the WFM deployment systems and methods described herein provide many advantages over the prior art. By leveraging the information that is already part of the contact center used by an entity, WFM systems can be easily and quickly deployed without significant input from an administrator. Accordingly, the WFM deployment systems and applications described herein can save these entities significant time and money.
- In an embodiment, a method for configuring an application for a contact center is provided. The method includes: interfacing with a contact center by an application; receiving contact center data from the contact center by the application; receiving a selection of an item of the application to configure by the application; based on the selected item, selecting a workflow corresponding to the selected item by the application; and configuring the item of the application automatically using the selected workflow and the contact center data by the application.
- Embodiments may include some or all of the following features. The application may be a WFM application. The method may further include: determining a plurality of agents associated with the contact center; and configuring the item of the application automatically using the selected workflow and the contact center data by the application comprises: configuring one or more of a minimum hours for the at least one agent, a break pattern for the at least one agent, and a shift for the at least one agent. The method may further include retrieving presence data for each agent from the contact center, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time. The method may further include: for the at least one agent of the plurality of agents, determining a location for the agent; retrieving one or more rules that relate to scheduling for the determined location; and for the at least one agent of the plurality of agents, generating the schedule for the at least one agent based on the one or more rules and the minimum hours for the at least one agent. Determining a location for the agent may include determining a telephone number associated with the agent and determining the location for the agent based on the telephone number. Interfacing with the contact center by the application may include: requesting credentials from a user associated with the contact center; and interfacing with the contact center using the requested credentials.
- In an embodiment, a method for configuring a workforce management system for a contact center is provided. The method includes: interfacing with a contact center by a workforce management system; determining a plurality of agents associated with the contact center by the workforce management system; retrieving presence data for each agent from the contact center by the workforce management system, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time; for at least one agent of the plurality of agents, determining a maximum hours for the at least one agent based on the presence data for the agent by the workforce management system; and for the at least one agent of the plurality of agents, generating a schedule for the at least one agent based on the determined maximum hours by the workforce management system.
- Embodiments may include some or all of the following features. The method may further include: for the at least one agent of the plurality of agents, determining a location for the at least one agent; retrieving one or more rules that relate to scheduling for the location; and for the at least one agent of the plurality of agents, determining the maximum hours for the at least one agent based on the presence data for the at least one agent and the one or more rules. Determining the maximum hours for the at least one agent based on the presence data for the at least one agent may include: inferring, from the presence data, a number of hours worked by the at least one agent for each week of a plurality of weeks; and determining the maximum hours for the at least one agent based on the number of hours worked by the at least one agent for each week of the plurality of weeks. The events may include one or more of computer logins, computer logouts, communications, and application activities. The method may further include for the at least one agent of the plurality of agents, determining a minimum hours for the at least one agent based on the presence data for the at least one agent. The method may further include for the at least one agent of the plurality of agents, generating the schedule for the at least one agent based on the determined maximum hours and the determined minimum hours. The method may further include, for the at least one agent of the plurality of agents, determining, based on the presence data, one or more shifts that the at least one agent is available to work, and one or more break patterns associated with the at least one agent. The method may further include generating the schedule for the at least one agent based on the determined maximum hours, the determined one or more shifts that the at least one agent is available to work, and the determined one or more break patterns associated with the at least one agent.
- In an embodiment, a method for configuring a workforce management system for a contact center is provided. The method includes: interfacing with a contact center by a workforce management system; determining a plurality of agents associated with the contact center by the workforce management system; retrieving presence data for each agent from the contact center by the workforce management system, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time; for at least one agent of the plurality of agents, determining one or more shifts for the at least one agent based on the presence data for the at least one agent by the workforce management system; and for the at least one agent of the plurality of agents, generating a schedule for the at least one agent by the workforce management system based on the determined one or more shifts.
- Embodiments may have some or all of the following features. The method may further include: for the at least one agent of the plurality of agents, determining a location for the agent; retrieving one or more rules that relate to scheduling for the location; and for the at least one agent of the plurality of agents, generating the schedule for the at least one agent based on the one or more rules and the determined one or more shifts. Determining the one or more shifts for the at least one agent based on the presence data for the at least one agent may include: inferring, from the presence data, times worked by the at least one agent for each week of a plurality of weeks; and determining the one or more shifts for the at least one agent based on the times worked by the at least one agent for each week of the plurality of weeks. The events may include one or more of computer logins, computer logouts, communications, and application activities. The method may further include, for the at least one agent of the plurality of agents, determining, based on the presence data, maximum hours for the at least one agent, minimum hours for the at least one agent, and a break pattern associated with the at least one agent. The method may further include generating the schedule for the at least one agent based on the determined maximum hours, the determined minimum hours, the determined one or more shifts that the at least one agent is available to work, and the determined break pattern associated with the at least one agent. Interfacing with the contact center by the workforce management system may include: requesting credentials from a user associated with the contact center; and interfacing with the contact center using the requested credentials.
- In an embodiment, a method for configuring a workforce management system for a contact center is provided. The method includes: interfacing with a contact center by a workforce management system; determining a plurality of agents associated with the contact center by the workforce management system; retrieving presence data for each agent from the contact center by the workforce management system, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time; for at least one agent of the plurality of agents, determining a break pattern associated with the at least one agent based on the presence data for the at least one agent by the workforce management system; and for the at least one agent of the plurality of agents, generating a schedule for the at least one agent based on the determined break pattern by the workforce management system.
- Embodiments may include some or all of the following features. The method may further include: for the at least one agent of the plurality of agents, determining a location for the agent; retrieving one or more rules that relate to scheduling for the location; and for the at least one agent of the plurality of agents, generating the schedule for the at least one agent based on the one or more rules and the determined break pattern. The method may further include: determining the break pattern associated with the at least one agent based on the presence data for the at least one agent comprises: inferring, from the presence data, breaks taken by the at least one agent for each day of a plurality of days; and determining the break pattern for the at least one agent based on the breaks taken by the at least one agent for each day of the plurality of days. The events may include one or more of computer logins, computer logouts, communications, and application activities. The method may further include, for the at least one agent of the plurality of agents, determining, based on the presence data, maximum hours for the at least one agent, minimum hours for the at least one agent, and one or more shifts that the at least one agent is available to work. The method may further include generating the schedule for the at least one agent based on the determined break pattern, the determined minimum hours, the determined maximum hours, and the determined one or more shifts that the at least one agent is available to work. Interfacing with the contact center by the workforce management system may include: requesting credentials from a user associated with the contact center; and interfacing with the contact center using the requested credentials.
- Other systems, methods, features and/or advantages will be or may 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/or advantages be included within this description and be protected by the accompanying claims.
- The components in the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding parts throughout the several views.
-
FIG. 1 is an illustration of an example system architecture; -
FIG. 2 is an illustration of an example environment for installing and configuring a WFM application; -
FIG. 3 is an illustration of an example method for configuring a WFM system; -
FIG. 4 is an illustration of an example method for automatically configuring items for a WFM application based on data received from a contact center; -
FIGS. 5-7 are illustrations of example methods for automatically configuring a WFM application; -
FIG. 8 is an illustration of an example method for automatically configuring a WFM application using workflows and for generating one or more forecasts and schedules; -
FIG. 9 illustrates an example computing device. - Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art. Methods and materials similar or equivalent to those described herein can be used in the practice or testing of the present disclosure. While implementations will be described within a cloud-based contact center, it will become evident to those skilled in the art that the implementations are not limited thereto.
-
FIG. 1 is anexample system architecture 100, and illustrates example components, functional capabilities and optional modules that may be included in a cloud-based contact center infrastructure solution. Customers 110 interact with acontact center 150 using voice, email, text, and web interfaces in order to communicate with theagents 120 through anetwork 130 and one or more of text or multimedia channels. The system that controls the operation of thecontact center 150 including the routing and handling of communications between customers 110 andagents 120 for thecontact center 150 is referred to herein as the contact routing system 153. Depending on the embodiment, the contact routing system 153 could be any of a contact center as a service (CCaS) system, an automated call distributor (ACD) system, or a case system, for example. - The
agents 120 may be remote from thecontact center 150 and handle communications with customers 110 on behalf of an enterprise. Theagents 120 may utilize devices, such as but not limited to, work stations, desktop computers, laptops, telephones, a mobile smartphone and/or a tablet. Similarly, customers 110 may communicate using a plurality of devices, including but not limited to, a telephone, a mobile smartphone, a tablet, a laptop, a desktop computer, or other. For example, telephone communication may traverse networks such as a public switched telephone networks (PSTN), Voice over Internet Protocol (VoIP) telephony (via the Internet), a Wide Area Network (WAN) or a Large Area Network. The network types are provided by way of example and are not intended to limit types of networks used for communications. - In some embodiments, the
agents 120 may be assigned to one or more queues. Theagents 120 assigned to a queue may handle communications that are placed in the queue by thecontact center 150. For example, there may be queues associated with a language (e.g., English or Chinese), topic (e.g., technical support or billing), or a particular country of origin. When a communication is received by thecontact center 150, the communication may be placed in a relevant queue, and one of theagents 120 associated with the relevant queue may handle the communication. - The
agents 120 of acontact center 150 may be further organized into one or more teams. Depending on the embodiment, theagents 120 may be organized into teams based on a variety of factors including, but not limited to, skills, location, experience, assigned queues, associated or assigned customers 110, and shift. Other factors may be used to assignagents 120 to teams. - Entities that employ workers such as
agents 120 typically use a WFM system. Typically, WFM systems are used to scheduleagents 120 based on workload forecasts. To generate schedules the WFM systems must take into account information such as local employment laws, time and shift preferences of eachagent 120, and the skills of eachagent 120, for example. - As may be appreciated, initially gathering and providing the information needed to set up a WFM system may be a time-consuming task. Accordingly, to solve this problem, the
environment 100 further includes aWFM application 250 that may be used to quickly deploy and configure WFM systems. The workings of theapplication 250 will be described in further detail with respect toFIG. 2 . - Initially, when an administrator associated with a contact routing system 153 desires to set up a WFM system, the administrator may first create or designate what is referred to as a deployment sever 170. The
deployment server 170 may implement the WFM system for thecontact center 150. Note that depending on the embodiment, the WFM system may be implemented on itsown deployment server 170. In addition, some or all of the contact routing system 153 or the WFM system may be implemented together on the same computer,deployment server 170, or cloud-computing environment. Anexample deployment server 170 is thecomputing system 900 illustrated with respect toFIG. 9 . - After creating the
deployment server 170, the administrator may then cause theWFM application 250 to be installed on thedeployment server 170 by anapplication server 160. Depending on the embodiment, theapplication server 160 may function similar to an “app store” where the administrator of thecontact center 150 may view one or more applications (including the application 250) that are available for download. After selecting theWFM application 250, theapplication server 160 may cause theapplication 250 to be installed on thedeployment server 170. - In order to configure the
WFM application 250, rather than have the administrator configure theapplication 250 from scratch, theapplication 250 may be configured to interface with, and retrieve data from, the contact routing system 153. As may be appreciated, because the contact routing system 153 already includes data that is relevant to the WFM application 250 (e.g., information onagents 120 such as hours worked and schedules, and information on customers 110 such as communications received), it may be desirable to import the data directly from the contact routing system 153. - After the relevant data has been imported into the
WFM application 250, the application may have one or more workflows that can be executed by the administrator to automatically set up and configure the application using the imported data. Each workflow may attempt to configure the application from the imported data with as little input from the administrator as possible. At the end of each workflow, the administrator may be asked to confirm or accept any proposed configurations or settings suggested by the workflow. - For example, there may be workflows that infer, for each
agent 120 or team ofagents 120, settings for theapplication 250 such asagent 120 hours, schedules, and work preferences. The particular workflows will be described further with respect toFIG. 2 . - As may be appreciated, the embodiments described herein are not limited to configuring the
WFM applications 250 using data imported from a contact routing system 153. Other sources of data may be used. For example, theapplication 250 may import data from a variety of systems including, but not limited to, customer relationship management systems and document management systems. Other systems may be included. -
FIG. 2 is an illustration of anexample environment 200 for installing and configuring aWFM application 250. As shown, theenvironment 200 includes adeployment server 170, acontact center 150 including a contact routing system 153, and anadministrator 290. Depending on the embodiment, each of the contact routing system 153,deployment server 170, andadministrator 290 may be implemented together or separately by one or more general purpose computing devices such as thecomputing system 900 illustrated with respect toFIG. 9 . - The
administrator 290 may cause theWFM application 250 to be installed on thedeployment server 170. As part of the configuration process, theadministrator 290 may allow theWFM application 250 to access the contact routing system 153. For example, theadministrator 290 may provide credentials (e.g., login and password) to theWFM application 250, and theWFM application 250 may use an API to access the contact routing system 153 using the credentials. Other methods for accessing a contact routing system 153 (or other data source) may be used. - The
WFM application 250 may initially downloadcontact center data 159 and may begin using thecontact center data 159 to configure theWFM application 250 for theadministrator 290. Depending on the embodiment, thecontact center data 159 may include information about thecontact center 150 such as information about theagents 120, teams that theagents 120 are organized into, queues associated with thecontact center 150, contacts 110 associated with thecontact center 150, skills associated with theagents 120 and queues, historical contact data (e.g., historical data for each queue about the volume of contacts, handling times, etc.), and event types. - The
contact center data 159 may further include information such as consistency rules (e.g., rules about whether shifts need to start and stop at the same time), and presence data (e.g., data showing whenagents 120 were available to receive communications or interact with customers 110). Other information may be included in thecontact center data 159. - The
WFM application 250 may use some or all of thecontact center data 159 to begin setting up theWFM application 250 for theadministrator 290. For example, theWFM application 250 may extract all of theagents 120 associated with thecontact center 150 and may enter them into theWFM application 250. TheWFM application 250 may similarly, extract information such as the customers 110 associated with thecontact center 150, the queues associated with thecontact center 150, and any teams associated with thecontact center 150. - In some implementations, the
WFM application 250 may provide a graphical-user interface (GUI) through which theadministrator 290 can review and control what information is imported into theWFM application 250 from thecontact center data 159. For example, theWFM application 250 may ask theadministrator 290 to confirm eachagent 120, contact 110, or team that it extracts from thecontact center 150. Depending on the embodiment, theadministrator 290 may also use the GUI to add any additional information to theWFM application 250 including anyagents 120, customers 110, teams, or queues that theWFM application 250 was unable to extract from thecontact center data 159. - As may be appreciated, by initially configuring the
WFM application 250 automatically using thecontact center data 159, a great amount of time and energy is saved by theadministrator 290. Previously, to configure aWFM application 250, theadministrator 290 would have had to manually add eachagent 120, contact 110, queue, or team to theWFM application 250. - In addition to the automatic importing of certain
contact center data 159. TheWFM application 250 described herein may use one or more workflows to inferadditional WFM application 250 items or settings to further reduce the amount of time that theadministrator 290 may spend configuring the application. - The
WFM application 250 may use workflows to infer or more items such as minimum ormaximum hours 171 foragents 120 individually or as a team, shifts 172 that eachagent 120 can work individually or as a team, breakpatterns 173 associated with eachagent 120 or team, and startrules 173 for eachagent 120 or team. Other items may be inferred and configured by theWFM application 250 using a workflow. - The
WFM application 250 may infer the one or more items from what is referred to herein aspresence data 155. Depending on the embodiment, thepresence data 155 may include a plurality of events associated with eachagent 120 or customer 110, and each event may be associated with a time. For anagent 120, the events may include logging in or out of a computer, receiving or responding to a communication such as an email or telephone call, and updating a record in an application, for example. Other types of events may be supported. - In some embodiments, the
presence data 155 may be received from the contact routing system 153 by theWFM application 250. Alternatively, or additionally, thepresence data 155 may be extracted from thecontact center data 159. The events included in thepresence data 155 may be selected by theadministrator 290, for example. - For a customer 110, the events may include sending a communication to the
contact center 150, receiving a communication from thecontact center 150, and interacting with anagent 120. Other types of events may be supported. - In one embodiment, the
WFM application 250 may configure various WFM related items on a team-by-team basis. As part of an initial setup procedure, theWFM application 250 may attempt to associate each team with a geographic location. As will be described further below, the location associated with a team (and theagents 120 associated with each team) can be used to determine location-basedrules 157 that govern howlong agents 120 can work, how many breaks eachagent 120 must receive, etc. - The
WFM application 250, may for each team, determine the geographic location associated with the team. TheWFM application 250 may infer the location of a team using thecontact center data 159. For example, theWFM application 250 may determine the location for a team based on the home or work addresses listed for theagents 120 on the team or may determine the location for a team based on the area codes of the phone numbers used by theagents 120 on the team. Alternatively, the WFM application 20 may infer the location based on an address associated with thecontact center 150, or an area code of one or more phone numbers associated with thecontact center 150. Any method for inferring the locations ofagents 120 or employees may be used. - After determining a possible location for a team, the
WFM application 250 may present the determined location to theadministrator 290 in a GUI. Theadministrator 290 may either confirm the determined location or may provide a different location using the GUI. - In some embodiments, after the
administrator 290 confirms or provides the location, theWFM application 250 may ask theadministrator 290, through the GUI, whether all of the teams of thecontact center 150 may be associated with the same location. If theadministrator 290 affirms that all of the teams may be associated with the same location, theWFM application 250 may associated each team with the location and stop the workflow. Otherwise, theWFM application 250 may continue the workflow and may determine a location for the next team based on thecontact center data 159. - After determining the location for each team, the
administrator 290 may select another item of theWFM application 250 to configure for a team. One example of such an item may be a minimum and maximum workinghours 171 for eachagent 120 in a team. Initially, theWFM application 250 may ask the administrator 290 (using the GUI) whether eachagent 120 in the team has the same minimum ormaximum hours 171. If theadministrator 290 answers affirmatively, theWFM application 250 may request the minimum andmaximum hours 171 for theagents 120 in the team from theadministrator 290. TheWFM application 250 may then consider a next team of thecontact center 150. - If the
administrator 290 answers negatively (i.e., eachagent 120 does not have the same minimum or maximum hours 171), theWFM application 250 may use a workflow to determine the minimum ormaximum hours 171. In some embodiments, theWFM application 250, for eachagent 120 of the team, may use thepresence data 155 to determine the minimum andmaximum hours 171 for theagent 120. - For example, the
WFM application 250 may determine the minimum and maximumweekly hours 171 for anagent 120 by using thepresence data 155 to determine events that indicate that theagent 120 was likely working such as computer logins, application usage information, phone usage information, etc. TheWFM application 250 may then use the times associated with each determined event to infer, for one or more weeks, the hours that theagent 120 was likely working during the one or more weeks. The maximum andminimum hours 171 for theagent 120 may then be inferred based on the likely hours determined for each of the one or more weeks. - Depending on the embodiment, the
WFM application 250 may use the location determined for the team oragent 120, to determine location-basedrules 157 that may apply to anagent 120. TheWFM application 250 may then ensure that the determined maximum orminimum hours 171 comply with the location-basedrules 157. Depending on the embodiment, the location-basedrules 157 may include legal rules related to the maximum number of hours that anagent 120 may work in a day or week, as well as entity orcontact center 150 policies about the minimum and maximum number of hours that anagent 120 may work during a day or week. For example, an entity such as a corporation may prefer that anagent 120 not work more than some number of overtime hours per week. Depending on the embodiment, the entity orcontact center 150 policies may be provided by anadministrator 290. - After the
WFM application 250 infers maximum andminimum hours 171 for theagents 120 in a team, theWFM application 250 may present the determined maximum andminimum hours 171 for eachagent 120 to theadministrator 290 through the GUI. Theadministrator 290 may then accept or modify the determined maximum andminimum hours 171 for eachagent 120. The maximum andminimum hours 171 for eachagent 120 may be used later by theWFM application 250 to generate one ormore schedules 255. - Another example of an item that the
WFM application 250 may infer for one or more teams and/oragents 120 using a workflow may beshifts 172 that eachagent 120 for a team can work. Depending on the embodiment, the contact routing system 153 of thecontact center 150 may scheduleagents 120 to one or more of a plurality ofshifts 172. Examples ofshifts 172 include a morning shift, an afternoon shift, and a night shift. More orfewer shifts 172 may be used by thecontact center 150. - Initially, the
WFM application 250 may ask the administrator 290 (using the GUI) whether eachagent 120 in the team works thesame shifts 172. If theadministrator 290 answers affirmatively, theWFM application 250 may request theshifts 172 for theagents 120 in the team from theadministrator 290. TheWFM application 250 may then consider a next team of thecontact center 150. - If the
administrator 290 answers negatively (i.e., eachagent 120 does not work the same shift 172), theWFM application 250, for eachagent 120 of the team, may use thepresence data 155 to determine theshifts 172 for theagent 120. - For example, the
WFM application 250 may determine theshifts 172 for anagent 120 by using thepresence data 155 to determine events that indicate that theagent 120 was likely working such as computer logins, application usage information, phone usage information, etc. TheWFM application 250 may then use the times associated with each determined event to infer, for one or more weeks, theshifts 172 that theagent 120 was likely working during the one or more weeks. Theshifts 172 for theagent 120 may then be determined based on theshifts 172 that theagent 120 was likely working for the one or more weeks. - Similarly as described above, the
WFM application 250 may use the location-basedrules 157 to ensure that the determined shifts for eachagent 120 comply with all local laws and entity policies. - After the
WFM application 250 infers theshifts 172 for eachagent 120 in a team, theWFM application 250 may present thedetermined shifts 172 for eachagent 120 to theadministrator 290 through the GUI. Theadministrator 290 may then accept or modify thedetermined shifts 172 for eachagent 120. - Another example of such an item that
application 250 may infer from thecontact center data 159 and/orpresence data 155 are startrules 173 for eachagent 120 of a team. Astart rule 173 for anagent 120 may indicate by how much the time at which theagent 120 begins their work day varies over the week. For example, oneagent 120 may start work at the same time every day of the week, while anotheragent 120 may start at a different time every day of the week. Thestart rule 173 for anagent 120 may generally indicate how flexible anagent 120 is regarding their start time, and therefore may be considered by theWFM application 250 when generating aschedule 255. - Initially, the
WFM application 250 may ask the administrator 290 (using the GUI) whether eachagent 120 in the team must start their shift at the same time each day. If theadministrator 290 answers affirmatively, theWFM application 250 may request the start time from theadministrator 290. TheWFM application 250 may then consider a next team of thecontact center 150. - If the
administrator 290 answers negatively (i.e., eachagent 120 does not have the same start-time each day), theWFM application 250, for eachagent 120 of the team, may use thepresence data 155 to determine the variability of the start times for eachagent 120. - For example, the
WFM application 250 may determine the different start times for anagent 120 by using thepresence data 155 to determine events that indicate that theagent 120 was likely working. TheWFM application 250 may then use the times associated with each determined event to infer, for one or more weeks, the different times that theagent 120 likely started each shift. - The different times may be used to construct a
start rule 173 for theagent 120. For example, if theWFM application 250 determines that the start times for anagent 120 varies as much as three hours, then theagent 120 may be associated with astart rule 173 that says that the start time for theagent 120 may be varied by at most three hours. In another example, if theWFM application 250 determines that the start times for anagent 120 does not vary at all, then theagent 120 may be associated with astart rule 173 that says that the start time for theagent 120 may not be varied. - After the
WFM application 250 infers the start rules 173 for eachagent 120 in a team, theWFM application 250 may present thedetermined start rules 173 for eachagent 120 to theadministrator 290 through the GUI. Theadministrator 290 may then accept or modify thedetermined start rules 173 for eachagent 120. - Another example of such an item that the
WFM application 250 may infer for eachagent 120 of a team is abreak pattern 174. Thebreak pattern 174 for anagent 120 may be indicators of when, and for how long, theagent 120 typically takes breaks during a workday or shift including longer breaks such as lunch and shorter breaks such as lavatory breaks, etc. - Initially, the
WFM application 250 may ask the administrator 290 (using the GUI) whether eachagent 120 in the team must have thesame break pattern 174 during their shifts. If theadministrator 290 answers affirmatively, theWFM application 250 may request thebreak pattern 174 from theadministrator 290. TheWFM application 250 may then consider a next team of thecontact center 150. - If the
administrator 290 answers negatively (i.e., eachagent 120 does not have the same break pattern 174), theWFM application 250, for eachagent 120 of the team, may use thepresence data 155 to determine thebreak pattern 174 for eachagent 120. - For example, the
WFM application 250 may use thepresence data 155 to determine events that indicate that theagent 120 has taken a break during their shift or workday. These events may include logging out on an application or workstation, or setting a presence indicator to away, for example. TheWFM application 250 may then use the times associated with each determined event to infer, for one or more weeks, the different times that theagent 120 likely took breaks. These times may be used to determine abreak pattern 174 for theagent 120. Depending on the embodiment, theWFM application 250 may use the location-basedrules 157 to ensure that thedetermined break pattern 174 for anagent 120 complies with all applicable laws and regulations (e.g., does theagent 120 take enough breaks as required by law), as well as any entity orcontact center 150 specific policies. - After the
WFM application 250 infers abreak pattern 174 for eachagent 120 in a team, theWFM application 250 may present thedetermined break pattern 174 for eachagent 120 to theadministrator 290 through the GUI. Theadministrator 290 may then accept or modify the presentedbreak pattern 174 for eachagent 120. - The
WFM application 250 may further us thecontact center data 159 and thepresence data 155 to generate one ormore forecasts 251 for thecontact center 150. Aforecast 251 for acontact center 150 may be an estimate or prediction of how busy thecontact center 150 will likely be at date or time in the future. - Depending on the embodiment, the
WFM application 250 may determine theforecast 251 for thecontact center 150 by processing thepresence data 155 andcontact center data 159 to determine indicators of how busy thecontact center 150 was in the past. These indicators can then be used by theWFM application 250 to train a model to predict how busy thecontact center 150 will likely be at a future date based on characteristics of the future date like day of the week or proximity to a holiday, for example. Other information may be used to train the model. Depending on the embodiment, the model may be further trained by comparingforecasts 251 generated by the model with actual observed workload data for thecontact center 150 for the same dates (e.g., using machine learning). - The
WFM application 250 may further generateschedules 255 for the contact center 150 (or team) based on theforecasts 251, and the various items that were inferred for eachagent 120 such as maximum andminimum hours 171, shifts 172, breakpatterns 174, and startrules 173. TheWFM application 250 may further consider the location-basedrules 157 to ensure that eachschedule 255 complies with all laws and regulations as well as entity policies. Any method forscheduling agents 120 may be used. - Depending on the embodiment, the
WFM application 250 may present each proposedschedule 255 to theadministrator 290 for approval through the GUI. Theadministrator 290 may either approve the proposedschedule 255, may reject the proposedschedule 255, or may make one or more changes to the proposedschedule 255. -
FIG. 3 is an illustration of anexample method 300 for configuring a WFM system. Themethod 300 may be performed by theWFM application 250. Depending on the embodiment, anadministrator 290 may have installed theWFM application 250, and themethod 300 may configure one or more items of theWFM application 250 usingcontact center data 159 andpresence data 155 automatically downloaded from a contact routing system 153 of acontact center 150. - At 301, an item is selected to configure. The item may be a configurable item or setting of the
WFM application 250. The configurable items may include minimum ormaximum hours 171, shifts 172, and breakpatterns 174. Other configurable items may be supported. Depending on the embodiment and items, the items may be configurable peragent 120, per customer 110, or per team, for example. The item may be selected automatically by theWFM application 250, or may be selected by a user (e.g., administrator 290) using a GUI. - At 303, a team is selected. The team may be a group of
agents 120 and may be selected by theadministrator 290 through the GUI. Alternatively, the team may be selected automatically (i.e., without user input) by theWFM application 250. Depending on the embodiment, the teams may be teams of thecontact center 150 and may have been determined fromcontact center data 159 downloaded from the contact routing system 153. Because the teams were determined from thecontact center data 159, theadministrator 290 did not have to manually enter the teams (and associated agents 120) into theWFM application 250. - At 305, a determination is made as to whether the selected item has a simple configuration with respect to the team. Depending on the embodiment, the
WFM application 250 may make the determination by asking theadministrator 290 using the GUI. - Whether or not an item has a simple configuration may be dependent on the item. Generally, an item has a simple configuration if all
agents 120 associated with the team have the same value or setting for the item. For example, for an item such asmaximum hours 171, the item may have a simple configuration if allagents 120 of the team have the same maximum hours 171 (e.g., 40). - If the
administrator 290 indicates that the item has a simple configuration, themethod 300 may continue at 307. Else, themethod 300 may continue at 309. - At 307, user input is received and the item is configured. Because the configuration was determined to be simple, the item may be configured by the
WFM application 250 asking theadministrator 290 to provide a value for the item (through the GUI). User input including the value may be received from theadministrator 290 and may be used by theWFM application 250 to configure the item for allagents 120 associated with the team. - Continuing the
maximum hours 171 example above, theadministrator 290 may provide the value “40” as themaximum hours 171 for theagents 120 in the team. TheWFM application 250 may then configure themaximum hours 171 to “40” for allagents 120 in the team. - At 309, automatic configuration of the item is performed. The automatic configuration of the item may be performed by the
WFM application 250 using one or both of thecontact center data 159 or thepresence data 155. In particular, the item may be configured by, for eachagent 120 of the team, inferring the value of the item from thecontact center data 159 or thepresence data 155. The value may be inferred using a workflow associated with the item. - Continuing the example above, for an item such as the
maximum hours 171, theWFM application 250, for eachagent 120 in the team, may analyze thepresence data 155 associated with theagent 120 to determine events such as logins and application usage, that may indicate when theagent 120 was likely working. Based on these determined events and their associated times, theWFM application 250 may infer themaximum hours 171 for theagent 120. - At 311, a user review is performed. The user review may be performed by the
WFM application 250. Depending on the embodiment, theWFM application 250 may display the proposed configuration for the item with respect to eachagent 120 in the team to theadministrator 290, and theadministrator 290 may approve the configurations, or may provide different values to use for some or all of the proposed item configurations. - At 313, a determination is made of whether there are more teams that the selected item may be configured for. The determination may be made by the
WFM application 250. If there are more teams, then themethod 300 may return to 303 where a new team may be selected. Else, themethod 300 may continue at 315. - At 315, a determination is made of whether there are more items that may be configured. The determination may be made by the
WFM application 250. If there are more items, then themethod 300 may return to 301 where a new item may be selected. Else, themethod 300 may exit at 317. -
FIG. 4 is an illustration of anexample method 400 for automatically configuring items for aWFM application 250 based on data received from a contact routing system 153. Themethod 400 may be implemented by theWFM application 250. - A 410, a contact routing system is interfaced with. The
WMF application 250 may interface with the contact routing system 153 using credentials provided by theadministrator 290. - At 415,
contact center data 159 is received. Thecontact center data 159 may be received by theWFM application 250 from the contact routing system 153 through the interface. - At 420, a selection of an item to configure is received. The selection of the item may be received by the
WFM application 250 from anadministrator 290 through a GUI. The GUI may be used by theadministrator 290 to configure theWFM application 250. - The selected item may be a configurable item associated with the
WFM application 250. The configurable items may include startrules 173, shifts 172,hours 171, and breakpatterns 174. Other items may be configured. The configurable items may be related toagents 120, teams, or customers 110 associated with thecontact center 150. - At 425, a workflow corresponding to the selected item is selected. The workflow may be selected by the
WFM application 250 from a plurality of workflows. For example, theWFM application 250 may have separate workflows to configure items such as start rules 173, breakpatterns 174, and shifts 172. - At 430, the selected item is configured automatically using the selected workflow and the contact center data. The selected item may be configured by the
WFM application 250. Depending on the embodiment, the item may be configured also usingpresence data 155 and one or more location-basedrules 157 corresponding to a location of one ormore agents 120, teams, or thecontact center 150. -
FIG. 5 is an illustration of anexample method 500 for automatically configuring aWFM application 250 based on data received from a contact routing system 153 of acontact center 150. Themethod 500 may be implemented by theWFM application 250. - A 510, a contact routing system is interfaced with. A
WFM application 250 may interface with the contact routing system 153 as part of configuring theWFM application 250. In some embodiments, an entity oradministrator 290 associated with thecontact center 150 may have determined to create and configure a WFM management system for theagents 120 and employees of thecontact center 150. Accordingly, theadministrator 290 may have caused an instance of theWFM application 250 to be installed on adeployment server 170. Thedeployment server 170 executing theWFM application 250 may be referred to as the WFM server. - At 515, a plurality of agents associated with the contact center are determined. The plurality of
agents 120 may be determined by theWFM application 250 fromcontact center data 159 received from the contact routing system 153. Depending on the embodiment, theWFM application 250 may further determine teams associated with thecontact center 150 and may determineagents 120 associated with each team. - At 520, presence data associated with each agent is received. The
presence data 155 may be received by theWFM application 250 from the contact routing system 153. Depending on the embodiment, thepresence data 155 for anagent 120 may include a plurality of events, and each event may be associated with a time. Example events may include logging in, or out, or a computer or application, using a particular application, setting a presence indicator to present or away, and handling a communication such as a phone call, email, or text message. Other events may be supported. Thepresence data 155 may be part of thecontact center data 159 or may be received separately from the contact routing system 153. - At 525, for at least one agent of the plurality of agents, a maximum and a
minimum hours 171 is determined. The maximum andminimum hours 171 may be determined by theWFM application 250 using thepresence data 155 associated with the at least oneagent 120. - The
maximum hours 171 for anagent 120 may be the maximum hours that theagent 120 is willing to work during some period such as a day, week, month, etc. Similarly, theminimum hours 171 may be the minimum hours that theagent 120 that theagent 120 is willing to work during the period. As may be appreciated, knowing the minimum andmaximum hours 171 for eachagent 120 is desirable when generating aschedule 255 to ensure that eachagent 120 is satisfied with the number of hours that they are assigned. -
FIG. 6 is an illustration of anexample method 600 for automatically configuring aWFM application 250 based on data received from contact routing system 153 of acontact center 150. Themethod 600 may be implemented by theWFM application 250. - A 610, a contact routing system is interfaced with. A
WFM application 250 may interface with the contact routing system as part of configuring theWFM application 250. - At 615, a plurality of agents associated with the contact center are determined. The plurality of
agents 120 may be determined by theWFM application 250 fromcontact center data 159 received from the contact routing system 153. Depending on the embodiment, theWFM application 250 may further determine teams associated with thecontact center 150 and may determineagents 120 associated with each team. - At 620, presence data associated with each agent is received. The
presence data 155 may be received by theWFM application 250 from the contact routing system 153. - At 625, for at least one agent of the plurality of agents, one or more shifts are determined. The shifts 172 (e.g., morning shift, day shift, or night shift) may be determined by the
WFM application 250 using thepresence data 155 associated with the at least oneagent 120. - The
shifts 172 for anagent 120 may be theshifts 172 that theagent 120 typically worked in the past for thecontact center 150. As may be appreciated, knowing theshifts 172 for eachagent 120 is desirable when generating aschedule 255 to ensure that eachagent 120 is only scheduled to work during a shift that they are willing to work. - In some embodiments, the
WFM application 250 may determine theshifts 172 using thepresence data 155. For example, theWFM application 250 may determine events from thepresence data 155 that indicate when theagent 120 was likely working. TheWFM application 250 may then determine what shifts of thecontact center 150 that the determined events occurred during based on the times associated with the determined events. The shifts with the most associated events may be determined as theshifts 172 for theagent 120. Other methods may be used. -
FIG. 7 is an illustration of anexample method 700 for automatically configuring aWFM application 250 based on data received from a contact routing system 153 of acontact center 150. Themethod 700 may be implemented by theWFM application 250. - A 710, a contact routing system is interfaced with. A
WFM application 250 may interface with the contact routing system 153 as part of configuring theWFM application 250. - At 715, a plurality of agents associated with the contact center are determined. The plurality of
agents 120 may be determined by theWFM application 250 fromcontact center data 159 received from the contact routing system 153. Depending on the embodiment, theWFM application 250 may further determine teams associated with thecontact center 150 and may determineagents 120 associated with each team. - At 720, presence data associated with each agent is received. The
presence data 155 may be received by theWFM application 250 from the contact routing system 153. - At 725, for at least one agent of the plurality of agents, a
break pattern 174 is determined. Thebreak pattern 174 may be determined by theWFM application 250 using thepresence data 155 associated with the at least oneagent 120. - The
break pattern 174 for anagent 120 may be a data structure that identifies the time and duration of each break taken by theagent 120 during a shift or other period (e.g., day or week). As may be appreciated, thebreak pattern 174 associated with theagent 120 may be used for generating aschedule 255 so that any breaks that theagent 120 is used to taking are scheduled at their expected times. - In some embodiments, the
WFM application 250 may determine thebreak pattern 174 using thepresence data 155. For example, theWFM application 250 may determine events from thepresence data 155 that indicate when theagent 120 was likely on break. These events may include logging out of a computer, closing one or more applications or setting a presence indicator to away. TheWFM application 250 may then determine the times usually associated with breaks for theagent 120 and may use those times to determine thebreak pattern 174 for theagent 120. Other methods may be used. - In some embodiments, the
WFM application 250 may determine the minimum andmaximum hours 171 for a period using thepresence data 155. For example, theWFM application 250 may, for previous periods, determine events from thepresence data 155 that indicate when theagent 120 was likely working. These events may include when theagent 120 first logged into their computer during a period, and when theagent 120 last logged out from their computer during the period. Average minimum and maximum hours worked by theagent 120 during the periods may be used as the minimum andmaximum hours 171 for theagent 120. Other methods may be used. -
FIG. 8 is an illustration of anexample method 800 for automatically configuring aWFM application 250 using workflows and for generating one or more forecasts and schedules. Themethod 800 may be implemented by theWFM application 250. - At 805, an application is deployed. The application may be a
WFM application 250 and may be deployed on adeployment server 170 by anadministrator 290. Depending on the embodiment, theadministrator 290 may have selected theapplication 260 to deploy from a plurality of applications made available by anapplication server 160. - At 810, a contact routing system is interfaced with. A
WFM application 250 may interface with the contact routing system 153 as part of configuring theWFM application 250. TheWFM application 250 may import data from the contact routing system 153 such ascontact center data 159 andpresence data 155. Other types of data may be imported from the contact routing system 153. - At 815, the application is configured. The
WFM application 250 may be configured automatically using one or more workflows and the data imported from the contact routing system 153. The items of theWFM application 250 that may be configured using workflows may include teams, locations, queues, event types, historical contact data,agents 120, minimum andmaximum hours 171, shifts 172, breaks or breakpatterns 174, constancy rules (e.g., start rules 173), andagent 120 availability. Other items may be configured. - At 820, one or more forecasts are generated. The one or
more forecast 251 may be generated by theWFM application 250. Eachforecast 251 may be an indication of how busy thecontact center 150 is likely to be at some future time or period (e.g., day, week, or month). Theforecast 251 may be generated using historical data about the workload or overall busyness of thecontact center 150 during past periods. The historical data may be part of the contactdata center data 159, for example. Any method for generating aforecast 251 for a future period based on historical data from past periods may be used. - At 825, the one or more forecasts are validated. The one or more forecasts may be validated by the
administrator 290. For example, the one ormore forecasts 251 may have been provided to theadministrator 290 in a GUI. If theadministrator 290 is satisfied by the one ormore forecasts 251, theadministrator 290 may use the GUI to validate the one or more forecasts. - At 830, one or more schedules are generated. The one or
more schedules 255 may be generated by theWFM application 250. Eachschedule 255 may be generated for one of the generatedforecasts 251 according to the items configured for theapplication 250 at 815. - For example, the
WFM application 250 may generate eachschedule 255 such thatsufficient agents 120 are scheduled to handle the workload predicted by the associatedforecast 251 while also complying with location-basedrules 157 associated with the location determined for theagents 120 or thecontact center 150. TheWFM application 250 may further generate eachschedule 255 to honor items such as start rules 173, breakpatterns 174,hours 171, and shifts 172 determined by theWFM application 250 for eachagents 120 or team. - At 825, the one or more schedules are validated. The one or
more schedules 835 may be validated by theadministrator 290 through the GUI. Depending on the embodiment, after the one ormore schedules 255 are validated by theadministrator 290 they may be implemented by thecontact center 150. -
FIG. 9 shows an exemplary computing environment in which example embodiments and aspects may be implemented. The computing system environment is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality. - Numerous other general purpose or special purpose computing system environments or configurations may be used. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers, servers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network personal computers (PCs), minicomputers, mainframe computers, embedded systems, distributed computing environments that include any of the above systems or devices, and the like.
- Computer-executable instructions, such as program modules, being executed by a computer may be used. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Distributed computing environments may be used where tasks are performed by remote processing devices that are linked through a communications network or other data transmission medium. In a distributed computing environment, program modules and other data may be located in both local and remote computer storage media including memory storage devices.
- With reference to
FIG. 9 , an exemplary system for implementing aspects described herein includes a computing device, such ascomputing device 900. In its most basic configuration,computing device 900 typically includes at least oneprocessing unit 902 andmemory 904. Depending on the exact configuration and type of computing device,memory 904 may be volatile (such as random access memory (RAM)), non-volatile (such as read-only memory (ROM), flash memory, etc.), or some combination of the two. This most basic configuration is illustrated inFIG. 9 by dashedline 906. -
Computing device 900 may have additional features/functionality. For example,computing device 900 may include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Such additional storage is illustrated inFIG. 9 byremovable storage 908 andnon-removable storage 910. -
Computing device 900 typically includes a variety of tangible computer readable media. Computer readable media can be any available tangible media that can be accessed bydevice 900 and includes both volatile and non-volatile media, removable and non-removable media. - Tangible computer storage media include volatile and non-volatile, and removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
Memory 904,removable storage 908, andnon-removable storage 910 are all examples of computer storage media. Tangible computer storage media include, but are not limited to, RAM, ROM, electrically erasable program read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computingdevice 900. Any such computer storage media may be part ofcomputing device 900. -
Computing device 900 may contain communications connection(s) 912 that allow the device to communicate with other devices.Computing device 900 may also have input device(s) 914 such as a keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 916 such as a display, speakers, printer, etc. may also be included. All these devices are well known in the art and need not be discussed at length here. - Returning to
FIG. 1 , agent(s) 120 and customers 110 may communicate with each other and with other services over thenetwork 130. For example, a customer calling on telephone handset may connect through the PSTN and terminate on a private branch exchange (PBX). A video call originating from a tablet may connect through thenetwork 130 terminate on the media server. A smartphone may connect via the WAN and terminate on an interactive voice response (IVR)/intelligent virtual agent (IVA) components. IVR are self-service voice tools that automate the handling of incoming and outgoing calls. Advanced IVRs use speech recognition technology to enable customers to interact with them by speaking instead of pushing buttons on their phones. IVR applications may be used to collect data, schedule callbacks and transfer calls to live agents. IVA systems are more advanced and utilize artificial intelligence (AI), machine learning (ML), advanced speech technologies (e.g., natural language understanding (NLU)/natural language processing (NLP)/natural language generation (NLG)) to simulate live and unstructured cognitive conversations for voice, text and digital interactions. In yet another example, Social media, email, SMS/MMS, IM may communicate with their counterpart's application (not shown) within thecontact center 150. - The
contact center 150 itself be in a single location or may be cloud-based and distributed over a plurality of locations. Thecontact center 150 may include servers, databases, and other components. In particular, thecontact center 150 may include, but is not limited to, a routing server, a SIP server, an outbound server, a reporting/dashboard server, automated call distribution (ACD), a computer telephony integration server (CTI), an email server, an IM server, a social server, a SMS server, and one or more databases for routing, historical information and campaigns. - The ACD is used by inbound, outbound and blended contact centers to manage the flow of interactions by routing and queuing them to the most appropriate agent. Within the CTI, software connects the ACD to a servicing application (e.g., customer service, CRM, sales, collections, etc.), and looks up or records information about the caller. CTI may display a customer's account information on the agent desktop when an interaction is delivered. Campaign management may be performed by an application to design, schedule, execute and manage outbound campaigns. Campaign management systems are also used to analyze campaign effectiveness.
- For inbound SIP messages, the routing server may use statistical data from reporting/dashboard information and a routing database to the route SIP request message. A response may be sent to the media server directing it to route the interaction to a
target agent 120. The routing database may include: customer relationship management (CRM) data; data pertaining to one or more social networks (including, but not limited to network graphs capturing social relationships within relevant social networks, or media updates made by members of relevant social networks); agent skills data; data extracted from third party data sources including cloud-based data sources such as CRM; or any other data that may be useful in making routing decisions. - The integration of real-time and non-real-time communication services may be performed by unified communications (UC)/presence sever. Real-time communication services include Internet Protocol (IP) telephony, call control, instant messaging (IM)/chat, presence information, real-time video and data sharing. Non-real-time applications include voicemail, email, SMS and fax services. The communications services are delivered over a variety of communications devices, including IP phones, personal computers (PCs), smartphones and tablets. Presence provides real-time status information about the availability of each person in the network, as well as their preferred method of communication (e.g., phone, email, chat and video).
- Recording applications may be used to capture and play back audio and screen interactions between customers and agents. Recording systems should capture everything that happens during interactions and what agents do on their desktops. Surveying tools may provide the ability to create and deploy post-interaction customer feedback surveys in voice and digital channels. Typically, the IVR/IVA development environment is leveraged for survey development and deployment rules. Reporting/dashboards are tools used to track and manage the performance of agents, teams, departments, systems and processes within the contact center. Reports are presented in narrative, graphical or tabular formats. Reports can be created on a historical or real-time basis, depending on the data collected by the contact center applications. Dashboards typically include widgets, gadgets, gauges, meters, switches, charts and graphs that allow role-based monitoring of agent, queue and contact center performance. Unified messaging (UM) applications include various messaging and communications media (voicemail, email, SMS, fax, video, etc.) stored in a common repository and accessed by users via multiple devices through a single unified interface.
- It should be understood that the various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the methods and apparatus of the presently disclosed subject matter, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the presently disclosed subject matter. In the case of program code execution on programmable computers, the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. One or more programs may implement or utilize the processes described in connection with the presently disclosed subject matter, e.g., through the use of an application programming interface (API), reusable controls, or the like. Such programs may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language and it may be combined with hardware implementations.
- Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (20)
1. A method for configuring a workforce management system for a contact center comprising:
interfacing with a contact center by a workforce management system;
determining a plurality of agents associated with the contact center by the workforce management system;
retrieving presence data for each agent from the contact center by the workforce management system, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time;
for at least one agent of the plurality of agents, determining a maximum hours for the at least one agent based on the presence data for the agent by the workforce management system; and
for the at least one agent of the plurality of agents, generating a schedule for the at least one agent based on the determined maximum hours by the workforce management system.
2. The method of claim 1 , further comprising:
for the at least one agent of the plurality of agents, determining a location for the at least one agent;
retrieving one or more rules that relate to scheduling for the location; and
for the at least one agent of the plurality of agents, determining the maximum hours for the at least one agent based on the presence data for the at least one agent and the one or more rules.
3. The method of claim 1 , wherein determining the maximum hours for the at least one agent based on the presence data for the at least one agent comprises:
inferring, from the presence data, a number of hours worked by the at least one agent for each week of a plurality of weeks; and
determining the maximum hours for the at least one agent based on the number of hours worked by the at least one agent for each week of the plurality of weeks.
4. The method of claim 1 , wherein the events comprise one or more of computer logins, computer logouts, communications, and application activities.
5. The method of claim 1 , further comprising:
for the at least one agent of the plurality of agents, determining a minimum hours for the at least one agent based on the presence data for the at least one agent.
6. The method of claim 5 , further comprising:
for the at least one agent of the plurality of agents, generating the schedule for the at least one agent based on the determined maximum hours and the determined minimum hours.
7. The method of claim 1 , further comprising:
for the at least one agent of the plurality of agents, determining, based on the presence data, one or more shifts that the at least one agent is available to work, and one or more break patterns associated with the at least one agent.
8. The method of claim 7 , further comprising generating the schedule for the at least one agent based on the determined maximum hours, the determined one or more shifts that the at least one agent is available to work, and the determined one or more break patterns associated with the at least one agent.
9. A system for configuring an application for a contact center comprising:
at least one processor; and
a non-transitory computer readable medium comprising instructions that, when executed by the at least one processor, cause the system to:
interface with a contact center;
determine a plurality of agents associated with the contact center;
retrieve presence data for each agent from the contact center, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time;
for at least one agent of the plurality of agents, determine a maximum hours for the at least one agent based on the presence data for the agent; and
for the at least one agent of the plurality of agents, generate a schedule for the at least one agent based on the determined maximum hours.
10. The system of claim 9 , further comprising instructions that, when executed by the at least one processor, cause the system to:
for the at least one agent of the plurality of agents, determine a location for the at least one agent;
retrieve one or more rules that relate to scheduling for the location; and
for the at least one agent of the plurality of agents, determine the maximum hours for the at least one agent based on the presence data for the at least one agent and the one or more rules.
11. The system of claim 9 , wherein determining the maximum hours for the at least one agent based on the presence data for the at least one agent comprises:
inferring, from the presence data, a number of hours worked by the at least one agent for each week of a plurality of weeks; and
determining the maximum hours for the at least one agent based on the number of hours worked by the at least one agent for each week of the plurality of weeks.
12. The system of claim 9 , wherein the events comprise one or more of computer logins, computer logouts, communications, and application activities.
13. The system of claim 9 , further comprising instructions that, when executed by the at least one processor, cause the system to:
for the at least one agent of the plurality of agents, determine a minimum hours for the at least one agent based on the presence data for the at least one agent.
14. The system of claim 13 , further comprising instructions that, when executed by the at least one processor, cause the system to:
for the at least one agent of the plurality of agents, generate the schedule for the at least one agent based on the determined maximum hours and the determined minimum hours.
15. The system of claim 9 , further comprising instructions that, when executed by the at least one processor, cause the system to:
for the at least one agent of the plurality of agents, determine, based on the presence data, one or more shifts that the at least one agent is available to work, and one or more break patterns associated with the at least one agent.
16. The system of claim 15 , further comprising generating the schedule for the at least one agent based on the determined maximum hours, the determined one or more shifts that the at least one agent is available to work, and the determined one or more break patterns associated with the at least one agent.
17. The system of claim 9 , wherein the system is a workforce management system.
18. A non-transitory computer-readable medium comprising instructions that, when executed by at least one processor, cause a computer system to:
interface with a contact center;
determine a plurality of agents associated with the contact center;
retrieve presence data for each agent from the contact center, wherein the presence data for an agent comprises a plurality of events and each event is associated with a time;
for at least one agent of the plurality of agents, determine a maximum hours for the at least one agent based on the presence data for the agent; and
for the at least one agent of the plurality of agents, generate a schedule for the at least one agent based on the determined maximum hours.
19. The computer-readable medium of claim 18 , further comprising instructions that, when executed by the at least one processor, cause the computer system to:
for the at least one agent of the plurality of agents, determine a minimum hours for the at least one agent based on the presence data for the at least one agent.
20. The computer-readable medium of claim 19 , further comprising instructions that, when executed by the at least one processor, cause the computer system to:
for the at least one agent of the plurality of agents, generate the schedule for the at least one agent based on the determined maximum hours and the determined minimum hours.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/656,139 US20210117884A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/654,356 US20210117882A1 (en) | 2019-10-16 | 2019-10-16 | Systems and methods for workforce management system deployment |
US16/656,139 US20210117884A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/654,356 Continuation US20210117882A1 (en) | 2019-10-16 | 2019-10-16 | Systems and methods for workforce management system deployment |
Publications (1)
Publication Number | Publication Date |
---|---|
US20210117884A1 true US20210117884A1 (en) | 2021-04-22 |
Family
ID=75491212
Family Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/654,356 Pending US20210117882A1 (en) | 2019-10-16 | 2019-10-16 | Systems and methods for workforce management system deployment |
US16/656,179 Abandoned US20210117906A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
US16/656,124 Abandoned US20210117903A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
US16/656,150 Abandoned US20210117904A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
US16/656,170 Abandoned US20210117885A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
US16/656,160 Active 2040-04-10 US11783246B2 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
US16/656,139 Abandoned US20210117884A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
Family Applications Before (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/654,356 Pending US20210117882A1 (en) | 2019-10-16 | 2019-10-16 | Systems and methods for workforce management system deployment |
US16/656,179 Abandoned US20210117906A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
US16/656,124 Abandoned US20210117903A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
US16/656,150 Abandoned US20210117904A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
US16/656,170 Abandoned US20210117885A1 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
US16/656,160 Active 2040-04-10 US11783246B2 (en) | 2019-10-16 | 2019-10-17 | Systems and methods for workforce management system deployment |
Country Status (1)
Country | Link |
---|---|
US (7) | US20210117882A1 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220129857A1 (en) * | 2020-10-27 | 2022-04-28 | Nice Ltd. | Systems and methods for analyzing worker conformance and efficiency |
CN114724265A (en) * | 2020-12-22 | 2022-07-08 | Jvc建伍株式会社 | Attendance management system |
Family Cites Families (616)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
SU1732352A1 (en) | 1990-03-26 | 1992-05-07 | Научно-Производственное Объединение "Орбита" | Queue system simulator |
US5862203A (en) | 1995-07-21 | 1999-01-19 | Call Manage | Telecommunications call management system |
US5970124A (en) | 1996-06-05 | 1999-10-19 | Voice Fx Corporation | Sponsored information distribution method and apparatus |
US6128415A (en) | 1996-09-06 | 2000-10-03 | Polaroid Corporation | Device profiles for use in a digital image processing system |
US7231035B2 (en) | 1997-04-08 | 2007-06-12 | Walker Digital, Llc | Method and apparatus for entertaining callers in a queue |
US7426268B2 (en) | 1997-04-11 | 2008-09-16 | Walker Digital, Llc | System and method for call routing and enabling interaction between callers with calls positioned in a queue |
US5966691A (en) | 1997-04-29 | 1999-10-12 | Matsushita Electric Industrial Co., Ltd. | Message assembler using pseudo randomly chosen words in finite state slots |
US5897616A (en) | 1997-06-11 | 1999-04-27 | International Business Machines Corporation | Apparatus and methods for speaker verification/identification/classification employing non-acoustic and/or acoustic models and databases |
US6370566B2 (en) | 1998-04-10 | 2002-04-09 | Microsoft Corporation | Generating meeting requests and group scheduling from a mobile device |
US6735574B2 (en) | 1997-11-05 | 2004-05-11 | Micron Technology, Inc. | Method and system for tracking employee productivity in a client/server environment |
GB9723813D0 (en) | 1997-11-11 | 1998-01-07 | Mitel Corp | Call routing based on caller's mood |
US20020169664A1 (en) | 1997-12-01 | 2002-11-14 | Walker Jay S. | System for providing offers using a billing statement |
US7907598B2 (en) | 1998-02-17 | 2011-03-15 | Genesys Telecommunication Laboratories, Inc. | Method for implementing and executing communication center routing strategies represented in extensible markup language |
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 |
US6181694B1 (en) | 1998-04-03 | 2001-01-30 | Vertical Networks, Inc. | Systems and methods for multiple mode voice and data communciations using intelligently bridged TDM and packet buses |
US6173053B1 (en) | 1998-04-09 | 2001-01-09 | Avaya Technology Corp. | Optimizing call-center performance by using predictive data to distribute calls among agents |
US7344066B1 (en) | 1998-04-17 | 2008-03-18 | Diebold, Incorporated | Wireless transfer of account data and signature from hand-held device to electronic check generator |
US6100891A (en) | 1998-06-09 | 2000-08-08 | Teledirect International, Inc. | Call center agent interface and development tool |
US7082397B2 (en) | 1998-12-01 | 2006-07-25 | Nuance Communications, Inc. | System for and method of creating and browsing a voice web |
US6377944B1 (en) | 1998-12-11 | 2002-04-23 | Avaya Technology Corp. | Web response unit including computer network based communication |
US6665395B1 (en) | 1998-12-11 | 2003-12-16 | Avaya Technology Corp. | Automatic call distribution system using computer network-based communication |
US7209889B1 (en) | 1998-12-24 | 2007-04-24 | Henry Whitfield | Secure system for the issuance, acquisition, and redemption of certificates in a transaction network |
US6643622B2 (en) | 1999-02-19 | 2003-11-04 | Robert O. Stuart | Data retrieval assistance system and method utilizing a speech recognition system and a live operator |
CA2364468A1 (en) | 1999-03-06 | 2000-09-14 | Coppercom, Inc. | System and method for administrating call and call feature set-up in a telecommunications network |
US6345093B1 (en) | 1999-04-13 | 2002-02-05 | Davox Corporation | System and method for providing automated take back and transfer functionality to a computer telephony system |
US6385584B1 (en) | 1999-04-30 | 2002-05-07 | Verizon Services Corp. | Providing automated voice responses with variable user prompting |
US6263057B1 (en) | 1999-05-07 | 2001-07-17 | Lucent Technologies Inc. | Automatic telecommunications provider selection system |
US6639982B1 (en) | 1999-08-12 | 2003-10-28 | Six Sigma, Inc. | Method and apparatus for agent forcing and call distribution for large team call servicing |
US6493695B1 (en) | 1999-09-29 | 2002-12-10 | Oracle Corporation | Methods and systems for homogeneously routing and/or queueing call center customer interactions across media types |
US6587831B1 (en) | 1999-10-21 | 2003-07-01 | Workforce Logistics Inc. | System and method for online scheduling and shift management |
US7725307B2 (en) | 1999-11-12 | 2010-05-25 | Phoenix Solutions, Inc. | Query engine for processing voice based queries including semantic decoding |
GB9930720D0 (en) | 1999-12-29 | 2000-02-16 | Ibm | Call centre agent automated assistance |
WO2001054388A1 (en) * | 2000-01-07 | 2001-07-26 | Ineto, Inc. | Customer communication service system |
US20020029272A1 (en) | 2000-02-11 | 2002-03-07 | Scott Weller | Method and system for assigning and distributing work over a computer network |
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 |
US20020038420A1 (en) | 2000-04-13 | 2002-03-28 | Collins Timothy S. | Method for efficient public key based certification for mobile and desktop environments |
US6754333B1 (en) | 2000-04-27 | 2004-06-22 | Avaya Technology Corp. | Wait time prediction arrangement for non-real-time customer contacts |
US7774790B1 (en) | 2000-07-18 | 2010-08-10 | Apple Inc. | Event logging and performance analysis system for applications |
TW486902B (en) | 2000-08-11 | 2002-05-11 | Neovue Inc | Method capable of preventing electronic documents from being illegally copied and its system |
US20040044585A1 (en) | 2000-08-15 | 2004-03-04 | Hector Franco | Customer service management system |
US7076047B1 (en) | 2000-09-01 | 2006-07-11 | Verizon Corporate Services Group Inc. | Method and apparatus for determining the carrier used for an AIN call |
US20060074727A1 (en) | 2000-09-07 | 2006-04-06 | Briere Daniel D | Method and apparatus for collection and dissemination of information over a computer network |
US6822945B2 (en) | 2000-11-08 | 2004-11-23 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for anticipating and planning communication-center resources based on evaluation of events waiting in a communication center master queue |
US7644057B2 (en) | 2001-01-03 | 2010-01-05 | International Business Machines Corporation | System and method for electronic communication management |
US7343406B1 (en) * | 2001-01-18 | 2008-03-11 | Cisco Technology, Inc. | Proactive call and contact center system |
US8467502B2 (en) | 2001-02-27 | 2013-06-18 | Verizon Data Services Llc | Interactive assistant for managing telephone communications |
US20030032409A1 (en) | 2001-03-16 | 2003-02-13 | Hutcheson Stewart Douglas | Method and system for distributing content over a wireless communications system |
US6668056B2 (en) | 2001-03-27 | 2003-12-23 | Qwest Communications International, Inc. | System and method for modeling resources for calls centered in a public switch telephone network |
US7478051B2 (en) * | 2001-04-02 | 2009-01-13 | Illah Nourbakhsh | Method and apparatus for long-range planning |
US8015042B2 (en) | 2001-04-02 | 2011-09-06 | Verint Americas Inc. | Methods for long-range contact center staff planning utilizing discrete event simulation |
US7155399B2 (en) | 2001-04-03 | 2006-12-26 | Witness Systems, Inc. | System and method for complex schedule generation |
US6952732B2 (en) | 2001-04-30 | 2005-10-04 | Blue Pumpkin Software, Inc. | Method and apparatus for multi-contact scheduling |
US7016936B2 (en) | 2001-05-15 | 2006-03-21 | Hewlett-Packard Development Company, L.P. | Real time electronic service interaction management system and method |
US7103562B2 (en) | 2001-05-17 | 2006-09-05 | Bay Bridge Decision Technologies, Inc. | System and method for generating forecasts and analysis of contact center behavior for planning purposes |
US8131993B2 (en) | 2001-05-23 | 2012-03-06 | Sharestream, Llc | System and method for a commercial multimedia rental and distribution system |
JP2005514673A (en) | 2001-06-22 | 2005-05-19 | オモイグイ,ノサ | Knowledge acquisition, management, communication and presentation system and method |
US7110525B1 (en) | 2001-06-25 | 2006-09-19 | Toby Heller | Agent training sensitive call routing system |
US20040044664A1 (en) | 2001-07-10 | 2004-03-04 | Sabre Inc. | Systems and methods for applying customer DNA to airline service and customer relationship management environments |
US7953219B2 (en) | 2001-07-19 | 2011-05-31 | Nice Systems, Ltd. | Method apparatus and system for capturing and analyzing interaction based content |
AU2002341859A1 (en) | 2001-09-26 | 2003-04-07 | Wisor Telecom | Intelligent service management system |
US6683941B2 (en) | 2001-12-17 | 2004-01-27 | International Business Machines Corporation | Controlling advertising output during hold periods |
US7209475B1 (en) | 2001-12-28 | 2007-04-24 | Cisco Technology, Inc. | System and method for providing on-hold content in a voice over internet protocol (VoIP) environment |
US20030167167A1 (en) | 2002-02-26 | 2003-09-04 | Li Gong | Intelligent personal assistants |
US7372952B1 (en) | 2002-03-07 | 2008-05-13 | Wai Wu | Telephony control system with intelligent call routing |
US7023979B1 (en) | 2002-03-07 | 2006-04-04 | Wai Wu | Telephony control system with intelligent call routing |
US8170197B2 (en) | 2002-03-15 | 2012-05-01 | Intellisist, Inc. | System and method for providing automated call center post-call processing |
US7292689B2 (en) | 2002-03-15 | 2007-11-06 | Intellisist, Inc. | System and method for providing a message-based communications infrastructure for automated call center operation |
US8068595B2 (en) | 2002-03-15 | 2011-11-29 | Intellisist, Inc. | System and method for providing a multi-modal communications infrastructure for automated call center operation |
US7657263B1 (en) * | 2002-03-21 | 2010-02-02 | Cisco Technology, Inc. | Method and system for automatic call distribution based on customized logic relating to agent behavior |
US7869998B1 (en) | 2002-04-23 | 2011-01-11 | At&T Intellectual Property Ii, L.P. | Voice-enabled dialog system |
AU2003272210A1 (en) * | 2002-08-16 | 2004-03-03 | Nuasis Corporation | Automatic management of the visual space while performing a task |
US7274787B1 (en) | 2002-08-16 | 2007-09-25 | Intervoice, Inc. | Scheduled return to queue with priority (SRQP) |
US7466334B1 (en) | 2002-09-17 | 2008-12-16 | Commfore Corporation | Method and system for recording and indexing audio and video conference calls allowing topic-based notification and navigation of recordings |
US6959080B2 (en) | 2002-09-27 | 2005-10-25 | Rockwell Electronic Commerce Technologies, Llc | Method selecting actions or phases for an agent by analyzing conversation content and emotional inflection |
US20040078257A1 (en) | 2002-10-21 | 2004-04-22 | Laborsage, Inc. | Labor and resource scheduling system |
EP1418519A1 (en) | 2002-11-05 | 2004-05-12 | Comhra Limited | A dialogue management system |
US20040098274A1 (en) | 2002-11-15 | 2004-05-20 | Dezonno Anthony J. | System and method for predicting customer contact outcomes |
US7698163B2 (en) | 2002-11-22 | 2010-04-13 | Accenture Global Services Gmbh | Multi-dimensional segmentation for use in a customer interaction |
US7606714B2 (en) | 2003-02-11 | 2009-10-20 | Microsoft Corporation | Natural language classification within an automated response system |
US20040162724A1 (en) * | 2003-02-11 | 2004-08-19 | Jeffrey Hill | Management of conversations |
US20040162753A1 (en) | 2003-02-14 | 2004-08-19 | Vogel Eric S. | Resource allocation management and planning |
US7418095B2 (en) | 2003-03-06 | 2008-08-26 | At&T Knowledge Ventures, L.P. | System and method for providing caller activities while in queue |
US7676034B1 (en) | 2003-03-07 | 2010-03-09 | Wai Wu | Method and system for matching entities in an auction |
US7275032B2 (en) | 2003-04-25 | 2007-09-25 | Bvoice Corporation | Telephone call handling center where operators utilize synthesized voices generated or modified to exhibit or omit prescribed speech characteristics |
US7409336B2 (en) | 2003-06-19 | 2008-08-05 | Siebel Systems, Inc. | Method and system for searching data based on identified subset of categories and relevance-scored text representation-category combinations |
JP4504099B2 (en) | 2003-06-25 | 2010-07-14 | 株式会社リコー | Digital certificate management system, digital certificate management apparatus, digital certificate management method, update procedure determination method and program |
WO2005006138A2 (en) * | 2003-06-30 | 2005-01-20 | Idocuments, Llc | Worker and document management system |
US7027463B2 (en) | 2003-07-11 | 2006-04-11 | Sonolink Communications Systems, Llc | System and method for multi-tiered rule filtering |
US7158628B2 (en) | 2003-08-20 | 2007-01-02 | Knowlagent, Inc. | Method and system for selecting a preferred contact center agent based on agent proficiency and performance and contact center state |
US8184782B1 (en) | 2003-09-17 | 2012-05-22 | Healthsense, Inc. | Method and apparatus for processing voice calls |
US8655837B2 (en) | 2003-09-30 | 2014-02-18 | Aspect Software, Inc. | Data session notification means and method |
US9208495B2 (en) | 2003-10-06 | 2015-12-08 | Yellowpages.Com Llc | Methods and apparatuses for advertisement presentation |
US20070162296A1 (en) | 2003-10-06 | 2007-07-12 | Utbk, Inc. | Methods and apparatuses for audio advertisements |
US9984170B2 (en) | 2004-02-19 | 2018-05-29 | Celeritasworks, Llc | Community awareness management systems and methods |
US9137366B2 (en) | 2004-03-29 | 2015-09-15 | West Corporation | Maintaining a work schedule |
GB0407735D0 (en) | 2004-04-05 | 2004-05-12 | Nokia Corp | Analysing designs of services provided by means of a communication system |
US20050228774A1 (en) | 2004-04-12 | 2005-10-13 | Christopher Ronnewinkel | Content analysis using categorization |
US7284107B2 (en) | 2004-04-30 | 2007-10-16 | Microsoft Corporation | Special-use heaps |
US7570754B2 (en) | 2004-06-02 | 2009-08-04 | Alcatel-Lucent Usa Inc. | System and method for routing calls in a telecommunications network |
US7672845B2 (en) | 2004-06-22 | 2010-03-02 | International Business Machines Corporation | Method and system for keyword detection using voice-recognition |
US20060062376A1 (en) | 2004-09-22 | 2006-03-23 | Dale Pickford | Call center services system and method |
US7949123B1 (en) | 2004-09-28 | 2011-05-24 | Avaya Inc. | Wait time predictor for long shelf-life work |
FI121255B (en) | 2004-10-08 | 2010-08-31 | Sap Ag | A method and apparatus for controlling the availability of mobile telephone service agents in a telephone service environment |
US7778398B2 (en) | 2004-12-14 | 2010-08-17 | At&T Intellectual Property I, L.P. | Communication center application |
US20060153357A1 (en) | 2005-01-08 | 2006-07-13 | Arup Acharya | Method and apparatus for providing contextual information with telephone calls |
US20060166669A1 (en) | 2005-01-27 | 2006-07-27 | Holger Claussen | Brokering services between wireless device users and operators |
US8335704B2 (en) * | 2005-01-28 | 2012-12-18 | Pegasystems Inc. | Methods and apparatus for work management and routing |
US8229761B2 (en) | 2005-02-25 | 2012-07-24 | Virtual Radiologic Corporation | Enhanced multiple resource planning and forecasting |
US7933399B2 (en) | 2005-03-22 | 2011-04-26 | At&T Intellectual Property I, L.P. | System and method for utilizing virtual agents in an interactive voice response application |
US7689455B2 (en) | 2005-04-07 | 2010-03-30 | Olista Ltd. | Analyzing and detecting anomalies in data records using artificial intelligence |
US7711103B2 (en) | 2005-04-22 | 2010-05-04 | Culbertson Robert F | System and method for intelligent service agent using VoIP |
US20060256953A1 (en) * | 2005-05-12 | 2006-11-16 | Knowlagent, Inc. | Method and system for improving workforce performance in a contact center |
US7752048B2 (en) | 2005-05-27 | 2010-07-06 | Oracle International Corporation | Method and apparatus for providing speech recognition resolution on a database |
US8266452B2 (en) | 2005-06-01 | 2012-09-11 | Cisco Technology, Inc. | System and method for communicating confidential messages |
US8583466B2 (en) | 2005-08-09 | 2013-11-12 | Oracle International Corporation | System and method for routing workflow items based on workflow templates in a call center |
US7769148B2 (en) | 2005-08-22 | 2010-08-03 | Avaya Inc. | Filler video streams in interactive voice response systems |
US20070078725A1 (en) | 2005-09-09 | 2007-04-05 | Marketsync, Inc. | Integrated customer fulfillment management |
US7894596B2 (en) | 2005-09-13 | 2011-02-22 | Language Line Services, Inc. | Systems and methods for providing language interpretation |
US8364540B2 (en) | 2005-09-14 | 2013-01-29 | Jumptap, Inc. | Contextual targeting of content using a monetization platform |
US10572879B1 (en) | 2005-10-03 | 2020-02-25 | Avaya Inc. | Agent driven media-agnostic work item grouping and sharing over a consult medium |
US8073129B1 (en) * | 2005-10-03 | 2011-12-06 | Avaya Inc. | Work item relation awareness for agents during routing engine driven sub-optimal work assignments |
US8116446B1 (en) * | 2005-10-03 | 2012-02-14 | Avaya Inc. | Agent driven work item awareness for tuning routing engine work-assignment algorithms |
US20070121902A1 (en) | 2005-11-03 | 2007-05-31 | Andrei Stoica | Transfer of live calls |
US7920693B2 (en) | 2005-11-25 | 2011-04-05 | Teletech Holdings, Inc. | Home agent access in call routing management based on caller language |
US20070136284A1 (en) | 2005-12-12 | 2007-06-14 | Sbc Knowledge Ventures Lp | Method for constructing and repurposing rhetorical content |
WO2007081734A2 (en) | 2006-01-04 | 2007-07-19 | Innofone.Com, Inc. | Interactive mobile messaging system |
US8090082B2 (en) | 2006-01-23 | 2012-01-03 | Icall, Inc. | System, method and computer program product for extracting user profiles and habits based on speech recognition and calling history for telephone system advertising |
US8112306B2 (en) | 2006-02-22 | 2012-02-07 | Verint Americas, Inc. | System and method for facilitating triggers and workflows in workforce optimization |
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 |
US7761321B2 (en) | 2006-02-22 | 2010-07-20 | 24/7 Customer, Inc. | System and method for customer requests and contact management |
US7864946B1 (en) | 2006-02-22 | 2011-01-04 | Verint Americas Inc. | Systems and methods for scheduling call center agents using quality data and correlation-based discovery |
US8160233B2 (en) | 2006-02-22 | 2012-04-17 | Verint Americas Inc. | System and method for detecting and displaying business transactions |
US7593522B2 (en) | 2006-03-09 | 2009-09-22 | At&T Intellectual Property I, L.P. | Call center user interface and methods of using same |
US7672746B1 (en) | 2006-03-31 | 2010-03-02 | Verint Americas Inc. | Systems and methods for automatic scheduling of a workforce |
US8300798B1 (en) | 2006-04-03 | 2012-10-30 | Wai Wu | Intelligent communication routing system and method |
US20070269031A1 (en) | 2006-04-05 | 2007-11-22 | Edward Honig | Method and apparatus for distributing advertisements to callers during telephone calls |
US7593523B2 (en) | 2006-04-24 | 2009-09-22 | Language Line Services, Inc. | System and method for providing incoming call distribution |
US8331549B2 (en) | 2006-05-01 | 2012-12-11 | Verint Americas Inc. | System and method for integrated workforce and quality management |
US8135125B2 (en) | 2006-05-10 | 2012-03-13 | Microsoft Corporation | Multi-party information analysis in a VoIP system |
US7653186B2 (en) | 2006-05-26 | 2010-01-26 | Aeris Communications, Inc. | System and method for event communication correlation |
US8107610B2 (en) | 2006-06-06 | 2012-01-31 | At&T Intellectual Property I, L.P. | Callback processing of interactive voice response requests |
US20080004933A1 (en) | 2006-06-29 | 2008-01-03 | Destination Excellence, Inc. | System and method for providing daily and long-term contact, allocation and full-time equivalent staff forecasting |
US7881471B2 (en) | 2006-06-30 | 2011-02-01 | Verint Systems Inc. | Systems and methods for recording an encrypted interaction |
WO2008044227A2 (en) | 2006-07-17 | 2008-04-17 | Open Pricer | Customer centric revenue management |
US7831034B2 (en) | 2006-07-20 | 2010-11-09 | Microsoft Corporation | Management of telephone call routing using a directory services schema |
US8488774B2 (en) | 2006-07-24 | 2013-07-16 | Fmr Llc | Predictive call routing |
US7797679B2 (en) | 2006-08-31 | 2010-09-14 | Research In Motion Limited | System and method for providing a parameter for an application operating on an electronic device |
US8811597B1 (en) * | 2006-09-07 | 2014-08-19 | Avaya Inc. | Contact center performance prediction |
US7925001B2 (en) | 2006-11-22 | 2011-04-12 | Avaya Inc. | Methods and apparatus for contact center agent selection |
WO2008092147A2 (en) | 2007-01-26 | 2008-07-31 | Information Resources, Inc. | Analytic platform |
US8948371B2 (en) | 2007-02-28 | 2015-02-03 | Intellisist, Inc. | System and method for managing hold times during automated call processing |
US20170011311A1 (en) | 2007-03-08 | 2017-01-12 | Qless, Inc. | Queue and reservation management system |
US20080225872A1 (en) | 2007-03-12 | 2008-09-18 | Collins Kevin T | Dynamically defining queues and agents in a contact center |
US20080255944A1 (en) | 2007-03-29 | 2008-10-16 | Shah Nitin J | Campaign Management Platform for Network-Based Online Advertising and Directed Media Transmission System |
US8064888B2 (en) | 2007-04-12 | 2011-11-22 | Apple Inc. | Communications system that provides user-selectable data when user is on-hold |
US8014512B2 (en) | 2007-04-18 | 2011-09-06 | International Business Machines Corporation | Method and system for user interaction within a queue |
US8243896B1 (en) | 2007-05-24 | 2012-08-14 | Securus Technologies, Inc. | Selection of a particular communication carrier from a plurality of communication carriers in a secure environment |
US20080300955A1 (en) * | 2007-05-30 | 2008-12-04 | Edward Hamilton | System and Method for Multi-Week Scheduling |
US10231077B2 (en) | 2007-07-03 | 2019-03-12 | Eingot Llc | Records access and management |
US9224147B2 (en) | 2007-07-16 | 2015-12-29 | Hector Franco | Customer service management system |
US10097695B2 (en) | 2007-08-10 | 2018-10-09 | Fonality, Inc. | System and method for providing carrier-independent VoIP communication |
US8996509B1 (en) | 2007-09-03 | 2015-03-31 | Google Inc. | Query results enhancement through agent interaction |
US8243902B2 (en) | 2007-09-27 | 2012-08-14 | Siemens Enterprise Communications, Inc. | Method and apparatus for mapping of conference call participants using positional presence |
US20090086945A1 (en) | 2007-09-27 | 2009-04-02 | Buchanan Annette L | Methods and Apparatus for Selecting a Service Provider on a Per-Call Basis |
US8275110B2 (en) | 2007-09-28 | 2012-09-25 | Ringcentral, Inc. | Active call filtering, screening and dispatching |
US20090171164A1 (en) | 2007-12-17 | 2009-07-02 | Jung Edward K Y | Methods and systems for identifying an avatar-linked population cohort |
US10255609B2 (en) | 2008-02-21 | 2019-04-09 | Micronotes, Inc. | Interactive marketing system |
US7925743B2 (en) | 2008-02-29 | 2011-04-12 | Networked Insights, Llc | Method and system for qualifying user engagement with a website |
US20090234732A1 (en) | 2008-03-14 | 2009-09-17 | Ilan Zorman | Apparatus, system and method for selectively receiving advertising related content |
US8270580B2 (en) | 2008-04-01 | 2012-09-18 | Microsoft Corporation | Interactive voice advertisement exchange |
US8407049B2 (en) | 2008-04-23 | 2013-03-26 | Cogi, Inc. | Systems and methods for conversation enhancement |
US9247063B2 (en) | 2008-05-16 | 2016-01-26 | West Interactive Corporation Ii | Method and system for personalising responses to customer communications |
US8738739B2 (en) | 2008-05-21 | 2014-05-27 | The Delfin Project, Inc. | Automatic message selection with a chatbot |
US20140279050A1 (en) | 2008-05-21 | 2014-09-18 | The Delfin Project, Inc. | Dynamic chatbot |
US20090307052A1 (en) | 2008-06-04 | 2009-12-10 | Accenture Global Services Gmbh | Workforce planning system, method and tool |
US9292861B2 (en) | 2008-09-08 | 2016-03-22 | Invoca, Inc. | Methods and systems for routing calls |
US8223951B1 (en) | 2008-09-29 | 2012-07-17 | Envid Technologies, Inc. | System and method for alternate path routing and redundancy based on cost sensitive network selection |
US20100106569A1 (en) | 2008-10-24 | 2010-04-29 | Cardlytics, Inc. | System and Methods for Offer Realization and Redemption in a Targeted Marketing Offer Delivery System |
US20100114646A1 (en) | 2008-10-30 | 2010-05-06 | Alliance Data Systems, Inc. | Method and System for Segmenting Customers for Marketing and Other Projects |
US8315370B2 (en) * | 2008-12-29 | 2012-11-20 | Genesys Telecommunications Laboratories, Inc. | System for scheduling routing rules in a contact center based on forcasted and actual interaction load and staffing requirements |
US11012568B2 (en) | 2009-01-28 | 2021-05-18 | Virtual Hold Technology Solutions, Llc | System and method for providing chat-based customer callbacks |
US8223956B2 (en) | 2009-01-28 | 2012-07-17 | Virtual Hold Technology, Llc | System and method for managing, directing, and queuing communication events |
US8195430B2 (en) | 2009-03-31 | 2012-06-05 | Microsoft Corporation | Cognitive agent |
US9955012B2 (en) | 2009-04-21 | 2018-04-24 | Genesys Telecommunications Laboratories, Inc. | Pacing in knowledge worker engagement |
US9654634B2 (en) | 2009-04-21 | 2017-05-16 | Genesys Telecommunications Laboratories, Inc. | Management of transaction routing to enterprise agents |
US8370155B2 (en) * | 2009-04-23 | 2013-02-05 | International Business Machines Corporation | System and method for real time support for agents in contact center environments |
US20110022461A1 (en) | 2009-04-29 | 2011-01-27 | Simeonov Simeon S | Privacy-safe targeted advertising method and system |
US20100287131A1 (en) | 2009-05-11 | 2010-11-11 | Hartford Fire Insurance Company | System and method for dynamic multi-platform handler assignment |
US8751293B2 (en) | 2009-05-14 | 2014-06-10 | Microsoft Corporation | Delivering contextual advertising to a vehicle |
US20100299268A1 (en) | 2009-05-20 | 2010-11-25 | Oracle International Corporation | Framework for shared procurement services |
US10241752B2 (en) | 2011-09-30 | 2019-03-26 | Apple Inc. | Interface for a virtual digital assistant |
US20100332287A1 (en) | 2009-06-24 | 2010-12-30 | International Business Machines Corporation | System and method for real-time prediction of customer satisfaction |
US20110014932A1 (en) | 2009-07-17 | 2011-01-20 | Texas Instruments Incorporated | Mobile Telephony Combining Voice and Ancillary Information |
US8290804B2 (en) | 2009-08-06 | 2012-10-16 | Verint Americas Inc. | Method and apparatus for automated time banking and workforce scheduling |
US9277021B2 (en) | 2009-08-21 | 2016-03-01 | Avaya Inc. | Sending a user associated telecommunication address |
US20110077994A1 (en) * | 2009-09-30 | 2011-03-31 | International Business Machines Corporation | Optimization of workforce scheduling and capacity planning |
KR20110036385A (en) | 2009-10-01 | 2011-04-07 | 삼성전자주식회사 | Apparatus for analyzing intention of user and method thereof |
US10115065B1 (en) | 2009-10-30 | 2018-10-30 | Verint Americas Inc. | Systems and methods for automatic scheduling of a workforce |
US8499148B2 (en) | 2009-11-02 | 2013-07-30 | Chi Eng | System and method for virtual team collaboration in a secure environment |
US8660258B2 (en) | 2009-11-19 | 2014-02-25 | Genesys Telecommunications Laboratories, Inc. | System and methods for selecting a dialing strategy for placing an outbound call |
US20110125697A1 (en) | 2009-11-20 | 2011-05-26 | Avaya Inc. | Social media contact center dialog system |
US20110143323A1 (en) | 2009-12-14 | 2011-06-16 | Cohen Robert A | Language training method and system |
US10276170B2 (en) | 2010-01-18 | 2019-04-30 | Apple Inc. | Intelligent automated assistant |
US8599836B2 (en) | 2010-01-27 | 2013-12-03 | Neobitspeak LLC | Web-based, hosted, self-service outbound contact center utilizing speaker-independent interactive voice response and including enhanced IP telephony |
US9537924B2 (en) | 2010-01-28 | 2017-01-03 | Genesys Telecommunications Laboratories, Inc. | Interaction management system and methods of use |
US8351594B2 (en) * | 2010-02-08 | 2013-01-08 | Genesys Telecommunications Laboratories, Inc. | System for indicating priority levels for transaction and task engagement in a call center |
US8898219B2 (en) | 2010-02-12 | 2014-11-25 | Avaya Inc. | Context sensitive, cloud-based telephony |
US8594306B2 (en) * | 2010-03-03 | 2013-11-26 | International Business Machines Corporation | Providing information by a contact center |
US20140254790A1 (en) | 2013-03-07 | 2014-09-11 | Avaya Inc. | System and method for selecting agent in a contact center for improved call routing |
US20110264581A1 (en) | 2010-04-23 | 2011-10-27 | Visa U.S.A. Inc. | Systems and Methods to Provide Market Analyses and Alerts |
US8437339B2 (en) | 2010-04-28 | 2013-05-07 | Hewlett-Packard Development Company, L.P. | Techniques to provide integrated voice service management |
US8861710B2 (en) | 2010-05-19 | 2014-10-14 | Avaya Inc. | Playing expected wait time on agent's notification |
US20110288897A1 (en) | 2010-05-24 | 2011-11-24 | Avaya Inc. | Method of agent assisted response to social media interactions |
US8369338B1 (en) | 2010-05-25 | 2013-02-05 | Amazon Technologies, Inc. | Region-associated ratings of wireless carriers |
US8447279B1 (en) | 2010-05-25 | 2013-05-21 | Amazon Technologies, Inc. | Selection of wireless devices and service plans |
WO2012003580A1 (en) | 2010-07-08 | 2012-01-12 | Christopher Bryson | Consumer, retailer and supplier computing systems and methods |
US9679265B1 (en) | 2010-08-10 | 2017-06-13 | WorkFlex Solutions, LLC | Method and apparatus for real time automated intelligent self-scheduling |
US9280754B1 (en) | 2010-08-10 | 2016-03-08 | WorkFlex Solutions, LLC | Method and apparatus for real time automated intelligent self-scheduling |
US20120046996A1 (en) | 2010-08-17 | 2012-02-23 | Vishal Shah | Unified data management platform |
US8626137B1 (en) | 2010-08-20 | 2014-01-07 | WhitePages, Inc. | Providing caller identification to mobile devices |
US8699694B2 (en) | 2010-08-26 | 2014-04-15 | Satmap International Holdings Limited | Precalculated caller-agent pairs for a call center routing system |
US8688557B2 (en) | 2010-09-29 | 2014-04-01 | Fiserv, Inc. | Systems and methods for customer value optimization involving relationship optimization |
US20120084217A1 (en) | 2010-09-30 | 2012-04-05 | Avaya Inc. | System and method for responding to changing conditions in contact centers |
US8396204B2 (en) | 2010-10-09 | 2013-03-12 | Hewlett-Packard Development Company, L.P. | Call center resource allocation |
US20140039962A1 (en) | 2010-10-19 | 2014-02-06 | ClearCare, Inc. | System and Apparatus for Generating Work Schedules |
US20120109830A1 (en) | 2010-10-29 | 2012-05-03 | Matt Vogel | Apparatus, system and method for a decentralized social network system and decentralized payment network system |
US8635226B2 (en) | 2011-03-02 | 2014-01-21 | Adobe Systems Incorporated | Computing user micro-segments for offer matching |
US8869245B2 (en) | 2011-03-09 | 2014-10-21 | Ebay Inc. | Device reputation |
US8786785B2 (en) | 2011-04-05 | 2014-07-22 | Microsoft Corporation | Video signature |
US11068954B2 (en) | 2015-11-20 | 2021-07-20 | Voicemonk Inc | System for virtual agents to help customers and businesses |
US8898290B2 (en) | 2011-05-11 | 2014-11-25 | Google Inc. | Personally identifiable information independent utilization of analytics data |
US20120290373A1 (en) | 2011-05-12 | 2012-11-15 | Ignite Media Solutions, Llc | Apparatus and method for marketing-based dynamic attribution |
US8903080B2 (en) | 2011-06-17 | 2014-12-02 | Avaya Inc. | Goal-based estimated wait time |
US9317825B2 (en) | 2011-06-27 | 2016-04-19 | Deltek, Inc. | System and method for managing projects |
US9351236B2 (en) | 2011-07-19 | 2016-05-24 | At&T Intellectual Property I, L.P. | UICC carrier switching via over-the-air technology |
US20130073361A1 (en) | 2011-09-20 | 2013-03-21 | Jonathan Silver | Methods and systems for offering targeted deals to customers and real-time automatic redemption thereof |
WO2013049683A1 (en) | 2011-09-30 | 2013-04-04 | Bloom Insurance Agency Llc | Meeting monitoring and compliance assurance system |
US20130090963A1 (en) | 2011-10-06 | 2013-04-11 | Verizon Patent And Licensing Inc. | Method and system for optimizing dispatch workflow information |
US20180032997A1 (en) | 2012-10-09 | 2018-02-01 | George A. Gordon | System, method, and computer program product for determining whether to prompt an action by a platform in connection with a mobile device |
US10290017B2 (en) | 2011-11-15 | 2019-05-14 | Tapad, Inc. | Managing associations between device identifiers |
US8713076B2 (en) | 2012-01-20 | 2014-04-29 | Cross Commerce Media, Inc. | Providing a multi-tenant knowledge network |
US9781263B2 (en) | 2012-02-23 | 2017-10-03 | Avaya Inc. | Context-based dynamic adjustment to pacing algorithm |
US9100480B2 (en) * | 2012-02-29 | 2015-08-04 | Avaya Inc. | Adjustment of contact routing decisions to reward agent behavior |
US20130236002A1 (en) | 2012-03-08 | 2013-09-12 | Avaya Inc. | Using factor analysis to improve work assignment performance |
US10702773B2 (en) | 2012-03-30 | 2020-07-07 | Videx, Inc. | Systems and methods for providing an interactive avatar |
US8488769B1 (en) | 2012-04-24 | 2013-07-16 | Noble Systems Corporation | Non-scheduled training for an agent in a call center |
US8914452B2 (en) | 2012-05-31 | 2014-12-16 | International Business Machines Corporation | Automatically generating a personalized digest of meetings |
US9595049B2 (en) | 2012-06-11 | 2017-03-14 | Retailmenot, Inc. | Cross-device geolocation sensing to geotarget offers |
US20140012603A1 (en) | 2012-07-09 | 2014-01-09 | James Scanlon | Capacity planning and modeling for optimization of task outcomes |
US8792624B2 (en) | 2012-07-16 | 2014-07-29 | Avaya Inc. | Local preservation of an agent message |
US8391466B1 (en) | 2012-07-24 | 2013-03-05 | Noble Systems Corporation | Generating communication forecasts and schedules based on multiple outbound campaigns |
US20140039944A1 (en) | 2012-08-02 | 2014-02-06 | Amadeus S.A.S. | Method and system providing inventory optimization for disrupted customers |
US10346542B2 (en) | 2012-08-31 | 2019-07-09 | Verint Americas Inc. | Human-to-human conversation analysis |
US20140079207A1 (en) | 2012-09-12 | 2014-03-20 | Genesys Telecommunications Laboratories, Inc. | System and method for providing dynamic elasticity of contact center resources |
US9105268B2 (en) | 2012-09-19 | 2015-08-11 | 24/7 Customer, Inc. | Method and apparatus for predicting intent in IVR using natural language queries |
US8535059B1 (en) * | 2012-09-21 | 2013-09-17 | Noble Systems Corporation | Learning management system for call center agents |
US20150262208A1 (en) | 2012-10-04 | 2015-09-17 | Bernt Erik Bjontegard | Contextually intelligent communication systems and processes |
US9501764B2 (en) | 2012-10-05 | 2016-11-22 | Oracle International Corporation | Method and system for communicating within a messaging architecture using a structured data object |
US9648492B2 (en) | 2012-10-10 | 2017-05-09 | Apple Inc. | Location-based update of subscriber identity information in a wireless device |
US8935172B1 (en) * | 2012-10-31 | 2015-01-13 | Noble Systems Coporation | Fulfilling staffing requirements via an interactive voice response system |
US8526576B1 (en) | 2012-11-02 | 2013-09-03 | Connexon Telecom, Inc. | Systems and methods for exchanging call routing policies for voice over IP calls |
US20140136346A1 (en) | 2012-11-13 | 2014-05-15 | Chirpify, Inc. | System and methods for processing in-stream transactions on micro-blogs and other social networks |
US9659087B2 (en) | 2012-11-19 | 2017-05-23 | Amplero, Inc. | Unsupervised prioritization and visualization of clusters |
US9912812B2 (en) | 2012-11-21 | 2018-03-06 | Genesys Telecommunications Laboratories, Inc. | Graphical user interface for configuring contact center routing strategies |
US9628623B2 (en) | 2012-11-21 | 2017-04-18 | Genesys Telecommunications Laboratories, Inc. | Graphical user interface for monitoring and visualizing contact center routing strategies |
US9674356B2 (en) | 2012-11-21 | 2017-06-06 | Genesys Telecommunications Laboratories, Inc. | Dynamic recommendation of routing rules for contact center use |
US20140143018A1 (en) | 2012-11-21 | 2014-05-22 | Verint Americas Inc. | Predictive Modeling from Customer Interaction Analysis |
US9912816B2 (en) | 2012-11-29 | 2018-03-06 | Genesys Telecommunications Laboratories, Inc. | Workload distribution with resource awareness |
US9497289B2 (en) | 2012-12-07 | 2016-11-15 | Genesys Telecommunications Laboratories, Inc. | System and method for social message classification based on influence |
US8798256B2 (en) | 2012-12-12 | 2014-08-05 | Hartford Fire Insurance Company | System and method for telephone call routing using a relational routing matrix |
US9088656B2 (en) | 2012-12-12 | 2015-07-21 | Genesys Telecommunications Laboratories, Inc. | System and method for access number distribution in a contact center |
US9117450B2 (en) | 2012-12-12 | 2015-08-25 | Nuance Communications, Inc. | Combining re-speaking, partial agent transcription and ASR for improved accuracy / human guided ASR |
CN103020047A (en) | 2012-12-31 | 2013-04-03 | 威盛电子股份有限公司 | Method for revising voice response and natural language dialogue system |
US10395271B2 (en) | 2013-01-15 | 2019-08-27 | Datorama Technologies, Ltd. | System and method for normalizing campaign data gathered from a plurality of advertising platforms |
US8671020B1 (en) | 2013-01-31 | 2014-03-11 | Marchex, Inc. | Call tracking system utilizing a pooling algorithm |
US20140219438A1 (en) | 2013-02-04 | 2014-08-07 | RingDNA, Inc. | Systems and methods involving real-time communications platforms and/or processing |
US20140219132A1 (en) | 2013-02-04 | 2014-08-07 | William J. Delveaux | Systems and methods for voice and data communications including a scalable tdm switch/multiplexer |
US9172747B2 (en) | 2013-02-25 | 2015-10-27 | Artificial Solutions Iberia SL | System and methods for virtual assistant networks |
US20140257908A1 (en) | 2013-03-07 | 2014-09-11 | Avaya Inc. | Viewer pattern analysis |
US9060057B1 (en) | 2013-03-07 | 2015-06-16 | Serdar Artun Danis | Systems and methods for caller ID authentication, spoof detection and list based call handling |
US20140278649A1 (en) | 2013-03-14 | 2014-09-18 | Oracle International Corporation | Modeling a gap between workload and number of employees to be scheduled by creating and using new workload levels |
US9349373B1 (en) | 2013-03-14 | 2016-05-24 | Verint Americas Inc. | Biometrics platform provider |
US20170006161A9 (en) | 2013-03-15 | 2017-01-05 | Genesys Telecommunications Laboratories, Inc. | Intelligent automated agent for a contact center |
US8644489B1 (en) * | 2013-03-15 | 2014-02-04 | Noble Systems Corporation | Forced schedule adherence for contact center agents |
US10726461B2 (en) | 2013-03-15 | 2020-07-28 | Ncr Corporation | System and method of completing an activity via an agent |
US10475075B2 (en) | 2013-03-15 | 2019-11-12 | Marchex, Inc. | Correlated consumer telephone numbers and user identifiers for advertising retargeting |
US9386152B2 (en) | 2013-03-15 | 2016-07-05 | Genesys Telecommunications Laboratories, Inc. | Intelligent automated agent and interactive voice response for a contact center |
US9247061B2 (en) | 2013-03-15 | 2016-01-26 | Avaya Inc. | Answer based agent routing and display method |
US20150287410A1 (en) | 2013-03-15 | 2015-10-08 | Google Inc. | Speech and semantic parsing for content selection |
US9154626B2 (en) | 2013-03-15 | 2015-10-06 | Avaya Inc. | Secret transfers in contact centers |
US20140279045A1 (en) | 2013-03-15 | 2014-09-18 | Turn Inc. | Cross-domain id synchronization in online advertisement |
US10771247B2 (en) | 2013-03-15 | 2020-09-08 | Commerce Signals, Inc. | Key pair platform and system to manage federated trust networks in distributed advertising |
US10154143B2 (en) | 2013-03-15 | 2018-12-11 | Genesys Telecommunications Laboratories, Inc. | System and method for dynamically selecting a dial plan |
US9100483B1 (en) * | 2013-03-15 | 2015-08-04 | Noble Systems Corporation | Properly ascertaining shift-related work deficiencies of contact center agents |
US10783568B1 (en) | 2013-03-15 | 2020-09-22 | Poshmark, Inc. | Social merchandising system |
US9380160B2 (en) | 2013-05-07 | 2016-06-28 | Yellowpages.Com Llc | Systems and methods to customize interactive voice response (IVR) prompts based on information about a caller |
US9786197B2 (en) | 2013-05-09 | 2017-10-10 | Rockwell Automation Technologies, Inc. | Using cloud-based data to facilitate enhancing performance in connection with an industrial automation system |
US10080112B2 (en) | 2013-05-13 | 2018-09-18 | Hiya, Inc. | Unwanted caller and message sender identification for restricted communication devices |
US9154627B2 (en) | 2013-05-13 | 2015-10-06 | Genesys Telecommunication Laboratories, Inc. | Activities assignment optimization for multi-skill contact center |
US8861691B1 (en) | 2013-05-24 | 2014-10-14 | Wipro Limited | Methods for managing telecommunication service and devices thereof |
WO2014210002A2 (en) | 2013-06-24 | 2014-12-31 | Psychability Inc. | Systems and methods to utilize subscriber history for predictive analytics and targeting marketing |
US9082094B1 (en) * | 2013-06-26 | 2015-07-14 | Noble Systems Corporation | Equitable shift rotation and efficient assignment mechanisms for contact center agents |
US20150012278A1 (en) | 2013-07-04 | 2015-01-08 | Michael D. Metcalf | System and method for transferring data to a customer relationship management platform |
US9420098B2 (en) | 2013-07-08 | 2016-08-16 | Nice-Systems Ltd | Prediction interactive vocla response |
US9247064B2 (en) | 2013-07-12 | 2016-01-26 | Verizon Patent And Licensing Inc. | Tiered call routing |
US9008286B2 (en) | 2013-07-22 | 2015-04-14 | Verizon Patent And Licensing Inc. | Dynamically generated graphical user interface for interactive voice response |
US9008285B2 (en) | 2013-07-24 | 2015-04-14 | Hartford Fire Insurance Company | System and method for interactive voice response unit table-based programming |
US9602665B1 (en) | 2013-07-24 | 2017-03-21 | Noble Systems Corporation | Functions and associated communication capabilities for a speech analytics component to support agent compliance in a call center |
US9420100B2 (en) | 2013-07-26 | 2016-08-16 | Accenture Global Services Limited | Next best action method and system |
US9654638B2 (en) | 2013-07-29 | 2017-05-16 | Avaya Inc. | Method and system for determining customer's skill, knowledge level, and/or interest |
US9026431B1 (en) | 2013-07-30 | 2015-05-05 | Google Inc. | Semantic parsing with multiple parsers |
US20150051957A1 (en) | 2013-08-15 | 2015-02-19 | Oracle International Corporation | Measuring customer experience value |
US20150066632A1 (en) | 2013-08-29 | 2015-03-05 | VennScore LLC | Systems, methods, and media for improving targeted advertising |
US20150066633A1 (en) | 2013-08-30 | 2015-03-05 | Google Inc. | Dynamic telephone number assignment |
US9426289B2 (en) | 2013-09-12 | 2016-08-23 | Avaya Inc. | Techniques for topical customer service menu reconfiguration based on social media |
US20150100473A1 (en) | 2013-10-09 | 2015-04-09 | Anantha Srinivasan Manoharan | Credit through unstructured supplementary service data |
US9754275B2 (en) | 2013-11-04 | 2017-09-05 | Mastercard International Incorporated | System and method for card-linked services |
US9542440B2 (en) | 2013-11-04 | 2017-01-10 | Microsoft Technology Licensing, Llc | Enterprise graph search based on object and actor relationships |
US10445670B2 (en) | 2013-11-07 | 2019-10-15 | Oracle International Corporation | Team-based approach to skills-based agent assignment |
US20160034995A1 (en) | 2013-11-19 | 2016-02-04 | Service Labs, Inc. | Method and system for automated indentification and engagement of service providers |
US9189742B2 (en) | 2013-11-20 | 2015-11-17 | Justin London | Adaptive virtual intelligent agent |
US9571645B2 (en) | 2013-12-16 | 2017-02-14 | Nuance Communications, Inc. | Systems and methods for providing a virtual assistant |
WO2015100362A1 (en) | 2013-12-23 | 2015-07-02 | 24/7 Customer, Inc. | Systems and methods for facilitating dialogue mining |
JP5986065B2 (en) | 2013-12-26 | 2016-09-06 | 株式会社富士通エフサス | Terminal device and recording program |
WO2015099587A1 (en) | 2013-12-29 | 2015-07-02 | Telefonaktiebolaget L M Ericsson (Publ) | Enabling provision of a service to a mobile terminal in a wireless communications network |
WO2015105994A1 (en) | 2014-01-08 | 2015-07-16 | Callminer, Inc. | Real-time conversational analytics facility |
US10614468B2 (en) | 2014-01-24 | 2020-04-07 | Oracle International Corporation | Event-based score processing |
US10270914B2 (en) | 2014-01-30 | 2019-04-23 | Avaya Inc. | Enhancing contact center calculations based on real-time speech analytics |
CA2940232A1 (en) | 2014-02-21 | 2015-08-27 | Rna Labs Inc. | Systems and methods for automatically collecting user data and making a real-world action for a user |
US10839432B1 (en) | 2014-03-07 | 2020-11-17 | Genesys Telecommunications Laboratories, Inc. | Systems and methods for automating customer interactions with enterprises |
US20190037077A1 (en) | 2014-03-07 | 2019-01-31 | Genesys Telecommunications Laboratories, Inc. | System and Method for Customer Experience Automation |
US20150256677A1 (en) | 2014-03-07 | 2015-09-10 | Genesys Telecommunications Laboratories, Inc. | Conversation assistant |
CN106105100B (en) | 2014-03-18 | 2019-09-06 | Twc专利信托公司 | The method and apparatus for handling Application Programming Interface request |
US20170214795A1 (en) | 2016-01-27 | 2017-07-27 | Joseph Charlson | System, Method, and Apparatus for Determining a Status of a Call Recipient in a Call System |
US9621726B2 (en) | 2014-03-25 | 2017-04-11 | Intellisist, Inc. | Computer-implemented system and method for detecting events for use in an automated call center environment |
US9392117B2 (en) | 2014-03-28 | 2016-07-12 | Intellisist, Inc. | Computer-implemented call center architecture and method for optimizing customer experience through in-band expert intervention |
US9699311B2 (en) | 2014-03-28 | 2017-07-04 | Dialogtech Inc. | Systems, method, and computer program product for cross-channel customer relationship management support with dynamically inserted voice call numbers |
US9185219B2 (en) | 2014-03-31 | 2015-11-10 | Angel.Com Incorporated | Recording user communications |
US10084668B2 (en) | 2014-04-09 | 2018-09-25 | Verizon Patent And Licensing Inc. | Method and system for on demand elastic management of devices and services |
US9514463B2 (en) | 2014-04-11 | 2016-12-06 | Bank Of America Corporation | Determination of customer presence based on communication of a mobile communication device digital signature |
KR101561245B1 (en) | 2014-04-11 | 2015-10-19 | 네이버 주식회사 | System and method for providing information of outgoing call |
US9213941B2 (en) | 2014-04-22 | 2015-12-15 | Google Inc. | Automatic actions based on contextual replies |
US9319524B1 (en) | 2014-04-28 | 2016-04-19 | West Corporation | Applying user preferences, behavioral patterns and/or environmental factors to an automated customer support application |
US9185222B1 (en) | 2014-04-30 | 2015-11-10 | Avaya Inc. | Identifying escalation events in communication sessions |
US20150339446A1 (en) | 2014-05-21 | 2015-11-26 | AON Global Operations Limited (Singapore Branch) (Reg. T12FC0122F) | Dashboard interface, system and environment |
US20150339769A1 (en) | 2014-05-22 | 2015-11-26 | C1 Bank | System and method for enforcing data integrity and loan approval automation by means of data aggregation and analysis |
US20150339620A1 (en) | 2014-05-23 | 2015-11-26 | Dst Technologies, Inc. | Scheduling Method and System |
US10586175B2 (en) | 2014-05-23 | 2020-03-10 | NewVoiceMedia Ltd. | System and method for an optimized, self-learning and self-organizing contact center |
US9864952B2 (en) | 2014-05-27 | 2018-01-09 | Genesys Telecommunications Laboratories, Inc. | Controlled question and answer knowledge system management confirming customer does not want to terminate/cancel service/relationship |
US20150350436A1 (en) | 2014-05-27 | 2015-12-03 | Genesys Telecommunications Laboratories, Inc. | System and method for executing interaction flow for contact centers |
US9930179B2 (en) * | 2014-05-29 | 2018-03-27 | Avaya Inc. | Mechanism for work assignment in a graph-based contact center |
US10063701B2 (en) | 2014-05-29 | 2018-08-28 | Genesys Telecommunications Laboratories, Inc. | Custom grammars builder platform |
US10382628B2 (en) | 2014-06-03 | 2019-08-13 | Avaya Inc. | System and method for routing work requests to a resource group of an enterprise |
US9740746B2 (en) | 2014-07-23 | 2017-08-22 | International Business Machines Corporation | Question answer system using physical distance data |
US10101974B2 (en) | 2014-07-31 | 2018-10-16 | Angel.Com Incorporated | Contact center application creating using reusable program modules |
US9781270B2 (en) | 2014-08-01 | 2017-10-03 | Genesys Telecommunications Laboratories, Inc. | System and method for case-based routing for a contact |
US9848084B2 (en) * | 2014-08-01 | 2017-12-19 | Genesys Telecommunications Laboratories, Inc. | Adaptable business objective routing for a contact center |
US20160042419A1 (en) | 2014-08-06 | 2016-02-11 | 24/7 Customer, Inc. | Method and apparatus for providing customized interaction experience to customers |
JP6122816B2 (en) | 2014-08-07 | 2017-04-26 | シャープ株式会社 | Audio output device, network system, audio output method, and audio output program |
US9178999B1 (en) | 2014-08-11 | 2015-11-03 | Verizon Patent And Licensing Inc. | Contact center monitoring |
US20160057284A1 (en) | 2014-08-21 | 2016-02-25 | Verizon Patent And Licensing Inc. | Method and system for determining telephony system response |
CA2901454C (en) | 2014-08-25 | 2023-01-17 | Accenture Global Services Limited | System architecture for customer genome construction and analysis |
US9398155B2 (en) | 2014-09-03 | 2016-07-19 | Verizon Patent And Licensing Inc. | Enterprise-wide split function IVR callback system |
US10084911B2 (en) | 2014-09-11 | 2018-09-25 | At&T Intellectual Property I, L.P. | Active records for interactive systems |
US10841425B1 (en) | 2014-09-16 | 2020-11-17 | United Services Automobile Association | Systems and methods for electronically predicting future customer interactions |
US9906648B2 (en) | 2014-09-23 | 2018-02-27 | Interactive Intelligence Group, Inc. | Method and system for prediction of contact allocation, staff time distribution, and service performance metrics in a multi-skilled contact center operation environment |
US20160105329A1 (en) | 2014-10-09 | 2016-04-14 | Splunk Inc. | Defining a service-monitoring dashboard using key performance indicators derived from machine data |
US9065915B1 (en) | 2014-10-10 | 2015-06-23 | Noble Syetems Corporation | Sending callback text messages from a contact center |
US9877191B2 (en) | 2014-10-15 | 2018-01-23 | Tracfone Wireless, Inc. | Device having a SIM card combined with a wireless service card and method of use thereof |
US20160124937A1 (en) | 2014-11-03 | 2016-05-05 | Service Paradigm Pty Ltd | Natural language execution system, method and computer readable medium |
US20160125456A1 (en) | 2014-11-03 | 2016-05-05 | Ds-Iq, Inc. | Advertising campaign targeting using contextual data |
SG11201703521UA (en) | 2014-11-03 | 2017-05-30 | Genentech Inc | Methods and biomarkers for predicting efficacy and evaluation of an ox40 agonist treatment |
US10063998B2 (en) | 2014-11-07 | 2018-08-28 | Tevnos LLC | Mobile authentication in mobile virtual network |
US20160140627A1 (en) | 2014-11-14 | 2016-05-19 | Adobe Systems Incorporated | Generating high quality leads for marketing campaigns |
US9152737B1 (en) | 2014-11-26 | 2015-10-06 | Sense Labs, Inc. | Providing notifications to a user |
US9378475B2 (en) | 2014-11-28 | 2016-06-28 | Xerox Corporation | Apparatus and method for call center service level prediction and action |
US20160173691A1 (en) | 2014-12-10 | 2016-06-16 | Interactive Intelligence Group, Inc. | Method and system for generating staffing requirements for deferred work in a contact center environment |
US20160171422A1 (en) * | 2014-12-10 | 2016-06-16 | Interactive Intelligence Group, Inc. | Method and System for Generating Staffing Requirements for Deferred Work in a Contact Center Environment |
US9160853B1 (en) | 2014-12-17 | 2015-10-13 | Noble Systems Corporation | Dynamic display of real time speech analytics agent alert indications in a contact center |
US10380246B2 (en) | 2014-12-18 | 2019-08-13 | International Business Machines Corporation | Validating topical data of unstructured text in electronic forms to control a graphical user interface based on the unstructured text relating to a question included in the electronic form |
US20160180381A1 (en) | 2014-12-19 | 2016-06-23 | Genesys Telecommunications Laboratories, Inc. | System and method for impression purchase based on skilled agent |
US10445152B1 (en) | 2014-12-19 | 2019-10-15 | Experian Information Solutions, Inc. | Systems and methods for dynamic report generation based on automatic modeling of complex data structures |
US10171656B2 (en) | 2014-12-29 | 2019-01-01 | Verizon Patent And Licensing Inc. | Systems and methods for providing real-time assistance to call center agents |
US9992341B2 (en) | 2014-12-31 | 2018-06-05 | Genesys Telecommunications Laboratories, Inc. | System and method for managing customer interactions for contact center based on agent proximity |
US9571636B2 (en) | 2014-12-31 | 2017-02-14 | Genesys Telecommunications Laboratories, Inc. | Call center builder platform |
US10291776B2 (en) | 2015-01-06 | 2019-05-14 | Cyara Solutions Pty Ltd | Interactive voice response system crawler |
US9300801B1 (en) | 2015-01-30 | 2016-03-29 | Mattersight Corporation | Personality analysis of mono-recording system and methods |
US10373171B2 (en) | 2015-02-23 | 2019-08-06 | Genesys Telecommunications Laboratories, Inc. | System and method for making engagement offers based on observed navigation path |
WO2016138067A1 (en) | 2015-02-24 | 2016-09-01 | Cloudlock, Inc. | System and method for securing an enterprise computing environment |
US10194027B1 (en) | 2015-02-26 | 2019-01-29 | Noble Systems Corporation | Reviewing call checkpoints in agent call recording in a contact center |
US9123009B1 (en) * | 2015-02-26 | 2015-09-01 | Noble Systems Corporation | Equitable shift rotation and efficient assignment mechanisms for contact center agents |
US9420106B1 (en) | 2015-03-05 | 2016-08-16 | Xerox Corporation | Methods and systems for assigning priority to incoming message from customer |
US10425534B2 (en) | 2015-03-30 | 2019-09-24 | Avaya, Inc. | System and method for optimizing agent time |
US20160300573A1 (en) | 2015-04-08 | 2016-10-13 | Google Inc. | Mapping input to form fields |
US9397985B1 (en) | 2015-04-14 | 2016-07-19 | Manifold Technology, Inc. | System and method for providing a cryptographic platform for exchanging information |
US20160335576A1 (en) | 2015-05-12 | 2016-11-17 | Uber Technologies, Inc. | Location-based prediction of transport services |
WO2016189350A1 (en) | 2015-05-23 | 2016-12-01 | Yogesh Chunilal Rathod | Calling to user(s) for real-time sharing, participation, e-commerce, workflow, communication & collaboration in the event of acceptance of call by caller user(s) |
US10097973B2 (en) | 2015-05-27 | 2018-10-09 | Apple Inc. | Systems and methods for proactively identifying and surfacing relevant content on a touch-sensitive device |
US10222933B2 (en) | 2015-05-30 | 2019-03-05 | Genesys Telecommunications Laboratories, Inc. | System and method for managing multiple interactions |
US10970682B1 (en) | 2015-06-04 | 2021-04-06 | Incontact, Inc. | System and method for agent scheduling using mixed integer linear programming |
US9667779B2 (en) | 2015-06-05 | 2017-05-30 | At&T Intellectual Property I, L.P. | Routing service |
CA3128629A1 (en) | 2015-06-05 | 2016-07-28 | C3.Ai, Inc. | Systems and methods for data processing and enterprise ai applications |
US9787840B1 (en) | 2015-06-11 | 2017-10-10 | Noble Systems Corporation | Forecasting and scheduling campaigns involving different channels of communication |
US9823949B2 (en) * | 2015-06-29 | 2017-11-21 | Genesys Telecommunications Laboratories, Inc. | System and method for intelligent task management and routing |
US9674361B2 (en) * | 2015-06-29 | 2017-06-06 | Genesys Telecommunications Laboratories, Inc. | System and method for intelligent task management in a workbin |
US20170004178A1 (en) | 2015-06-30 | 2017-01-05 | Avaya Inc. | Reference validity checker |
US20170024762A1 (en) | 2015-07-20 | 2017-01-26 | Sambasivan Swaminathan | System and methods for monetizing digital assets |
CN108352025B (en) | 2015-07-24 | 2022-10-11 | 安普视频有限公司 | Television advertisement slot targeting based on consumer online behavior |
US10140642B2 (en) | 2015-07-27 | 2018-11-27 | Data Capable, Inc. | Automated customer engagement and issue location, prediction, and response through utilization of public and private data sources |
US9473637B1 (en) | 2015-07-28 | 2016-10-18 | Xerox Corporation | Learning generation templates from dialog transcripts |
US10154071B2 (en) | 2015-07-29 | 2018-12-11 | International Business Machines Corporation | Group chat with dynamic background images and content from social media |
US20170068436A1 (en) | 2015-09-03 | 2017-03-09 | Microsoft Technology Licensing, Llc | Interpreting and Supplementing Captured Stroke Information |
US10210383B2 (en) | 2015-09-03 | 2019-02-19 | Microsoft Technology Licensing, Llc | Interacting with an assistant component based on captured stroke information |
US10277696B2 (en) | 2016-09-10 | 2019-04-30 | Intelligence Machine Inc. | Method and system for processing data used by creative users to create media content |
US9955021B1 (en) | 2015-09-18 | 2018-04-24 | 8X8, Inc. | Analysis of call metrics for call direction |
US10116796B2 (en) | 2015-10-09 | 2018-10-30 | Ooma, Inc. | Real-time communications-based internet advertising |
US9426291B1 (en) | 2015-10-16 | 2016-08-23 | Noble Systems Corporation | Forecasting and scheduling campaigns involving sending outbound communications that generate inbound communications |
US9716792B2 (en) | 2015-10-19 | 2017-07-25 | Genesys Telecommunications Laboratories, Inc. | System and method for generating a network of contact center agents and customers for optimized routing of interactions |
US9635181B1 (en) | 2015-10-19 | 2017-04-25 | Genesys Telecommunications Laboratories, Inc. | Optimized routing of interactions to contact center agents based on machine learning |
US10455088B2 (en) | 2015-10-21 | 2019-10-22 | Genesys Telecommunications Laboratories, Inc. | Dialogue flow optimization and personalization |
US10382623B2 (en) | 2015-10-21 | 2019-08-13 | Genesys Telecommunications Laboratories, Inc. | Data-driven dialogue enabled self-help systems |
US20170132536A1 (en) | 2015-11-10 | 2017-05-11 | Hipmunk, Inc. | System-initiated actions on behalf of user |
US10861031B2 (en) | 2015-11-25 | 2020-12-08 | The Nielsen Company (Us), Llc | Methods and apparatus to facilitate dynamic classification for market research |
US10431215B2 (en) | 2015-12-06 | 2019-10-01 | Voicebox Technologies Corporation | System and method of conversational adjustment based on user's cognitive state and/or situational state |
US20180061256A1 (en) | 2016-01-25 | 2018-03-01 | Wespeke, Inc. | Automated digital media content extraction for digital lesson generation |
TWI579758B (en) | 2016-01-29 | 2017-04-21 | 物聯智慧科技(深圳)有限公司 | User Electronic Device, User Interface And Computer Program Product |
US11049059B2 (en) | 2016-02-03 | 2021-06-29 | Operr Technologies, Inc | Method and system for on-demand customized services |
US9858927B2 (en) | 2016-02-12 | 2018-01-02 | Amazon Technologies, Inc | Processing spoken commands to control distributed audio outputs |
US9774731B1 (en) | 2016-03-28 | 2017-09-26 | Verizon Patent And Licensing Inc. | Adding additional information to caller ID information |
US20170288866A1 (en) | 2016-03-30 | 2017-10-05 | AVAST Software s.r.o. | Systems and methods of creating a distributed ring of trust |
US11144761B2 (en) | 2016-04-04 | 2021-10-12 | Xerox Corporation | Deep data association for online multi-class multi-object tracking |
US20170337578A1 (en) | 2016-04-19 | 2017-11-23 | Anto Chittilappilly | Dynamic media buy optimization using attribution-informed media buy execution feeds |
US11263532B2 (en) | 2016-04-22 | 2022-03-01 | Spotify Ab | System and method for breaking artist prediction in a media content environment |
US20170316386A1 (en) | 2016-04-29 | 2017-11-02 | Microsoft Technology Licensing, Llc | Contextually-aware scheduling exceptions |
US20170323344A1 (en) | 2016-05-03 | 2017-11-09 | International Business Machines Corporation | Customer segmentation using customer voice samples |
US20170344988A1 (en) | 2016-05-24 | 2017-11-30 | Ubs Ag | System and method for facilitating blockchain-based validation |
US10346635B2 (en) * | 2016-05-31 | 2019-07-09 | Genesys Telecommunications Laboratories, Inc. | System and method for data management and task routing based on data tagging |
US10673954B2 (en) | 2016-06-08 | 2020-06-02 | Genesys Telecommunications Laboratories, Inc. | Digital service interface |
US20170372436A1 (en) | 2016-06-24 | 2017-12-28 | Linkedln Corporation | Matching requests-for-proposals with service providers |
US10635973B1 (en) | 2016-06-28 | 2020-04-28 | Amazon Technologies, Inc. | Recommendation system using improved neural network |
US20180018705A1 (en) | 2016-07-18 | 2018-01-18 | Catalyst Trade C/O Jeffrey Tognetti | Data management platform and method of bridging offline and online retargeted advertising with a telecom platform |
US10154138B2 (en) | 2016-07-29 | 2018-12-11 | Genesys Telecommunications Laboratories, Inc. | System and method for optimizing physical placement of contact center agents on a contact center floor |
US20180054464A1 (en) | 2016-08-16 | 2018-02-22 | Rulai, Inc. | Method and system for collaborative intelligent virtual agents |
US20180052664A1 (en) | 2016-08-16 | 2018-02-22 | Rulai, Inc. | Method and system for developing, training, and deploying effective intelligent virtual agent |
US10861320B2 (en) | 2016-08-22 | 2020-12-08 | Rapidsos, Inc. | Predictive analytics for emergency detection and response management |
US10990931B2 (en) | 2016-09-01 | 2021-04-27 | Nice Ltd. | System and method for work period scheduler |
US10554590B2 (en) | 2016-09-09 | 2020-02-04 | Microsoft Technology Licensing, Llc | Personalized automated agent |
US20180121766A1 (en) * | 2016-09-18 | 2018-05-03 | Newvoicemedia, Ltd. | Enhanced human/machine workforce management using reinforcement learning |
CN109952572B (en) | 2016-09-20 | 2023-11-24 | 谷歌有限责任公司 | Suggested response based on message decal |
US10165081B2 (en) | 2016-09-30 | 2018-12-25 | The Toronto-Dominion Bank | System and method for processing an interaction response |
US10387899B2 (en) | 2016-10-26 | 2019-08-20 | New Relic, Inc. | Systems and methods for monitoring and analyzing computer and network activity |
EP3321873A1 (en) | 2016-11-15 | 2018-05-16 | Amadeus S.A.S. | Contextual service systems and methods |
KR102501714B1 (en) | 2016-11-16 | 2023-02-21 | 삼성전자주식회사 | Device and method for providing response message to user’s voice input |
US10984391B2 (en) | 2016-11-17 | 2021-04-20 | International Business Machines Corporation | Intelligent meeting manager |
US10057419B2 (en) | 2016-11-29 | 2018-08-21 | International Business Machines Corporation | Intelligent call screening |
US11373100B2 (en) | 2016-11-29 | 2022-06-28 | Microsoft Technology Licensing, Llc | Using various artificial intelligence entities as advertising media |
US10520477B2 (en) | 2016-12-09 | 2019-12-31 | Idex Health & Science Llc | High pressure valve with multi-piece stator assembly |
US10026092B2 (en) | 2016-12-09 | 2018-07-17 | Nuance Communications, Inc. | Learning and automating agent actions |
US20180165723A1 (en) | 2016-12-12 | 2018-06-14 | Chatalytic, Inc. | Measuring and optimizing natural language interactions |
US9998596B1 (en) | 2016-12-12 | 2018-06-12 | At&T Intellectual Property I, L.P. | Call volume reduction based upon a propensity to call in connection with a reason code |
US10691407B2 (en) | 2016-12-14 | 2020-06-23 | Kyruus, Inc. | Methods and systems for analyzing speech during a call and automatically modifying, during the call, a call center referral interface |
WO2018112280A1 (en) | 2016-12-14 | 2018-06-21 | Interactive Intelligence Group, Inc. | System and method for social behavior mapping |
US10135973B2 (en) | 2016-12-20 | 2018-11-20 | Hiya, Inc. | Using CNAM injection to deliver caller information |
WO2018118190A1 (en) | 2016-12-20 | 2018-06-28 | Walmart Apollo, Llc | Vector-based optimization of media presentations |
US10009465B1 (en) | 2016-12-22 | 2018-06-26 | Capital One Services, Llc | Systems and methods for customer sentiment prediction and depiction |
US20180189273A1 (en) | 2016-12-23 | 2018-07-05 | OneMarket Network LLC | Maintaining context in transaction conversations |
US9930181B1 (en) | 2016-12-30 | 2018-03-27 | Avaya Inc. | Systems and methods for optimal scheduling of resources in a contact center |
US10235990B2 (en) | 2017-01-04 | 2019-03-19 | International Business Machines Corporation | System and method for cognitive intervention on human interactions |
US10878479B2 (en) | 2017-01-05 | 2020-12-29 | Microsoft Technology Licensing, Llc | Recommendation through conversational AI |
US10445742B2 (en) | 2017-01-31 | 2019-10-15 | Walmart Apollo, Llc | Performing customer segmentation and item categorization |
US10440180B1 (en) | 2017-02-27 | 2019-10-08 | United Services Automobile Association (Usaa) | Learning based metric determination for service sessions |
US10594633B2 (en) | 2017-02-28 | 2020-03-17 | Ncr Corporation | Auto-initiated messaging chat |
US11308523B2 (en) | 2017-03-13 | 2022-04-19 | Adobe Inc. | Validating a target audience using a combination of classification algorithms |
US10277745B1 (en) | 2017-05-30 | 2019-04-30 | Noble Systems Corporation | Answering machine detection for a contact center |
US10079939B1 (en) | 2017-03-20 | 2018-09-18 | International Business Machines Corporation | Performing contextual analysis of incoming telephone calls and suggesting forwarding parties |
US10692157B2 (en) | 2017-03-28 | 2020-06-23 | International Business Machines Corporation | Selection of information sources based on social activities |
US20180286000A1 (en) | 2017-03-31 | 2018-10-04 | At&T Intellectual Property I, L.P. | Identity Management for Offline User Data |
US9813495B1 (en) | 2017-03-31 | 2017-11-07 | Ringcentral, Inc. | Systems and methods for chat message notification |
US11061918B2 (en) | 2017-04-05 | 2021-07-13 | Splunk Inc. | Locating and categorizing data using inverted indexes |
US20180293532A1 (en) | 2017-04-07 | 2018-10-11 | Microsoft Technology Licensing, Llc | Calendar control based on free/busy change detection |
US11276012B2 (en) | 2017-04-12 | 2022-03-15 | International Business Machines Corporation | Route prediction based on adaptive hybrid model |
GB201706047D0 (en) | 2017-04-14 | 2017-05-31 | Digital Genius Ltd | Automated tagging of text |
US12026685B2 (en) | 2017-04-21 | 2024-07-02 | Blockdaemon Inc. | Method and apparatus for blockchain management |
US10044862B1 (en) | 2017-04-28 | 2018-08-07 | International Business Machines Corporation | Dynamic topic guidance in the context of multi-round conversation |
US10452251B2 (en) | 2017-05-23 | 2019-10-22 | Servicenow, Inc. | Transactional conversation-based computing system |
US10038788B1 (en) | 2017-05-09 | 2018-07-31 | Oracle International Corporation | Self-learning adaptive routing system |
US20180361253A1 (en) | 2017-05-22 | 2018-12-20 | Scientific Revenue, Inc. | Method of automating segmentation of users of game or online service with limited a priori knowledge |
US10331402B1 (en) | 2017-05-30 | 2019-06-25 | Amazon Technologies, Inc. | Search and knowledge base question answering for a voice user interface |
US10460292B2 (en) | 2017-05-31 | 2019-10-29 | International Business Machines Corporation | Preventing activity delays using smart device analysis |
US9883037B1 (en) | 2017-06-08 | 2018-01-30 | Aspect Software, Inc. | Systems and methods in an electronic contact management system to estimate required staff levels for multi-skilled agents |
US10909505B2 (en) | 2017-06-15 | 2021-02-02 | Rovi Guides, Inc. | Systems and methods for delaying the start time of an event based on event attendee arrival times |
US10460728B2 (en) | 2017-06-16 | 2019-10-29 | Amazon Technologies, Inc. | Exporting dialog-driven applications to digital communication platforms |
US10986232B2 (en) | 2017-06-16 | 2021-04-20 | Genesys Telecommunications Laboratories, Inc. | Systems and methods for sizing modular routing applications |
US9894478B1 (en) | 2017-06-19 | 2018-02-13 | International Business Machines Corporation | Dynamic geo-fence size adjustment |
WO2018232622A1 (en) | 2017-06-21 | 2018-12-27 | Microsoft Technology Licensing, Llc | Media content recommendation through chatbots |
US10694038B2 (en) | 2017-06-23 | 2020-06-23 | Replicant Solutions, Inc. | System and method for managing calls of an automated call management system |
US10591288B2 (en) | 2017-06-27 | 2020-03-17 | The Boeing Company | System and method for evaluation of used components |
KR20190004495A (en) | 2017-07-04 | 2019-01-14 | 삼성에스디에스 주식회사 | Method, Apparatus and System for processing task using chatbot |
JP6218057B1 (en) | 2017-07-14 | 2017-10-25 | Jeインターナショナル株式会社 | Automatic response server device, terminal device, response system, response method, and program |
US10931724B2 (en) | 2017-07-18 | 2021-02-23 | NewVoiceMedia Ltd. | System and method for integrated virtual assistant-enhanced customer service |
CN109299961A (en) | 2017-07-24 | 2019-02-01 | 北京嘀嘀无限科技发展有限公司 | Prevent the method and device, equipment and storage medium of customer churn |
US10565634B2 (en) | 2017-08-01 | 2020-02-18 | Facebook, Inc. | Training a chatbot for a digital advertisement to simulate common conversations associated with similar digital advertisements |
WO2019027992A1 (en) | 2017-08-03 | 2019-02-07 | Telepathy Labs, Inc. | Omnichannel, intelligent, proactive virtual agent |
US10313521B2 (en) | 2017-08-15 | 2019-06-04 | Genesyc Telecommunications Laboratories, Inc | Automatic quality management of chat agents via chat bots |
US10855844B1 (en) | 2017-08-22 | 2020-12-01 | United Services Automobile Association (Usaa) | Learning based metric determination for service sessions |
US10673787B2 (en) | 2017-10-03 | 2020-06-02 | Servicenow, Inc. | Virtual agent conversation service |
US10553208B2 (en) | 2017-10-09 | 2020-02-04 | Ricoh Company, Ltd. | Speech-to-text conversion for interactive whiteboard appliances using multiple services |
US11223723B2 (en) | 2017-10-23 | 2022-01-11 | Accenture Global Solutions Limited | Call center system having reduced communication latency |
US20190132443A1 (en) | 2017-10-31 | 2019-05-02 | Perfect Pitch Technology, Llc | Devices and methods for facilitating training and quality assurance in contact centers |
US20190146647A1 (en) | 2017-11-16 | 2019-05-16 | [24]7.ai, Inc. | Method and system for facilitating collaboration among enterprise agents |
US20190172291A1 (en) | 2017-12-04 | 2019-06-06 | Black Hills Solutions | Automated stockroom for service management, dispensing & asset control |
KR102561712B1 (en) | 2017-12-07 | 2023-08-02 | 삼성전자주식회사 | Apparatus for Voice Recognition and operation method thereof |
US20190182383A1 (en) | 2017-12-08 | 2019-06-13 | Asapp, Inc. | Transfer of customer support to automated processing |
US10963688B2 (en) | 2017-12-10 | 2021-03-30 | Walmart Apollo, Llc | Systems and methods for a customer feedback classification system |
US20190197568A1 (en) | 2017-12-21 | 2019-06-27 | International Business Machines Corporation | Segmentation via weather susceptibility scoring |
US20190196676A1 (en) | 2017-12-26 | 2019-06-27 | Avaya Inc. | System and method for dynamically loaded application/agent terminal integration |
US11663672B2 (en) | 2017-12-29 | 2023-05-30 | Nanthealth, Inc. | User interface log validation via blockchain system and methods |
GB2569952A (en) | 2017-12-30 | 2019-07-10 | Innoplexus Ag | Method and system for identifying key terms in digital document |
WO2019142225A1 (en) | 2018-01-16 | 2019-07-25 | 株式会社小林製作所 | Display control device, program, and display control method |
US10715669B2 (en) | 2018-01-29 | 2020-07-14 | Avaya Inc. | Systems and methods for controlling transfer of contacts in a contact center |
US10762113B2 (en) | 2018-01-31 | 2020-09-01 | Cisco Technology, Inc. | Conversational knowledge graph powered virtual assistant for application performance management |
US10623565B2 (en) | 2018-02-09 | 2020-04-14 | Afiniti Europe Technologies Limited | Techniques for behavioral pairing in a contact center system |
US20190258825A1 (en) | 2018-02-20 | 2019-08-22 | Exotel Techcom Pvt. Ltd. | System and Method for Data Masking and Managing Communications |
US11861653B1 (en) | 2018-03-12 | 2024-01-02 | 8×8, Inc. | Contact center management for contact list generation in data communications systems |
US10699703B2 (en) | 2018-03-19 | 2020-06-30 | At&T Intellectual Property I, L.P. | System and method for artificial intelligence routing of customer service interactions |
US20190295027A1 (en) | 2018-03-26 | 2019-09-26 | International Business Machines Corporation | Cognitive scheduling for cooperative tasks |
US10694037B2 (en) | 2018-03-28 | 2020-06-23 | Nice Ltd. | System and method for automatically validating agent implementation of training material |
US11082562B2 (en) | 2018-04-30 | 2021-08-03 | Aurelio Luis Miguel ALONSO Y CALOCA | Contact center system and methods for handling voice and data teleservices through mobile devices |
US11158310B2 (en) | 2018-05-01 | 2021-10-26 | Dell Products, L.P. | Intelligent assistance for handling usage modes |
US10742806B2 (en) | 2018-05-08 | 2020-08-11 | Salesforce.Com, Inc. | Method, system and bot architecture for automatically sending a user content, that is responsive to user messages from that user, to solicit additional information from that user |
US10728361B2 (en) | 2018-05-29 | 2020-07-28 | Cisco Technology, Inc. | System for association of customer information across subscribers |
US10636425B2 (en) | 2018-06-05 | 2020-04-28 | Voicify, LLC | Voice application platform |
US10235999B1 (en) | 2018-06-05 | 2019-03-19 | Voicify, LLC | Voice application platform |
US10803865B2 (en) | 2018-06-05 | 2020-10-13 | Voicify, LLC | Voice application platform |
US11386381B2 (en) | 2018-06-06 | 2022-07-12 | International Business Machines Corporation | Meeting management |
US10824810B2 (en) | 2018-06-07 | 2020-11-03 | Honeywell International Inc. | System and method for identifying correlated operator action events based on text analytics of operator actions |
US20190385597A1 (en) | 2018-06-14 | 2019-12-19 | Behavioral Signal Technologies, Inc. | Deep actionable behavioral profiling and shaping |
US11438262B2 (en) | 2018-06-19 | 2022-09-06 | Good Egg Media LLC | Systems and methods for triaging and routing of emergency services communications sessions |
US10791222B2 (en) | 2018-06-21 | 2020-09-29 | Wells Fargo Bank, N.A. | Voice captcha and real-time monitoring for contact centers |
US20190392357A1 (en) | 2018-06-22 | 2019-12-26 | Uber Technologies, Inc. | Request optimization for a network-based service |
US20200005375A1 (en) | 2018-06-27 | 2020-01-02 | Ebay Inc. | Virtual assistant guidance based on category familiarity |
US10812654B2 (en) | 2018-06-29 | 2020-10-20 | At&T Intellectual Property I, L.P. | Interactive voice response system design, development and testing tool |
CN110674429B (en) | 2018-07-03 | 2022-05-31 | 百度在线网络技术(北京)有限公司 | Method, apparatus, device and computer readable storage medium for information retrieval |
US11562304B2 (en) | 2018-07-13 | 2023-01-24 | Accenture Global Solutions Limited | Preventative diagnosis prediction and solution determination of future event using internet of things and artificial intelligence |
US11108911B2 (en) | 2018-07-17 | 2021-08-31 | Avaya Inc. | System and method for flexible routing |
EP4418146A1 (en) | 2018-08-07 | 2024-08-21 | Google Llc | Assembling and evaluating automated assistant responses for privacy concerns |
US20200050996A1 (en) | 2018-08-09 | 2020-02-13 | Servicenow, Inc. | High level workforce as a service delivery using a cloud-based platform |
US10764435B2 (en) | 2018-08-29 | 2020-09-01 | Avaya Inc. | Smart customer assistant in a contact center |
US10853577B2 (en) | 2018-09-21 | 2020-12-01 | Salesforce.Com, Inc. | Response recommendation system |
KR20200035577A (en) | 2018-09-27 | 2020-04-06 | 베스핀글로벌 주식회사 | Method for enhanced schedule management based on rotation pattern and apparatus for the same |
US20200118215A1 (en) | 2018-10-12 | 2020-04-16 | DigiSure, Inc. | Dynamic pricing of insurance policies for shared goods |
US10756912B2 (en) | 2018-10-12 | 2020-08-25 | Avaya Inc. | Distributed ledger and blockchain to confirm validity of call recordings |
US11068942B2 (en) | 2018-10-19 | 2021-07-20 | Cerebri AI Inc. | Customer journey management engine |
US11037048B2 (en) | 2018-10-22 | 2021-06-15 | Moveworks, Inc. | Virtual conversation method or system |
US12001972B2 (en) | 2018-10-31 | 2024-06-04 | Accenture Global Solutions Limited | Semantic inferencing in customer relationship management |
US11037576B2 (en) | 2018-11-15 | 2021-06-15 | International Business Machines Corporation | Distributed machine-learned emphatic communication for machine-to-human and machine-to-machine interactions |
US10623572B1 (en) | 2018-11-21 | 2020-04-14 | N3, Llc | Semantic CRM transcripts from mobile communications sessions |
US11250387B2 (en) | 2018-11-30 | 2022-02-15 | Microsoft Technology Licensing, Llc | Sentence attention modeling for event scheduling via artificial intelligence and digital assistants |
US10554817B1 (en) | 2018-12-12 | 2020-02-04 | Amazon Technologies, Inc. | Automation of contact workflow and automated service agents in contact center system |
US20200193335A1 (en) | 2018-12-13 | 2020-06-18 | Accenture Global Solutions Limited | Seamless management of connected environments |
KR20200072907A (en) | 2018-12-13 | 2020-06-23 | 현대자동차주식회사 | Vehicle equipped with dialogue processing system and control method thereof |
US10497361B1 (en) | 2018-12-26 | 2019-12-03 | Capital One Services, Llc | Systems and methods for providing a virtual assistant |
US10977738B2 (en) | 2018-12-27 | 2021-04-13 | Futurity Group, Inc. | Systems, methods, and platforms for automated quality management and identification of errors, omissions and/or deviations in coordinating services and/or payments responsive to requests for coverage under a policy |
US10978066B2 (en) | 2019-01-08 | 2021-04-13 | International Business Machines Corporation | Analyzing information to provide topic avoidance alerts |
US20200242540A1 (en) | 2019-01-30 | 2020-07-30 | International Business Machines Corporation | Predicting a work progress metric for a user |
US11443212B2 (en) | 2019-01-31 | 2022-09-13 | International Business Machines Corporation | Learning policy explanations |
US11151324B2 (en) | 2019-02-03 | 2021-10-19 | International Business Machines Corporation | Generating completed responses via primal networks trained with dual networks |
US11140269B2 (en) | 2019-03-01 | 2021-10-05 | Genesys Telecommunications Laboratories, Inc. | Systems and methods for extended agent capacity |
US20200279266A1 (en) | 2019-03-01 | 2020-09-03 | Mastercard Technologies Canada ULC | Multi-page online application origination (oao) service for fraud prevention systems |
US20200285936A1 (en) | 2019-03-05 | 2020-09-10 | STATGRAF Research LLP. | Cognitive system |
US20220129905A1 (en) | 2019-03-08 | 2022-04-28 | [24]7.ai, Inc. | Agent console for facilitating assisted customer engagement |
US11017176B2 (en) | 2019-03-15 | 2021-05-25 | ContactEngine Limited | Omnichannel data communications system using artificial intelligence (AI) based machine learning and predictive analysis |
US10750019B1 (en) | 2019-03-29 | 2020-08-18 | Genesys Telecommunications Laboratories, Inc. | System and method for assisting agents via artificial intelligence |
US11563853B2 (en) | 2019-04-11 | 2023-01-24 | Baptist Health South Florida, Inc. | Method, system, and computer program product to accurately route a call request |
CA3135275A1 (en) | 2019-04-18 | 2020-10-22 | Greeneden U.S. Holdings Ii, Llc. | A system and method for analyzing web application network performance |
CN110096191B (en) | 2019-04-24 | 2021-06-29 | 北京百度网讯科技有限公司 | Man-machine conversation method and device and electronic equipment |
US10951768B2 (en) | 2019-05-03 | 2021-03-16 | Genesys Telecommunications Laboratories, Inc. | Measuring cognitive capabilities of automated resources and related management thereof in contact centers |
US10715648B1 (en) | 2019-05-09 | 2020-07-14 | Cisco Technology, Inc. | User interface for virtual assistant interactions on telephony device |
US10943267B2 (en) | 2019-05-10 | 2021-03-09 | Adobe Inc. | Machine learning assisted target segment audience generation |
US11094324B2 (en) | 2019-05-14 | 2021-08-17 | Motorola Mobility Llc | Accumulative multi-cue activation of domain-specific automatic speech recognition engine |
US11301722B2 (en) | 2019-05-14 | 2022-04-12 | Here Global B.V. | Method, apparatus, and system for providing map embedding analytics |
US10728384B1 (en) | 2019-05-29 | 2020-07-28 | Intuit Inc. | System and method for redaction of sensitive audio events of call recordings |
US20200395008A1 (en) | 2019-06-15 | 2020-12-17 | Very Important Puppets Inc. | Personality-Based Conversational Agents and Pragmatic Model, and Related Interfaces and Commercial Models |
US11461788B2 (en) | 2019-06-26 | 2022-10-04 | International Business Machines Corporation | Matching a customer and customer representative dynamically based on a customer representative's past performance |
US20210004836A1 (en) | 2019-07-05 | 2021-01-07 | Talkdesk, Inc. | System and method for pre-populating forms using agent assist within a cloud-based contact center |
US10789956B1 (en) | 2019-08-20 | 2020-09-29 | Capital One Services, Llc | Text-to-speech modeling |
US11445062B2 (en) | 2019-08-26 | 2022-09-13 | Afiniti, Ltd. | Techniques for behavioral pairing in a task assignment system |
US20210081955A1 (en) | 2019-09-13 | 2021-03-18 | Talkdesk, Inc | Systems and methods for integrating business processes into voice assistant platforms |
US20210081869A1 (en) | 2019-09-13 | 2021-03-18 | Talkdesk, Inc | Systems and methods for performing business processes based on data received from voice assistant platforms |
US20210084149A1 (en) | 2019-09-13 | 2021-03-18 | Talkdesk, Inc | Systems and methods for performing business processes based on data received from voice assistant platforms |
US20210082418A1 (en) | 2019-09-13 | 2021-03-18 | Talkdesk, Inc | Systems and methods for integrating business processes into voice assistant platforms |
US20210082417A1 (en) | 2019-09-13 | 2021-03-18 | Talkdesk, Inc | Systems and methods for integrating business processes into voice assistant platforms |
US10574822B1 (en) | 2019-09-16 | 2020-02-25 | Capital One Services, Llc | Computer-based systems and methods configured for one or more technological applications for the automated assisting of telephone agent services |
US20210084156A1 (en) | 2019-09-17 | 2021-03-18 | Talkdesk, Inc. | System for context data prioritization for a graphically interactive voice response system |
EP4032009A1 (en) | 2019-09-19 | 2022-07-27 | HRL Laboratories, LLC | Learning actions with few labels in the embedded space |
US11158321B2 (en) | 2019-09-24 | 2021-10-26 | Google Llc | Automated calling system |
US10623233B1 (en) | 2019-09-24 | 2020-04-14 | Intradiem Inc. | Live monitoring to trigger automation |
US11153440B2 (en) | 2019-10-07 | 2021-10-19 | Gladly, Inc. | Systems and methods for flexible and extensible contact center routing |
US10735585B1 (en) | 2019-10-15 | 2020-08-04 | Verint Americas Inc. | System and method of sentiment modeling and application to determine optimized agent action |
US20210125275A1 (en) | 2019-10-29 | 2021-04-29 | Talkdesk, Inc. | Methods and systems for customer identifier in data management platform for contact center |
WO2021087173A1 (en) | 2019-10-29 | 2021-05-06 | Greeneden U.S. Holdings Ii, Llc | Systems and methods related to the utilization, maintenance, and protection of personal data by customers |
US20210136205A1 (en) | 2019-10-30 | 2021-05-06 | Talkdesk, Inc. | Methods and systems of virtual agent real-time recommendation, suggestion and advertisement |
US20210133765A1 (en) | 2019-10-30 | 2021-05-06 | Talkdesk, Inc. | Methods and systems for socially aware virtual agents |
US20210134282A1 (en) | 2019-10-30 | 2021-05-06 | Talkdesk, Inc. | Methods and systems for personalized virtual agents to learn from customers |
US10929795B1 (en) | 2019-10-30 | 2021-02-23 | Talkdesk, Inc. | Scheduling agents using skill group weights |
US10812655B1 (en) | 2019-10-30 | 2020-10-20 | Talkdesk Inc. | Methods and systems for seamless outbound cold calls using virtual agents |
US20210134284A1 (en) | 2019-10-30 | 2021-05-06 | Talkdesk, Inc. | Methods and systems for personalized virtual agents to learn from customers |
US20210136204A1 (en) | 2019-10-30 | 2021-05-06 | Talkdesk, Inc. | Virtual agents within a cloud-based contact center |
US20210136206A1 (en) | 2019-10-30 | 2021-05-06 | Talkdesk, Inc. | Virtual agents within a cloud-based contact center |
US20210134283A1 (en) | 2019-10-30 | 2021-05-06 | Talkdesk, Inc. | Methods and systems of virtual agent real-time recommendation, suggestion and advertisement |
US20210133763A1 (en) | 2019-10-30 | 2021-05-06 | Talkdesk, Inc. | Methods and systems for socially aware virtual agents |
US20210201359A1 (en) | 2019-12-30 | 2021-07-01 | Genesys Telecommunications Laboratories, Inc. | Systems and methods relating to automation for personalizing the customer experience |
US11531950B2 (en) | 2019-12-30 | 2022-12-20 | Liveperson, Inc. | Dynamic analytics and forecasting for messaging staff |
US11501222B2 (en) | 2020-03-20 | 2022-11-15 | International Business Machines Corporation | Training operators through co-assignment |
EP4172785A1 (en) | 2020-06-30 | 2023-05-03 | ARRIS Enterprises LLC | Virtual elastic queue |
US20230007123A1 (en) | 2021-07-02 | 2023-01-05 | Talkdesk, Inc. | Method and apparatus for automated quality management of communication records |
-
2019
- 2019-10-16 US US16/654,356 patent/US20210117882A1/en active Pending
- 2019-10-17 US US16/656,179 patent/US20210117906A1/en not_active Abandoned
- 2019-10-17 US US16/656,124 patent/US20210117903A1/en not_active Abandoned
- 2019-10-17 US US16/656,150 patent/US20210117904A1/en not_active Abandoned
- 2019-10-17 US US16/656,170 patent/US20210117885A1/en not_active Abandoned
- 2019-10-17 US US16/656,160 patent/US11783246B2/en active Active
- 2019-10-17 US US16/656,139 patent/US20210117884A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
US20210117882A1 (en) | 2021-04-22 |
US20210117903A1 (en) | 2021-04-22 |
US20210117885A1 (en) | 2021-04-22 |
US20210117904A1 (en) | 2021-04-22 |
US20210117905A1 (en) | 2021-04-22 |
US20210117906A1 (en) | 2021-04-22 |
US11783246B2 (en) | 2023-10-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11146681B2 (en) | Systems and methods for scheduling deferred queues | |
US10824978B1 (en) | Systems and methods for optimizing performance metrics for contact centers | |
US20210136198A1 (en) | Capacity manager for multi-dimensional presence model to manage call-center agent load | |
US20210201245A1 (en) | Systems and methods for predicting and handling slack periods | |
US10931824B1 (en) | Scheduling agents using skill group weights | |
US11076049B2 (en) | Systems and methods for routing communications to agents based on attributes | |
US11783246B2 (en) | Systems and methods for workforce management system deployment | |
US11157856B2 (en) | Systems and methods for quality management system deployment | |
US20210081968A1 (en) | Systems and methods for predicting and resolving surge periods | |
US20210142247A1 (en) | Systems and methods for scheduling contractor agents based on residuals | |
US20210158266A1 (en) | Systems and methods for automating workforce management systems | |
US10887463B1 (en) | Method of using multi-dimensional presence model to manage call-center agent load | |
US10868914B1 (en) | Capacity manager for multi-dimensional presence model to manage call-center agent load | |
US20210125116A1 (en) | Systems and methods for recommending rules for routing calls |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |