WO2015009281A1 - System and method for predictive live interaction offering and hosting - Google Patents

System and method for predictive live interaction offering and hosting Download PDF

Info

Publication number
WO2015009281A1
WO2015009281A1 PCT/US2013/050593 US2013050593W WO2015009281A1 WO 2015009281 A1 WO2015009281 A1 WO 2015009281A1 US 2013050593 W US2013050593 W US 2013050593W WO 2015009281 A1 WO2015009281 A1 WO 2015009281A1
Authority
WO
WIPO (PCT)
Prior art keywords
agent
invitations
invitation
user
steps
Prior art date
Application number
PCT/US2013/050593
Other languages
French (fr)
Inventor
Jonathan M. KELLER
Gregory P. CUNNINGHAM
Original Assignee
Interactive Intelligence, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Interactive Intelligence, Inc. filed Critical Interactive Intelligence, Inc.
Priority to PCT/US2013/050593 priority Critical patent/WO2015009281A1/en
Publication of WO2015009281A1 publication Critical patent/WO2015009281A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0281Customer communication at a business location, e.g. providing product or service information, consulting

Definitions

  • the present invention generally relates to telecommunications systems and methods. More particularly, the present invention pertains to handling invitations of communications with users through points of service.
  • a system and method are presented for predictive live interaction offering and hosting.
  • a mechanism may be provided for controlling outstanding offerings, or invitations, of communications with users through points of service.
  • Offerings may include a live chat or a telephone callback request.
  • invitations may be optimized by analyzing factors such as agent history to predict when and how many agents will be available. Calculations may be continuously performed as offers are accepted, declined, timed out, etc., to make certain more offers than can be handled are not extended.
  • a method for controlling invitations to users through points of service comprising the steps of: allowing one or more invitations fitting an interaction profile to be distributed; optimizing a number of invitations; and performing an analysis to determine if a limit of accepted pending invitations is reached.
  • a method for controlling invitations to users through points of service comprising the steps of: predicting a number of free agents at a point in the future; applying a multiplier to said number of free agents to determine a number of invitations to make based on agent availability; setting aside a number of reservations of invitations; and distributing invitations to users.
  • a method for controlling invitations to users through points of service comprising the steps of: computing a number of predicted available agents using at least one of: an expected acceptance rate, a maximum time limit for an invitation to remain available, and agent availability; allocating a number of invitation tokens; returning a live invitation to a user via a method of communication; and determining if a user has accepted an invitation.
  • a system for controlling invitations to users through points of service comprising the steps of: means for allowing one or more invitations fitting an interaction profile to be distributed; means for tracking a number of invitations; and means for performing an analysis to determine if an accepted pending invitation limit is reached.
  • Figure 1 is a diagram illustrating the basic components of an embodiment of the system.
  • Figure 2 is a flowchart illustrating a process of an embodiment.
  • Figure 3 is a flowchart illustrating a process of an embodiment.
  • Figure 4 is a sequence diagram illustrating an embodiment of acceptance of an invitation.
  • FIG. 5 is a sequence diagram illustrating an embodiment of an invitation decline.
  • a point of service may include, but not be limited to, a web site or a mobile application.
  • An offer of a live chat may only occur if an agent is available immediately. The intention of this feature is to entice a potential customer or a user into direct human interaction by the immediacy of an agent being available. However, a free agent may be offered to more than person. If more than one user is at the point of service, but only one agent is available, offering an interaction to more than one user increases the probability that more than one will accept. At least one of the users may then be without an agent and waiting, which may be referred to as an "abandon".
  • a mechanism is provided for controlling outstanding invitations, optimizing the number of invitations, and monitoring the allowable limits of offer acceptance.
  • Mechanisms may control outstanding offerings, or invitations, in several different ways.
  • one or more offerings may be allowed that fit a specific interaction profile. These pending offerings may be referred to as "Reservations”.
  • a limit to the number of offerings that are accepted may also be provided.
  • the duration for an offer to remain valid may also be set.
  • the number of offerings may be optimized.
  • an agent answer history may be used to predict when agents will be free.
  • a certain level of confidence may be determined that, for an amount of time, a certain number of agents may be available. For example, if for the next 10 seconds, it is confident that there are at least 5 agents available with a 60% chat acceptance rate, then 8 invitations may be extended to users. It may also be predicted how long the agents will be free. Predictions may be made by re-evaluating every agent's change of status, such as "available", "busy”, etc. Predictions may be based on a configurable time window to reduce the computation load of the prediction.
  • the answer history may also be used to predict how many offers will be answered based on past history.
  • a predictive dialer such as Interactive Intelligence's Interaction Dialer® may be used to make such predictions. Aggressiveness factors within a predictive dialer may be utilized to factor in the allowable number of invitations to be answered. Abandon limit factors may also be included that are used in a predictive dialer to decrease the aggressiveness of offerings to achieve desired abandon limits either by desire, such as manually by the agent, or as required by current or future regulation. Predictions may also be made using categorization of calls that allow incorporation of agent skills or other customer subdivisions of the interactions into any statistical grouping of customers' choice.
  • a check is performed to determine if the accepted limit is reached. If the accepted limit has been reached, then the outstanding invitations are revoked. A re-calculation may also be performed to determine if offers can continue to be made based on current agents and future predictions.
  • FIG. 1 is a diagram illustrating the basic components in one embodiment of a system, indicated generally at 100.
  • the basic components of the system 100 may include: a User 105, a Service Provider 1 10, a Network 1 15, and a Managing Tracking Agent Module 120 which may comprise a Routing Module 121, a Tracking Module 122, and a Data Module 123.
  • System 100 may also include a plurality of Agent Workstations 125.
  • a User 105 may comprise a potential customer who is accessing a point of service. For example, a user 105 may be browsing on a website on the Internet and be identified as a potential customer to be made an invitation for communication. Such an offer may comprise a chat, instant message, telephone call or a callback request.
  • a telephone call may be of the "click to call" type, where a User 105 is immediately called by the system and placed in queue to talk to an agent. In a situation where a User 105 does not have time to talk at the moment or an agent is unavailable, a callback may be desired.
  • Identification of a User 105 as a potential customer may be made by monitoring the navigation of the User 105 on a webpage. For example, if a User 105 is clicking on links within a page to learn more about a product or exploring the site, they may be identified as a potential customer. If a page is opened and no activity occurs, for example, this behavior may not be indicative of a potential customer.
  • a Service Provider 1 10 may function as a gateway for a device.
  • the Service Provider 1 10 may comprise a web server, a User Interface Application between public users and services, or any type of customer relations application on any networkable computing device, either mobile or non- mobile.
  • Such an example may include Interactive Intelligence, Inc.'s, Interaction Mobilizer product.
  • the network 1 15 may be in the form of a Local Area Network (LAN), Municipal Area Network (MAN), Wide Area Network (WAN), such as the Internet, a combination of these, or such other network arrangement as would occur to those skilled in the art.
  • the operating logic of system 100 may be embodied in signals transmitted over network 1 15, in programming instructions, dedicated hardware, or a combination of these.
  • the network 1 15 may, in one embodiment, regulate the User's 105 view of the process.
  • the Network 1 15 may also provide communication between the Service Provider 1 10 and the Server 120.
  • a Managing Tracking Agent Module 120 may comprise a server that the client communication software is stored on. Such an example may include the Interactive Intelligence's Customer Interaction Center ® or Cisco CallManager.
  • the Managing Tracking Agent Module 120 may be comprised of modules such as the Routing Module 121, a Tracking Module 122, and a Data Module 123.
  • the Routing Module 121 may route an agent interaction to the user.
  • the Tracking User Module 122 may track users that are available or receptive to receive an offer.
  • the Data Module 123 may be responsible for providing predictive statistics and/or processing future predictive data of agent availability.
  • An agent workstation 125 may include a work station computer 128 coupled to a display 127.
  • Workstation computers 128 may be of the same type, or a heterogeneous combination of different computer devices.
  • displays 127 may be of the same type or a heterogeneous combination of different visual devices. It should be understood that while one work station 125 is described in the illustrative embodiment, more may be utilized.
  • Contact center applications of system 100 typically include many more workstations of this type at one or more physical locations, but only one is illustrated in Figure 1 to preserve clarity.
  • a digital telephone 126 may be associated with an Agent Workstation 125. Additionally, a digital telephone 126 may be integrated into the Agent Computer 128 and/or implemented in software. It should be understood that a digital telephone 126, which is capable of being directly connected to network 1 15, may be in the form of a handset, headset, or other arrangement as would occur to those skilled in the art. It shall be further understood that the connection from computer network 1 15 to an agent workstation 125 can be made first to the associated workstation telephone, then from the workstation telephone to the workstation computer by way of a pass through connection on the workstation telephone. Alternatively, two connections from the network can be made, one to the workstation telephone and one to the workstation computer. Although not shown to preserve clarity, an agent workstation 125 may also include one or more operator input devices such as a keyboard, mouse, track ball, light pen, and/or microtelecommunicator, to name just a few representative examples.
  • operator input devices such as a keyboard, mouse, track ball, light pen, and/or microtelecommunicator, to name
  • one or more other output devices may be included such as a loudspeaker(s) and/or a printer.
  • FIG. 2 is a flowchart illustrating an embodiment of the process.
  • the process 200 may be operative in the system 100 ( Figure 1). In one embodiment, the process 200 may occur concurrently with process 300 as described in Figure 3.
  • the process 200 loops in a continuous cycle which may be based on a time period, the assignment of an interaction, or any other event that may require a new prediction to be made.
  • the process 200 may be triggered at any point that a user's interactions with a point of service may be monitored. Any system that sends information about user navigation and the appropriate requests may trigger the logic. Such information from process 300 may be used to triggers operations within process 200.
  • triggers may include but not be limited to: agent status, agent login and logout, number of interactions active with each agent, time each agent is active with the interactions, after call work being performed, an auxiliary work state, other work agents might be performing, compliance information from work force management, future schedule changes from workforce management systems, and forecasts of current and future interaction activity.
  • agent answer history may be used to predict when agents will be free and for the duration of time they will be free.
  • the length of time that an agent is free may be re-evaluated with every agent change of state. For example, if an agent is busy, the amount of time that the agent remains in this state is monitored and used for evaluation along with other changes in state to determine how long an agent may be free. In another embodiment, a set period may be monitored for agent statuses to determine the length of time an agent is free. Any sort of prediction mechanism may be used, such as a predictive dialer in a call center, which may use statistics regarding each agent's passage through the various stages of an active call.
  • Control is passed to operation 210 and the process 200 continues.
  • a multiplier is applied. For example, the acceptance rate of a user accepting an offer may have a multiplier to determine how many or how few invitations to make based on agent availability. Control is passed to operation 215 and the process 200 continues.
  • reservations are set aside. For example, a number of reservations may be set aside such as some number of 'x' agents to fill a number 'y' of offers to distribute. Control is passed to operation 220 and the process 200 continues.
  • invitations are extended. For example, an offer is delivered to a user at the point of service.
  • a prompt or dialog may ask a user browsing a website if they want to immediately connect to a company representative via a Chat, Instant Message, or telephone call.
  • the process 200 ends.
  • Figure 3 is a flowchart illustrating an embodiment of the process.
  • the process 300 may be operative in the system 100 ( Figure 1).
  • the process 200 overlaps with the process 300.
  • the process 300 may utilize the information from the back-end agent predictions and triggers the operations in process 200.
  • the process 200 may loop in a continuous cycle each time an assignment of an offer is made.
  • Process 300 then cycles if is determined that offers are to be distributed.
  • a user visits a point of service. For example, a user may navigate to a webpage and click on links on the webpage. By clicking on links, interest in a product, service, or more information, may be exhibited. Control is passed to operation 310 and the process 300 continues.
  • operation 310 it is determined whether or not the user is interested. If it is determined that a user is interested, control is passed to operation 320 and the process 300 continues. If it is determined that a user is not interested, control is passed to operation 315 and the process 300 continues.
  • the determination in operation 310 may be based on any suitable criteria. For example, it may be determined if a user is interested based on the number of links selected on a webpage. A user may select several links on a page if they are interested in learning more information about a particular product or service. Users who are not interested, may simply leave the page. In another example, a user may navigate to a web page and pause for a time period. This pause may be construed to indicate that the user needs assistance and may trigger an invitation. Other factors may be considered, such as the time spent on a webpage.
  • the status of a queue or routing context is obtained.
  • the web processor polls the server to obtain the status of a queue or routing context of interest.
  • the routing context or queue may be of interest because it has been recently queried.
  • Control is passed to operation 325 and the process 300 continues.
  • operation 325 it is determined whether or not the queue has capacity. If it is determined that the queue has capacity, control is passed to operation 335 and the process 300 continues. If it is determined that the queue does not have capacity, control is passed to operation 330 and the process 300 continues.
  • the determination in operation 325 may be based on any suitable criteria. For example, factors may be considered such as the number of acceptances, how many agents are free, etc.
  • the information is based on a statistical calculation to determine how many offers to hand out and if the queue has the capacity to handle these. Such a statistical calculation may be made using those known in the art. For example, the acceptance rate prediction algorithms generally used in automatic dialing systems may be used. Aggressiveness calculations may also be used to determine the risk multiplier for the risk of abandoned calls versus offers.
  • the duration of interest is sent.
  • the processor may send the "duration" of interest so that the predictive algorithm may know the span of time it is covering.
  • a "duration" of interest may comprise how frequently the system expects to update the results. Control is passed to operation 340 and the process 300 continues.
  • operation 340 the request is processed and control is passed to operation 345.
  • the process 300 continues.
  • a handle is returned.
  • the processing operation may return "HowManyChatsToOffer", "HowManyChatsToAccept”, "HowLongToOffer”, etc., from a cache.
  • calls may be offered instead of chat. If a call is offered, then a power-dial may occur from the dialer. The handler may then return "HowManyCallsToOffer" or
  • tokens may be used. For a current query for the status of a queue or future requests up to the next polling time indicate that offers may be made to no more than “ToOffer” less the number of "HasAccepted” while “HasAccepted” is less than or equal to "ToAccept" for each media type.
  • a token may be allocated to represent any outstanding invitations for a media type.
  • the "ToOffer” handle from the call or chat may be decremented that are non-zero.
  • the Boolean operator "true” or “false” may be returned for the "CallOffer” or "ChatOffer” in the web queue status, which may indicate whether the user is entitled to a chat or to a call, or both.
  • a wait may then occur for the web user up to "HowLongToOffer". If a response of "AcceptCall” or “AcceptChat” is returned as true, then handle "HowMany*Accept” of the call or chat that was accepted may be decremented. For any unused tokens, the matching "HowMany*Offer” is incremented and the token is disposed of. Tokens may be unused due to timeout, an offer rejection, or use of only the call or the chat. Control is passed to operation 350 and the process 300 continues.
  • operation 350 it is determined whether or not the customer accepts a communication. If it is determined that a customer accepts the communication, control is passed to operation 360 and the process 300 continues. If it is determined that a customer does not accept the communication, control is passed to operation 355 and the process 300 continues.
  • the determination in operation 350 may be made based on any suitable criteria. For example, a customer may trigger acceptance by opting to receive a communication such as a call or chat from an agent. Declining an invitation may be done by the customer manually, or if may be done automatically by the system. A time out may be triggered if a customer does not decline or accept an offer within a specified period of time. This may be a predetermined period lasting seconds or longer, depending on the desired limits. The system may treat a time out the same as a decline and decrease the pending offers count. Decreasing the pending offers count may allow the system to make more offers.
  • the cache updates the state of the handle and alters a number of offerings and a number to accept. For example, when the web processor receives the results, the cache is updated with the value of the handle such as "HowManyCallsToOffer" or "HowManyChatsToAccept". An offer is then freed up for redistribution. In one embodiment, a check is performed to determine if the accepted limit of interactions have been accepted. If the accepted limit has been reached, the any outstanding offers may be revoked early in order to avoid having more offers accepted than available agents. The process 300 ends.
  • a communication is sent.
  • a communication may be sent in a manner specified by the user. For example, a chat may be performed through the User Interface or alternatively, a customer may elect to receive a telephone call from an agent. Control is passed to operation 365 and the process 300 continues.
  • the cache updates the state of the handle and alters a number of offerings and a number to accept. For example, when the web processor receives the results, the cache is updated with the value of the handle such as "HowManyCallsToOffer" or "HowManyChatsToAccept", for example. A value may vary depending on the implantation. An offer may then be freed for re-distribution. The process 300 ends.
  • FIG. 4 is a sequence diagram illustrating an embodiment of the process with the acceptance of an offer.
  • the vertical axes correspond to Statistics and Services 405a, Predictive Service 405b, Web Services 405c, Web/App Client 405d, and the User Interface 405e.
  • Actions in the User Interface may trigger the need or desire to offer a live interaction 406.
  • Statistics and Services 405a may send information to the Predictive Service 405b, such as the agent availability 407, wait time statistics 408, and agent handle time statistics 409.
  • the Statistics and Services 405a may be a constant data stream occurring in real time.
  • the Web/App Client 405d may send information from at least one web/app live interaction query 410 to the web services 405c.
  • the Predictive Service then receives availability information 411 from the web services 405c.
  • the Predictive Service 405b may compute the predicted number of agents that are expected to be available 412. The computation, in at least one embodiment, may be performed using an expected acceptance rate, the predicted number of agents available, and/or a maximum time limit for an offer duration.
  • the Predictive Service then returns agent availability 413 to the web services 405c. Offer Tokens may be allocated 414.
  • the Web Services 405c may return a live offer to chat or call to the number of live agents 415 to the Web/App Client 405d.
  • a live interaction invitation 416 is indicated to the User Interface 405e.
  • a timeout may occur in which pending live offers may be canceled.
  • the Web Services 405c may wait up to the time limit for the maximum offer duration to cancel such pending live offers 417.
  • a cancel status 418 is then returned to the Web/App Client 405d.
  • the Live Interaction Offer status 419 is then updated.
  • the web/app client 405d may indicate such acceptance of the live offer 421 to the Web services. If such an offer is not canceled, then the pending offer count may be decremented or pending offers may be cancelled 422. Web Services 405c sends accepted offers and cancelled offer status 423 to the web/app client 405d. A live interaction may be initiated if it has been accepted 424.
  • FIG. 5 is a sequence diagram illustrating an embodiment of the process with the decline of an offer.
  • the steps are similar to those of Figure 4, except that the user declines an offer 505.
  • the Web/App Client 405d may indicate to Web services 405c that the live offer has been declined 506.
  • the system may decrement the pending offer count and offer again any free offers 507.
  • a cancel status 508 is sent to the web/app client 405d.
  • a time-out may occur which may be treated in a similar manner.
  • a time out may be triggered if a customer does not decline or accept an offer within a specified period of time.
  • the system may decrease the pending offer count in a similar manner as step 507 and perform a re-offer.
  • an open offer can be managed by the system without having to expire said offer, the original offer may also be extended.

Abstract

A system and method are presented for predictive live interaction offering and hosting. A mechanism may be provided for controlling outstanding offerings, or invitations, of communications with users through points of service. Offerings may include a live chat or a telephone callback request. In one embodiment, offerings may be optimized by analyzing factors such as agent history to predict when and how many agents will be available. Calculations may be continuously performed as invitations are accepted, declined, timed out, etc., to make certain more offers than can be handled are not extended.

Description

SYSTEM AND METHOD FOR PREDICTIVE LIVE INTERACTION OFFERING AND HOSTING BACKGROUND
[1] The present invention generally relates to telecommunications systems and methods. More particularly, the present invention pertains to handling invitations of communications with users through points of service.
SUMMARY
[2] A system and method are presented for predictive live interaction offering and hosting. A mechanism may be provided for controlling outstanding offerings, or invitations, of communications with users through points of service. Offerings may include a live chat or a telephone callback request. In one embodiment, invitations may be optimized by analyzing factors such as agent history to predict when and how many agents will be available. Calculations may be continuously performed as offers are accepted, declined, timed out, etc., to make certain more offers than can be handled are not extended.
[3] In one embodiment, a method for controlling invitations to users through points of service is presented, comprising the steps of: allowing one or more invitations fitting an interaction profile to be distributed; optimizing a number of invitations; and performing an analysis to determine if a limit of accepted pending invitations is reached.
[4] In another embodiment, a method for controlling invitations to users through points of service is presented, comprising the steps of: predicting a number of free agents at a point in the future; applying a multiplier to said number of free agents to determine a number of invitations to make based on agent availability; setting aside a number of reservations of invitations; and distributing invitations to users.
[5] In another embodiment, a method for controlling invitations to users through points of service is presented, comprising the steps of: computing a number of predicted available agents using at least one of: an expected acceptance rate, a maximum time limit for an invitation to remain available, and agent availability; allocating a number of invitation tokens; returning a live invitation to a user via a method of communication; and determining if a user has accepted an invitation. [6] In another embodiment, a system for controlling invitations to users through points of service is presented, comprising the steps of: means for allowing one or more invitations fitting an interaction profile to be distributed; means for tracking a number of invitations; and means for performing an analysis to determine if an accepted pending invitation limit is reached.
BRIEF DESCRIPTION OF THE DRAWINGS
[7] Figure 1 is a diagram illustrating the basic components of an embodiment of the system.
[8] Figure 2 is a flowchart illustrating a process of an embodiment.
[9] Figure 3 is a flowchart illustrating a process of an embodiment.
[10] Figure 4 is a sequence diagram illustrating an embodiment of acceptance of an invitation.
[1 1] Figure 5 is a sequence diagram illustrating an embodiment of an invitation decline.
DETAILED DESCRIPTION
[12] For the purposes of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. Any alterations and further modifications in the described embodiments, and any further applications of the principles of the invention as described herein are contemplated as would normally occur to one skilled in the art to which the invention relates.
[13] Many web sites and products, for example, have implemented features that will offer a live chat or a telephone callback request if a potential user, or customer, is viewing or accessing content on their point of service. A point of service may include, but not be limited to, a web site or a mobile application. An offer of a live chat may only occur if an agent is available immediately. The intention of this feature is to entice a potential customer or a user into direct human interaction by the immediacy of an agent being available. However, a free agent may be offered to more than person. If more than one user is at the point of service, but only one agent is available, offering an interaction to more than one user increases the probability that more than one will accept. At least one of the users may then be without an agent and waiting, which may be referred to as an "abandon".
[14] In at least one embodiment, a mechanism is provided for controlling outstanding invitations, optimizing the number of invitations, and monitoring the allowable limits of offer acceptance.
Mechanisms may control outstanding offerings, or invitations, in several different ways. In at least one embodiment, one or more offerings may be allowed that fit a specific interaction profile. These pending offerings may be referred to as "Reservations". A limit to the number of offerings that are accepted may also be provided. The duration for an offer to remain valid may also be set.
[15] In at least one embodiment, the number of offerings may be optimized. For example, an agent answer history may be used to predict when agents will be free. A certain level of confidence may be determined that, for an amount of time, a certain number of agents may be available. For example, if for the next 10 seconds, it is confident that there are at least 5 agents available with a 60% chat acceptance rate, then 8 invitations may be extended to users. It may also be predicted how long the agents will be free. Predictions may be made by re-evaluating every agent's change of status, such as "available", "busy", etc. Predictions may be based on a configurable time window to reduce the computation load of the prediction. The answer history may also be used to predict how many offers will be answered based on past history. A predictive dialer, such as Interactive Intelligence's Interaction Dialer® may be used to make such predictions. Aggressiveness factors within a predictive dialer may be utilized to factor in the allowable number of invitations to be answered. Abandon limit factors may also be included that are used in a predictive dialer to decrease the aggressiveness of offerings to achieve desired abandon limits either by desire, such as manually by the agent, or as required by current or future regulation. Predictions may also be made using categorization of calls that allow incorporation of agent skills or other customer subdivisions of the interactions into any statistical grouping of customers' choice.
[16] In at least one embodiment, when offered interactions are accepted, a check is performed to determine if the accepted limit is reached. If the accepted limit has been reached, then the outstanding invitations are revoked. A re-calculation may also be performed to determine if offers can continue to be made based on current agents and future predictions.
[17] Figure 1 is a diagram illustrating the basic components in one embodiment of a system, indicated generally at 100. The basic components of the system 100 may include: a User 105, a Service Provider 1 10, a Network 1 15, and a Managing Tracking Agent Module 120 which may comprise a Routing Module 121, a Tracking Module 122, and a Data Module 123. System 100 may also include a plurality of Agent Workstations 125.
[18] A User 105 may comprise a potential customer who is accessing a point of service. For example, a user 105 may be browsing on a website on the Internet and be identified as a potential customer to be made an invitation for communication. Such an offer may comprise a chat, instant message, telephone call or a callback request. A telephone call may be of the "click to call" type, where a User 105 is immediately called by the system and placed in queue to talk to an agent. In a situation where a User 105 does not have time to talk at the moment or an agent is unavailable, a callback may be desired.
Identification of a User 105 as a potential customer may be made by monitoring the navigation of the User 105 on a webpage. For example, if a User 105 is clicking on links within a page to learn more about a product or exploring the site, they may be identified as a potential customer. If a page is opened and no activity occurs, for example, this behavior may not be indicative of a potential customer.
[19] A Service Provider 1 10 may function as a gateway for a device. For example, the Service Provider 1 10 may comprise a web server, a User Interface Application between public users and services, or any type of customer relations application on any networkable computing device, either mobile or non- mobile. Such an example may include Interactive Intelligence, Inc.'s, Interaction Mobilizer product.
[20] The network 1 15 may be in the form of a Local Area Network (LAN), Municipal Area Network (MAN), Wide Area Network (WAN), such as the Internet, a combination of these, or such other network arrangement as would occur to those skilled in the art. The operating logic of system 100 may be embodied in signals transmitted over network 1 15, in programming instructions, dedicated hardware, or a combination of these. The network 1 15 may, in one embodiment, regulate the User's 105 view of the process. The Network 1 15 may also provide communication between the Service Provider 1 10 and the Server 120.
[21] A Managing Tracking Agent Module 120 may comprise a server that the client communication software is stored on. Such an example may include the Interactive Intelligence's Customer Interaction Center ® or Cisco CallManager. The Managing Tracking Agent Module 120 may be comprised of modules such as the Routing Module 121, a Tracking Module 122, and a Data Module 123. The Routing Module 121 may route an agent interaction to the user. The Tracking User Module 122 may track users that are available or receptive to receive an offer. The Data Module 123 may be responsible for providing predictive statistics and/or processing future predictive data of agent availability.
[22] An agent workstation 125 may include a work station computer 128 coupled to a display 127. Workstation computers 128 may be of the same type, or a heterogeneous combination of different computer devices. Likewise, displays 127 may be of the same type or a heterogeneous combination of different visual devices. It should be understood that while one work station 125 is described in the illustrative embodiment, more may be utilized. Contact center applications of system 100 typically include many more workstations of this type at one or more physical locations, but only one is illustrated in Figure 1 to preserve clarity.
[23] A digital telephone 126 may be associated with an Agent Workstation 125. Additionally, a digital telephone 126 may be integrated into the Agent Computer 128 and/or implemented in software. It should be understood that a digital telephone 126, which is capable of being directly connected to network 1 15, may be in the form of a handset, headset, or other arrangement as would occur to those skilled in the art. It shall be further understood that the connection from computer network 1 15 to an agent workstation 125 can be made first to the associated workstation telephone, then from the workstation telephone to the workstation computer by way of a pass through connection on the workstation telephone. Alternatively, two connections from the network can be made, one to the workstation telephone and one to the workstation computer. Although not shown to preserve clarity, an agent workstation 125 may also include one or more operator input devices such as a keyboard, mouse, track ball, light pen, and/or microtelecommunicator, to name just a few representative examples.
Additionally, besides display 127, one or more other output devices may be included such as a loudspeaker(s) and/or a printer.
[24] Figure 2 is a flowchart illustrating an embodiment of the process. The process 200 may be operative in the system 100 (Figure 1). In one embodiment, the process 200 may occur concurrently with process 300 as described in Figure 3. The process 200 loops in a continuous cycle which may be based on a time period, the assignment of an interaction, or any other event that may require a new prediction to be made. The process 200 may be triggered at any point that a user's interactions with a point of service may be monitored. Any system that sends information about user navigation and the appropriate requests may trigger the logic. Such information from process 300 may be used to triggers operations within process 200. Other examples of triggers may include but not be limited to: agent status, agent login and logout, number of interactions active with each agent, time each agent is active with the interactions, after call work being performed, an auxiliary work state, other work agents might be performing, compliance information from work force management, future schedule changes from workforce management systems, and forecasts of current and future interaction activity.
[25] In operation 205, the number of free agents is predicted. For example, in one embodiment agent answer history may be used to predict when agents will be free and for the duration of time they will be free. The length of time that an agent is free may be re-evaluated with every agent change of state. For example, if an agent is busy, the amount of time that the agent remains in this state is monitored and used for evaluation along with other changes in state to determine how long an agent may be free. In another embodiment, a set period may be monitored for agent statuses to determine the length of time an agent is free. Any sort of prediction mechanism may be used, such as a predictive dialer in a call center, which may use statistics regarding each agent's passage through the various stages of an active call. Control is passed to operation 210 and the process 200 continues. [26] In operation 210, a multiplier is applied. For example, the acceptance rate of a user accepting an offer may have a multiplier to determine how many or how few invitations to make based on agent availability. Control is passed to operation 215 and the process 200 continues.
[27] In operation 215, reservations are set aside. For example, a number of reservations may be set aside such as some number of 'x' agents to fill a number 'y' of offers to distribute. Control is passed to operation 220 and the process 200 continues.
[28] In operation 220, invitations are extended. For example, an offer is delivered to a user at the point of service. A prompt or dialog may ask a user browsing a website if they want to immediately connect to a company representative via a Chat, Instant Message, or telephone call. The process 200 ends.
[29] Figure 3 is a flowchart illustrating an embodiment of the process. The process 300 may be operative in the system 100 (Figure 1). The process 200 overlaps with the process 300. The process 300 may utilize the information from the back-end agent predictions and triggers the operations in process 200. The process 200 may loop in a continuous cycle each time an assignment of an offer is made.
Process 300 then cycles if is determined that offers are to be distributed.
[30] In operation 305, a user visits a point of service. For example, a user may navigate to a webpage and click on links on the webpage. By clicking on links, interest in a product, service, or more information, may be exhibited. Control is passed to operation 310 and the process 300 continues.
[31] In operation 310, it is determined whether or not the user is interested. If it is determined that a user is interested, control is passed to operation 320 and the process 300 continues. If it is determined that a user is not interested, control is passed to operation 315 and the process 300 continues.
[32] The determination in operation 310 may be based on any suitable criteria. For example, it may be determined if a user is interested based on the number of links selected on a webpage. A user may select several links on a page if they are interested in learning more information about a particular product or service. Users who are not interested, may simply leave the page. In another example, a user may navigate to a web page and pause for a time period. This pause may be construed to indicate that the user needs assistance and may trigger an invitation. Other factors may be considered, such as the time spent on a webpage.
[33] In operation 315, no invitations are made and the process 300 ends.
[34] In operation 320, the status of a queue or routing context is obtained. For example, the web processor polls the server to obtain the status of a queue or routing context of interest. In at least one embodiment, the routing context or queue may be of interest because it has been recently queried.
Control is passed to operation 325 and the process 300 continues.
[35] In operation 325, it is determined whether or not the queue has capacity. If it is determined that the queue has capacity, control is passed to operation 335 and the process 300 continues. If it is determined that the queue does not have capacity, control is passed to operation 330 and the process 300 continues.
[36] The determination in operation 325 may be based on any suitable criteria. For example, factors may be considered such as the number of acceptances, how many agents are free, etc. The information is based on a statistical calculation to determine how many offers to hand out and if the queue has the capacity to handle these. Such a statistical calculation may be made using those known in the art. For example, the acceptance rate prediction algorithms generally used in automatic dialing systems may be used. Aggressiveness calculations may also be used to determine the risk multiplier for the risk of abandoned calls versus offers.
[37] In operation 330, no invitations are made and the process 300 ends.
[38] In operation 335, the duration of interest is sent. For example, the processor may send the "duration" of interest so that the predictive algorithm may know the span of time it is covering. A "duration" of interest may comprise how frequently the system expects to update the results. Control is passed to operation 340 and the process 300 continues.
[39] In operation 340, the request is processed and control is passed to operation 345. The process 300 continues. [40] In operation 345, a handle is returned. For example, the processing operation may return "HowManyChatsToOffer", "HowManyChatsToAccept", "HowLongToOffer", etc., from a cache. In another embodiment, calls may be offered instead of chat. If a call is offered, then a power-dial may occur from the dialer. The handler may then return "HowManyCallsToOffer" or
"HowManyCallsToAccept" if a call is offered. In at least one embodiment, tokens may be used. For a current query for the status of a queue or future requests up to the next polling time indicate that offers may be made to no more than "ToOffer" less the number of "HasAccepted" while "HasAccepted" is less than or equal to "ToAccept" for each media type.
[41] If "HowMany*ToOffer" is greater than zero, and "HowMany*ToAccept" is greater than zero, then a token may be allocated to represent any outstanding invitations for a media type. The "ToOffer" handle from the call or chat may be decremented that are non-zero. For any allocated tokens, the Boolean operator "true" or "false" may be returned for the "CallOffer" or "ChatOffer" in the web queue status, which may indicate whether the user is entitled to a chat or to a call, or both. For example,
"CallOffer=false, ChatOffer=true" may indicate a chat offering while "CallOffer=true, ChatOffer=false" may indicate a call offering.
[42] A wait may then occur for the web user up to "HowLongToOffer". If a response of "AcceptCall" or "AcceptChat" is returned as true, then handle "HowMany*Accept" of the call or chat that was accepted may be decremented. For any unused tokens, the matching "HowMany*Offer" is incremented and the token is disposed of. Tokens may be unused due to timeout, an offer rejection, or use of only the call or the chat. Control is passed to operation 350 and the process 300 continues.
[43] In operation 350 it is determined whether or not the customer accepts a communication. If it is determined that a customer accepts the communication, control is passed to operation 360 and the process 300 continues. If it is determined that a customer does not accept the communication, control is passed to operation 355 and the process 300 continues.
[44] The determination in operation 350 may be made based on any suitable criteria. For example, a customer may trigger acceptance by opting to receive a communication such as a call or chat from an agent. Declining an invitation may be done by the customer manually, or if may be done automatically by the system. A time out may be triggered if a customer does not decline or accept an offer within a specified period of time. This may be a predetermined period lasting seconds or longer, depending on the desired limits. The system may treat a time out the same as a decline and decrease the pending offers count. Decreasing the pending offers count may allow the system to make more offers.
[45] In operation 355, the cache updates the state of the handle and alters a number of offerings and a number to accept. For example, when the web processor receives the results, the cache is updated with the value of the handle such as "HowManyCallsToOffer" or "HowManyChatsToAccept". An offer is then freed up for redistribution. In one embodiment, a check is performed to determine if the accepted limit of interactions have been accepted. If the accepted limit has been reached, the any outstanding offers may be revoked early in order to avoid having more offers accepted than available agents. The process 300 ends.
[46] In operation 360, a communication is sent. A communication may be sent in a manner specified by the user. For example, a chat may be performed through the User Interface or alternatively, a customer may elect to receive a telephone call from an agent. Control is passed to operation 365 and the process 300 continues.
[47] In operation 365, the cache updates the state of the handle and alters a number of offerings and a number to accept. For example, when the web processor receives the results, the cache is updated with the value of the handle such as "HowManyCallsToOffer" or "HowManyChatsToAccept", for example. A value may vary depending on the implantation. An offer may then be freed for re-distribution. The process 300 ends.
[48] Figure 4 is a sequence diagram illustrating an embodiment of the process with the acceptance of an offer. The vertical axes correspond to Statistics and Services 405a, Predictive Service 405b, Web Services 405c, Web/App Client 405d, and the User Interface 405e. Actions in the User Interface may trigger the need or desire to offer a live interaction 406. Statistics and Services 405a may send information to the Predictive Service 405b, such as the agent availability 407, wait time statistics 408, and agent handle time statistics 409. The Statistics and Services 405a may be a constant data stream occurring in real time. The Web/App Client 405d may send information from at least one web/app live interaction query 410 to the web services 405c. The Predictive Service then receives availability information 411 from the web services 405c. The Predictive Service 405b may compute the predicted number of agents that are expected to be available 412. The computation, in at least one embodiment, may be performed using an expected acceptance rate, the predicted number of agents available, and/or a maximum time limit for an offer duration. The Predictive Service then returns agent availability 413 to the web services 405c. Offer Tokens may be allocated 414. The Web Services 405c may return a live offer to chat or call to the number of live agents 415 to the Web/App Client 405d. A live interaction invitation 416 is indicated to the User Interface 405e.
[49] A timeout may occur in which pending live offers may be canceled. The Web Services 405c may wait up to the time limit for the maximum offer duration to cancel such pending live offers 417. A cancel status 418 is then returned to the Web/App Client 405d. The Live Interaction Offer status 419 is then updated.
[50] If a User accepts 420 an offer, then the web/app client 405d may indicate such acceptance of the live offer 421 to the Web services. If such an offer is not canceled, then the pending offer count may be decremented or pending offers may be cancelled 422. Web Services 405c sends accepted offers and cancelled offer status 423 to the web/app client 405d. A live interaction may be initiated if it has been accepted 424.
[51 ] Figure 5 is a sequence diagram illustrating an embodiment of the process with the decline of an offer. The steps are similar to those of Figure 4, except that the user declines an offer 505. The Web/App Client 405d may indicate to Web services 405c that the live offer has been declined 506. The system may decrement the pending offer count and offer again any free offers 507. A cancel status 508 is sent to the web/app client 405d. Alternatively, instead of a decline by a user, a time-out may occur which may be treated in a similar manner. A time out may be triggered if a customer does not decline or accept an offer within a specified period of time. The system may decrease the pending offer count in a similar manner as step 507 and perform a re-offer. In another embodiment, if an open offer can be managed by the system without having to expire said offer, the original offer may also be extended.
[52] While the invention has been illustrated and described in detail in the drawings and foregoing description, the same is to be considered as illustrative and not restrictive in character, it being understood that only the preferred embodiment has been shown and described and that all equivalents, changes, and modifications that come within the spirit of the invention as described herein and/or by the following claims are desired to be protected.
[53] Hence, the proper scope of the present invention should be determined only by the broadest interpretation of the appended claims so as to encompass all such modifications as well as all relationships equivalent to those illustrated in the drawings and described in the specification.

Claims

1. A method for controlling invitations to users through points of service comprising the steps of: a. allowing one or more invitations fitting an interaction profile to be distributed; b. optimizing a number of invitations; and
c. performing an analysis to determine if a limit of accepted pending invitations is reached.
2. The method of claim 1, wherein step (b) further comprises the steps of:
a. determining a number of reservations of invitations to be made;
b. determining a number of invitations that are accepted by a user; and
c. setting a duration of time for an invitation to remain valid.
3. The method of claim 2, wherein step (b) further comprises at least one of the following steps: a. reevaluating a contact list; and
b. expiring the reservations outstanding.
4. The method of claim 2, wherein step (a) further comprises the steps of:
a. examining at least one agent history to determine when said at least one agent will be available; and
b. examining an agent history to determine how long said agent will be available.
5. The method of claim 4 further comprising the steps of:
a. basing a prediction on a configurable time window to reduce computation load; and b. using a predictive dialer to make said prediction.
6. The method of claim 4, wherein the steps are continuously performed over a time period.
7. The method of claim 6, wherein the time period is based on agent status changes.
8. The method of claim 6, wherein the time period is based on increments of time.
9. The method of claim 5, wherein step (b) further comprises the step of:
a. using aggressiveness factors within said predictive dialer to factor in an allowable
number of invitations to be made in making a prediction.
10. The method of claim 5, wherein step (b) further comprises the step of: a. using abandon limit factors to decrease the aggressiveness of invitations extended to achieve desired abandon limits in making a prediction.
1 1. The method of claim 5, wherein step (b) further comprises the step of:
a. using categorization of calls allowing incorporation of information into statistical groups to make a prediction.
12. The method of claim 1, wherein step (c) further comprises the steps of:
a. revoking outstanding invitations if the accepted limits are reached; and
b. performing recalculations to determine if invitations can continue to be made based on at least one of current agents and future predictions.
13. The method of claim 1, wherein step (b) is guided by the interactions of step (a).
14. A method for controlling invitations to users through points of service comprising the steps of: a. predicting a number of free agents at a point in the future;
b. applying a multiplier to said number of free agents to determine a number of invitations to make based on agent availability;
c. setting aside a number of reservations of invitations; and
d. distributing invitations to users.
15. The method of claim 14, wherein step (a) further comprises the step of:
a. examining at least one of agent history and current agent activity to predict at least one of when an agent will be free and for the duration of time said agent will be free;
16. The method of claim 15, wherein the agent history comprises the agent handle time history for specific interaction types.
17. The method of claim 15 wherein the agent history comprises state changes.
18. The method of claim 14, wherein step (a) further comprises the step of:
a. optimizing software to determine further agent availability based on at least one of
workload and agent schedules.
19. The method of claim 14, wherein step (a) further comprises the steps of: a. monitoring a set period for agent statuses to determine a length of time an agent is free.
20. The method of claim 19, wherein the agent statuses comprise at least one of: agent state, contact handle time, and activity.
21. The method of claim 14 wherein the number of reservations in step (c) comprise a number of agents to fill a number of invitations to distribute.
22. The method of claim 14 wherein step (d) further comprises the step of:
a. providing an option to chat via a text box with an agent to a user.
23. The method of claim 14 wherein step (d) further comprises the step of:
a. providing an option to instant message with an agent to a user.
24. The method of claim 14 wherein step (d) further comprises the step of:
a. providing an option to receive a real time communication from an agent to a user.
25. The method of claim 14, wherein step (d) further comprises the step of:
a. determining at least one of: whether an agent can handle more than one interaction, whether an agent can handle more than one type of interaction, and which agent can handle said interaction.
26. The method of claim 14 further comprising the steps of:
a. determining whether or not a user may be interested in receiving an invitation;
b. providing an invitation if the user is interested;
c. obtaining a status of a queue;
d. determining whether or not the queue has the capacity to provide an invitation;
e. sending a duration of interest if the queue has the capacity to provide an invitation; f. processing a request to allow routing of an invitation;
g. returning a handle;
h. determining if a user has accepted an invitation;
i. updating a cache with results;
j. sending a communication to a user; and k. updating a cache with results.
27. A method for controlling invitations to users through points of service comprising the steps of: a. computing a number of predicted available agents using at least one of: an expected acceptance rate, a maximum time limit for an invitation to remain available, and agent availability;
b. allocating a number of invitation tokens;
c. returning a live invitation to a user via a method of communication; and
d. determining if a user has accepted an invitation.
28. The method of claim 27 further comprising the steps of:
a. decrementing a pending invitation count if a user has accepted an invitation; and b. cancelling a pending invitation.
29. The method of claim 27 further comprising the steps of:
a. decrementing the pending invitation count if a user has not accepted an invitation; and b. making a new invitation.
30. The method of claim 27 further comprising the step of:
a. extending a time limit for an invitation to remain available if a user does not accept said invitation during said time limit for an invitation to remain available.
31. The method of claim 27 further comprising the step of:
a. repeating reevaluation of an allocated invitation token time limit for expiration.
32. The method of claim 27, wherein said method of communication comprises sending a chat via a text box.
33. The method of claim 27, wherein said method of communication comprises sending a telephone call.
34. A system for controlling invitations to users through points of service comprising:
a. means for allowing one or more invitations fitting an interaction profile to be distributed; b. means for tracking a number of invitations; and means for performing an analysis to determine if an accepted pending invitation limit is reached.
PCT/US2013/050593 2013-07-16 2013-07-16 System and method for predictive live interaction offering and hosting WO2015009281A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2013/050593 WO2015009281A1 (en) 2013-07-16 2013-07-16 System and method for predictive live interaction offering and hosting

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2013/050593 WO2015009281A1 (en) 2013-07-16 2013-07-16 System and method for predictive live interaction offering and hosting

Publications (1)

Publication Number Publication Date
WO2015009281A1 true WO2015009281A1 (en) 2015-01-22

Family

ID=52346579

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/050593 WO2015009281A1 (en) 2013-07-16 2013-07-16 System and method for predictive live interaction offering and hosting

Country Status (1)

Country Link
WO (1) WO2015009281A1 (en)

Citations (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5815566A (en) * 1991-10-10 1998-09-29 Executone Information Systems, Inc. Apparatus and method for dynamic inbound/outbound call management and for scheduling appointments
US20040083195A1 (en) * 2002-10-23 2004-04-29 Mccord Alan Wayne Method and system for enabling automated and real-time discovery of skills available to agents and systems in a multimedia communications network
US20040184593A1 (en) * 1997-03-13 2004-09-23 Metro One Telecommunications, Inc. Technique for effectively providing concierge-like services in a directory assistance system
US20050002515A1 (en) * 1999-07-13 2005-01-06 Mewhinney Brian E. Dialing techniques for a contact center
US20050228723A1 (en) * 2004-04-08 2005-10-13 Malik Dale W Conveying self-expiring offers
US6973176B1 (en) * 2003-09-30 2005-12-06 Avaya Technology Corp. Method and apparatus for rotating auto reserve agents
US20060116918A1 (en) * 2004-12-01 2006-06-01 Flora Joel L Network scheduler with linked information
US20060147026A1 (en) * 2000-10-23 2006-07-06 Mci, Inc. Retrieval of data related to a call center
US20060153173A1 (en) * 1998-09-11 2006-07-13 Beck Christopher Clemmett M Method for routing transactions between internal and external partners in a communication center
US20060165066A1 (en) * 2000-01-07 2006-07-27 Aastra Intecom Inc. Customer communication service system
US20070015518A1 (en) * 2005-07-15 2007-01-18 Agilis Systems, Inc. Mobile resource location-based customer contact systems
US7406515B1 (en) * 2000-06-27 2008-07-29 Aspect Communications System and method for automated and customizable agent availability and task assignment management
US20100111288A1 (en) * 2008-11-06 2010-05-06 Afzal Hassan Time to answer selector and advisor for call routing center
US20100138534A1 (en) * 2008-11-25 2010-06-03 Rishi Mutnuru Systems and methods for monitor an access gateway
US20110153375A1 (en) * 2000-08-18 2011-06-23 The Crawford Group, Inc. Method and System for Managing Rental Vehicle Reservations with User Authorization Limits
US20120116830A1 (en) * 2010-11-05 2012-05-10 Timetrade Systems, Inc. Availability-Based Contact Routing and Scheduling System
US20120213356A1 (en) * 2009-06-01 2012-08-23 Shashkov Georgiy N System and Methods for Predicting Future Agent Readiness for Handling an Interaction in a Call Center
US20120321070A1 (en) * 2011-05-25 2012-12-20 Echopass Corporation Systems and methods for managing multi-tenant callback services
US20130051546A1 (en) * 2011-08-26 2013-02-28 Lance Fried Network predictive customer service queue management

Patent Citations (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5815566A (en) * 1991-10-10 1998-09-29 Executone Information Systems, Inc. Apparatus and method for dynamic inbound/outbound call management and for scheduling appointments
US20040184593A1 (en) * 1997-03-13 2004-09-23 Metro One Telecommunications, Inc. Technique for effectively providing concierge-like services in a directory assistance system
US20060153173A1 (en) * 1998-09-11 2006-07-13 Beck Christopher Clemmett M Method for routing transactions between internal and external partners in a communication center
US20050002515A1 (en) * 1999-07-13 2005-01-06 Mewhinney Brian E. Dialing techniques for a contact center
US20060165066A1 (en) * 2000-01-07 2006-07-27 Aastra Intecom Inc. Customer communication service system
US7406515B1 (en) * 2000-06-27 2008-07-29 Aspect Communications System and method for automated and customizable agent availability and task assignment management
US20110153375A1 (en) * 2000-08-18 2011-06-23 The Crawford Group, Inc. Method and System for Managing Rental Vehicle Reservations with User Authorization Limits
US20060147026A1 (en) * 2000-10-23 2006-07-06 Mci, Inc. Retrieval of data related to a call center
US20040083195A1 (en) * 2002-10-23 2004-04-29 Mccord Alan Wayne Method and system for enabling automated and real-time discovery of skills available to agents and systems in a multimedia communications network
US6973176B1 (en) * 2003-09-30 2005-12-06 Avaya Technology Corp. Method and apparatus for rotating auto reserve agents
US20050228723A1 (en) * 2004-04-08 2005-10-13 Malik Dale W Conveying self-expiring offers
US20060116918A1 (en) * 2004-12-01 2006-06-01 Flora Joel L Network scheduler with linked information
US20070015518A1 (en) * 2005-07-15 2007-01-18 Agilis Systems, Inc. Mobile resource location-based customer contact systems
US20100111288A1 (en) * 2008-11-06 2010-05-06 Afzal Hassan Time to answer selector and advisor for call routing center
US20100138534A1 (en) * 2008-11-25 2010-06-03 Rishi Mutnuru Systems and methods for monitor an access gateway
US20120213356A1 (en) * 2009-06-01 2012-08-23 Shashkov Georgiy N System and Methods for Predicting Future Agent Readiness for Handling an Interaction in a Call Center
US20120116830A1 (en) * 2010-11-05 2012-05-10 Timetrade Systems, Inc. Availability-Based Contact Routing and Scheduling System
US20120321070A1 (en) * 2011-05-25 2012-12-20 Echopass Corporation Systems and methods for managing multi-tenant callback services
US20130051546A1 (en) * 2011-08-26 2013-02-28 Lance Fried Network predictive customer service queue management

Similar Documents

Publication Publication Date Title
US10645190B2 (en) System and method for predictive live interaction offering and hosting
US10171669B2 (en) System and method for routing interactions for a contact center based on intelligent and dynamic routing considerations
US9712671B2 (en) Method and apparatus for intent prediction and proactive service offering
US9350867B2 (en) System and method for anticipatory dynamic customer segmentation for a contact center
US9781270B2 (en) System and method for case-based routing for a contact
AU2020264378B2 (en) Adaptable business objective routing for a contact center
US20180124246A1 (en) System and method to select a resource in an enterprise
US10382628B2 (en) System and method for routing work requests to a resource group of an enterprise
US9871923B2 (en) System and method for managing resources
US20210075750A1 (en) Method for controlling display of a consultation session
US20110191134A1 (en) Contact offer time for agents supporting contact centers
WO2015009281A1 (en) System and method for predictive live interaction offering and hosting
CN113379229A (en) Resource scheduling method and device
WO2018064178A1 (en) System and method for distributed dynamic resource commitment
US20230186317A1 (en) Systems and methods relating to managing customer wait times in contact centers
US20140189509A1 (en) Passive interaction guide system and method
WO2023122256A1 (en) Techniques for optimizing assistance channel routing
KR20230078624A (en) Communication server apparatus and method for allocating resources to service requests related to shared economy on-demand services or asset provision
CN114189590A (en) Session regulation and control processing method, system, equipment and medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13889463

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13889463

Country of ref document: EP

Kind code of ref document: A1