EP3186947B1 - Gestion d'interaction commandée par le client - Google Patents

Gestion d'interaction commandée par le client Download PDF

Info

Publication number
EP3186947B1
EP3186947B1 EP15836852.2A EP15836852A EP3186947B1 EP 3186947 B1 EP3186947 B1 EP 3186947B1 EP 15836852 A EP15836852 A EP 15836852A EP 3186947 B1 EP3186947 B1 EP 3186947B1
Authority
EP
European Patent Office
Prior art keywords
customer
interaction
routing
agent
contact center
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP15836852.2A
Other languages
German (de)
English (en)
Other versions
EP3186947A4 (fr
EP3186947A1 (fr
Inventor
Herbert Willi Artur Ristock
Merijn TE BOOIJ
Akbar Riahi
Vladimir Mezhibovsky
Kentis GOPALLA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Genesys Cloud Services Holdings II LLC
Original Assignee
Greeneden US Holdings II LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/470,913 external-priority patent/US20160065741A1/en
Priority claimed from US14/470,898 external-priority patent/US9654637B2/en
Application filed by Greeneden US Holdings II LLC filed Critical Greeneden US Holdings II LLC
Publication of EP3186947A1 publication Critical patent/EP3186947A1/fr
Publication of EP3186947A4 publication Critical patent/EP3186947A4/fr
Application granted granted Critical
Publication of EP3186947B1 publication Critical patent/EP3186947B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
    • H04M3/5232—Call distribution algorithms
    • H04M3/5235—Dependent on call type or called number [DNIS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2203/00—Aspects of automatic or semi-automatic exchanges
    • H04M2203/40—Aspects of automatic or semi-automatic exchanges related to call centers
    • H04M2203/408—Customer-specific call routing plans
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
    • H04M3/5232—Call distribution algorithms

Definitions

  • Typical processing of interactions between a customer and a contact center are generally under the control of the contact center.
  • the contact center generally selects the agent to which an inbound/outbound interaction from/to a customer is to be routed.
  • contact centers do employ certain business driven customization and personalization, such customization and personalization generally sides with the interests of the business.
  • US 2014/100902 A1 discloses a method for providing personalized customer services on an end-user device.
  • the end-user device sends a request for agent-assisted service to an agent administration server, and receives from the server information on various customer service agents.
  • the information may include information such as agent availability status and agent communication channels.
  • a request may be sent to communicate with a preferred agent selected from the plurality of agents, utilizing a preferred communication channel selected from the agent communication channels.
  • US 6,064,730 discloses a customer self-routing call center.
  • the call center provides an interactive graphical display with information on the status of one or more agent stations, a device that allows a user to select an agent station from the display, and a device for effecting a communications link between the caller and the agent station.
  • the system includes a processor and a memory.
  • the memory has stored therein instructions that, when executed by the processor, cause the processor to execute the following acts.
  • the processor receives a request to reserve a contact center resource for handling an interaction.
  • the processor also receives data about the interaction.
  • the processor identifies a routing point for routing the interaction based on the received data.
  • the routing point is associated with routing logic controlled by a customer instead of the contact center.
  • the processor routes the interaction to the identified routing point for giving the customer control of the routing of the interaction.
  • the interaction is a telephony interaction
  • the system includes a switch that is coupled to the processor for establishing a voice path between the end user device and a device of the contact center resource.
  • the received data includes a caller identifier.
  • the processor transmits a software application to the customer end user device over a communications network, where the software application includes instructions for executing the routing logic.
  • the software application monitors presence of the contact center resource.
  • the software application includes instructions for receiving the presence information from a contact center server.
  • the software application is transmitted to the customer end user device in response to identifying the customer as belonging to a particular customer segment.
  • the interaction is a telephony interaction
  • the software application invokes a dialer for initiating the telephony interaction
  • the software application provides an interface for prompting the customer to configure the routing logic.
  • the software application provides an interface for prompting the customer to identify one or more preferred contact center agents.
  • the software application provides an interface for prompting the customer to rate the interaction.
  • the software application is configured to share the rating with other customers.
  • the routing point is identified by a telephone number.
  • embodiments of the present invention are directed to a system and method for customer controlled interaction management (CCIM) where a customer is given control of interactions with a contact center where such control would typically reside with the contact center.
  • the control exercised by the customer is the routing of interactions to contact center resources (e.g. agents).
  • the contact center exposes real-time status information of certain resources of the contact center, such as, for example, presence information of certain agents of the contact center. Based on this information, the customer dictates when to initiate the interaction, and the selection of the agent to whom the interaction is to be routed.
  • the traditional role of the contact center (business) and the customer are reversed. Instead of the contact center acting in the best interest of the contact center, the customer controls interactions according to his best interest.
  • CCIM eligibility may be given for certain types of customers, such as, for example, customers deemed to be important to the contact center. For example, CCIM eligibility may be given to customers in certain customer segments (e.g. customers labeled as "Gold" customers). In some embodiments, CCIM eligibility may be provided as compensation for bad customer service experience. Also, in some embodiments, CCIM eligibility may be revoked by the contact center.
  • CCIM By enabling CCIM for "Gold" customers, the need for agent reservation for such customers is reduced if not eliminated. CCIM may allow such a "Gold" customer to experience the same or even better customer experience than what would be achieved by having dedicated, reserved agents for such customers, while at the same time, avoiding the risk of such reserved agents sitting idle when there is traffic overload for other agents. CCIM also allows the reduction or avoidance of call parking (queuing) at the business by establishing the call only when the desired agent is actually available. If there is some waiting involved for a CCIM session, it may not count towards meeting the business' service level, allowing service compliance for CCIM sessions to be relaxed.
  • FIG. 1 is a schematic block diagram of a generalized system for customer controlled interaction management according to one embodiment of the invention.
  • the system includes an end user device 10 coupled to a contact center system 12 over a communications network 14 conventional in the art.
  • the communications network 14 may include a private or public switched telephone network (PSTN), local area network (LAN), private wide area network (WAN), and/or public wide area network such as, for example, the Internet.
  • PSTN public switched telephone network
  • LAN local area network
  • WAN private wide area network
  • the communications network 14 may also include a wireless carrier network including a code division multiple access (CDMA) network, global system for mobile communications (GSM) network, or any wireless network/technology conventional in the art, including but to limited to 3G, 4G, LTE, and the like.
  • CDMA code division multiple access
  • GSM global system for mobile communications
  • the end user device 10 may be a communication device conventional in the art, such as, for example, a smart phone, laptop, desktop, electronic tablet, and/or the like.
  • a customer operating the end user device 10 may initiate, manage, and respond to telephone calls, emails, chats, text messaging, web-browsing sessions, and other multi-media transactions via the end user device.
  • the end user device includes a client interaction (iXn) controller 16, vendor relationship management (VRM) module 20, and data storage device 22.
  • the client iXn controller 16 may be configured with logic to initiate interactions, and manage, control and/or assist a customer in the CCIM of those interactions.
  • the client iXn controller 16 may further be configured to communicate with the contact center system (including the associated business and/or vendor) to exchange data to enable/facilitate the CCIM. Exemplary data that may be exchanged is presence data of agents at the contact center.
  • the client iXn controller 16 is also equipped with capability (e.g. a tool or application) to develop control logic for CCIM at the customer side.
  • the control logic may include a customized routing logic.
  • the client iXn controller 16 may also be equipped for customer side case management, knowledge management, recording, and/or reporting.
  • a customer that is identified as being appropriate for CCIM capability may be offered to download an application hosting the client iXn controller 16 and/or VRM module 20 on the end user device.
  • the customer may be logged into the business' web site.
  • the web site may recognize the customer as being a "Gold” customer, and display a prompt saying to "click here" if he wants to download the app.
  • the customer may also be identified as a "Gold" customer during a current interaction with a contact center agent.
  • the agent may ask the customer if the wants to download the app. If the answer is YES, the agent may send a link to the customer's end user device (e.g. as a text message, email, or the like) that the user may select to perform the download.
  • the application may be downloaded from an app store, from a website of the business, and/or the like. Once installed, the customer may be prompted to configure specific CCIM details such as, for example, a communication protocol to use in the event that multiple protocols are available. According to one embodiment, an available protocol for selection may be a session-initiation protocol (SIP) conventional in the art.
  • SIP session-initiation protocol
  • Other parameters to be configured may include, for example, data (e.g. information on the customer's preferred agents) that is to be shared between the end user device and the contact center system, interaction recording options, reporting options, and the like.
  • the customer may be prompted to identify agents that the customer wants to monitor for presence, and/or customers that the customer wants to add to his preferred agent list.
  • the customer may be provided with a complete list of agents for the business.
  • the list of agents may be categorized, for example, based on skills, departments, and the like.
  • the customer may select to monitor presence of an agent group. In this regard, if any member of the group is available, the group is identified as being available.
  • the customer may be further prompted to generate a personalized routing script for routing interactions for the customer.
  • Templates may be provided to the customer for guiding the customer in setting up the routing script.
  • Default routing scripts may also be provided to the customer if he does not want to set up a personalized one.
  • the routing script generated for the customer may be configured to replace or plug-into the routing script utilized by the contact center.
  • the routing script may also control timing of the interaction, target selection (e.g. specific agents, interaction voice response applications, etc.), and the like.
  • the routing script may be configured to identify an agent or agent group to which to route an interaction.
  • the customer's personal routing script may be configured to prompt or await specific selection of the agent or agent group by the customer prior to the routing of the interaction.
  • the routing script may automatically select a preferred agent for a particular interaction.
  • the routing logic may be configured to connect to the mass storage device 22 to identify ratings of agents (e.g. by the customer, other customers, and the like), and select an agent identified to have, for example, the highest rating.
  • the rating of agents may be adjusted based on past interaction information provided by the customer or other third parties.
  • the client iXn controller 16 may also provide a tool to develop, manage, and utilize (load) other types of scripts.
  • dialogue scripts may be generated for guiding the customer during a live conversation with the contact center.
  • the dialogue script may automate certain steps of the conversation, such as, for example, passing personal information about the customer, greetings, and the like.
  • Scripts may also be generated for granting to the enterprise filtered access to the customer's CCIM data.
  • the VRM module 20 includes logic for allowing the customer to not only be in control of customer interactions, but also be in control of data exchanged between the customer and different enterprises (vendors), referred to as vendor relationship management (VRM).
  • VRM vendor relationship management
  • the VRM module 20 is configured to communicate with one or more vendor systems 28 associated with one or more businesses, such as, for example, the business for which contact center services are provided via the contact center system 12, to exchange relevant data according to rules set up by the customer.
  • the term vendor is also intended to encompass the contact center system for which contact center services are provided.
  • the VRM module 20 provides a tool to allow the customer to control what kind of data to share, when to share, and with which businesses to share.
  • the tool may further allow the customer to control the type and timing of data that is received from the various vendors with which the customer has a relationship, as is described in further detail in U.S. Application Serial No. 14/201,738, filed on March 7, 2014 .
  • the customer may expose, via the VRM module 20, customer account information that will be needed to communicate with certain vendors.
  • the vendors in turn may expose their availability information, such as their business hours of the contact center system 12, certain tips on communicating with the vendors, and the like.
  • Part of VRM may include maintaining track of interactions with the vendors, including, for example, interactions controlled by the customer via the client iXn controller, and other interactions not controlled by the customer if CCIM is not provided for those interactions.
  • the VRM module may allow the user to maintain personal notes or scores relating to the vendors and individual interactions with such vendors. For example, the customer may provide a scoring of service quality and of individual agents. The customer may also keep notes on how to communicate best with a particular company (e.g. best media type, best timing, how to fast-track IVR menu, and other do's and don'ts), learned from past experience or from data shared by other customers, such as, for example, via social media. Some of the information may be fed by the vendors themselves. This information may be accessed by the client iXn controller for initiating an interaction with the vendor, or during a CCIM session to allow the interaction to progress more efficiently.
  • the client iXn controller 16 and VRM module 20 are coupled to the mass storage device 22 which may take the form of a disk drive or drive array conventional in the art.
  • the mass storage device 22 may store different types of records, such as, for example, interactions records, vendor records, configuration data, scripts, and the like.
  • the vendor records may include VRM details of different vendors with which the customer has relations.
  • the vendor records may include, without limitation, vendor metadata (e.g. contact numbers/addresses, office hours, type of business, and types of offered services), vendor profile or classification (e.g. values reflective of the vendor's speed in providing committed service, ease of doing business with the vendor, and corporate assessment data (e.g. risk of bankruptcy)), assessment of agents with whom the customer has had interaction (e.g.
  • Each vendor record may also include data on how to improve the customer's interaction experience with the vendor such as, for example, "tricks" to fast-track IVR dialogue (e.g. a series of numbers to press to reach certain departments), data that is to be exposed (or not) to the vendor (e.g. last 4 digits of the customer's social security number which is a question that is always asked during an IVR dialogue with the vendor), and other data exposed by the vendor or collected from data shared by other customers.
  • "tricks" to fast-track IVR dialogue e.g. a series of numbers to press to reach certain departments
  • data that is to be exposed (or not) to the vendor e.g. last 4 digits of the customer's social security number which is a question that is always asked during an IVR dialogue with the vendor
  • other data exposed by the vendor or collected from data shared by other customers e.g. last 4 digits of the customer's social security number which is a question that is always asked during an IVR dialogue with the vendor
  • the interaction records maintained in the mass storage device include, without limitation, interaction metadata (e.g. time, parties, and service type), case reference where each case may include multiple individual interactions (e.g. a case reference may be provided to process an accident claim), business outcome (e.g. sales, or credit card offer accepted), status of interaction (e.g. case closed, finished, or not finished), and customer's annotations (e.g. satisfaction ratings or things learned from the experience).
  • interaction metadata e.g. time, parties, and service type
  • case reference where each case may include multiple individual interactions
  • business outcome e.g. sales, or credit card offer accepted
  • status of interaction e.g. case closed, finished, or not finished
  • customer's annotations e.g. satisfaction ratings or things learned from the experience
  • Portions of the data stored in the mass storage device 22 may be shared with the vendor servers 28, contact center system 12, and/or other customers according to set rules. For example, agent satisfaction scores may be posted onto one or more social media website according to the rules. The data may also be updated from these entities according to set rules.
  • the client iXn controller 16 and VRM module 20 are assumed to be separate functional units, a person of skill in the art should recognize that the functionality of these units may be combined or integrated into a single component, or further subdivided into.
  • the client iXn controller 16 and VRM module 20 are locally hosted by the end user device as, for example, a local application.
  • the controller and module may be hosted in a third party system and accessed in real-time by the end user device as a service (e.g. over the web) during an actual CCIM session.
  • a hybrid solution may be provided where the processing logic resides at the end-user device, but the data stored in the storage device 22 is maintained in a remote computing environment such as, for example a cloud computing environment.
  • the contact center system includes a contact center (CC) iXn controller 18 providing logic for the business-side CCIM.
  • the CC iXn controller 18 communicates with the client iXn controller for enabling CCIM of interactions by the customer. For example, messages may be exchanged to expose agent presence information to the end user device. The messages may also be for giving control to the client iXn controller 16 for routing an interaction initiated by the customer. In exchanging such messages with the end user device 10, the CC iXn controller 18 further communicates with traditional CC components 24 as described in further detail below.
  • the contact center system may be deployed in equipment of the corresponding enterprise, a third-party service provider, and/or deployed in a remote computing environment such as, for example, a private or public cloud environment with infrastructure for supporting multiple contact centers for multiple enterprises.
  • a remote computing environment such as, for example, a private or public cloud environment with infrastructure for supporting multiple contact centers for multiple enterprises.
  • the various components of the contact center system may also be distributed across various geographic locations and computing environments and not necessarily contained in a single location, computing environment, or even computing device.
  • an iXn control gateway 26 may be optionally coupled in-between the end user device 10 and contact center system 12.
  • the iXn control gateway 26 may expose an application programming interface (API) and/or protocols for allowing the client iXn controller 16 to exchange messages with the CC iXn controller 18.
  • API application programming interface
  • a single iXn control gateway 26 may be provided for different contact center systems.
  • the functionality of the client iXn controller 16 and/or CC iXn controller 18 may reside in the iXn control gateway 26.
  • the functionality may be accessed by both customers and businesses as a service, such as, for example, software-as-a service (SaaS), as a managed service, or the like. Both customers and businesses may subscribe to this service.
  • SaaS software-as-a service
  • data exchanged via the media and control channels may flow through the iXn control gateway 26, or the session may be conducted directly between the end user device 10 and contact center system 12 in a peer-to-peer fashion.
  • CCIM is not provided as a service, but is fully owned and operated by the customer (e.g. CCIM application running on the customer's mobile device), and all business side CCIM is owned and operated by the business directly, there may be no need for the iXn control gateway 26.
  • the CCIM communications between the end user device 10 and contact center system 12 may be peer-to-peer.
  • Certain components of the contact center such as, for example, a contact center router, may also act as the iXn control gateway 26.
  • FIG. 2 is a more detailed block diagram of the contact center components 24 according to one exemplary embodiment of the invention.
  • the contact center system includes a switch/media gateway 100 coupled to the communications network 14 for receiving and transmitting calls between the customers and the contact center.
  • the switch/media gateway 100 may include a telephony switch configured to function as a central switch for agent level routing within the center.
  • the switch 100 may include an automatic call distributor, a private branch exchange (PBX), an IP-based software switch, and/or any other switch configured to receive Internet-sourced calls and/or telephone network-sourced calls from a customer, and route those calls to, for example, an agent telephony device.
  • the switch/media gateway establishes a voice path (not shown) between the calling customer and, for example, the agent telephony device.
  • the switch is coupled to a call server 102 which may, for example, serve as an adapter or interface between the switch and the remainder of the routing, monitoring, and other call-handling components of the contact center.
  • a call server 102 may, for example, serve as an adapter or interface between the switch and the remainder of the routing, monitoring, and other call-handling components of the contact center.
  • the call server 102 may be configured to process PSTN calls, VoIP calls, and the like.
  • the call server 102 may include a session initiation protocol (SIP) server for processing SIP calls.
  • SIP session initiation protocol
  • the call server 102 may, for example, extract data about the customer interaction such as the caller's telephone number, often known as the automatic number identification (ANI) number, or the customer's internet protocol (IP) address, or email address, and communicate with other CC components and/or CC iXn controller 18 in processing the call.
  • ANI automatic number identification
  • IP internet protocol
  • the contact center system 24 further includes an interactive media response (IMR) server 104, which may also be referred to as a self-help system, virtual assistant, or the like.
  • the IMR server 104 may be similar to an interactive voice response (IVR) server, except that the IMR server is not restricted to voice, but may cover a variety of media channels including voice. Taking voice as an example, however, the IMR server may be configured with an IMR script for querying calling customers on their needs. For example, a contact center for a bank may tell callers, via the IMR script, to "press 1" if they wish to get an account balance. If this is the case, through continued interaction with the IMR, customers may complete service without needing to speak with an agent.
  • the IMR server 104 may also ask an open ended question such as, for example, "How can I help you?" and the customer may speak or otherwise enter a reason for contacting the contact center.
  • the routing server 106 may be configured to take appropriate action for processing the call. For example, for non-CCIM interactions, the routing server 106 may use data about the call to determine how the call should be routed. If the call is to be routed to a contact center agent, the routing server 106 may select an agent for routing the call based, for example, on a routing strategy employed by the routing server 106, and further based on information about agent availability, skills, and other routing parameters provided, for example, by a statistics server 108. For CCIM interactions, the routing server 106 may pass control of the routing to the client iXn controller 16, or receive instructions from the client iXn controller to route the call.
  • the routing server 106 may query a customer database, which stores information about existing clients, such as contact information, service level agreement (SLA) requirements, nature of previous customer contacts and actions taken by contact center to resolve any customer issues, and the like.
  • the database may be managed by any database management system conventional in the art, such as Oracle, IBM DB2, Microsoft SQL server, Microsoft Access, PostgreSQL, MySQL, FoxPro, and SQLite, and may be stored in a mass storage device 110.
  • the routing server 106 may query the customer information from the customer database via an ANI or any other information collected by the IMR 104.
  • the statistics server 108 or a separate present server may be configured to provide agent availability information to all subscribing clients.
  • clients may include, for example, the routing server 106, CC iXn controller 18, and/or client iXn controller 16.
  • each agent device 112 may include a telephone adapted for regular telephone calls, VoIP calls, and the like.
  • the agent device 112 may also include a computer for communicating with one or more servers of the contact center and performing data processing associated with contact center operations, and for interfacing with customers via voice and other multimedia communication mechanisms.
  • the contact center may also include a reporting server 114 configured to generate reports from data aggregated by the statistics server 108.
  • reports may include near real-time reports or historical reports concerning the state of resources, such as, for example, average waiting time, abandonment rate, agent occupancy, and the like.
  • the reports may be generated automatically or in response to specific requests from a requestor (e.g. agent/administrator, contact center application, and/or the like).
  • the contact center may also include a multimedia/social media server 116 for engaging in media interactions other than voice interactions with the end user devices 10 and/or web servers 118.
  • the media interactions may be related, for example, to email, vmail (voice mail through email), chat, video, text-messaging, web, social media, co-browsing, and the like.
  • the web servers 118 may include, for example, social interaction site hosts for a variety of known social interaction sites to which an end user may subscribe, such as, for example, Facebook, Twitter, and the like.
  • the web servers may also provide web pages for the enterprise that is being supported by the contact center. End users may browse the web pages and get information about the enterprise's products and services.
  • the web pages may also provide a mechanism for contacting the contact center, via, for example, web chat, voice call, email, web real time communication (WebRTC), or the like.
  • WebRTC web real time communication
  • deferrable also referred to as back-office or offline interactions/activities may also be routed to the contact center agents.
  • Such deferrable activities may include, for example, responding to emails, responding to letters, attending training seminars, or any other activity that does not entail real time communication with a customer.
  • an iXn server 122 interacts with the routing server 106 for selecting an appropriate agent to handle the activity. Once assigned to an agent, the activity may he pushed to the agent, or may appear in the agent's workbin 120a-120c (collectively referenced as 120) as a task to be completed by the agent.
  • the agent's workbin may be implemented via any data structure conventional in the art, such as, for example, a linked list, array, and/or the like.
  • the workbin may be maintained, for example, in buffer memory of each agent device 112.
  • deferrable interactions may also be subject to CCIM.
  • the mass storage device(s) 110 may store one or more databases relating to agent data (e.g. agent profiles, schedules, etc.), customer data (e.g. customer profiles), interaction data (e.g. details of each interaction with a customer, including reason for the interaction, disposition data, time on hold, handle time, etc.), and the like.
  • agent data e.g. agent profiles, schedules, etc.
  • customer data e.g. customer profiles
  • interaction data e.g. details of each interaction with a customer, including reason for the interaction, disposition data, time on hold, handle time, etc.
  • CCM customer relations management
  • the mass storage device may take form of a hard disk or disk array as is conventional in the art.
  • the contact center may also include a reporting server 114 configured to generate reports from data aggregated by the statistics server 108.
  • reports may include near real-time reports or historical reports concerning the state of resources, such as, for example, average waiting time, abandonment rate, agent occupancy, and the like.
  • the reports may be generated automatically or in response to specific requests from a requestor (e.g. agent/administrator, contact center application, and/or the like).
  • the various servers of FIG. 2 may each include one or more processors executing computer program instructions and interacting with other system components for performing the various functionalities described herein.
  • the computer program instructions are stored in a memory implemented using a standard memory device, such as, for example, a random access memory (RAM).
  • the computer program instructions may also be stored in other non-transitory computer readable media such as, for example, a CD-ROM, flash drive, or the like.
  • the functionality of each of the servers is described as being provided by the particular server, a person of skill in the art should recognize that the functionality of various servers may be combined or integrated into a single server, or the functionality of a particular server may be distributed across one or more other servers without departing from the scope of the embodiments of the present invention.
  • the functionality the functionality of the CC iXn controller 18 may be incorporated into one or more of the CC components 24 or vice versa as will be apparent to a person of skill in the art.
  • interaction is used generally to refer to any real-time and non-real time interaction that uses any communication channel including, without limitation telephony calls (PSTN or VoIP calls), emails, vmails (voice mail through email), video, chat, screen-sharing, text messages, social media messages, web real-time communication (e.g. WebRTC calls), and the like.
  • PSTN or VoIP calls telephony calls
  • vmails voice mail through email
  • video chat
  • chat screen-sharing
  • text messages e.g. WebRTC calls
  • web real-time communication e.g. WebRTC calls
  • FIG. 3 is a more detailed block diagram of a client iXn controller 16a and a CC iXn controller 18a according to one embodiment of the invention.
  • client iXn controller 16a may be similar to client iXn controller 16
  • CC iXn controller 18a may be similar to CC iXn controller 18.
  • the CC iXn controller 18a provides CCIM capability to the client iXn controller 16a as a web service over the communications network 14.
  • Any web protocol conventional in the art may be used for the web communication, such as, for example, SOAP and/or HTTP.
  • the CC iXn controller 18a may include a routing server 106a which may be similar to the routing server 106 of FIG. 2 .
  • the CC routing server 106a is coupled to a CC statistics server 108a and a CC telephony server 240a which may be similar to the statistics server 108 and call server 240 of FIG. 2 .
  • the client iXn controller 16a includes a client router 200a and client iXn media controller 202.
  • the client router 200a may be configured as a "lite” version of the CC routing server 106a
  • the client iXn media controller 202 may be configured as a "lite” version of the CC telephony server 240a.
  • the client router 200a and iXn media controller 202a provide functionality similar to the basic functionality provided respectively by the CC routing server 106a and telephony server 240a.
  • the client iXn controller 16a may be configured to monitor the presence of monitored agents (e.g. agents in a customer's preferred agent list). This may be done, for example, by the client router 200a requesting status of one or more of the monitored agents, either periodically or on an as-needed basis.
  • the CC iXn controller 18a receives the request, and invokes the CC routing server 106a to in turn query the statistics server 108a for status information of the one or more agents.
  • the agent status information for a particular agent may indicate, for example, whether the agent is available, the communication medium for which the agent is agent, and the like.
  • the retrieved agent status information is forwarded to the client router 200a over the communication network 14.
  • the routing logic for routing interactions involving the customer resides in the client iXn controller.
  • the client router 200a and/or iXn media controller 202a communicates with the CC routing server 106a to request that an interaction be routed to an agent or agent group as instructed by the customer's routing logic.
  • agent may be selected automatically by the customer's routing logic based on, for example, agents that have been identified by the customer as being preferred, and current availability of such agents.
  • the routing request may include data of the requesting user (e.g. a customer phone number), and identification of the desired agent or agent group.
  • the CC routing server 106a then interacts with the CC telephony server 240a to cause the interaction to be routed to the agent device of the selected agent.
  • FIG. 4 is a more detailed block diagram of a client iXn controller 16b and a CC iXn controller 18b according to one embodiment of the invention.
  • SIP is used for exchanging interaction data between the client iXn controller [6b and CC iXn controller 18b.
  • the CC iXn controller includes a SIP server 256a which may be similar to the call server 102 of FIG. 2 .
  • the client iXn controller 16b is equipped with a client router 200b, client SIP server 250a, and client statistics server 252a, which may be "lite" versions of respectively the routing server 106, CC SIP server 256a, and the contact center CC statistics server 108.
  • the client statistics server 252a may be configured to exchange messages with a contact center presence server 254 using SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions) to detect presence of desired agents.
  • SIMPLE Session Initiation Protocol
  • the contact center presence server may be in communication with, or incorporated into, the contact center statistics server, to provide status of the identified agents.
  • the client statistics server 252a may expose the agent status data to the client router 200b for selecting an agent or agent group with which to communicate.
  • the agent status data may also be provided for display by the CCIM application to allow a customer to manually select the agent with whom he wants to communicate.
  • the client router 200b invokes the client SIP server 250a to exchange SIP messages with the CC SIP server 256a to cause routing of an interaction from/to the end user device to a particular agent or agent group. Data about the end-user as well as the requested agent or agent group may be transmitted via the SIP messages.
  • the CC SIP server 256a then interacts with one or more CC components to cause the interaction to be routed to the agent device of the selected agent.
  • FIG. 5 is a more detailed block diagram of a client iXn controller 16c and a CC iXn controller 18c according to one embodiment of the invention.
  • a proprietary protocol is used for exchanging messages between the client iXn controller 16c and CC iXn controller 18c.
  • the CC iXn controller 18c includes a CC routing server 106c which may be similar to the routing server 106 of FIG. 2 , for exchanging messages via the proprietary protocol.
  • the contact center system 12c also includes a CC telephony server 240b and a CC statistics server 108b which may be similar, respectively, to the call server 102 and statistics server 108 of FIG. 2 .
  • the client iXn controller 16c is equipped with a client router 200c, client telephony server 280a, and client statistics server 252b, which may be "lite" versions of respectively the CC routing server 106c, CC telephony server 240b, and CC statistics server 108b.
  • the client statistics server 252b may be configured to request and receive agent status information from the CC statistics server 108b using the proprietary protocol.
  • the client statistics server 252b subscribes to the CC statistics server 108b to receive agent status information as would any other client located at the contact center (e.g. the CC routing server 106c).
  • the client statistics server 252b exposes the agent status data to its subscribing clients, such as, for example, the client telephony server 208a and client router 200c.
  • the client telephony server 280a invokes the client router 200c to exchange messages with the CC routing server 106c to cause routing of an interaction to a particular agent or agent group. Data about the end-user as well as the requested agent or agent group may be transmitted via the proprietary protocol.
  • the contact center telephony server 240b then allows the end user device to establish connection with the available agent device.
  • FIG. 6 is a more detailed block diagram of a client iXn controller 16d and a CC iXn controller 18d according to one embodiment of the invention.
  • federation principles are used for exchanging messages between the client iXn controller 16d and CC iXn controller 18d.
  • the CC iXn controller 18d includes a CC federation proxy 292 that acts as an intermediary for receiving interaction data from the client iXn controller 16d.
  • the federation proxy 292 may be configured to authenticate requests from the client iXn controller and give access to certain services and data based on the authentication.
  • the contact center system 12d also includes a CC telephony server 240c and a CC statistics server 108c which may be similar, respectively, to the call server 102 and statistics server 108 of FIG. 2 .
  • the client iXn controller 16c is also equipped with a federation proxy 290 for transmitting interaction routing requests to the CC iXn controller 18d.
  • the client iXn controller 16d may further include an iXn media controller 202b, client router 200d, and client statistics server 252c, which may be "lite" versions of respectively the CC telephony server 240c, routing server 106, and CC statistics server 108c.
  • the client statistics server 252c may be configured to request and receive agent status information from the CC statistics server 108c after the customer has been authenticated by the CC federation proxy 292.
  • the client statistics server 252c subscribes to the CC statistics server 108c to receive agent status information as would any other client located at the contact center (e.g. the CC telephony server 240c).
  • the client statistics server 252c exposes the agent status data to its subscribing clients, such as, for example, the iXn media controller 202b and client router 200d.
  • the iXn media controller 202b invokes the client router 200d to transmit requests to cause routing of an interaction to a particular agent or agent group. Data about the end-user as well as the requested agent or agent group may be transmitted in the request. According to one embodiment, the request is forwarded to the CC iXn controller 18d via the client federation proxy 290.
  • the telephony/SIP servers at the customer and client side are replaced with a CC or client interaction server similar to the interaction server 122 of FIG. 2 which is configured to process non-voice interactions.
  • FIG. 7 is a flow diagram of a process executed by the client iXn controller 16 to allow CCIM for a customer according to one embodiment of the invention.
  • the process may start in response to a customer invoking or launching the CCIM application hosting the client iXn controller 16.
  • the application may be dedicated to a single business (e.g. Bank of America), a class of businesses (all banks used by the customer), and/or the like.
  • the customer may launch the application to initiate contact with a particular business.
  • the application determines, in act 300, whether any unresolved interactions exist for the customer. If the answer is YES, the unresolved interaction is resumed in act 302. For simplicity purposes, this step is generally identified as a single block 302.
  • the resuming of the unresolved interaction may involve execution of one or more of the acts identified in FIG. 7 .
  • determination as to whether an unresolved interaction exists is performed by searching the mass storage device 22 for interaction records stored for the customer that have been identified as being unresolved. Such records may further indicate the routing strategy that was invoked, and the portion of the routing strategy that was executed when the interaction was left uncompleted.
  • the application may be configured to resume the interaction from this point on. For example, a next step in the routing strategy may be to select an agent with the right skills to handle the interaction.
  • the resumed interaction may utilize the same or different communication channels that were used during the last interaction.
  • the customer may have started a flight booking process on the web page of the business when the interaction was discontinued.
  • the customer may be able to resume the interaction by invoking the application and placing a call to his preferred agent.
  • the application may be configured to inquire whether the customer wants to resume this interaction before doing so.
  • the application waits and detects a condition to initiate an interaction to an identified agent or agent group.
  • the condition may be, for example, receipt of a customer command to initiate the interaction.
  • the application may provide a graphical user interface with availability/presence information of preferred agents and/or agent groups, along with an option to "call,” "email,” or “chat” with such agents. Selection of one of the interaction options initiates the corresponding interaction with the identified agent or agent group.
  • the presence information may indicate whether the agent is busy with another interaction, not scheduled for work, and/or the like.
  • the list of preferred agents and agent groups is configurable and modifiable by the customer at any time.
  • the graphical user interface may provide options to add, delete, or modify agents or agent groups from the customer's preferred list.
  • detecting a particular event may automatically trigger the interaction, or display a question to the user as to whether he wants to initiate the interaction.
  • the events may be, for example, detecting a particular time (e.g. if the user has set a timer to initiate the interaction), or detecting a monitored condition (e.g. if charge on a credit card was above a preset amount).
  • the application may detect a conflict and either block the call, or display the conflict and ask the user to confirm that he wants to proceed with the interaction.
  • the application may have access to a preconfigured rule (e.g. set by the customer) that no calls are to be initiated when the customer is driving (e.g. when the bluetooth device in the car is active).
  • the application may have access to the customer's calendar and detect that the customer is scheduled to have a meeting that would overlap with the interaction.
  • the customer has selected a telephony interaction by selecting the "call" option, and no conflicts have been detected to allow the interaction.
  • the number that is called may be a general telephone number of the contact center.
  • the customer simply transmits a "call" command, and the routing logic at the customer end selects an agent according to, for example, preference settings, user ratings, and the like.
  • the application may respond by asking the customer if he or she wants to try connecting anyway, or whether he or she wants to try later when the agent's presence status indicates that he is available. If the customer indicates that he or she wants to try later, the application may be configured to monitor the identified agent's presence information, and once the agent is indicated to be present, automatically launch the interaction with the identified agent. Of course, a prompt may be displayed to the customer to confirm that the interaction is still desired. For example, the prompt may say, "Agent X is now available, please click to connect.” Prior to sending the prompt, the contact center system may reserve the agent for a configurable short time (e.g.
  • the first customer who reacts gets the connection to the agent.
  • a negative alert may be sent by the contact center system to the other customers indicating that the agent is no longer available, and asking if they want to be notified again.
  • the customers who originally got the positive alert of the agent availability get the negative alert if the connection cannot be established for those customers despite their clicking to connect.
  • the client iXn controller 16 transmits an agent reservation request in act 306 to the CC iXn controller 18 to reserve the selected agent or agent group.
  • the request is transmitted to the CC iXn controller 18 over the data channel prior to or concurrently with the transmitting of call data.
  • the reservation request is received at a central place at the contact center where logic for agent reservation resides, such as, for example, at a CC telephony server 240. If the reservation request identities an agent group or a list with various possible agents, the CC telephony server 240 may be configured to select (e.g. randomly) one of the various agents of the group or list for reservation.
  • the agent is blocked for any other interactions for a particular period of time (e.g. 15 seconds).
  • the agent may be identified by the statistics server 108 as being in a busy/unavailable state. It is possible that multiple agent reservation requests for the same agent may be concurrently received from multiple routing servers (e.g. client routers 200 or CC routing servers 105). In this case, priority data associated with the requests may be used for determining to whom to assign the agent. Priority determinations may be made based on, for example, customer segmentation information about the customer associated with the interaction. According to this example, requests relating to "Gold" customers may be given higher priority than requests relating to "Bronze" customers.
  • the routing logic at the client router 200 determines whether to retry the same agent/agent group, or select a next preferred agent or agent group. Identification of the next preferred agent or agent group may be pre-configured by the customer. The customer may also manually select a different agent or agent group in response to indication of the unsuccessful agent reservation request. Of course, instead of the agent selecting a specific agent, freedom may be given to the enterprise to select an available agent as would be done according to conventional routing mechanisms.
  • the client iXn controller 16 transmits a call control message to the CC iXn controller 18 over the data channel.
  • the telephony server 240 coupled to the switch/media gateway 100 that receives the voice call via the voice channel, receives the call control message via the data channel.
  • the call control message may contain, for example, data about the interaction, customer, and/or reserved agent.
  • the client iXn controller 16 further provides a dialer application for launching the actual voice call towards the contact center. In this regard, the dialer application functions as a switch for the end user device.
  • the voice call lands on the switch/media gateway 100 at the contact center until routed to an appropriate destination.
  • the CC telephony server 240 determines a routing point (also referred to an external route point) to which the call should be transferred based on the received interaction data.
  • the identified routing point is a personal routing point that is enabled for CCIM.
  • the client iXn controller 16 receives a call transfer message from the CC iXn controller 18 that identifies the transfer routing point, along with any interaction data collected by the CC iXn controller.
  • the client iXn controller 16 receives a call transfer message from the CC iXn controller 18 that identifies the transfer routing point, along with any interaction data collected by the CC iXn controller.
  • the transfer routing point is associated with the client telephony server 280 hosted by the client iXn controller 16.
  • the call transfer message is received by the client telephony server 280 over the data channel.
  • the actual call is also received by the dialer application that acts as the switch for the end user device.
  • the client telephony server 280 informs the client router 200 of the call.
  • the client router proceeds to route the call according to its routing logic.
  • the routing logic may be configured to identify the preferred agent that has been reserved for the interaction (e.g. based on the received interaction data), and proceed to route the call to the reserved agent.
  • the routing logic may optionally check whether the reserved agent is indeed still available.
  • the client router 200 invokes the dialer application to call the access (directory) number of the reserved agent.
  • the access number may be provided in the call transfer message from the CC iXn controller transmitted in act 310. A voice connection is then made with the customer and the reserved agent.
  • FIG. 8 is a flow diagram of a process executed by the CC iXn controller 18 to allow CCIM for a customer according to one embodiment of the invention.
  • the process starts, and the CC iXn controller receives, in act 400, the call control message containing interaction data from the client iXn controller 16 over the data channel.
  • the CC telephony server 240 identifies an external route point based on the received interaction data. For example, the CC telephony server 240 may identify the caller number in the interaction data as one that is enabled for CCIM. A personal route point is thus identified and reserved for routing the call. The interaction data received from the client iXn controller is then saved in association with the personal route point. According to one embodiment, the personal route point is associated with a directory number of the dialer application hosted by the client iXn controller 16.
  • act 404 the actual voice call launched by the end user device is received at the switch/media gateway 100, and the call is matched to the data saved in association with the personal route point.
  • the CC telephony server 240 transfers the call to the personal route point.
  • the transfer of the call further causes transfer of the interaction data to the client telephony server 280.
  • transfer of the call to the client telephony server relinquishes control of the call by the contact center.
  • further routing of the call to the reserved agent is performed based on routing logic controlled by the customer instead of routing logic under the control of the contact center.
  • routing is used herein as a main example of interaction processing by the customer, a person of skill in the art should recognize that the customer may be in control of other aspects of interaction processing, such as, for example, obtaining interaction history data, checking status of interactions, and the like.
  • customer controlled interactions relate to inbound real-time interactions initiated by the customer (e.g. voice calls, chat, directly routed emails, etc.), a person of skill in the art should recognize that deferrable interactions could also be controlled by the customer, such as, for example, emails that are placed in the agent's workbin for handling as time permits.
  • Outbound interactions initiated by the contact center may also be controlled by the customer, such as, for example, by enabling the customer to control the customer's entries in calling lists by removing the customers number, changing the time of the outbound contact, selecting a telephone number, assigning the outbound interaction to certain agents, and the like.
  • a hybrid solution is also contemplated where certain parts of the interaction processing are controlled by the customer, and other parts are controlled by the business. For example, certain internal processes for claim approval will stay under business control while the customer may control the claim adjuster who ultimately handles the claim.
  • a "soft" CCIM may be provided to a customer where the customer merely expresses interaction intent and preferred agent(s), but the actual final assignment of the interaction to an agent is done by the business that tries to accommodate the customer's preference.
  • a customer may share personal ranking, recommendation, and/or satisfaction information (collectively referred to as "rating") about agents, services, and/or products, with other users.
  • the agent ratings may be indicative of qualifications of the agents, customer satisfaction provided by the agents, and/or the like.
  • the VMR module 20 may be invoked to collect and share the rating information on social media sites such as Facebook and Twitter. The information may also be shared on rating websites such as Yelp.
  • the CCIM application provides a graphical user interface to prompt a user to rate an agent (e.g. after an interaction with such agent).
  • the client CC iXn controller 16 and/or VRM module 20 may be configured to automatically monitor websites on the Internet for ratings of agents of a particular contact center that are posted by other customers. For example, ratings may be obtained for all agents listed in the customer's preferred agent list, and an average of such ratings may be displayed by the CCIM application along with any personal rating provided by the customer.
  • the collected ratings for an agent may be used to propose the agent to a preferred status, or demote the agent to a less preferred status.
  • the rating information may also be used to select an agent to whom to route an interaction enabled for CCIM, if no manual selection was made by the customer.
  • the exposing of agent rating information in addition to agent presence information allows the customer to have a more complete set of data for deciding when and with which agent to have a CCIM enabled interaction. For example, if a first agent with a low rating is identified as being available for a voice interaction, but a second agent with a higher rating is identified as being busy for such voice interaction, the customer may want to wait until agent two becomes available prior to initiating the call.
  • FIGS. 9A-9B are exemplary signaling diagrams of messages exchanged between an end user and the contact center system in a non-CCIM enabled interaction according to one embodiment of the invention.
  • the end user device 10 may host an application that allows interaction with the contact center system 12 to gather information about agents, products, and services of the contact center.
  • the end user device 10 invokes the application and submits a message to the contact center system 12 indicating that the customer has a problem that needs to be solved. For example, the customer may select an "I have a problem" button displayed by the application.
  • the contact center system receives the data, and in response, transmits a second message to the application for gathering information on the cause of the problem. For example, the customer may be prompted to enter the name of the product to which the problem is related. In another embodiment, the history of interactions with the application may provide clue as to the product or service that is causing problems for the customer.
  • the application transmits details on the problem, such as, for example, the product name.
  • the customer identifies that the problem is product related, and the product name is "Vacuum 502.”
  • the contact center system may be configured, in act 410, to retrieve product metadata including, for example, available services relating to the product, agent skills required to deal with issues with the product, and the like. Such information may be retrieved, for example, from the mass storage device 100 located at the contact center system 12.
  • the options may include self-help options as well as interaction options with live agents that have been identified as having skills for handling the interaction.
  • the contact center system 12 exposes agent presence information to the application for each type of interaction channel.
  • agent 1 and agent 2 have skills to have a chat about the identified product/issue, while agent 2 has skills to conduct a voice conversation about the identified product/issue.
  • Agent 1 is identified as being available for chat, while agent 2 is busy.
  • Agent 2 is identified as being busy for voice interactions.
  • the application at the end user device 10 may be configured to search, in act 414, one or more social networks for ratings by other people on the product and/or agents identified by the contact center system 12.
  • the application may be configured to go inquire social networks like Facebook to see is any of the customer's friends have provided a rating for the product or agents (e.g. a total number of "likes” or "dislikes" for a particular agent). If such information is available, the agent rating information is returned to the application in act 416 for display to the customer.
  • Embodiments of the present invention thus provide the customer full information as to agent availability as well as agent ratings for helping the customer decide how he wants to interact with the contact center.
  • the customer may configure the application to automatically select the agent with the highest rating if the agent is available. If the highest rated agent is not available, the application may be configured to prompt the customer to indicate how he would like to proceed. For example, the customer may want to proceed with a lower rated agent that is currently available, wait for the higher rated agent, or the like.
  • the end user device 10 transmits, in act 418, a message to the contact center system 12 indicating that the customer will wait for agent 2.
  • the contact center system e.g. call server 102
  • the contact center system 12 further transmits a message, in act 422, that the customer will be notified when agent 2 becomes available.
  • agent 2 When agent 2 does become available, the contact center system 12 reserves agent 2 in act 424 and pushes notification to the customer in act 426 as to this fact.
  • the customer is also provided information on the choices that he can take, such as receiving the number of agent 2, requesting that agent 2 call the customer at his number, or requesting additional time before engaging in the interaction with agent 2.
  • the contact center system releases agent 2, re-reserves him, and inquires the customer as to whether he wants to engage in the interaction (collectively referenced as acts 428 and 430), until the customer indicates, in act 432, that he wants the access telephone number of agent 2 to initiate the interaction. In response, the contact center system 12 allocates the number and associates it to the customer.
  • acts referred generally as 436 the customer dials the telephone number for agent 2, and the contact center system 12 matches the incoming call to the stored customer data and routes the call to an agent device for agent 2 400.
  • the contact center system 12 may transmit a survey to get feedback on the experience.
  • the customer may respond or decline the survey. Even if the customer declines, he or she may be willing to share his experience with his friends.
  • the application or VRM module 20 may provide a graphical user interface to allow the customer to capture information about the experience. Such information may include, for example, a rating given to the agent based on the experience.
  • the information is stored in the customer's mass storage device 22 but may be exposed, in act 438, to one or more businesses, social media networks, and the like, based on settings configured by the customer.
  • the VRM module 20 may access APIs exposed by various social networks to automatically post the experience information on those networks.
  • the interaction in FIGS. 9A-9B are described as non-CCIM enabled interaction, a person of skill in the art should recognize that the interaction may also be a CCIM enabled interaction where the routing logic that is executed to route the interaction is controlled by the customer instead of the contact center.
  • the CCIM application may be configured to, either automatically or in response to a user command, request an interaction specifying the higher rated agent, employing a process similar to the process described with respect to FIGS. 7 and 8 .
  • Each of the various servers, controllers, switches, gateways, engines, and/or modules (collectively referred to as servers) in the afore-described figures may be a process or thread, running on one or more processors, in one or more computing devices 1500 (e.g., FIG. 10A , FIG. 10B ), executing computer program instructions and interacting with other system components for performing the various functionalities described herein.
  • the computer program instructions are stored in a memory which may be implemented in a computing device using a standard memory device, such as, for example, a random access memory (RAM).
  • the computer program instructions may also be stored in other non-transitory computer readable media such as, for example, a CD-ROM, flash drive, or the like.
  • a computing device may be implemented via firmware (e.g. an application-specific integrated circuit), hardware, or a combination of software, firmware, and hardware.
  • firmware e.g. an application-specific integrated circuit
  • a person of skill in the art should also recognize that the functionality of 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, which may also simply be referred to as a module.
  • the set of modules in the contact center may include servers, and other modules.
  • the various servers may be located on a computing device on-site at the same physical location as the agents of the contact center or may be located off-site (or in the cloud) in a geographically different location, e.g., in a remote data center, connected to the contact center via a network such as the Internet.
  • some of the servers may be located in a computing device on-site at the contact center while others may be located in a computing device off-site, or servers providing redundant functionality may be provided both via on-site and off-site computing devices to provide greater fault tolerance.
  • functionality provided by servers located on computing devices off-site may be accessed and provided over a virtual private network (VPN) as if such servers were on-site, or the functionality may be provided using a software as a service (SaaS) to provide functionality over the internet using various protocols, such as by exchanging data using encoded in extensible markup language (XML) or JavaScript Object notation (JSON).
  • VPN virtual private network
  • SaaS software as a service
  • XML extensible markup language
  • JSON JavaScript Object notation
  • FIG. 10A and FIG. 10B depict block diagrams of a computing device 1500 as may be employed in exemplary embodiments of the present invention.
  • Each computing device 1500 includes a central processing unit 1521 and a main memory unit 1522.
  • the computing device 1500 may also include a storage device 1528, a removable media interface 1516, a network interface 1518, an input/output (I/O) controller 1523, one or more display devices 1530c, a keyboard 1530a and a pointing device 1530b, such as a mouse.
  • the storage device 1528 may include, without limitation, storage for an operating system and software. As shown in FIG.
  • each computing device 1500 may also include additional optional elements, such as a memory port 1503, a bridge 1570, one or more additional input/output devices 1530d, 1530e and a cache memory 1540 in communication with the central processing unit 1521.
  • the input/output devices 1530a, 1530b, 1530d, and 1530e may collectively be referred to herein using reference numeral 1530.
  • the central processing unit 1521 is any logic circuitry that responds to and processes instructions fetched from the main memory unit 1522. It may be implemented, for example, in an integrated circuit, in the form of a microprocessor, microcontroller, or graphics processing unit (GPU), or in a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC).
  • the main memory unit 1522 may be one or more memory chips capable of storing data and allowing any storage location to be directly accessed by the central processing unit 1521. As shown in FIG. 10A , the central processing unit 1521 communicates with the main memory 1522 via a system bus 1550. As shown in FIG. 10B . the central processing unit 1521 may also communicate directly with the main memory 1522 via a memory port 1503.
  • FIG. 10B depicts an embodiment in which the central processing unit 1521 communicates directly with cache memory 1540 via a secondary bus, sometimes referred to as a backside bus.
  • 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 main memory 1522.
  • the central processing unit 1521 communicates with various I/O devices 1530 via the local system bus 1550.
  • Various buses may be used as the local system bus 1550, including a Video Electronics Standards Association (VESA) Local bus (VLB), an Industry Standard Architecture (ISA) bus, an Extended Industry Standard Architecture (EISA) bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI Extended (PCI-X) bus, a PCI-Express bus, or a NuBus.
  • VESA Video Electronics Standards Association
  • VLB Video Electronics Standards Association
  • ISA Industry Standard Architecture
  • EISA Extended Industry Standard Architecture
  • MCA MicroChannel Architecture
  • PCI Peripheral Component Interconnect
  • PCI-X PCI Extended
  • PCI-Express PCI-Express bus
  • NuBus NuBus.
  • FIG. 10B depicts an embodiment of a computer 1500 in which the central processing unit 1521 communicates directly with I/O device 1530e.
  • FIG. 10B also depicts an embodiment in which local busses and direct communication are mixed: the
  • I/O devices 1530 may be present in the computing device 1500.
  • Input devices include one or more keyboards 1530a, mice, trackpads, trackballs, microphones, and drawing tablets.
  • Output devices include video display devices 1530c, speakers, and printers.
  • An I/O controller 1523 may control the I/O devices.
  • 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 optical pen.
  • the computing device 1500 may support one or more removable media interfaces 1516, such as a floppy disk drive, a CD-ROM drive, a DVD-ROM drive, tape drives of various formats, a USB port, a Secure Digital or COMPACT FLASHTM memory card port, or any other device suitable for reading data from read-only media, or for reading data from, or writing data to, read-write media.
  • An I/O device 1530 may be a bridge between the system bus 1550 and a removable media interface 1516.
  • the removable media interface 1516 may for example be used for installing software and programs.
  • the computing device 1500 may further comprise a storage device 1528, such as one or more hard disk drives or hard disk drive arrays, for storing an operating system and other related software, and for storing application software programs.
  • a removable media interface 1516 may also be used as the storage device.
  • the operating system and the software may be run from a bootable medium, for example, a bootable CD.
  • the computing device 1500 may comprise or be connected to multiple display devices 1530c, which each may be of the same or different type and/or form.
  • any of the I/O devices 1530 and/or the I/O controller 1523 may comprise any type and/or form of suitable hardware, software, or combination of hardware and software to support, enable or provide for the connection to, and use of, multiple display devices 1530c by the computing device 1500.
  • the computing device 1500 may include any type and/or form of video adapter, video card, driver, and/or library to interface, communicate, connect or otherwise use the display devices 1530c.
  • a video adapter may comprise multiple connectors to interface to multiple display devices 1530c.
  • the computing device 1500 may include multiple video adapters, with each video adapter connected to one or more of the display devices 1530c. In some embodiments, any portion of the operating system of the computing device 1500 may be configured for using multiple display devices 1530c. In other embodiments, one or more of the display devices 1530c may be provided by one or more other computing devices, connected, for example, to the computing device 1500 via a network. These embodiments may include any type of software designed and constructed to use the display device of another computing device as a second display device 1530c for the computing device 1500. One of ordinary skill in the art will recognize and appreciate the various ways and embodiments that a computing device 1500 may be configured to have multiple display devices 1530c.
  • a computing device 1500 of the sort depicted in FIG. 10A and FIG. 10B may operate under the control of an operating system, which controls scheduling of tasks and access to system resources.
  • the computing device 1500 may be running any operating system, any embedded operating system, any real-time operating system, any open source operating system, any proprietary operating system, any operating systems for mobile computing devices, or any other operating system capable of running on the computing device and performing the operations described herein.
  • the computing device 1500 may be any workstation, desktop computer, laptop or notebook computer, server machine, handheld computer, mobile telephone or other portable telecommunication device, media playing device, gaming system, mobile computing device, or any other type and/or form of computing, telecommunications or media device that is capable of communication and that has sufficient processor power and memory capacity to perform the operations described herein.
  • the computing device 1500 may have different processors, operating systems, and input devices consistent with the device.
  • the computing device 1500 is a mobile device, such as a Java-enabled cellular telephone or personal digital assistant (PDA), a smart phone, a digital audio player, or a portable media player.
  • the computing device 1500 comprises a combination of devices, such as a mobile phone combined with a digital audio player or portable media player.
  • the central processing unit 1521 may comprise multiple processors P1, P2, P3, P4, and may provide functionality for simultaneous execution of instructions or for simultaneous execution of one instruction on more than one piece of data.
  • the computing device 1500 may comprise a parallel processor with one or more cores.
  • the computing device 1500 is a shared memory parallel device, with multiple processors and/or multiple processor cores, accessing all available memory as a single global address space.
  • the computing device 1500 is a distributed memory parallel device with multiple processors each accessing local memory only.
  • the computing device 1500 has both some memory which is shared and some memory which may only be accessed by particular processors or subsets of processors.
  • the central processing unit 1521 comprises a multicore microprocessor, which combines two or more independent processors into a single package, e.g., into a single integrated circuit (IC).
  • the computing device 1500 includes at least one central processing unit 1521 and at least one graphics processing unit 1521'.
  • a central processing unit 1521 provides single instruction, multiple data (SIMD) functionality, e.g., execution of a single instruction simultaneously on multiple pieces of data.
  • SIMD single instruction, multiple data
  • several processors in the central processing unit 1521 may provide functionality for execution of multiple instructions simultaneously on multiple pieces of data (MIMD).
  • MIMD multiple pieces of data
  • the central processing unit 1521 may use any combination of SIMD and MIMD cores in a single device.
  • a computing device may be one of a plurality of machines connected by a network, or it may comprise a plurality of machines so connected.
  • FIG. 10E shows an exemplary network environment.
  • the network environment comprises one or more local machines 1502a, 1502b (also generally referred to as local machine(s) 1502, client(s) 1502, client node(s) 1502, client machine(s) 1502, client computer(s) 1502, client device(s) 1502, endpoint(s) 1502, or endpoint node(s) 1502) in communication with one or more remote machines 1506a, 1506b, 1506c (also generally referred to as server machine(s) 1506 or remote machine(s) 1506) via one or more networks 1504.
  • local machines 1502a, 1502b also generally referred to as local machine(s) 1502, client(s) 1502, client node(s) 1502, client machine(s) 1502, client computer(s) 1502, client device(s) 1502, endpoint(s) 1502, or endpoint node(s) 1502
  • a local machine 1502 has the capacity to function as both a client node seeking access to resources provided by a server machine and as a server machine providing access to hosted resources for other clients 1502a, 1502b. Although only two clients 1502 and three server machines 1506 are illustrated in FIG. 10E , there may, in general, be an arbitrary number of each.
  • the network 1504 may be a local-area network (LAN), e.g., a private network such as a company Intranet, a metropolitan area network (MAN), or a wide area network (WAN), such as the Internet, or another public network, or a combination thereof.
  • LAN local-area network
  • MAN metropolitan area network
  • WAN wide area network
  • the computing device 1500 may include a network interface 1518 to interface to the network 1504 through a variety of connections including, but not limited to, standard telephone lines, local-area network (LAN), or wide area network (WAN) links, broadband connections, wireless connections, or a combination of any or all of the above. Connections may be established using a variety of communication protocols.
  • the computing device 1500 communicates with other computing devices 1500 via any type and/or form of gateway or tunneling protocol such as Secure Socket Layer (SSL) or Transport Layer Security (TLS).
  • the network interface 1518 may comprise a built-in network adapter, such as a network interface card, suitable for interfacing the computing device 1500 to any type of network capable of communication and performing the operations described herein.
  • An I/O device 1530 may be a bridge between the system bus 1550 and an external communication bus.
  • the network environment of FIG. 10E may be a virtual network environment where the various components of the network are virtualized.
  • the various machines 1502 may be virtual machines implemented as a software-based computer running on a physical machine.
  • the virtual machines may share the same operating system. In other embodiments, different operating system may be run on each virtual machine instance.
  • a "hypervisor" type of virtualization is implemented where multiple virtual machines run on the same host physical machine, each acting as if it has its own dedicated box. Of course, the virtual machines may also run on different host physical machines.
  • NFV Network Functions Virtualization

Landscapes

  • Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Claims (14)

  1. Système de gestion d'interaction d'un centre de contact client, le système comprenant :
    un processeur (1521) ; et
    une mémoire (1522), dans lequel la mémoire (1522) contient des instructions stockées dans celle-ci qui, lorsqu'elles sont exécutées par le processeur (1521), amènent le processeur (1521) à :
    recevoir une demande de réservation d'un agent de centre de contact pour gérer une interaction ;
    recevoir des données sur l'interaction ;
    identifier un point de routage pour acheminer l'interaction sur la base des données reçues, dans lequel le point de routage est associé à une logique de routage commandée par un client au lieu du centre de contact ; et
    acheminer l'interaction vers le point de routage identifié pour donner au client la commande du routage de l'interaction ;
    caractérisé en ce que
    l'agent de centre de contact est réservé pour une durée configurable en réponse à la demande ; et
    en ce que la logique de routage est un script de routage personnalisé généré par le client, et que le script de routage personnalisé est appelé pour acheminer l'interaction vers l'agent de centre de contact réservé.
  2. Système selon la revendication 1, dans lequel l'interaction est une interaction téléphonique, le système comprenant en outre :
    un commutateur (100) couplé au processeur (1521) pour établir un chemin vocal entre le dispositif d'utilisateur final (10) et un dispositif (112) de l'agent de centre de contact.
  3. Système selon l'une des revendications 1 ou 2, dans lequel les données reçues comprennent un identifiant d'appelant.
  4. Système selon l'une des revendications 1 à 3, dans lequel les instructions amènent en outre le processeur à :
    transmettre une application logicielle au dispositif d'utilisateur final client (10) sur un réseau de communications (14), dans lequel l'application logicielle comprend des instructions pour exécuter la logique de routage.
  5. Système selon la revendication 4, dans lequel l'application logicielle comprend des instructions pour surveiller la présence de l'agent de centre de contact.
  6. Système selon la revendication 5, dans lequel l'application logicielle comprend des instructions pour recevoir les informations de présence d'un serveur de centre de contact (102) .
  7. Système selon l'une des revendications 4 et 6, dans lequel l'interaction est une interaction téléphonique, et l'application logicielle
    - comprend des instructions pour appeler un numéroteur afin de lancer l'interaction téléphonique,
    - fournit une interface pour inviter le client à configurer la logique de routage,
    - fournit une interface pour inviter le client à identifier un ou plusieurs agents de centre de contact préférés, et/ou
    - fournit une interface pour inviter le client à évaluer l'interaction.
  8. Système selon la revendication 7, dans lequel l'application logicielle est configurée pour partager l'évaluation avec d'autres clients.
  9. Système selon l'une des revendications 1 à 8, dans lequel le point de routage est identifié par un numéro de téléphone.
  10. Procédé de gestion des interactions d'un centre de contact client, le procédé comprenant :
    la réception, par un processeur (1521), d'une demande de réservation d'un agent de centre de contact pour gérer une interaction ;
    la réception, par le processeur (1521), de données sur l'interaction ;
    l'identification, par le processeur (1521), d'un point de routage pour acheminer l'interaction sur la base des données reçues, dans lequel le point de routage est associé à une logique de routage commandée par un client au lieu du centre de contact ; et
    l'acheminement de l'interaction vers le point de routage identifié pour donner au client la commande du routage de l'interaction ;
    caractérisé en ce que
    l'agent de centre de contact est réservé pour une durée configurable en réponse à la demande ; et
    en ce que la logique de routage est un script de routage personnalisé généré par le client, et que le script de routage personnalisé est appelé pour acheminer l'interaction vers l'agent de centre de contact réservé.
  11. Procédé selon la revendication 10, dans lequel l'interaction est une interaction téléphonique, et le procédé comprend en outre :
    l'établissement d'un chemin vocal entre le dispositif d'utilisateur final et un dispositif de l'agent de centre de contact par l'intermédiaire d'un commutateur (100).
  12. Procédé selon l'une des revendications 10 et 11, dans lequel les données reçues comprennent un identifiant d'appelant.
  13. Procédé selon l'une quelconque des revendications 10 à 12, comprenant en outre :
    la transmission d'une application logicielle au dispositif d'utilisateur final client sur un réseau de communications (14), dans lequel l'application logicielle comprend des instructions pour exécuter la logique de routage.
  14. Procédé selon la revendication 13, dans lequel l'application logicielle surveille la présence de l'agent de centre de contact.
EP15836852.2A 2014-08-27 2015-08-27 Gestion d'interaction commandée par le client Active EP3186947B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US14/470,913 US20160065741A1 (en) 2014-08-27 2014-08-27 Social media integrated agent routing
US14/470,898 US9654637B2 (en) 2014-08-27 2014-08-27 Customer controlled interaction management
PCT/US2015/047271 WO2016033371A1 (fr) 2014-08-27 2015-08-27 Gestion d'interaction commandée par le client

Publications (3)

Publication Number Publication Date
EP3186947A1 EP3186947A1 (fr) 2017-07-05
EP3186947A4 EP3186947A4 (fr) 2017-11-29
EP3186947B1 true EP3186947B1 (fr) 2020-03-04

Family

ID=55400602

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15836852.2A Active EP3186947B1 (fr) 2014-08-27 2015-08-27 Gestion d'interaction commandée par le client

Country Status (2)

Country Link
EP (1) EP3186947B1 (fr)
WO (1) WO2016033371A1 (fr)

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6064730A (en) * 1996-06-18 2000-05-16 Lucent Technologies Inc. Customer-self routing call center
US7962644B1 (en) * 2002-03-18 2011-06-14 Oracle International Corporation Systems and methods for handling a plurality of communications
US20100080378A1 (en) * 2008-09-30 2010-04-01 Avaya Inc. Accommodating telecommunications call-center
US8718272B2 (en) * 2011-03-01 2014-05-06 Verizon Patent And Licensing Inc. Contact center routing
US9047631B2 (en) * 2011-10-14 2015-06-02 Sears Brands, L.L.C. Customer assistance platform
US8874636B2 (en) * 2012-01-03 2014-10-28 Teletech Holdings, Inc. Method for providing support services using consumer selected specialist and specialist ratings
US20140100902A1 (en) * 2012-10-09 2014-04-10 Futurewei Technologies, Inc. Method and system for personal customer service solution
US8995644B2 (en) * 2012-11-02 2015-03-31 Genesys Telecommunications Laboratories, Inc. System and method for exposing customer availability to contact center agents
US8781103B2 (en) * 2012-12-12 2014-07-15 Genesys Telecommunications Laboratories, Inc. System and method for call and data matching in a contact center

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
WO2016033371A1 (fr) 2016-03-03
EP3186947A4 (fr) 2017-11-29
EP3186947A1 (fr) 2017-07-05

Similar Documents

Publication Publication Date Title
US10498896B2 (en) Customer controlled interaction management
US10171669B2 (en) System and method for routing interactions for a contact center based on intelligent and dynamic routing considerations
US10038783B2 (en) System and method for handling interactions with individuals with physical impairments
US9350867B2 (en) System and method for anticipatory dynamic customer segmentation for a contact center
US9781270B2 (en) System and method for case-based routing for a contact
CN106062803B (zh) 用于客户体验管理的系统和方法
US8938221B2 (en) System and method for providing a callback cloud
US9294624B2 (en) System and method for client interaction application integration
AU2020264378B2 (en) Adaptable business objective routing for a contact center
US20160065741A1 (en) Social media integrated agent routing
US20160205253A1 (en) System and method for client interaction application integration
US11689662B2 (en) System and method for providing personalized context
EP3186947B1 (fr) Gestion d'interaction commandée par le client
WO2014066003A1 (fr) Système et procédé pour fournir un nuage de rappel
AU2022409475A1 (en) Systems and methods relating to managing customer wait times in contact centers

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170322

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIC1 Information provided on ipc code assigned before grant

Ipc: H04M 3/51 20060101AFI20170714BHEP

Ipc: H04M 3/523 20060101ALI20170714BHEP

A4 Supplementary search report drawn up and despatched

Effective date: 20171030

RIC1 Information provided on ipc code assigned before grant

Ipc: H04M 3/51 20060101AFI20171024BHEP

Ipc: H04M 3/523 20060101ALI20171024BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04M 3/51 20060101AFI20191107BHEP

Ipc: H04M 3/523 20060101ALI20191107BHEP

INTG Intention to grant announced

Effective date: 20191211

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1241757

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200315

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015048321

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200604

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200304

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200604

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200605

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200704

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200729

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1241757

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200304

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015048321

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

26N No opposition filed

Effective date: 20201207

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200831

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200827

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200831

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200827

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200304

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230510

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230810

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230821

Year of fee payment: 9

Ref country code: DE

Payment date: 20230822

Year of fee payment: 9