KR20170048366A - System and method for case-based routing for a contact center - Google Patents

Abstract

Systems and methods for case-based routing in contrast to atomic interaction routing. The processor opens the case in the customer database. A case is associated with a workflow where there are steps that are expected to be performed on the case. The processor identifies the first and second steps of the workflow and further identifies the personnel with the skill to process the first and second steps. The processor generates at least a task for processing the first phase of the workflow and sends a command to route the task to the identified personnel.

Description

[0001] CASE-BASED ROUTING SYSTEM AND METHOD FOR CONTACT CENTER [0002] SYSTEM AND METHOD FOR CASE-BASED ROUTING FOR CONTACT CENTER [

Customer-centric organizations need to seamlessly integrate their operations with customer intelligence to ensure a 360-degree view of the customer that is complete and actionable. All interactions are generally viewed as opportunities to improve the customer experience through superior service, which improves satisfaction, loyalty and retention. If done correctly, this will ensure a high success rate on both profit-based and nonprofit-based businesses and services.

To this end, various types of inbound and outbound interaction (e.g., conventional voice-over-IT, email, web chat / IM, SMS / MMS, video, fax, Based, or hybrid (cloud-based) customer interaction management platform that handles a wide variety of resources (eg, contact center agents, back office, expert / knowledge workers, branch offices, - service operations, outsourced operations, etc.). Clients can work with multiple types of individuals (e.g., contact centers, knowledge workers, back-office staff, etc.) and multiple channels (e.g., contact center / IVR, proactive engagements, , Mobile, etc.) through the platform.

In one embodiment, the customer interaction management platform incorporates a contact center, a personnel station, and, optionally, a customer relationship management (CRM) server. Typically, the contact center, agent station, and customer relationship management server are coupled through one or more networks, which may be the Internet, a private network, or a telephone network. The customer relationship management server may be physically located within the contact center, maintained by a third party, or remote from the contact center and still operational. The end-user interaction requesting management is routed from the CRM server, for example, for processing by contact center personnel. In one exemplary operating scenario, the contact center implements and maintains an object-based agent state model that includes data such as agent identification, work flow assignments, media function descriptions, and state elements associated with communications and media elements. The elements of this agent state model are dynamic and updated in real time as the agent proceeds to receive or initiate the interaction and use one or more multimedia applications to communicate with the end user.

Routing of interactions typically involves sending control signals to one or more agent queues (as opposed to the media portion of the interaction itself, which is typically not routed). There may be queues associated with certain types of interactions, and there may be dedicated queues associated with the skill or other characteristics of the agent. In general, routing logic assigns interactions to agents based on configured logic such as the longest idle agent, least-occupied agent, skill level, and so on. In alternative scenarios, the interaction is routed to the agent queue, where the interaction is picked up by a person with the appropriate skill level and availability to provide the necessary communication with the available personnel and customers associated with it. A hybrid approach may be implemented where the agent may include a personal workbench where deferrable interactions (e.g., responding to e-mail or customer letters, other activities such as actively contacting the customer, etc.) Associated; In this mode, the agent is usually free to decide what to do next. Agents use workbenches to store interactions that they started and want to continue working on later. Interactions can also be distributed to the workbench by the routing server. A workbench is generally like a queue in that it is associated with a specific agent, but maintains interaction. A shared group workbench can be used by multiple agents in a group or place. The agent can view the contents of the workbench and pull the interaction in any order. Thus, in scenarios where the agent has the flexibility to choose an interaction, an agent typically has some details about the queue, including all the interactions that they are assigned to handle (for example, the number of interactions in the queue, Average latency, or service level). Although agents have the opportunity to interact with identifiable or visible interactions, interaction processing in queues is generally automated. In the latter case, and given the choice (which may be limited by service level or other policy), the agent can choose the interactions that are the easiest to solve or choose the contact they are most familiar with. In general, an agent is trained for a specific activity / task, some of which may be scheduled for processing by an agent based on a specified "skill" attribute that may be activated or deactivated at a particular time, for example. Also, as certain customer interactions progress, the customer may be transferred from one agent to another due to the business process workflow instructions, or because of the other reasons, because the first agent can not address the customer's needs. Although agent switching is sometimes required, it is desirable to avoid or reduce the impact of the context switch, especially if a particular agent knows the previous contact history and may be able to handle the expected follow-up.

In a typical interaction, the contact center agent assignment logic preferably routes the inbound interaction to the determination that the system is the "best" or target agent. Agents typically have one or more criteria, such as availability, share, static customer segment, priority, skills needed to handle interactions of a particular media type, agent capability, customer interaction history (e.g., last agent routing) , Upward or cross-sell opportunities, agent skill, and so on.

While this technique works, it is desirable to provide an improved contact center routing strategy.

Embodiments of the present invention are directed to a system and method for case-based routing in a contact center. The processor opens the case in the customer database. A case is associated with a workflow that has steps that are expected to be performed on the case. The processor identifies the first and second steps of the workflow and further identifies the personnel with the skill to process the first and second steps. The processor sends an instruction to at least create a task to process the first phase of the workflow and route the task to the identified personnel.

According to one embodiment, the case is a record that contains the history of the interaction that occurs in the case.

According to one embodiment, the case is associated with a case ID, and the instruction to route the task includes a case ID.

According to one embodiment, the processor retrieves the history of the interaction associated with the case based on the case ID and displays the history of the interaction on the agent device for the identified agent.

According to one embodiment, the processor creates a second job for processing the second phase of the workflow and sends a command to route the second job to the identified personnel.

According to one embodiment, the processor monitors a trigger event, and the creation of a task is based on the occurrence of a trigger event being detected.

According to one embodiment, the trigger event is an elapse of a set time period between two workflow steps.

According to one embodiment, the trigger event is a predetermined date.

According to one embodiment, the processor retrieves an identification of a first customer segment to which a customer associated with the case belongs. The first customer segment is associated with a first goal of the contact center. The processor predicts the result of the work being processed by the personnel according to the first customer segment. The processor also identifies the second customer segment based on the predicted result and reassociates the customer with the second customer segment. According to one embodiment, the second customer segment is associated with a second target of the contact center different from the first target. The task is then processed according to the second goal instead of the first goal.

According to one embodiment, the processor identifies the first and second targets of the contact center, wherein the first target is identified as being more important to the contact center than the second target. The processor determines whether the agent has the skill needed to achieve the first goal and determines the success probability of the first agent when the first goal is achieved. The processor also identifies a second agent for processing the second target, and the second agent also has the skill to process the first and second steps of the workflow associated with the case. The processor determines the success probability of the second agent in achieving the second goal that is greater than the success probability of achieving the first goal by the agent by the second agent. The processor sends a command to route the task to the second agent and prompts the second agent to pursue the second goal.

These and other features, aspects and advantages of the present invention will become more fully understood when considered in connection with the following detailed description, the appended claims and the accompanying drawings. Of course, the true scope of the invention is defined by the appended claims.

Embodiments of the present invention are directed to a system and method for enhanced interaction processing in a contact center. In this regard, the processor detects pending interactions with the customer. In response to detecting the pending interaction, the processor retrieves an identification of the first customer segment to which the customer belongs. The first customer segment is associated with a first goal of the contact center. The processor predicts the result of the pending interaction and identifies the second customer segment based on the predicted result. The processor again associates the customer with a second customer segment, wherein the second customer segment is associated with a second target of the contact center, different from the first business goal. The processor processes the pending interaction according to the second target instead of the first target.

According to one embodiment, predicting the outcome of the pending interaction includes predicting the outcome of the business opportunity presented to the customer by the processor. A business opportunity can be a cross-selling or up-selling opportunity of a product or service.

According to one embodiment, the processor evaluates a number of factors associated with the pending interaction, and the identification of the second customer segment is based on the evaluated factors.

According to one embodiment, the predicted outcome of the pending interaction is matched with the set of criteria for the second customer segment.

According to one embodiment, the predicted result is associated with a second goal of the contact center.

According to one embodiment, the second goal includes a business opportunity not included in the first goal.

According to one embodiment, the pending interaction is to achieve the steps of the workflow associated with the case, and the agent selected to handle the pending interaction is the agent with the skill to handle the next step of the workflow.

According to one embodiment, the second customer segment is also associated with a third target, wherein the second target is identified as being more important to the contact center than the third target. The processor identifies the first agent for processing the second target and determines the success probability of the first agent in achieving the second target. The processor identifies a second agent for processing the third target and determines the success probability of the second agent in achieving the third target. If the probability of success in achieving the third goal by the second agent is greater than the success probability of achieving the second objective by the first agent, the processor sends an instruction to route the pending interaction to the second agent . The processor also prompts the second agent to pursue the second goal.

These and other features, aspects and advantages of the present invention will become more fully understood when considered in connection with the following detailed description, the appended claims and the accompanying drawings. Of course, the true scope of the invention is defined by the appended claims.

Embodiments of the present invention are directed to a system and method for enhanced interaction processing in a contact center. The processor detects pending interactions with the customer. The processor identifies the first and second targets of the contact center in response to detecting a pending interaction, wherein the first target is identified as being more important to the contact center than the second target. The processor identifies the first agent for processing the first goal and determines the success probability of the first agent in achieving the first goal. The processor identifies a second agent for processing the second target and determines the success probability of the second agent in achieving the second target. If the success probability of achieving the second goal by the second agent is greater than the success probability of achieving the first goal by the first agent, the processor sends an instruction to route the pending interaction to the second agent. The processor also prompts the second agent to pursue the second goal.

According to one embodiment, the first goal is associated with a first business result that is determined to be more desirable to the contact center than a second business result associated with the second goal.

According to one embodiment, the business results are related to the revenue, sales or sales of the contact center.

According to one embodiment, the business results are related to customer satisfaction.

According to one embodiment, the probability of a first or second agent achieving a first or second goal is determined based on an analysis of the historical performance of the first or second agent with respect to the first and second targets .

According to one embodiment, the second goal is associated with a business opportunity to be presented to the customer. A business opportunity can be an opportunity to cross-sell or up-sell a product or service.

According to one embodiment, the pending interaction is to accomplish the steps of the workflow associated with the case, and the selected agent to handle the pending interaction is the agent with the skill to handle the next step of the workflow.

According to one embodiment, in response to detecting a pending interaction, the processor retrieves an identification of a first customer segment to which the customer belongs, wherein the first customer segment is associated with a third target of the contact center. The processor predicts the result of the pending interaction and identifies the second customer segment based on the predicted result. The processor re-associates the customer to the second customer segment. According to one embodiment, the second customer segment is associated with a second target.

These and other features, aspects and advantages of the present invention will become more fully understood when considered in connection with the following detailed description, the appended claims and the accompanying drawings. Of course, the true scope of the invention is defined by the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS For a more complete understanding of the disclosed subject matter and advantages thereof, reference is now made to the following description taken in connection with the accompanying drawings, in which:
1 is a block diagram of a customer interaction management platform in which the techniques described herein may be practiced;
2 is a block diagram of a contact center system in accordance with one embodiment of the present invention;
3 is a block diagram of a telephone-based computing infrastructure, such as a contact center, in which the techniques described herein may be practiced;
Figure 4 is a block diagram of an alternative SIP based environment in which a customer interaction management platform is used;
Figure 5 is a detailed block diagram of a hybrid (pre-cloud) environment in which one skilled in the art can make the teachings of the present disclosure;
6 is a detailed block diagram of another hybrid cloud based communication system in which the techniques of the present invention may be implemented;
Figure 7 is a process flow diagram illustrating a dynamic customer segmentation routing scheme in accordance with the present invention;
8A-8B are flow diagrams of a process for adaptive business objective routing in accordance with the present invention;
9 is a diagram illustrating a case routing plan according to the present invention;
Figure 10 is a process flow diagram illustrating how two or more routing plans may be performed concurrently or sequentially to improve contact center agent assignment logic;
11A is a block diagram of a computing device according to one embodiment of the present invention;
11B is a block diagram of a computing device according to one embodiment of the present invention;
Figure 11C is a block diagram of a computing device according to one embodiment of the present invention;
11D is a block diagram of a computing device according to one embodiment of the present invention; And
11E is a block diagram of a network environment including some computing devices in accordance with an embodiment of the present invention.

In general, embodiments of the invention relate to a customer interaction management platform that uses a set of one or more interactive routing strategies to determine which agent should receive and process a particular contact. The platform includes an agent assignment mechanism that is complemented to implement one or more sets of routing plans. The first routing plan actively coordinates the customer service level at which the agent assignment mechanism is implemented. The second routing plan operates during a predetermined interaction using an agent assignment mechanism to automatically adjust which of the set of business goals should be handled by available personnel. The third routing plan provides one or more parameters associated with the case to the agent assignment mechanism to facilitate assignment. Such a routing strategy may be performed in whole or in part simultaneously or sequentially.

One or more routing strategies may include a "dynamic customer segmentation" strategy that provides an assessment or a priori reassessment of the customer's existing customer segmentation (e.g., gold, silver, bronze, etc.) Based on the anticipated outcome of the customer interaction processing of the customer, the customer's segmentation relevance (for new interactions) should be promoted or demoted. For example, if this expected result promotes the customer to the next higher segment, the current interaction can be processed according to the policy of this higher level segmentation. Promotion or demotion of customer segmentation associations can be context-dependent and can be performed on a per-interaction basis or for a number of interactions.

Another routing strategy is to implement an "Adaptive Business Objective" strategy that is based on business objective (BO) mediation during the Agent Assignment process, in part, without relying on predefined or configured fixed or static business objectives . In this approach, the business objective is made up of two components: the reason for the interaction (potentially improved through the IVR dialog) and a set of business opportunities (eg, cross-sell / up-sell) that change based on the known customer profile . Given these factors, a set of business objectives is defined for the customer. Routing logic during the agent selection process finds the most appropriate agent to handle both elements and begins with the first (best) business objective. If no such agent is found, then the next best BO is used, and this continues until the appropriate agent has processed the interaction according to the (potentially adjusted) BO. The BO-agent pair is then rated based on the probability that a particular agent will succeed when processing a particular BO. According to one embodiment, agents with the highest rating are selected and the interaction is routed to the agent to process the associated BO.

Another routing strategy implements a "case routing" strategy at least partially determined in a "case record" associated with interactions such as (but not limited to) CRM-sourced interaction. A CRM system or server or other customer database system (collectively referred to as a CRM system) that is or is a component of a contact center models the customer support interaction (between the customer and the system) as a "case". The case (or "ticket") is associated with the case, the type of it, the predefined workflow into the potential solution (through a defined or ordered set of steps), expected timing, escalation path, Have a case record. Depending on the CRM system in which the case occurs, the case may be associated with a particular template depending on the nature of the customer support issue. In case routing, the case history associated with the case is used to influence which agent should be identified in the set of agents in the contact center to resolve the case. Without limitation, the identity of the step in the processing of the next specified interaction or case (as defined by the case workflow), preferably by the same agent, and (for example, One or more anticipated future interactions for a given case (based on dynamic adjustments based on predefined steps in accordance with the flow and / or the expected outcome of a particular step), one or more pre- In the presence, the best or target agent is selected based on one or more factors, including whether or not any such interaction has been resumed, the remaining completion time of the case, and the like.

According to a feature of the invention, the routing techniques described above can be used alone or in combination. Thus, in one embodiment, a dynamic customer segmentation strategy is implemented in association with an adaptive business goal strategy or case routing. In another embodiment, the adaptive business goal strategy is implemented in association with case routing. Another alternative is to combine all three of the strategies described above. This routing strategy can be performed in whole or in part simultaneously (synchronously) or sequentially (asynchronously).

Figure 1 illustrates a customer interaction management platform 100 that may be a cloud-based, premise-based, or hybrid implementation. The platform may be operated by a dedicated service provider but is not required. In general, the platform 100 handles all types of interactions, whether inbound or outbound. As shown, these interactions include voice, email, web, chat / IM, SMS, video, fax / work items, and the like. Interactions are delivered to a variety of resources such as call centers, outsourcers, back offices, experts (knowledge workers), branch offices, self-service capabilities, Preferably, the platform includes a configuration layer that provides configuration, data integrity control, access control and runtime notification, a management layer (e.g., solution control, etc.) that allows the customer to monitor the operation and status of applications running on the platform, A framework that includes a set of operating layers, such as a service layer that provides state and statistics, and a media layer that provides external interfaces, provides switch independence for applications and provides data distribution, and a service layer that provides state and statistics. .

2 is a schematic block diagram of a system supporting a contact center providing contact center services in accordance with an embodiment of the present invention. A contact center can be a business or an in-house facility that serves a business that performs sales and service functions with respect to products and services offered through the enterprise. In another aspect, the contact center may be a third party service provider. The contact center may be located in equipment dedicated to an enterprise or a third party service provider and / or may be remote computing, such as a private or public cloud environment having an infrastructure to support multiple contact centers for multiple companies, for example. Environment. The various components of the contact center can be distributed across multiple geographical locations and computing environments and may not necessarily be included in a single location, computing environment, or computing device.

According to one exemplary embodiment, the contact center includes resources (e.g., personnel, computers, and communications equipment) that enable the delivery of services via telephone or other communication mechanisms. These services may vary depending on the type of contact center and may vary from customer service to help desk, emergency response, telemarketing, order processing, and so on.

A customer, prospective customer, or other end user (collectively referred to as a customer) who desires to receive service from the contact center receives the inbound to the contact center via end user devices 10a through 10c (collectively referred to as 10) A call can be started. Each of the end user devices 10 may be a conventional communication device in the art such as, for example, a telephone, a wireless telephone, a smart phone, a personal computer, an electronic tablet and / or the like. A user operating the end user device 10 may initiate, manage and respond to phone calls, email, chat, text messaging, web browsing sessions, and other multimedia transactions.

Inbound and outbound calls with the end user device 10 may traverse the telephone, cellular and / or data communication network 14 depending on the type of device used. For example, communication network 14 may include a public or private switched telephone network (PSTN), a local area network (LAN), a private wide area network (WAN) and / or a public wide area network such as the Internet. The communication network 14 may also include a wireless carrier network that includes a Code Division Multiple Access (CDMA) network, a Global System for Mobile Communications (GSM) network, and / or any 3G or 4G network as is conventional in the art. have.

According to one embodiment, the contact center includes a switch / media gateway 12 coupled to the communications network 14 for receiving and transmitting calls between the end user and the contact center. The switch / media gateway 12 may include a telephony switch configured to function as a central switch for agent level routing within the center. In this regard, the switch 12 may be an automatic call distributor, a private branch exchange (PBX), an IP-based software switch, and / or an Internet-source call and / And any other switch configured to receive. According to one embodiment of the present invention, the switch is coupled to a call server 18 and the call server 18 can be used as an adapter or interface between, for example, the switch and other call processing components of the remaining routing, monitoring and contact centers Function.

The contact center may also include a multimedia / social media server for participating in media interactions other than voice interaction with the end user device 10 and / or the web server 32. Media interaction may be, for example, about email, vmail (voicemail via email), chat, video, text messaging, the web, social media, Web server 32 may include social interaction site hosts for various known social interaction sites to which end users such as Facebook, Twitter, etc. may subscribe. The web server may also provide a corporate web page supported by the contact center. The end user can browse the web page and get information about the company's products and services. The web page may also provide a mechanism for contacting the contact center via, for example, web chat, voice call, e-mail, Web real-time communication (WebRTC)

According to one embodiment of the present invention, the switch is connected to an interactive media response (IMR) server 34, which may be referred to as a self-help system, a virtual assistant, . The IMR server 34 may be similar to an interactive voice response (IVR) server, except that the IMR server can cover a variety of media channels, including voice, without being limited to voice. However, as an example of voice, the IMR server can be configured with an IMR script to query the customer's needs. For example, a bank's contact center can notify the caller if they want to check their account balance via an IMR script, "Press 1". In this case, the ongoing interaction with the IMR allows the customer to complete the service without talking to the agent. The IMR server 34 may also provide open questions such as, for example, "How can I help you ?, " and the customer may enter a reason for contacting the contact center or enter another reason. The customer's response is then used by the routing server 20 to route the call to the appropriate contact center resource.

If the call is to be routed to the agent, a call is delivered to the call server 18 interacting with the routing server 20 to find the appropriate agent to process the call. The call server 18 may be configured to process PSTN calls, VoIP calls, and the like. For example, the call server 18 may include a session initiation protocol (SIP) server for processing SIP calls. According to some exemplary embodiments, the call server 18 may be configured to provide the caller 18 with an automatic number identification (ANI) number or a customer's internet protocol (IP) address or e-mail address, You can extract data about customer interaction.

In some embodiments, the routing server 20 stores information about an existing client, such as contact information, Service Level Agreement (SLA) requirements, the nature of previous customer contacts, and the actions that the contact center took to resolve customer issues You can query the customer database. The database can be managed by conventional database management systems in the industry such as Oracle, IBM DB2, Microsoft SQL Server, Microsoft Access, PostgreSQL, MySQL, FoxPro and SQLite, and can be stored in the mass storage device 30. The routing server 20 may query customer information from the customer database via ANI or any other information collected by the IMR 34 and may be transmitted by the call server 18 to the routing server.

Once the appropriate agent is available to handle the call, a connection is made between the caller and the identified agent's agent devices 38a-39c (collectively referred to as 38). The information collected about the caller's and / or the caller's history information may be provided to the agent machine to assist the agent in order to better serve the call. In this regard, each of the agent devices 38 may include a telephone suitable for regular telephone calls, VoIP calls, and the like. Agent machine 38 may also include a computer for communicating with one or more servers of the contact center, performing data processing related to contact center operations, and for interfacing with customers through voice and other multimedia communication mechanisms.

The selection of the appropriate agent for routing the inbound call may be based, for example, on the routing strategy employed by the routing server 20 and may include, for example, the availability of the agent provided by the statistical server 22, May further be based on information about other routing parameters.

The contact center may also include a reporting server 28 configured to generate reports from the data collected by the statistical server 22. Such reports may include near-real-time reports or historical reports of the status of the resource, such as average latency, abandonment rate, agent occupancy, and the like. The report can be generated automatically or in response to a specific request of the requester (e.g., agent / manager, contact center application and / or the like).

According to one embodiment of the present invention, the routing server 20 is enhanced with the ability to manage back office / offline activities assigned to agents. These activities may include, for example, responding to emails, responding to correspondence, attending educational seminars, or other activities that do not involve real-time communication with customers. Once assigned to an agent, the activity may appear as an action to be completed by the agent in the agent's workbenches 26a-26c (collectively indicated at 26) as an action that may be pushed to the agent or completed by the agent . An agent's workbench may be implemented via any conventional data structure in the art, such as, for example, a linked list, an array, and / or the like. The work bean can be maintained, for example, in the buffer memory of each agent machine 38.

In accordance with one embodiment of the present invention, the mass storage device (s) 30 may store agent data (e.g., agent profiles, schedules, etc.), customer data (e.g., customer profiles) For example, the details of each interaction with the customer, including the reason for the interaction, processing data, latency, processing time, etc.). According to one embodiment, some data (e.g., customer profile data) may be provided by a third party database, such as a third party customer relationship management (CRM) database. The mass storage device may take the form of a hard disk or disk array as is conventional in the art.

The various servers in FIG. 1 may each include one or more processors that execute computer program instructions and interact with other system components to perform the various functions described below. The computer program instructions are stored in a memory implemented using standard memory devices, such as, for example, random access memory (RAM). The computer program instructions may also be stored on other non-volatile computer readable media, such as, for example, CD-ROMs, flash drives, and the like. Further, although the function of each server has been described as being provided by a particular server, it is to be understood that the functions of the various servers may be combined or integrated into a single server, or that the functionality of a particular server does not depart from the scope of embodiments of the present invention Those skilled in the art will appreciate that the invention may be distributed across one or more other servers.

In various embodiments, the term interaction includes, but is not limited to, telephone calls (PSTN or VoIP calls), emails, vmails (voice mail via email), video, screen sharing, text messages, Real-time and non-real-time interactions using any communication channel, including, for example, the Internet (e.g., WebRTC calls), and the like.

3 illustrates a typical customer interaction management platform 250 that interacts with a telephony infrastructure such as the PSTN 252, in accordance with another embodiment of the present invention. In this embodiment, platform 250 includes switch 254, IVR 256, telephony server 258, and agent desktop set 260.

4 illustrates that a customer interaction management platform 300 interacts with the PSTN 302 and the VoIP gateway 304 and communicates with the SIP server 306, the IVR 308, and the IP- Over-IP embodiment that includes an IP-based softphone 309 or an IP-based softphone 310. The voice-over-

Although not shown, the customer interaction management platform typically includes basic support for all types of standard media such as voice (TDM / VoIP), email, chat, co-browsing, web format and others.

Figure 5 illustrates a hybrid on-premises and cloud-based implementation of a customer interaction management platform. In this embodiment, there are three prime locations 402,404, and 406, each of which is associated with a control server 408 to which agents associated with the platform can be connected. The customer interfaces to the platform via network switch 410. The control server 408 interfaces to a global router 414 that is associated with the network switch and implements a routing strategy for interactive routing. The database server 416 provides an interface to one or more databases 418. An IVR (interactive voice response) unit 412 is associated with the network switch 410, and the IVR can be controlled by its control server 415. The central network routing element is typically located within router 414, which can instruct the network switch to send the call (via server 408) to the IVR; Once the IVR has finished the call it can be terminated or forwarded to the agent. However, the call may be unconditionally transmitted to the IVR, in which case the IVR control server 415 determines whether to terminate or forward to the agent. The former scenario is referred to as the IVR-behind switch, and the latter scenario is referred to as the IVR-in-front. Each control server 408 typically provides various control functions such as agent telephonic state propagation, call control and monitoring, call model integration, inter-site session negotiation (e.g., call forwarding, And provides for a common message bus for other applications. The routing engine in global router 414 provides strategy-driven interaction flow control, referred to herein as a routing strategy. Each premise may be associated with a "state" server 420 that provides platform global agent state / capability data and real-time metric computation. Configuration server 424 provides dynamic configuration management. The management layer 426 provides application monitoring and control, centralized logging, alarms, and the like. This drawing shows direct network-level routing to an agent, but it is not required, because there may be multi-level routing (for example, from a network to a site, from a site level to an agent via a site level router).

Figure 6 is a more detailed structural overview of the communication environment in which the techniques of the present invention may be implemented. In this embodiment, a system is provided that integrates a contact center, a personnel station, and a customer relationship management (CRM) server. This is a typical environment and should not be accepted as limited. In this embodiment, the communication environment 200 includes a public-switched-telephone-network (PSTN) 202, an internet network 207 and a communication or contact center 210. The PSTN network 202 may be another type or configuration of a telephone network. For example, the network 202 may be a wireless network or a combination of wireless and wired networks. Likewise, the network 202 may be a private or public telephone network. If the network is a public PSTN network, it may include a switch 203 that may function as a service control point (SCP). If the network is a private network, it may include a local telephone switch (LSW) 203 for receiving and routing telephone calls within the network. The LSW 203 may be another call switching hardware that may also function as an automated call distributor (ACD), a private branch exchange (PBX), or a service control point (SCP). In this example, the LSW 203 is connected to the communication center 210 via the telephony trunk 205. Also in this example, the LSW 203 is enhanced with computer-telephony-integration (CTI) that runs an instance of the telephony server T-S. The processor 204 provides intelligent telephony and interaction functions to the LSW 203. [ Examples include intelligent peripheral live interactive voice response systems and other similar functions. An instance of a telephony server (T-S) running on processor 204 provides an array of intelligent routing services that can be integrated with CTI and intelligent peripheral functions.

The communication center 210 has a switch (CSW) 211 (such as a PBX or ACD) provided internally and receives an incoming call from the PSTN 202 for internal routing to the communication center personnel and automated help or service system Lt; / RTI > Of course, the CSW 211 also applies to outbound calls. The CSW 211 may be a PBX or other type of telephone switch as described above with reference to the LSW 203. The CSW 211 is connected to the LSW by the telephone trunk 205. Like the LSW 203, the CSW 211 is also connected to the CTI processor 215 that is executed in the instance of the TS server.

The processor 215 preferably uses a separate data network 206 to communicate with the processor 204. In this way, intelligent routing routines can be created and implemented at the PSTN level to perform internal call routing at the network level. The data requested from the caller may be transmitted to the center 210 prior to the actual telephone call by use of the network 206 and the connected CTI processor and T-S instances. Agent level routing may be performed at the network level and may be controlled by the center 210.

The center 210 preferably has a local-area-network (LAN) 218 provided therein and is used to connect multiple workstations and systems together for communication. In this example, a workstation workstation 522 and a workstation workstation 523 having LAN connectivity are shown. The workstation 522 includes general personnel equipment for communication that is not limited to a personal LAN-connected computer 227 having a video display unit (VDU) such as a computer monitor and an agent telephone 226. [ The telephone 226 has connectivity to the CSW 211 via the internal telephone wiring 217. The workstation 523 is adapted to communicate in a manner similar but not necessarily identical to the station 522 by the LAN connection computer 225 and by the agent telephone 224. Additional communication equipment types may be represented within stations 523 and 522; These include, but are not limited to, fax machines, answering systems, other processing terminals, and other types of network-enabled devices. The agent may be a home agent (a person working at his or her home) and may be connected to the contact center via, for example, a voice-over-IP (VoIP) connection. In one embodiment, telephones 224 and 226 may be data phones connected to respective computer hosts as terminal computers. There are as many configuration possibilities and equipment diversity as possible.

The CTI processor 215 preferably has a LAN connection that allows an administrator with administrator rights to modify or create a new routing routine or the like. The functionality of the TS in the processors 215 and 204 depends on the accessibility of the T-Server Library 220 connected to the LAN 218 in this example. Library 550 preferably enables all objects, descriptors, and integrated CTI / transactional intelligent call processing. Typically, a library is an embedded part of a server that uses the library to communicate with other network elements.

Without limitation, the Internet network 207 is part of the communication environment 200. The Internet 207 may be another type of wide area network (WAN). For example, network 207 may be a corporate or private WAN or metro-area-network (MAN). The Internet network 207 is extended there through a network backbone 209 that represents all or part of the equipment, lines and access points that make up the Internet network as a whole, including any connected subnetworks. As mentioned above, there are no geographic or logical limitations.

A customer relationship management (CRM) server 208 is provided or exemplified within the Internet network 207 and manages customer relationships relating to one or more customer bases, such as one hosting communication center 210, . The CRM system or service 208 may be provided by a third party company. Third-party CRM solutions can be implemented on the basis of third-party companies that may include third-party customer care services. Likewise, the CRM server 208 may be part of a customer premise equipment (CPE) solution whereby all or a portion of the customer base is associated with the host company and serviced internally at a particular communication center, such as the center 210. The CRM server 208 may be hosted within the physical domain of the center 210 and connected to the LAN 218. In another embodiment, the CRM system 208 may be configured to service a plurality of geographically distributed contacts of a region or a customer base associated with a communication center of the same enterprise. In this case, a separate but centralized facility may be provided within the domain of the Internet 207, whereby the customers of the multiple centers can be managed according to the policies and rules set at each center.

In this example, the center 210 is a multimedia-enabled communication center with Internet connectivity for communication and interaction with customers and businesses. The IPR 221 is provided in the center 210 and connected to the LAN 218. The IPR 221 is configured to receive multimedia and communication events from the Internet 207 and route such events to a personnel station, such as the station 222 or 223, via the LAN 218. Multimedia events can include email events, web-based interaction, voice-over-IP interaction, web-messaging interaction, multimedia-enabled or text chat sessions, video mail interaction, network conferencing sessions and IP telephony sessions. Thus, organized channels (media channels) and routing systems can be placed to handle this type of network interaction or event. In another embodiment, the CRM system does not directly deal with agents (endpoints), but instead connects to the service provider's media services (e.g., a Genesis T-Server for voice, a Genesis interaction server for multimedia) do. Similarly, one or more Internet servers (not shown) may be provided to host specific network interactions, such as chat or web-meeting. Such a server can be assumed to be provided in the domain of the Internet 207 and is provided in the domain of the Internet 207 and includes the domain of the LAN 218 when connected on-line.

Among other services, the CRM system 208 may be configured to provide automated self-help services, web-format services, email services, automated fax services, and other multimedia services. Likewise, back-end data in the CRM system includes history information; Statistical information; Additional contact information; And links to other resources.

In this embodiment, the CC / CRM adapter system 214 is provided within the communication center 210 and is configured to integrate CRM functionality with agent and call-control / management functions at the level of an agent workstation or desktop. The CC / CRM system adapter 214 is configured to provide integration between the CRM system 208 and the CTI-TS capabilities (processor 215) using one or more dynamic agent state models 213. As noted above, the models 213 represent a collection of agent models that represent the work assignments of these agents assigned to the personal agents, the agent functions, and the domain of the system 214, or in this case, Represent the available personnel through contacting the communication center 210.

Within the system 214, contact center functionality and management as well as CRM service functionality and management can be abstracted and managed and monitored simultaneously in a convenient agent user interface with graphical display capabilities at the agent level. The CRM adapter system 214 has a parent application (not shown) that communicates with client applications that are distributed to agent stations. An instance of the interaction control / agent control (IC / AC) and CRM client interface 228a is provided in the domain of the agent workstation 223 and is executable, for example, as a software instance from the desktop of the computer 223 . An instance of a similar IC / AC / CRM 228b is provided in the domain of the station 223 and is executable as a software instance, for example from the computer 557. [

By executing the instance IC / AC / CRM instance 228a, an agent operating at the station 223 can receive voice and media events, and at the same time, the caller or interaction participant To provide CRM services. The agent state model for the station 223 preferably defines all (or at least a part of) the agent's communication capabilities, including all CRM services available to the customer's personnel, and the personnel associated with the customer. In addition, the model for the agent preferably includes dynamic call and session management including current agent status and presence over multiple media channels including live voice channels. The client instance 228a effectively bridges the CRM and CTI-related services that are specific to the agent model, customer definition, and event objective using the manual and, where appropriate, automated, services and data needed to enhance the transaction experience for both agents and callers .

An agent operating at the station 223 may receive a telephone voice call event from the PSTN 202 via routing via, for example, the CSW 211 and the internal telephone wiring 217. [ The presence of these calls in the system is noted and recorded in the CTI / T-S processor 215 having a connection to the CC / CRM adapter 214 via the processor LAN. In one embodiment, a direct data link (bridge) may be provided between the CTI / T-S processor 215 and the adapter 214. The CC / CRM adapter 214 prompts the CRM system 208 when a communication event associated with the agent station 223 is routed.

During routing, the telephone call is routed to agent telephone 224, while the data relating to the call is routed to computer 225 via LAN 218 and is often discclosed prior to picking up a telephone call. The previous prompt or request made to the CRM 208 by the CTI / TS processor 215 may be sent to an initial machine-to-server connection using a hypertext transfer protocol (HTTP) / simple object access protocol (SOAP) And may be an access line 216 for connecting to the agent desktop 225, in this case routing the connection, using the HTTP protocol to be ready to send data for the sender to the agent desktop 225, And via a network-accessible path defined by LAN 218 and IPR 221. < RTI ID = 0.0 > CRM 108 may be in a monitored state or a connection to the agent system may be connected to the main system at all times.

In a typical operational scenario, the CRM 208 is in a standby state and awaits a request from the agent operating station 223. [ In this scenario, data about the telephone and the caller may arrive at the computer 225 before the call is picked up at telephone 224. When the agent picks up the call, it uses the IC / AC / CRM instance to send a request for specific services and / or data available on the desktop. As an example of a CRM service solution provided by the CRM server 208, a CTI telephony call transfer service and a multi-party connection may be utilized. The CRM server 208 may be prompted to deliver the solution implemented in the CSW 211, such as a multi-party-bridge connection or a meeting where an agent drops out and starts the next call after the agent has initiated the connection.

In another embodiment, a data network telephony (DNT) caller may contact the center 210 using a softphone (IP based) or an internet capable cellular telephone, smartphone, tablet or other device. In this scenario, there may be more media channels available for interactions such as messaging, chat, e-mail, and so on. In the pure DNT sense, the IPR 221 may notify the CC / CRM adapter of an event for the station 223, such as a videoconference using a host server (not shown). In addition, the CRM can set the initial space and format of the meeting for the agent, and the agent can add the specific contact provided by the CRM server 208. This contact can be displayed in the agent's desktop interface's interaction list. Agents can interact and bring new media channels and functionality to dynamic instant interactions.

Preferably, the agent state model 213 is updated during the activity period and rendered into an inactive or non-accessible state when the relevant personnel are not available for communication. When the agent is online, the agent state model is activated and ready for interaction. For example, both the CC / CRM adapter 114 and the agent instances of the IC / AC / CRM 228a are responsible for reporting status data to the appropriate destination.

Agent stations 223 and 223 need not be located within the contact center. As shown, a remote agent may use his or her telephone line and the Internet or a dominant WAN or MAN connection, as long as his or her phone call is routed from the CSW 211. In this example, the roaming agent 229 is shown to have a wireless connection to the LAN 218 (230). Agent 229 may also connect to LAN 218 and cellular telephone using his or her wireless access to implement the invention. Also, preferably all phone calls are routed through CSW 211 or similar CTI-enhanced switches.

Adapter 214 may be a soft adapter running on CTI / T-S processor 215, IPR 221, or some other connected host. In addition, the CRM system 208 may be provided as a third party service or CPE implementation.

Typically, the contact center includes an agent interaction layer configured to provide abstraction of communication center data and CTI data for any particular agent. The abstracted data is used to provide and update the agent state represented in the CC / CRM adapter 214 in the form of an object model.

One or more functions of the technology platform as described above may be implemented in a "cloud-based" architecture. Cloud computing enables on-demand network access to a shared pool of configurable computing resources (e.g., network, network bandwidth, server, processing, memory, storage, applications, virtual machines, and services) Service provisioning model, which can be quickly provisioned and released with minimal administrative effort or interaction with a service provider. Available service models that may be utilized, in whole or in part, include: Software as a Service (SaaS) (a provider's application running in the cloud infrastructure); Platform as a service (PaaS), which includes applications that customers can create using provider tools in the cloud infrastructure; Infrastructure as a service (IaaS), which allows customers to provide their own processing, storage, network and other computing resources and to deploy and run operating systems and applications. A cloud-based platform may include co-located hardware and software resources, or other resources physically, logically, virtually and / or geographically. The communication network used to communicate with the platform services may be packet based, non-packet based, secure or non-secure, or a combination thereof.

More generally, the techniques described herein are provided using a set of one or more computing related entities (systems, machines, processes, programs, libraries, functions, etc.) that facilitate or provide the functionality described above. In a typical implementation, representative machines on which the software is executed include general purpose hardware, an operating system, an application runtime environment, and a set of applications or processes and associated data, networking techniques, etc., which together provide the functionality of a given system or subsystem do. As described, the functionality may be implemented via a standalone machine or a distributed set of machines.

As mentioned above, the front-end of the infrastructure described above also represents a conventional web site (e.g., one or more page sets formatted according to a markup language).

The client device accesses the service provider infrastructure to retrieve content, including HTML, media players, video content, and other objects, as described. Typical client devices are personal computers, laptops, mobile devices, tablets, and the like. Typical mobile devices are Apple iPad® or iPad5, iPad Mini, Android ™ -based smartphones or tablets, Windows®-based smartphones or tablets. This type of device typically includes any Intel- or AMD- (or other) -based chip, a computer memory 304 such as RAM, and a central processing unit (CPU) such as a flash drive. Device software includes the operating system (for example, Apple iOS, Google® Android ™, etc.), general support applications and utilities. The device may also include a graphics processing unit (GPU) and a touch sensitive device or interface configured to receive input from a user's touch. The touch sensing device is typically a touch screen. The mobile device includes appropriate programming to facilitate gesture-based control in a manner known in the art. Clients are not limited to mobile devices because they can be traditional desktops, laptops, or other Internet-accessible devices running Internet browsers, Internet Explorer, FireFox, Safari, Chrome, Content retrieved to the client may be rendered in a browser, mobile app, or other rendering engine.

Improved Routing Techniques

In the context of a content center (or, more generally, a customer interaction management platform), routing generally refers to the process of sending an interaction to a target. The routing "strategy" commands how to handle and direct interactions in different situations. In addition to selecting a target, the concept of routing can include determining interaction characteristics such as type (voice, email, chat, etc.), priority, customer segment, service type, target SLA, Routing strategies can be created in the development environment using tools such as the Genesys® Interaction Routing Designer (IRD), which allow users to test, modify, and load routing strategies. Genesys Universal Routing Server (URS) is a server that implements the routing strategy developed in this way, in particular using routing strategy commands. The following techniques may be implemented within the contact center personnel assignment logic or in association with contact center personnel assignment logic. More generally, the contact center agent assignment mechanism limits one or more various agent mechanisms including skill-based routing, business priority-based routing, sharing agents by service level-based routing, cost-based routing and other known . The contact center agent assignment mechanism may be augmented to include one or more of the enhanced routing techniques described in the present invention. A representative but non-limiting platform for implementing these agent assignment functions is the Genesys Orchestration Server (ORS). The server provides session-based routing and integrates other back-end contact center functions with other contact center systems, servers, programs and processes.

Any of the functions described herein may be implemented in a corporate environment, a cloud-based environment, or a hybrid (a combination of cloud and enterprise) environments.

The following sections describe various routing (contact-to-agent) tasks that may be implemented to provide enhanced agent assignment in accordance with the present invention (or more generally to increase such existing agent assignment mechanisms) )) Method or strategy. As mentioned above, these routing methods are sometimes referred to as "dynamic customer segmentation", "adaptive business goal routing", and "case routing". This nomenclature is provided for illustrative purposes only and should not be considered limiting. As will be appreciated by those skilled in the art, two or more of the routing techniques described above may be used together. Accordingly, in one embodiment, a dynamic customer segmentation strategy is implemented in association with an adaptive business goal strategy or case routing. In another embodiment, the adaptive business goal strategy is implemented in association with case routing. Another embodiment is to associate (combine) all three strategies described above. The routing strategy may be performed wholly or partially or concurrently or sequentially. More generally, two or more of these routing strategies may be implemented asynchronously to each other or synchronously with respect to each other. These can be configured or specified using development / configuration tools such as those described above.

Expected dynamic customer segmentation routing

As is known, when a customer intends to contact a contact center, the contact center is typically based on the current customer segment (or association), such as gold, silver, bronze, etc. (regardless of how the segment can be specified) Apply the policy. According to one embodiment, the customer segment reflects the customer ' s ' value ' to the company, and the ranking generally refers to a preferred or enhanced level of care or service ("service level"). In this regard, customer segment identification may be considered an identification of a service level that desires to be provided to a customer belonging to a customer segment. For example, a silver customer's currency may be connected to an IVR system while the gold customer's currency is directly connected to the actual agent. In addition, various business objectives can be identified for interaction with customers based on customer segment identification. These business goals can be related to customer satisfaction and / or business results. For example, a silver customer's business objective might be to earn a specific NPS score and / or to finalize a deal for a particular business opportunity offered to a silver customer. The gold customer's business objective is to close the deal on business opportunities that are offered to Gold customers and / or to a higher NPS score.

The current customer segmentation of the contact center as described above is relatively static and generally considers the customer's current and potential future value for the company. Even if segmentation associations of customers are evaluated in existing systems, they are typically post-reviewed (and potentially adjusted), especially as a result of given (past) interactions. According to these existing systems, the new segment associativity becomes effective for future interactions.

According to the dynamic customer segmentation system according to the embodiment of the present invention, the service level of the customer is actively and potentially active, for example, prior to a particular new interaction (or a new set of interactions) . According to one embodiment, the dynamic customer segmentation process is invoked in response to detecting a current interaction with a customer. An interaction can be an atomic interaction or an interaction associated with a particular case. One or more static and / or dynamic factors may be considered when actively adjusting the customer's service level. For example, one or more of the static and / or dynamic factors may be taken into account to allow the customer to move from a current granularity state (e.g., as stored in a customer record) to a higher granularity state (e.g., Can promote customers (promotion). According to one embodiment, the expected outcome of a pending interaction can be predicted based on one or more dynamic factors, for example, to promote or not to associate an associated customer segment at the start of interactive processing. For example, an a priori decision on whether to treat a silver customer, for example, as being treated as a gold customer, may lead to a consequence (for example, repair of a proposal related to a business opportunity) Which is actually matched to the customer's gold classification criteria. If the probability of success is above a certain threshold, a silver customer can be treated as a gold customer and, depending on the set of business goals for a gold customer, a business opportunity that might not be presented as a silver customer in some cases may be presented.

Static factors that may be considered when reassessing a customer segment include, for example, customer profile changes, changes in a customer's business set, business by contact center or web monitoring records, etc., and based on prior interactions with others A change in applied criteria, an expected actual impact of a person (e.g., for social media interaction). For example, a customer who is likely to have a high impact on his or her social media network can be promoted from a customer segment.

With regard to changes in customer profiles, for example, customers have moved to a more prominent geographic location, recently purchased a home, changed marital status, and / or changed their occupations / It can be considered as a factor to move the customer up or down in the segment.

With respect to changing a customer's business set, an entity may change the list of criteria / characteristics within the customer model that is used to evaluate the customer segment. For example, a company may add or remove factors such as "klout score" (social media popularity / impact), and / or remove factors such as "TV ownership" This is not a differentiating factor in giving different treatment.

Regarding the change in the criteria applied when a customer decides a customer segment, the entity must determine whether a regulation (eg, Basel 3 for banks), a revaluation of previous criteria (eg, a previous bad / (Gold, silver, bronze) based on new statistical results (e.g., which may gradually improve), or new statistical results (e.g., other associations between gender / age and driving safety).

Exemplary dynamic factors that may be considered for reassessing customer segments include new business proposals (s) that may be of interest to the customer, cross-sell / up-sell opportunities during a given interaction (depending on interactions / media channels) Availability of agents that are both skilled (for example, highly skilled) agents for cross-customer / up-sell offerings at the same time as a given customer, and other side effects of a given interaction such as visibility to social communities or similar . For a new business offer, a particular service or product with an associated criteria for a Gold / Silver / Bronze customer may be identified as having a particular customer interest during the current interaction. For example, a customer may explicitly indicate interest in a service or product. The customer may be reassigned to the customer segment according to the identification of the product and / or related criteria. The reallocation may be, for example, a general reassignment, or a subset of the proposal.

For cross-sell / up-sell opportunities, conversations between agents and customers can proceed smoothly and open up unexpected opportunities for promising cross-sell / up-sell, The customer is treated as gold). In this case, the customer can be dynamically reassigned to an upper customer segment.

For the availability of highly skilled (eg highly skilled) agents for cross-selling / upselling, these agents can be booked to handle calls from gold customers. A particular one of the reserved agents may be suitable to handle the current interaction with a particular silver customer. In this case, the Silver customer can be treated as a Gold customer and the pending interaction for that customer can be delivered to the scheduled agent.

According to one embodiment, the new interaction with the customer may trigger a re-evaluation of the customer segment based on one or more of the static and / or dynamic factors described above before determining how the new interaction should be handled. Typically, the primary use case for dynamic customer segmentation is a "promotion" in which a customer is promoted to the next higher customer segment, thereby promoting the customer to the next highest customer segment, but one or more of these triggers (typically dynamic reasons) May be a reason for demotion to a lower level (e.g., the next lowest) than the refinement status for the customer stored in his or her customer record. Dynamic reasons for demotion include, for example, the knowledge that the agents capable of providing services to customers are not more appropriate than the current customer segments, the high interaction with customers who will cross a given customer, the best fit for a given customer Non-availability of media channels, and / or the like.

In one embodiment, a result of the demotion in the customer segment may be that the business opportunity associated with the superior customer segment is bypassed. As a result, if an agent that is not suitable for the current customer segment handles the interaction with the customer, then releasing the customer to the lower customer segment before the agent can handle the interaction can prevent the agent from presenting the business opportunity , It would not have been successful if it was presented by a specific agent.

According to one embodiment, for an incoming interaction, the routing strategy begins with an a priori reevaluation of the customer segmentation in response to receipt of the incoming interaction. Depending on the result, the processing of the dynamically determined segment is applied to some configurable interaction set and proceeds for a period of time. And so on. As noted above, reassessment (or initial evaluation) may be based on one or more static factors (not related to a given new interaction (s)) and / or one or more dynamic factors (specific context of a given interaction) Can be considered.

In one implementation approach, a customer segment evaluation prior to processing an excellent interaction includes a calculation of the probability of all possible business results (or a defined subset) of a given interaction. If the probability of a business outcome that places a customer in a higher class segment exceeds a configured threshold, the interaction is handled according to this higher class segment. When the probability is processed, the customer's service level is adjusted accordingly (promoted or demoted). As mentioned above, promotion or demotion of customer service levels can be an interactive unit or a longer lasting formula. Service level adjustments can be made not only for inbound (initiated by the customer) but also for other media channels (e.g. voice, email, chat, web browsing and social media) as well as outbound Lt; / RTI > Also, once promoted (or demoted) to a customer segment, the first and second business objectives for the new customer segment can be evaluated when selecting the agent to handle the interaction. According to one embodiment, even though the value of the first business objective is lower than the second business objective, it is more successful in dealing with the first business objective than in the second agent having a lower success probability in dealing with the second business objective An agent with probability can be selected.

7 is a flowchart of a process for dynamic customer segmentation according to an embodiment of the present invention. The process may be implemented by a processor based on instructions stored in the repository. However, those skilled in the art will appreciate that the process may be executed via hardware, firmware (e.g., via an ASIC), or any combination of software, firmware, and / or hardware. Also, the order of the steps of the process is not fixed, but may be changed in any desired order recognized by those skilled in the art.

The process begins and at step 600 the processor detects pending interactions with the customer and retrieves an existing customer segment service level estimate for the customer. According to one embodiment, the detection of pending interactions serves as a trigger to retrieve the customer segment service level. Existing segment information may be stored, for example, in a customer profile record for the customer.

At step 602, the processor performs a test to determine if a reassessment of the customer segmentation designation should be performed. This test can be performed periodically or in real time, for example, upon detection of a specific occurrence, such as the receipt of a new interaction request. For example, testing to determine the need for re-evaluation may be performed by the routing server 20 in response to receipt of a request from the call server 18 to route the pending interaction.

If the test result at step 602 is negative, then the routine is returned and cycled. However, if the test result at step 602 is affirmative, the routine performs the re-evaluation at step 604 in the manner described above. The revaluation can be based on the expected outcome of the pending interactions that the customer may use and can use one or more static or dynamic factors or some combination. In performing this reevaluation, the processor may be configured to determine the opportunity to successfully achieve a business objective that is a business objective for the current customer segment, the next highest segment, and / or the lower-level segment . According to one embodiment, a set of rules or rules is invoked to re-evaluate the customer segment service level. The rules can take into account static and / or dynamic factors to carry out the revaluation.

At step 606, a test is performed to determine whether a service level adjustment is required. However, if the customer segment service level adjustment is required as a result of the reassessment, then the routine proceeds to step 608 where it can be adjusted (promoted to a given customer segment service level, demoted to a given customer segment service level, ). The routine continues at step 610 to store a new customer segment service level. The re-evaluated customer segmentation data may be temporarily stored (e.g., without modifying the customer segment information in the customer record). In another embodiment, the current customer segmentation information in the customer record is replaced with the re-evaluated customer segmentation data.

According to one embodiment, the adjustment of the customer segment service level may be performed such that the interaction with the customer (e.g., an atomic interaction or a task associated with the case) is handled differently from the processing prior to the adjustment (e.g., Business goals, etc.). For example, the skill sets of the agents handling the interactions may be different, the priorities of handling the interactions may be different, the business opportunities offered to the customer may vary, and / or the like.

According to one embodiment, if the revaluation is temporary, the customer returns to the customer segment stored in the customer record after the current interaction (or the number of discrete interactions) is over.

Adaptive business goal routing

The current contact center interaction routing (agent assignment) assumes that the business objective (BO) to be achieved for a given interaction / activity is analyzed, defined, and fixed at an early stage in interaction processing. Using the existing fixed BO, the agent routing logic typically tries to find the agent that best matches a particular BO. If the most matching agent is unavailable, the matching requirement is relaxed until an available agent is found. One of the disadvantages of this approach is that BO (eg, upsell / cross-sell) can be handled at a lower quality level (ie, by less qualified personnel) Reducing the likelihood of future success with customers).

According to one embodiment, instead of relying on a fixed BO during the agent assignment process, an adaptive business objective routing strategy may be used to minimize the chance of customer dissatisfaction when a suitably skilled agent is not available to handle the inbound interaction If necessary, adjust business objectives. According to one embodiment, the business objective may be based on several factors or factors: (1) the primary reason for the interaction, generally determined by the selected interaction channel (potentially refined through the IVR dialog); (2) a set of business opportunities (e.g., cross-sell / up-sell).

According to one embodiment, the reason for the interaction can be explicitly or implicitly identified according to various mechanisms. For example, the call reason may be inferred based on the customer's interaction with the IMR server 34 (FIG. 2). For example, the IMR server 34 may be configured to provide an open-ended question to the customer to elicit information on the reason for the call. For example, the IMR server 34 may be configured to ask "How can I help?" The customer can answer by saying the reason for the call (for example, "Am I eligible to upgrade the phone?"). According to one embodiment, the speech by the customer is analyzed by the speech analysis module 40, and the call is classified into a particular category, for example the "upgrade entitlement" category. In another embodiment, the question asked by the IMR server 34 is not open, but limits the sender's response to, for example, a particular subject. Of course, the IMR server 34 may be configured to serve as a traditional IVR in which a list of call reason is provided to the customer and the customer presses a number that matches the call reason. The reason for the call can be deduced from the specific number the customer has pressed.

In other embodiments, the reason for the call may also be inferred based on other ways such as interaction of a customer using another communication channel, such as a web, retail store, email, chat channel, mobile application, social media channel, have. Multichannel analysis solutions, such as Genesys Text Analytics, offered by Genesys Telecommunications Laboratories, Inc., can be used to analyze the customer's previous contract and identify previous issues and / or needs before connecting the current currency to contact center personnel. For example, if a customer selects the "Talk to Agent" option, the customer can browse the company web pages related to "go to flight policy with pets". Information about the page being searched may be sent with a call request to the agent, and it may be assumed that the reason for wanting to consult with the customer through the transmitted information is related to "flying with the pet".

With respect to identifying business opportunities as part of identifying contact centers' business objectives, these business opportunities can be identified based on criteria such as, for example, knowledge of the customer, current business goals, and the like. Exemplary business opportunities may include credit card upsell, contract renewal upsell, and / or the like. According to one embodiment, the business opportunity for a particular customer is identified based on the customer ' s profile and the currently available matching business offer. According to one embodiment, the business opportunity can be identified based on customer segment identification (which can be re-evaluated before processing the current interaction as described above).

According to one embodiment, the purpose or goal of a business opportunity is to maximize business results and / or customer satisfaction. The desired business outcome may vary from organization to organization, and / or from time to time. For example, an organization may have a global target for a particular NPS (net promoter score), sales, collection and / or revenue. More specific goals may be set for different product lines, business units and / or the like. For example, a business based business opportunity may have a conversion rate, sales and sales related goals, but a service based opportunity may have customer effort, NPS and / or other related goals.

According to one embodiment, after identifying the BOs that are deemed important to the contact center due to business outcomes and / or the possibility of maximizing customer satisfaction, the routing logic determines the two parts of the BO Opportunity) to find the best matching agent. According to one embodiment, the assignment logic (e. G., Routing strategy / logic) searches for an agent having a skill set (e. G., Qualification, authentication, etc.) identified for the BO. If such an agent can not be found, then according to one embodiment, the BO may select a BO of the lane, for example, for a given customer (e.g., having the same reason for the interaction but second best in business results) Thereby adjusting the BO. The second BO may be considered less important to the contact center as compared to the first BO because it is less likely to maximize business results and / or customer satisfaction. The process then repeats until it is found to process the interaction according to the BO (which may have been adjusted).

According to one embodiment, an evaluation of the probability of success of a particular agent for a particular BO may be low, or even less than the probability of success for the second best BO, even though the appropriate agent for processing the BO is identified. In this scenario, the second best BO may be selected to operate instead of the first best BO.

When the process is complete, the customer's profile is updated to reflect the actual BO used. A new attempt at the top-level BO may be attempted at the next interaction opportunity (i.e., when the customer interacts with the contact center next time).

In a typical implementation, given an interaction channel, a customer profile, and a proposal set, a set of business objectives is identified in response to concealment of pending interactions with the customer. During the agent selection process, the routing logic tries to find the best matching agent to handle both the main reason for the interaction and the identified business opportunity, and in accordance with one embodiment, the first (e.g., top-level or top-level) Start with a goal. If no agent is available to handle both the reason for the interaction and the currently identified business objective then the next best agent is used to handle the interaction with the (potentially adjusted) BO, .

According to one particular implementation, the class R _ik is assigned to each pair of i-th BO (I = 1 ... N) and available agents (k = 1 ... M). A rating may relate, for example, to a business result (eg, benefit) that can be achieved from interaction with a particular BO by a particular skill's agent. For example, a BO that is expected to generate a profit of $ 100 could have a higher rating than another BO, which is expected to generate a profit of $ 80. According to one embodiment, the probability of success in achieving the business outcome by a particular agent as well as the business outcome is also considered when assigning a rating to the BO / agent pair. The probability of success can be determined based on, for example, the performance history of the personnel related to the BO. According to one embodiment, the grade may be calculated based on the calculation of the expected value as is generally understood in the field of probability theory. In one embodiment, the expected value is used as a rank.

According to one embodiment, the expected value may be a weighted average of all possible business results for a particular agent. In one example, the expected value E (X) can be calculated and used as follows. Each BO has a value S if successful. S may vary depending on the customer and other factors given. In some instances, a loss value L may also be introduced. In most cases, L is zero, but it can be positive (if the attempt itself has a positive effect) or negative (if the failed attempt has a negative impact on future business with the customer).

Each X = BO / Agent combination has a success probability P, depending on the ability of the agent to "sell" the BO to a given customer in a given situation. then:

E (X) = P * S + (1-P) * L

According to one embodiment, the expected value E (X) is calculated for all possible BO / Agent combinations and the one with the highest value is selected.

According to one embodiment, all possible ratings and / or expected values may be predefined based on, for example, recent contact history or may be estimated during runtime. Both the business objective and the set of available agents are obtained for all interactions waiting to be routed to the agent. The best interaction-agent matching is then selected according to the maximum rating.

The resulting interaction (between the selected agent and the BO, as coordinated) would then be expected to occur to maximize business results, potentially avoiding customer dissatisfaction.

The expression "business objective" is not limited to specific product implementations.

The generalization of this approach is to estimate the probability that a particular agent will achieve a given business objective for the current customer; If the probability is below a configurable threshold, the process attempts to meet the next best business goal.

If all expected outcomes are below the threshold, one or more of the possible subsequent strategies can be evaluated. These include choosing the business objective that most closely matches the threshold, applying one or more weights to the business objective, making the selection, routing it according to the initial cause of the interaction, no longer adjusting according to business objectives, and so on. do. All these variant scenarios are within the solution described.

8A and 8B are flowcharts of a process for adaptive business goal routing according to an embodiment of the present invention. The process may be implemented by a processor based on instructions stored in the repository. For example, the process may be implemented by a software module operating in the routing server 20. [ However, those skilled in the art will appreciate that the process may be implemented through hardware, firmware (e.g., via an ASIC), or any combination of software, firmware, and / or hardware. In addition, the order of the steps of the process is not fixed, but may be changed in any desired order recognized by those skilled in the art.

The routine begins and at step 700 the processor detects the pending interaction with the customer (e.g., an atomic interaction or a task associated with the case) and determines, for example, an estimate of the interaction Identify or retrieve business objective data, including the reason for and the business opportunity first identified in relation to the customer.

At step 702, the processor starts the agent selection process. In this regard, the processor may interact with the statistics server 22 to identify the availability of personnel having skills corresponding to the identified business objectives. The skill level of each identified agent may also be identified.

At step 704, the processor determines whether or not agents suitable for processing each identified business goal have been discovered. This compliance is determined not only by the availability of the personnel, but also by how the skill level of the identified personnel is compared to the skill level considered suitable for handling a particular business objective, as well as the appropriate skill. If the skill level of an agent exceeds the threshold level identified for the business objective, the agent may be considered appropriate for the business objective.

At step 706, one or more matched agents are assigned to the business goals.

If, however, at step 704 the result of the test is negative (no matching agent can be located to process the current business goal), then the routine continues at step 708 to identify the next business goal. The following business objectives can identify the second business opportunity in relation to the customer.

Once a set of business goals and one or more agents that match are identified, the process proceeds to select a BO-agent pair based on the assigned rating of the BO-agent pair as shown in FIG. 8B. In this regard, in step 800, the processor selects a first BO-agent pair and, in step 802, assigns a rating (which may be only an expected value) to the pair. According to one embodiment, a rating may be based on the probability of success by a specific agent and the identification of a business result in achieving the business outcome. According to one embodiment, expected values for business results are calculated and used to assign ratings.

According to one illustration, a first BO may have a projected business result of $ 100, while a second BO may have a projected business result of $ 80. However, the first agent identified as a match for processing the first B0 may be identified as being 40% successful for the first B0 based on past performance to process the first B0. The second agent identified as a match for processing the second BO may be identified as 80% successful for the second BO based on the performance of the second agent in processing the second BO. According to one embodiment, the process assigns to the second BO agent pair a rating higher than the rating assigned to the first BO agent pair. In this regard, the process considers the pursuit of the second BO, although not the best in terms of business outcomes, to be more valuable than the first BO.

At step 804, a determination is made as to whether there are more BO-agent pairs to rank. If the answer is no, the processor evaluates the assigned rating and, in step 806, selects the BO-agent pair with the highest rating.

At step 808, the pending interaction is routed to the agent of the selected BO agent pair. In this regard, the call routing server 20 may send an instruction to the call server 18 identifying the address of the agent device to which the interaction is to be routed.

At step 810, the agent is prompted to pursue a business goal. For example, an alleged reason for the interaction can be displayed on the agent machine, and the agent can handle the reason for the call with the client as they become aware of the reason. In addition, the processor can display prompts to present the business opportunities contained in the BO to the customer and help them present such business opportunities through scripts. As will be appreciated by those skilled in the art, the business opportunity provided by a particular agent does not necessarily have to be a business opportunity with the highest return.

According to one embodiment, a business goal may be associated with a particular customer segment. In this regard, the customer can be dynamically reassigned to a particular customer segment first, before deciding on the business goals to consider when selecting the appropriate agent.

Case-Based Routing

Embodiments of the present invention relate to case routing in contrast to atomic interaction routing. In one embodiment, case-based routing can be viewed as taking a holistic view of the entire case by considering the past steps, the next step, and the anticipated future steps, and selecting agents based on a holistic view . In this regard, the routing routine attempts to select agents who are familiar with the pre-context of the case and who are capable of performing anticipated follow-up processing steps and / or other interactions related to a potentially given customer. In this regard, the selected agent is an agent that is deemed suitable for the entire case, or at least for a particular subset of the tasks associated with that case.

According to one embodiment, the customer segmentation may also be pre-adjusted prior to processing one or more steps (tasks) in a particular case. The mechanism may be similar to the customer segmentation adjustment for atomic interaction routing described above.

According to one embodiment, an agent selected to route one or more steps in a particular case may be based on a contact center / business goal. According to one embodiment, the agents with the highest probability of avoiding customer dissatisfaction and maximizing business results are selected as described in more detail above.

Figure 9 is a block diagram of a contact center solution suite (such as Genesys®) (804) integrated with a CRM enterprise service and marketing application (such as Salesforce.com® or Oracle® Siebel®) (802). The identified product / system is provided for illustrative purposes, and is not intended to be limiting. Thus, in another embodiment, the logic of case routing can be implemented outside the CRM context, e.g., in Genesys® Orchestration and Conversation Management.

This type of integration allows organizations to take advantage of the synergy of two important functions: managing customer data (via the CRM system) and real-time interaction management (via the contact center). With the seamless integration of CRM and contact center solutions, businesses can offer customers the choice of access options such as email, fax, web chats, work items and existing voice. Customer interactions are processed in real time and automatically prioritized, matched, and assigned to the best available resources according to customer needs, history, service class and business rules. The contact center solution is best served by contact center software, predefined routing strategies and templates, installation and ongoing support. To this end, the platform provides SIP-based functionality (by deploying agents whenever necessary to free contact centers from PBX constraints), business-based interaction routing (preferably routing templates that are tailored to the customer's business needs To enable the customer to connect with the right person), and real-time and historical reporting (to enable customer service tracking).

The above-described platform is extensible to enable additional routing strategies, referred to herein as "case routing ". This routing strategy is described below using an exemplary implementation.

Preferably, the integrated system uses a single agent interface for CRM and customer interaction management (e.g., but not limited to, based on the Siebel® desktop). When a single agent logs in to the desktop, the agent can access the embedded email and chat and work on the Siebel desktop, eliminating the need to toggle between applications. This approach provides a single real-time management point for inbound call processing, for example, via the Siebel CRM interface. In order to facilitate the technology of the present invention, in one embodiment, the contact center routing mechanism includes a Siebel CRM data client (or "case") client that is preferably attached to all interactions (voice, email, work items, ) ≪ / RTI > record 805 to shorten processing time. Other CRM systems may use other terms instead of "cases" and this technology should be considered to apply to other CRM-based environments regardless of the specific term employed. Preferably, it increases the upload of transaction opportunities and campaign results by running a contact center-based outbound campaign through updates that are imported and real-time in the CRM contact list. The integrated system also provides real-time intelligent routing for content management for all types of content such as documents, faxes, web forms, images, and real-time workflow optimizations such as service requests, customer ordering / fulfillment, and provisioning. A more personalized cross-channel conversation is available by giving the customer center agent a full view of customer data. The integrated approach facilitates real-time processing of customer requests based on the customer's service class, requirements, history and profile. The integrated desktop approach also dramatically reduces operating costs and improves customer responsiveness.

The contact center can provide an application programming interface (API) or a software development kit (SDK) for integrating the CRM system with the CRM provider. For example, the contact center can provide a Customer Interaction Management (CIM) platform that exposes scalable software modules through serviceable APIs that allow third parties to integrate CRM systems, services, and software. An application communicates through an abstraction layer, through a web service, or through a low-level (granular) interface. As discussed above, in an alternative embodiment, the CRM system is part of the contact center itself.

In the prior art, the contact center implements one or more types of agent-based routing, such as skill-based best available agent routing. According to this routing strategy, this prior art has been improved in consideration of case-based information. In "case-based" routing, which agent should receive certain interactions for processing within the context of the contact center is, for example, at least partially in the "case record" Is determined. Therefore, the CRM system or server models the customer support interaction (between the customer and the system) as a "case". The case (or "ticket" or "work item") has an associated case record with given information identifying the case, its type, and the expected workflow, including potential solutions, expected timing, escalation path, Depending on the CRM system in which the case occurs, the case may be associated with a particular template depending on the nature of the customer support issue.

In case routing, the case record (or information therein) associated with the case is used to determine which of a set of agents in the contact center should perform additional work / processing of the case. As can be seen, the identity of the particular interaction or case processing step (as defined by the case workflow), the expected one or more future interactions for a given case desired to be processed by the same agent, The best or target agent is selected based on one or more factors such as the presence of one or more pre-performed interactions, whether this interaction is re-opened, the remaining time of completion of the case,

In case routing, rather than routing individual interactions (e.g., voice calls, chats, e-mail, etc.) to the best available agent with the appropriate skill, rather than routing the interaction to a particular case, It is affected by parameters. Moreover, preferably "being routed" is the case itself (as opposed to the interaction associated with the case). As a simple example scenario, future interactions are triggered in future specific and / or case idle times (or other triggers) because of the nature of the events that need to interact with the customer in the future. In case-based routing, when a trigger occurs, the case is routed to the appropriate agent (or its or her queue) with the appropriate skill and availability, and the agent communicates the necessary communication with the customer (for example, Chat, etc.). Using case routing, the case-based trigger is pushed to be handled by the agent in advance when it occurs. This reduces the likelihood that an agent will ignore the interaction (by other interactions that the agent first tries to deal with) (but of course there may be situations where other assigned interactions take precedence over that case). Case routing , The case is preferably pushed to the agent (or agent queue) in the order in which it is submitted (or according to a case trigger or other priority) and delivered to an agent with the appropriate skill to handle that type of case. Preferably, since the case-based routing includes case-based parameters, when the agent / user receives the case (if there is no higher-priority interaction), he or she will typically perform other interactions Work on the case instead of choosing. Thus, in the case-based routing, it is desirable to be provided to the agent to be processed by the agent (by being pushed for immediate processing or immediately pushed to the agent's workbench). Regardless of whether it is characterized by push or pull, the model used in routing ensures that the workflow associated with the CRM case is strictly enforced and that the target agent is actively working to resolve the case Transfer the case to an agent who can.

The case routing agents may communicate with each other, otherwise interact with each other, and preferably multiple agents may view each case simultaneously. If the agent decides to transfer the case to another agent or entity (assuming the receiving agent is appropriate), preferably the receiving agent / entity has the option to accept or reject the case, preferably So the case can raise the priority so that they can work first. When the case is updated, preferably the update is pushed to the agent handling the first interaction or still working on the case.

The case routing technique may be implemented in the context of assignment logic using a reservation approach where the logic performs arbitration between multiple requests for an agent based on the priority, Time and the like.

According to this disclosure, it is assumed that there is a mechanism (e.g., API, Web service, some other request-response protocol, etc.) for conveying information between the CRM system and the contact center server responsible for the selection of the contact center agent. The case is opened in the CRM system in the usual way when the end user / customer opens the ticket. The case has an associated case identifier (caseID) and is associated with a data record, sometimes referred to herein as a case record. As noted above, the case history is typically a configuration related to the CRM system and identifies expected workflows (through a defined or ordered set of steps) for case, type, potential solution, expected timing, escalation path, . The case record may include the contact record of the case if the case is reopened in a previous interaction. More generally, a case record is an object (or case object) in an object-oriented database system associated with CRM. The contact center typically includes a contact center server API for external case management for connecting to interaction (both active and historical) in the contact center environment.

Preferably, the contact center reporting system or subsystem reports the case processing method. The report may include how many cases were worked, terminated, resolved, waiting for information, as well as how many agents worked in a particular state. Case routing may provide more granular reporting than previous reports on agent interaction. Thus, for example, if a case is pushed to an agent and the agent accepts it, the agent can monitor and report the time it is working in this case. If the agent returns the case (for example, by closing or resolving, by finding more information, etc.), the system can record the time of occurrence and the new case can be pushed to the agent. By monitoring the processing time and assuming the determined case to be a fixed processing step, you can identify the time it takes a particular agent to process the case and provide training and other remedial action to resolve the deficiency if necessary. The report can also indicate which agents are handling the most difficult cases, which agents are handling many cases, and the nature of those cases. The report can also indicate when an agent has consulted other personnel in connection with the case. If many agents are consulting with a particular agent, this may indicate that the consultant has the most appropriate knowledge of the case type, and / or that other personnel may require appropriate training. If a case is sent between agents or agents, this counseling is reported and indicates that there is a likelihood of needing agent training again. Preferably escalation is also reported so that management can understand when it is necessary to change other processes depending on the nature and extent of the escalation.

Preferably, the agent receiving the case (and the "owner" of the new case) can access the case history associated with the case ID. Preferably, only agents actively activating the case (i.e., having an active window open and focused) are reported as time for the case. This ensures that the first agent processes the case for a period of time and then does not lose the credit for the job when the case is sent to the second agent. The second agent only reports the time during which he is actively working on the case (i.e., the time the active window is open). Preferably, the CRM records also reflect the same activities by each agent or user working on the case.

Case routing does not affect case history and should not be changed. Thus, regardless of the identity of the person who last worked on the case, all personnel who worked on the case should receive a credit for the work. The contact center and / or CRM provides a comprehensive report on the time spent in each case so that all times are accurately recorded (for example, by monitoring the open and focused activity windows on the agent desktop) The identity of the agent / user who has worked on, and any issues (trends, exceptions, etc.).

In this way, case routing and associated reporting can expose important information about the agent and reveal whether the actual data supports his or her perceived value. As mentioned above, case routing data provides a much more subtle and accurate view of agent activity when routing agents receive cases to handle based on case-specific parameters (ie, they do not need to pick and choose their interactions). Thus, an agent can have a very large number of transmissions and counseling, or a low close-rate, and such data may be (even if it is related to what appears to be a very efficient agent) (Actual or perceived). This information may indicate that case routing logic needs to be adjusted. Conversely, case routing and related reporting may require consultation on a large number of cases where the agent that was previously considered to be only normal (e.g., fewer closed interactions) is on the receiving end of the current transmission, I can show that I am doing. The agent was terminating a hard-working interaction that other agents refused to fetch from the work queue; Now, based on case-based parameters, the case can be pushed to handle the traditionally evasive case depending on the other agent.

There are, of course, only representative examples, but case routing provides very useful information about agent work habits, showing how interactions could not be used when delivered to the model agents described above. Preferably, agent monitoring and case reporting statistics are generated in an automated manner; Such records may be reanalyzed by the automated system to generate an output report identifying (e.g., grading) the personnel with the case processing function.

More generally, case routing enables agents that are capable of performing subsequent processing steps that are familiar with or anticipated to be pre-contexts or who are involved in other interactions, such as those potentially associated with a given customer, Provides advantages over routing.

There is no time limit for implementing case routing, but it is more likely that atomic interactions will be handled by the contact center, although this can be done more often with back office functions in general. When the contact center becomes less efficient, it may be desirable to use case routing to help the contact center process the backlog or reduce delays.

According to one example of implementing case routing, an employee of an insurance company may open a case record in a CRM system (802). The case record may, for example, be for handling an insurance claim for an automobile accident associated with the customer. According to one embodiment, the case record identifies the workflow of anticipated steps to be taken in handling the claim. For example, steps may include obtaining details of an accident, determining a defective party, allowing a customer to take the car to a body shop, scheduling a claim coordinator to inspect the car, Getting a report from a claim coordinator, repairing a car and paying money to a body shop. Once a specific phase of the workflow is completed, information about the worker who processes the particular phase, the date and time the particular phase was processed, etc., can be tracked in the case record.

According to one embodiment, the various stages of the workflow may be handled by one or more workers / agents of the enterprise. In this regard, the autonomous tasks are created at specific stages of the workflow that require agent action, and the tasks are routed to agents determined to have a skill set to handle the interaction. According to one embodiment, instead of looking for an agent with the skill set to handle the immediate next step of the workflow, a determination is made as to the next step, and at the same time a determination of the skill set to process each of the one or more future steps (Immediately following the next step) analysis of one or more future phases of the workflow is performed. The processor may be configured with logic that determines whether there is a single agent with a technique to process two or more of the identified steps. Again, a decision is made simultaneously for all identified steps. This type of continuity can be maintained from the perspective of the agent handling the case. Thus, for example, if Agent 1 with Skill A can handle the first stage, but Agent 2 with Skills A and B can handle the first and second stages, then Agent 2 has priority over Agent 1 You can choose. Most of the time, two steps at different points. Furthermore, an agent may initially receive work to process the next step directly in the workflow, and may or may not know that it has been assigned to a subsequent step. Nevertheless, in some embodiments, the agent is notified of the assignment of the next step. Jobs for subsequent steps can be created immediately or at a later time with job creation for the next step. The generated job can be routed to an agent at the same time or at another time. If the task for the next step is later routed, the processor detects that the agent is already selected and routes the follow-up task, for example, without invoking logic to make the skill determination for best agent identification to handle the subsequent task.

In a typical interaction / task routing, the best target (agent) is defined based on:

Availability, share, etc.

Customer segment

Priority

Skills required to handle the interaction of a given media type

Agent capacity

Customer interaction history (for example, last agent routing)

Additional criteria such as upward / cross-sell opportunities and each agent skill

In accordance with embodiments of the present invention, a complete case record may be considered when selecting the best matching agent for routing case records:

Specific individual interactions that are the next "steps" in case processing

Expected future interactions for a given case (based on case class / category), preferably processed by the same agent

Interactions for a given case that may potentially need to be reopened

Remaining completion time for the entire case

The routing target is selected with all of the above in mind

If multiple agents are identified as being equally suitable for processing a number of upcoming workflow steps, the ultimate selection of agents may depend, for example, on the skill level of the identified agent. Agents with higher skill levels may be preferable to agents with lower skill levels.

According to one embodiment, instead of routing the autonomous work to the selected agent, the relevant case history is routed to provide the context of the agent where the current step is in the workflow to which it belongs, and to understand the history surrounding the case. According to one embodiment, the routing of the case may be enabled by identifying the case ID in the task being routed to the agent. You can then use Case ID to retrieve case data from the CRM system.

According to one embodiment, the interaction with the agent or the routing of the task can be triggered automatically based on parameters set for the case and / or parameters surrounding one or more steps of the workflow. For example, a task can be triggered automatically based on the date / time setting. A task can also be triggered based on the elapsed time between two or more workflow steps or since the last workflow step has completed. In this regard, the processor monitors the trigger event and, in response to detecting the occurrence of such a trigger event, automatically generates and transmits a task associated with the trigger event.

Routing strategy combination

As described above, according to an aspect of the present invention, one or preferably multiple routing strategies described above are implemented simultaneously and / or sequentially. Figure 10 shows various scenarios.

Routing strategies can be implemented as interacting units or can be implemented for multiple interactions.

As an exemplary scenario (a), a dynamic customer segmentation 900 is initially performed, followed by an adaptive business objective routing strategy 902.

Another example scenario (b) begins with adaptive business goal routing 902 and leads to case routing 904.

As a second exemplary scenario (c), dynamic customer segmentation 900 is initially performed, followed by case routing 904.

Another example scenario d includes concurrent and / or sequential implementation of dynamic customer segmentation 900, adaptive business goal routing 902 and case routing 904.

The sequence or order indicated above (Strategy 900, then Strategy 902, then Strategy 904) is not intended to be limiting. All orders or orders can be implemented in order of use. As can be seen in this figure, here one or more routing strategies are designed to reinforce other routing strategies implemented in the agent assignment mechanism.

Customers can use the Web-based configuration tool or other interface mechanisms to identify the above identified plans alone or in combination with the required skills to handle interactions of availability, occupancy, static customer segments (static), priorities, In combination with existing agent assignment mechanisms based on, for example, agent capabilities, customer interaction history (eg, last agent routing) and other criteria such as upward or cross-selling opportunities, agent skills, and the like to provide a customized routing strategy Or can be configured.

While the above description illustrates the specific order of operations performed by a particular embodiment, it should be understood that the order is exemplary because other embodiments may perform operations in different orders, combine particular operations, or overlap certain operations do. Reference to an embodiment given in the description indicates that the embodiment described may include a particular feature, structure, or characteristic, but not necessarily all embodiments may include a particular feature, structure, or characteristic.

Although the disclosed subject matter has been described in connection with a method or process, the present invention also pertains to an apparatus for performing the operations herein. The apparatus may be specially configured for the required purpose, or may comprise a general purpose computing entity selectively activated or reconfigured by a stored computer program stored thereon. Such a computer program may be stored in a computer readable storage medium, such as an optical disc, a CD-ROM, and any type of disc, including flash memory, read only memory, Random access memory (RAM), magnetic or optical card, or any type of non-transitory medium suitable for storing electronic instructions.

Although a given component of the system has been described individually, those skilled in the art will appreciate that some functionality may be combined or shared in certain instructions, program sequences, code portions, and so on.

As used herein, an agent may be implicitly assigned, for example, by an agent assignment mechanism dedicated to that purpose, or by, for example, an IVR.

The various servers, controllers, switches, gateways, engines and / or modules (collectively referred to as servers) in the preceding figures execute computer program instructions and perform the various functions described herein Or may be a process or thread running on one or more processors in one or more computing devices 1500 (e.g., Figs. 11A, 11B) that interact with other system components in order to facilitate the operation of the system. Computer program instructions are stored in a memory that can be implemented in a computing device using standard memory devices, such as, for example, random access memory (RAM). The computer program instructions may also be stored in other non-volatile computer readable media, such as, for example, CD-ROMs, flash drives, and the like. Those skilled in the art should also recognize that a computing device may be implemented in firmware (e.g., an application specific integrated circuit), hardware, or a combination of software, firmware, and hardware. Those skilled in the art will also appreciate that the functionality of the various computing devices may be combined or integrated into a single computing device or the functionality of a particular computing device may be distributed across one or more other computing devices without departing from the scope of the exemplary embodiments of the present invention . A server may be a software module, also referred to simply as a module. The contact center module set may include servers and other modules.

The various servers may be located at the same physical location as the personnel at the contact center, or may be located at the off-site (or in the cloud) at geographically different locations, for example, via a network such as the Internet, It can be located in the contact center. In addition, some servers may be located in a computing device on-site at the contact center, other servers may be located at an off-site computing device, or servers providing redundancy may be provided both onsite and offsite And provides more robust fault tolerance. In some embodiments of the invention, the functionality provided by the server located on the off-site computing device may be accessed and provided via a virtual private network (VPN) as if such a server were onsite or using software (SaaS) as a service And provides functions through the Internet using various protocols such as exchanging data encoded with Extensible Markup Language (XML) or JavaScript Object Notation (JSON).

11A and 11B show a block diagram of a computing device 1500 that may be used in an exemplary embodiment of the invention. Each computing device 1500 includes a central processing unit 1521 and a main memory unit 1522. 11A, the computing device 1500 also includes a storage device 1528, a removable media interface 1516, a network interface 1518, an input / output (I / O) controller 1523, A pointing device 1530c, a keyboard 1530a, and a pointing device 1530b such as a mouse. Storage device 1528 may include, without limitation, storage for operating system and software. 11B, each computing device 1500 includes a memory port 1503, a bridge 1570, one or more additional input / output devices 1530d and 1530e, and a cache memory 1530 that communicate with the central processing unit 1521. [ (1540). Input / output devices 1530a, 1530b, 1530d, and 1530e may be collectively referred to herein using reference numeral 1530. [

Central processing unit 1521 is any logic circuit that responds to and processes instructions fetched from main memory unit 1522. It may be implemented in, for example, a microprocessor, a microcontroller, or a graphics processing unit (GPU), or a field-programmable gate array (FPGA) ASIC). The main memory unit 1522 may be one or more memory chips that store data and allow any storage location to be directly accessed by the central processing unit 1521. [ 11A, the central processing unit 1521 communicates with the main memory 1522 via the system bus 1550. [ 11B, the central processing unit 1521 can also communicate directly with the main memory 1522 via the memory port 1503.

11B illustrates an embodiment in which central processing unit 1521 communicates directly with cache memory 1540 via a secondary bus, sometimes referred to as a backside bus. In another embodiment, the central processing unit 1521 communicates with the cache memory 1540 using the system bus 1550. The cache memory 1540 typically has a faster response time than the main memory 1522. Referring to FIG. 11A, central processing unit 1521 communicates with various I / O devices 1530 via a local system bus 1550. A Video Electronics Standards Association (VESA) local bus, an Industry Standard Architecture (ISA) bus, an Extended Industry Standard Architecture (EISA) bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect ), Or NuBus may be used as the local system bus 1550. [ In an embodiment where the I / O device is a display device 1530c, the central processing device 1521 may communicate with the display device 1530c via an advanced graphics port (AGP). 11B illustrates one embodiment of a computer 1500 in which the central processing unit 1521 communicates directly with the I / O unit 1530e. 11B also illustrates an embodiment in which direct communication with the local bus is intermixed: the central processing unit 1521 communicates with the I / O device 1530d using the local system bus 1550 to communicate with the I / ).

A wide variety of I / O devices 1530 may be present in computing device 1500. The input device includes one or more keyboards 1530a, a mouse, trackpads, trackballs, a microphone, and a picture tablet. The capture device includes an image display device 1530c, a speaker, and a printer. The I / O controller 1523 can control the I / O device as shown in FIG. 11A. The I / O controller may control one or more I / O devices, such as a keyboard 1530a and a pointing device 1530b, e.g., a mouse or an optical pen.

11A, computing device 1500 may include a floppy disk drive, a CD-ROM drive, a DVD-ROM drive, various types of tape drives, a USB port, a secure digital or compact flash memory card port COMPACT may support one or more removal media interface 1516, such as any other suitable device for writing on the writing media - ^TM FLASH memory card port), reading read data from the medium for, or read the data. The I / O device 1530 may be a bridge between the system bus 1550 and the removable media interface 1516.

The removable media interface 1516 can be used, for example, to install software and programs. The computing device 1500 may further include a storage device 1528, such as one or more hard disk drives or hard disk drive arrays, for storing operating systems and other related software, and for storing application software programs . Alternatively, the removable media interface 1516 may also be used as a storage device. For example, the operating system and software may be run as a bootable medium, e.g., a bootable CD.

In some embodiments, computing device 1500 is coupled to or includes multiple display devices 1530c, each of which may have the same or different types and / or formats. As such, any one of the I / O devices 1530 and / or the I / O controller 1523 may be any kind of device that supports, permits, or provides the connection and use of the multiple display device 1530c by the computing device 1500 And / or form of suitable hardware, software, or a combination of hardware and software. For example, the computing device 1500 may include any type and / or type of video adapter, video card, driver, and / or library for interfacing, communicating, connecting, or otherwise using the display device 1530c have. In some embodiments, any portion of the operating system of the computing device 1500 may be configured to use the multiple display device 1530c. In another embodiment, the one or more display devices 1530c are provided by one or more computing devices and are connected to the computing device 1500, for example, via a network. This embodiment may include any type of software designed and constructed to use a display device of another computing device as a secondary display device 1530c for the computing device 1500. [ Those of ordinary skill in the art will understand and appreciate the various ways and embodiments in which computing device 1500 can be configured to have multiple display devices 1530c.

Such as the computing device 1500 shown in Figures 11A and 11B, can operate under the control of an operating system that controls access to the schedule and system resources of a job. The computing device 1500 may operate on any operating system, any embedded operating system, any proprietary operating system, any operating system for a mobile computing device, or a computing device and may perform any of the operations described herein Any other operating system that can be operated.

The computing device 1500 may be a workstation, a desktop computer, a notebook, a notebook computer, a server device, a handheld computer, a mobile phone, or other portable communication device, a media player, a gaming system, a mobile computing device, Any other type and / or form of computing, communication, or communication device having sufficient processing power and memory capacity to perform the operations described herein may be a media device. In some embodiments, computing device 1500 may have other processors, operating systems, and input devices consistent with the device.

In another embodiment, the computing device 1500 is a mobile device, such as a cellular telephone or a personal digital assistant (PDA), a smartphone, a digital audio player, or a portable media player that enables Java use. In some embodiments, the computing device 1500 includes a combination of a mobile phone and a device combined with a digital audio player or portable media player.

11C, the central processing unit 1521 may include multiple processors P1, P2, P3, P4 and may be used for simultaneous execution of instructions or simultaneous execution of a single instruction on one or more pieces of data. Function can be provided. In some embodiments, computing device 1500 may include a parallel processor having one or more cores. In one such embodiment, computing device 1500 is a shared memory parallel device that has multiple processors and / or multiple processor cores and accesses all available memory in a single global address space. In another of these embodiments, computing device 1500 is a distributed memory parallel device having multiple processors, each of which accesses only local memory. In another of these embodiments, computing device 1500 has both a shared memory and a memory that can only be accessed by a particular processor or a subset of the processors. In another of these embodiments, central processing unit 1521 includes a multicore microprocessor that combines two or more independent processors into a single chip, e.g., a single integrated circuit (IC). In one exemplary embodiment, shown in FIG. 11D, computing device 1500 includes at least one central processing unit 1521 and at least one graphics processing unit 1521 '.

In some embodiments, the central processing unit 1521 provides a single instruction that simultaneously executes a single instruction on multiple data functions (SIMD), e.g., multiple data frames. In another embodiment, the various processors in the central processing unit 1521 can provide the functionality (MIMD) to execute multiple instructions on multiple data frames. In yet another embodiment, any combination of central processing unit 1521 SIMD and MIMD cores may be used in a single device.

The computing device may be a plurality of devices connected by a network, or may comprise a plurality of devices thus connected. 11E illustrates an exemplary network environment. The network environment may include one or more remote machines 1506a, 1506b and 1506c (also commonly referred to as server device (s) 1506 or one or remote device (s) 1506) One or more local devices 1502a and 1502b (typically local device (s) 1502, client (s) 1502, client node (s) 1502, (S) 1502, client computer (s) 1502, client device (s) 1502, endpoint (s) 1502, or endpoint node (s) . In some embodiments, the local device 1502 may function as both a client node seeking access to resources provided by the server device and a server device providing access to resources hosted for other clients 1502a 1502b . In FIG. 11E, only two clients 1502 and three server devices 1506 are shown, but in general, each may be in any number. Network 1504 may be a local-area network (LAN), for example a private network such as a corporate intranet, a metropolitan area network (MAN), or a wide area network (WAN) such as the Internet, or other public network or a combination thereof .

The computing device 1500 may be connected to the Internet through various connections including but not limited to a standard telephone line, a local area network (LAN), or a wide area network (WAN) link, a broadband connection, a wireless connection, And may include a network interface 1518 for interfacing to the network 1504. The connection can be established using various communication protocols. In one embodiment, the computing device 1500 communicates with another computing device 1500 via any type and / or type of gateway or tunneling protocol, such as Secure Socket Layer (SSL) or Transport Layer Security (TLS). Network interface 1518 may include a built-in network adapter suitable for interfacing computing device 1500 with any type of network capable of performing the operations described herein, such as a network interface card. An I / O device 1530 may be a bridge between the system bus 1550 and an external communication bus.

According to one embodiment, FIG. 11E can be a virtual network environment in which various components of the network are virtualized. For example, the various devices 1502 may be virtual devices implemented as software-based computers running on physical devices. Virtual machines can share the same operating system. In another embodiment, different operating systems may be running on each virtual machine instance. According to one embodiment, the "hypervisor" type of virtualization operates as if multiple virtual devices were operating on the same host physical device, each having its own private box. Of course, the virtual machine may also be running on another host physical machine.

Other types of virtualization are also contemplated, such as, for example, a network (e.g., via Software Defined Networking (SDN)). Functions such as session boundary controller functionality and other types of functionality may also be virtualized, for example, via Network Functions Virtualization (NFV).

Applicant ' s intent is to disclose all such uses of the invention, and all changes and modifications that may be made thereto without departing from the spirit and scope of the invention, . The specific manner in which the template details are presented to the user may be different. Accordingly, it is to be understood that the embodiments of the present invention are all illustrative and non-restrictive, and the scope of the present invention is indicated by the claims and their equivalents.

Claims (52)

A case-based routing method for a contact center, the method comprising:
Opening said case associated with a workflow having steps that are expected by the processor to be executed for a case in a customer database;
Identifying the first and first steps of the workflow by the processor;
Identifying, by the processor, an agent having a skill for processing the first and second steps;
Generating, by the processor, a task for processing at least the first step of the workflow; And
And sending an instruction for routing the job to the identified agent by the processor.
A case-based routing method for a contact center.
The method according to claim 1,
Wherein the case is a record including a history of an interaction occurring in the case,
A case-based routing method for a contact center.
The method according to claim 1,
Wherein the case is associated with a case ID, and the instruction to route the task comprises the case ID.
A case-based routing method for a contact center.
The method of claim 3,
Retrieving, by the processor, the history of the interaction associated with the case by the case ID; And
And displaying the history of the interaction on the personnel equipment for the identified personnel by the processor.
A case-based routing method for a contact center.
The method according to claim 1,
Generating, by the processor, a second task for processing the second step of the workflow; And
And sending, by the processor, an instruction to route the second job to the identified agent.
A case-based routing method for a contact center.
The method according to claim 1,
Further comprising the step of monitoring, by the processor, for a trigger event,
Wherein the generating of the task is based on the occurrence of the trigger event being detected,
A case-based routing method for a contact center.
The method according to claim 6,
Wherein the trigger event is an elapsed set period of time between two workflow steps,
A case-based routing method for a contact center.
The method according to claim 6,
Wherein the trigger event is a predetermined date,
A case-based routing method for a contact center.
A system for routing one or more tasks associated with a case, the system comprising:
A processor;
Wherein the instructions store the instructions and if the instructions are executed by the processor, the instructions cause the processor to:
Open the case associated with a workflow having steps that are expected to be executed for the case in the customer database;
Identify the first and first steps of the workflow;
Identify an agent having a skill for processing said first and second steps;
Create a task for processing at least the first step of the workflow;
Sending an instruction to route the job to the identified agent,
A system for routing one or more tasks associated with a case.
10. The method of claim 9,
Wherein the case is a record including a history of an interaction occurring in the case,
A system for routing one or more tasks associated with a case.
10. The method of claim 9,
Wherein the case is associated with a case ID, and the instruction to route the task comprises the case ID.
A system for routing one or more tasks associated with a case.
12. The method of claim 11,
Wherein the instructions further cause the processor to:
Retrieve a history of interactions associated with the case by the case ID;
And to display the history of the interaction on the personnel equipment for the identified personnel,
A system for routing one or more tasks associated with a case.
12. The method of claim 11,
Wherein the instructions further cause the processor to:
Create a second task for processing the second step of the workflow;
To send an instruction to route the identified job to the identified < RTI ID = 0.0 >
A system for routing one or more tasks associated with a case.
10. The method of claim 9,
Wherein the instructions further cause the processor to:
Wherein the step of generating the task comprises: monitoring a trigger event;
A system for routing one or more tasks associated with a case.
15. The method of claim 14,
Wherein the trigger event is an elapsed set period of time between two workflow steps,
A system for routing one or more tasks associated with a case.
15. The method of claim 14,
Wherein the trigger event is a predetermined date,
A system for routing one or more tasks associated with a case.
10. The method of claim 9,
Wherein the instructions further cause the processor to:
To retrieve an identification of a first customer segment to which a customer associated with the case belongs, wherein the first customer segment is associated with a first target of a contact center;
Predicting a result of the job being processed by the personnel according to the first customer segment;
Identify a second customer segment based on the predicted result;
Cause the customer to re-associate with the second customer segment, wherein the second customer segment is associated with a second target of a contact center different from the first target;
And to process the job according to the second target instead of the first target,
A system for routing one or more tasks associated with a case.
10. The method of claim 9,
Wherein the instructions further cause the processor to:
Identify a first and second target of the contact center, wherein the first goal is identified as being more important to the contact center than the second target;
Determine that the agent has the skills necessary to achieve the first goal;
Determine the likelihood of success of the first agent in achieving the first goal;
To identify a second agent for processing the second object, wherein the second agent also has a skill to process the first and second steps;
To determine the likelihood of success of the second agent in achieving the second goal, wherein the likelihood of success achieving the second goal by the second agent is a success Greater than likely;
Send an instruction to route the task to the second agent;
The second agent prompts the second agent to pursue the second target,
A system for routing one or more tasks associated with a case.
A method for enhanced interaction processing in a contact center, the method comprising:
Detecting a pending interaction with a customer by a processor;
In response to detecting the pending interaction by the processor, retrieving an identification of a first customer segment to which the customer belongs and associated with a first target of the contact center;
Predicting a result of the pending interaction by the processor;
Identifying a second customer segment based on the predicted result by the processor;
Associating the customer with the second business segment associated with the second target of the contact center differently than the first business goal by the processor; And
And processing, by the processor, the pending interaction in accordance with the second target instead of the first target.
A method for improved interaction processing in a contact center.
20. The method of claim 19,
Wherein predicting a result of the pending interaction comprises predicting a result of a business opportunity presented to the customer by the processor.
A method for improved interaction processing in a contact center.
21. The method of claim 20,
The business opportunity is a cross-selling or up-selling opportunity for a product or service,
A method for improved interaction processing in a contact center.
20. The method of claim 19,
Further comprising evaluating a number of factors associated with the pending interaction by the processor, wherein the identification of the second customer segment is based on the evaluated factor,
A method for improved interaction processing in a contact center.
20. The method of claim 19,
Wherein the predicted result of the pending interaction matches a set of criteria for the second customer segment,
A method for improved interaction processing in a contact center.
20. The method of claim 19,
Wherein the predicted result is for the second target of the contact center.
A method for improved interaction processing in a contact center.
20. The method of claim 19,
Wherein the second goal comprises a business opportunity that is excluded from the first target,
A method for improved interaction processing in a contact center.
A system for enhanced interaction processing in a contact center, the system comprising:
A processor; And
Wherein the instructions store the instructions and if the instructions are executed by the processor, the instructions cause the processor to:
Detect pending interactions with the customer;
In response to detecting the pending interaction, cause the customer to belong and retrieve an identification of a first customer segment associated with the first target of the contact center;
Cause the result of the pending interaction to be predicted;
Identify a second customer segment based on the predicted result;
Associating the customer with a second customer segment associated with a second target of the contact center different from the first target;
Cause the pending interaction to be processed according to the second target instead of the first target,
A system for improved interaction processing at the contact center.
27. The method of claim 26,
Wherein the instructions for predicting a result of the pending interaction comprise instructions for predicting a result of a business opportunity presented to the customer,
A system for improved interaction processing at the contact center.
27. The method of claim 26,
The business opportunity is a cross-selling or up-selling opportunity for a product or service,
A system for improved interaction processing at the contact center.
27. The method of claim 26,
Wherein the instructions further cause the processor to:
Wherein the identification of the second customer segment is based on the evaluated factor,
A system for improved interaction processing at the contact center.
27. The method of claim 26,
Wherein the predicted result of the pending interaction matches a set of criteria for the second customer segment,
A system for improved interaction processing at the contact center.
27. The method of claim 26,
Wherein the predicted result is for the second target of the contact center.
A system for improved interaction processing at the contact center.
27. The method of claim 26,
Wherein the second goal comprises a business opportunity that is excluded from the first target,
A system for improved interaction processing at the contact center.
27. The method of claim 26,
Wherein the pending interaction is for accomplishing a step of a workflow associated with the case, and the selected agent for processing the pending interaction is an agent having a skill for processing the next step of the workflow,
A system for improved interaction processing at the contact center.
27. The method of claim 26,
Wherein the second customer segment is also associated with a third target, wherein the second target is identified as being more important to the contact center than the third target, and wherein the instructions further cause the processor to:
Identify a first agent for processing the second target, and determine the likelihood of success of the first agent in achieving the second target;
To identify a second agent for processing the third object and to determine the likelihood of success of the second agent in achieving the third object, wherein the second agent The likelihood of success being greater than the likelihood of success by the first agent to achieve the second goal;
Send a command to route the pending interaction to the second agent,
Prompting the second agent to pursue the second goal,
A system for improved interaction processing at the contact center.
A method for enhanced interaction processing in a contact center, the method comprising:
Detecting a pending interaction with a customer by a processor;
Identifying a first and second target of the contact center in response to detecting the pending interaction by the processor, wherein the first target is identified as being more important to the contact center than the second target ;
Identifying a first agent for processing the first target by the processor and determining the likelihood of success of the first agent in achieving the first target;
Identifying a second agent for processing the second target by the processor and determining the likelihood of success of the second agent in achieving the second target, The likelihood of success in achieving the goal is greater than the likelihood of success in achieving the first goal by the first agent;
Sending an instruction by the processor to route the pending interaction to the second agent; And
And prompting the second agent to pursue the second goal by the processor.
A method for improved interaction processing in a contact center.
36. The method of claim 35,
The first goal being associated with a first business result determined to be more desirable to the contact center than a second business result associated with the second target,
A method for improved interaction processing in a contact center.
36. The method of claim 35,
The business results are related to revenue, sales or sales of the contact center,
A method for improved interaction processing in a contact center.
36. The method of claim 35,
The business outcome is about customer satisfaction,
A method for improved interaction processing in a contact center.
36. The method of claim 35,
Wherein the probability of the first or second agent achieving the first or second goal is determined based on an analysis of the hysteretic performance of the first or second agent with respect to the first and second targets.
A method for improved interaction processing in a contact center.
36. The method of claim 35,
The second target being associated with a business opportunity to be presented to the customer,
A method for improved interaction processing in a contact center.
36. The method of claim 35,
The business opportunity may be a cross-selling or up-selling opportunity for a product or service,
A method for improved interaction processing in a contact center.
A system for enhanced interaction processing in a contact center, the system comprising:
A processor; And
Wherein the instructions store the instructions and if the instructions are executed by the processor, the instructions cause the processor to:
Detect pending interactions with the customer;
Identify the first and second targets of the contact center in response to detecting the pending interaction, wherein the first target is identified as being more important to the contact center than the second target;
Identify a first agent for processing the first target, and determine the likelihood of success of the first agent in achieving the first goal;
Identify a second agent for processing the second target and determine the likelihood of success of the second agent in achieving the second goal, wherein the second agent achieves the second goal by the second agent The likelihood of success is greater than the likelihood of success of the first goal by the first agent;
Send a command to route the pending interaction to the second agent;
Prompting the second agent to pursue the second goal,
A system for improved interaction processing at the contact center.
43. The method of claim 42,
The first goal being associated with a first business result determined to be more desirable to the contact center than a second business result associated with the second target,
A system for improved interaction processing at the contact center.
43. The method of claim 42,
The business results are related to revenue, sales or sales of the contact center,
A system for improved interaction processing at the contact center.
43. The method of claim 42,
The business outcome is about customer satisfaction,
A system for improved interaction processing at the contact center.
43. The method of claim 42,
Wherein the probability of the first or second agent achieving the first or second goal is determined based on an analysis of the hysteretic performance of the first or second agent with respect to the first and second targets.
A system for improved interaction processing at the contact center.
43. The method of claim 42,
The second target being associated with a business opportunity to be presented to the customer,
A system for improved interaction processing at the contact center.
49. The method of claim 47,
The business opportunity may be a cross-selling or up-selling opportunity for a product or service,
A system for improved interaction processing at the contact center.
43. The method of claim 42,
Wherein the pending interaction is to accomplish a step of a workflow associated with the case and the selected agent to process the pending interaction is an agent having a skill to process the next step of the workflow,
A system for improved interaction processing at the contact center.
43. The method of claim 42,
Wherein the instructions further cause the processor to:
In response to detecting the pending interaction, to retrieve an identification of a first customer segment to which the customer belongs, wherein the first customer segment is associated with a third target of the contact center;
Cause the result of the pending interaction to be predicted;
Identify a second customer segment based on the predicted result;
Associate the customer with the second customer segment, wherein the second customer segment is associated with the second target,
A system for improved interaction processing at the contact center.
Substantially as hereinbefore described with reference to the accompanying drawings.
Substantially as hereinbefore described with reference to the accompanying drawings.

Images