SYSTEM AND METHOD FOR ADDING CONTENT TO CONTACT CENTER INTERACTIONS - Patent application

The system addresses inefficiencies in contact center interactions by delivering context-sensitive content through embedded applications, enhancing agent productivity and user experience.

JP7564831B6Active Publication Date: 2024-12-03GENESYS CLOUD SERVICES INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2021572058
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-06-10
Filing Date
2020-06-10
Publication Date
2024-12-03
Estimated Expiration
2040-06-10

AI Technical Summary

Technical Problem

Contact center agents face inefficiencies in accessing multiple data sources during interactions, requiring manual navigation and resource consumption, with existing solutions being labor-intensive, error-prone, and lacking context sensitivity.

Method used

A system and method for adding configurable, dynamic, and context-sensitive content to contact center interactions using embedded client applications, allowing asynchronous loading and context-aware delivery of relevant information through interruption providers.

Benefits of technology

Enables efficient, context-specific delivery of focused content to agents, reducing manual effort, minimizing resource consumption, and enhancing user experience by providing customizable and programmatically controlled add-ons.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007564831000001
    Figure 0007564831000001
  • Figure 0007564831000002
    Figure 0007564831000002
  • Figure 0007564831000003
    Figure 0007564831000003
Patent Text Reader

Abstract

A system and method are presented for adding content to contact center interactions. The interactions are routed to agents within the contact center environment. The interactions are routed through one or more providers of embedded client applications. The providers can be first-party, DSL providers, or programmatic providers. The providers trigger a user interface that displays one or more specified embedded client applications to the agent, which are loaded asynchronously via an iframe when the agent selects one of the applications.
Need to check novelty before this filing date? Find Prior Art

Description

[Background technology]

[0001] The present invention relates generally to contact center interaction systems and methods and adding content to such interactions, and more particularly to the application of content in configurable, dynamic and context-sensitive interactions.

[0002] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 62 / 859,262, entitled “SYSTEM AND METHOD FOR CONFIGURABLE, DYNAMIC, CONTEXT-SENSITIVE CONTENT FOR CONTACT CENTER INTERACTIONS,” filed in the U.S. Patent and Trademark Office on June 10, 2019. Summary of the Invention [Problem to be solved by the invention]

[0003] A system and method are presented for adding content to contact center interactions. The interactions are routed to agents in a contact center environment. The interactions are routed through one or more providers of embedded client applications. The provider can be a first party, a DSL provider, or a programmatic provider. The provider triggers a user interface that displays one or more specified embedded client applications to the agent, which are loaded asynchronously via an inline frame when the agent selects one of the applications.

[0004] In one embodiment, a method for adding content to an interaction received in a contact center environment is presented, the method including steps of: routing the interaction to an agent, where the interaction is routed through one or more providers of embedded client applications; triggering, by the one or more providers, a user interface that displays one or more specified embedded client applications to the agent; and asynchronously loading the one or more embedded client applications, where when the agent selects one of the specified embedded client applications, an address of a web page is loaded in an inline frame.

[0005] The embedded client application enables one or more parties to add dynamic content to an interaction, the one or more parties including at least one of an internal party and a third party.

[0006] The provider, the interaction, and the embedded client application include a tuple, and multiple inline frames of the embedded client application are executed.

[0007] Applications are pooled Applications are evicted from the pool based on at least one of a configurable maximum size and an eviction algorithm.

[0008] Providers include first party in-code providers that are written directly into the UI Shell and allow for notification of changes in UI Shell interaction and monitoring of state. Providers may also include DSL providers that allow defined Boolean logic to determine if an application should be displayed for a given interaction. Providers may also include programmatic providers that use any Turing complete code to determine if an application should be displayed for a given interaction.

[0009] In another embodiment, a system for adding content to interactions received in a contact center environment is presented, the system including a processor and a memory in communication with the processor, the memory storing instructions that, when executed by the processor, cause the processor to route the interaction to an agent and route the interaction through one or more providers of embedded client applications, trigger a user interface that displays one or more specified embedded client applications to the agent by the one or more providers, and asynchronously load the one or more embedded client applications to load an address of a web page in an inline frame when the agent selects one of the specified embedded client applications. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating one embodiment of a communications infrastructure.

[0011] [Diagram 2] FIG. 2 is a flow diagram illustrating one embodiment of the process.

[0012] [Figure 3A] FIG. 3A is a diagram illustrating one embodiment of a computing device.

[0013] [Figure 3B] FIG. 3B is a diagram illustrating one embodiment of a computing device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] For the purposes of promoting an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. Notwithstanding the above, it will be understood that no limitation of the scope of the invention is intended. Any changes and further modifications in the described embodiments, and any further applications of the principles of the invention as described herein, are contemplated as would normally occur to one skilled in the art to which the invention pertains.

[0015] A system and method for configurable, dynamic, and context-sensitive content for contact center interactions is presented. The configurable, dynamic, and context-sensitive embedded client applications described herein may also be referred to as "interapptions." Contact center agents often require multiple data sources to assist customers. For example, agents may need to cross-reference a customer's account with a Customer Relationship Management (CRM) system, refer to a reference tool to get relevant information, or view an internal inventory management system. The number and type of data sources vary by domain and individual customer. Previously, agents had to navigate multiple applications on their computer desktop to view information. At worst, agents must manually open other applications and either copy / paste or search to get the information they need. At best, administrators in a contact center environment can manually build screen pops (to launch external applications) or scripts to display relevant data to agents.

[0016] Existing options suffer from several pitfalls, such as manual searching and / or copy / paste by agents, screen pops, scripts, etc. Manual agent interaction is error-prone, labor / time intensive, and requires opening multiple applications per interaction or keeping multiple applications open at all times, which consumes system resources. Screen pops (i.e., dynamically opening new windows) can also be distracting to agents. Also, optimal use may require agents to manually position new windows for each interaction. In addition, the screen popped application may not be built around a use case that is centered around assisting agents and may contain extraneous information (e.g., headers, branding, navigation, etc.). The developer of the screen popped application may also not have control over the display of the application. Furthermore, the developer of the screen popped application may also not know the context in which the application is being used.

[0017] Scripts have to be built manually by contact center administrators. They are usually built for the purpose of a specific use case (such as an outbound dialing campaign or an inbound billing inquiry). Scripts are usually limited in scope, making them difficult to maintain and difficult to extend to other use cases. Scripts cannot be easily built and maintained by external software engineers and Small and Mid-sized Enterprises (SMEs). Scripts have to be built, updated and maintained manually in-house. They cannot be used on a Software-as-a-Service (SaaS) based delivery principle, where applications cannot be developed, tested and iterated outside of the contact center itself.

[0018] The Interruption System enables application developers and administrators (including first, second, and third parties) to deliver dynamic, customized, and focused content to contact center agents on a per-interaction basis. Developers can use both aspects of the interaction as well as external systems and data to determine whether an interaction would benefit from their dynamic content. Developers can use information about the interaction (customer information, media type, interaction source), the interaction content (messages and information exchanged between the customer and the agent), and metadata attached to the interaction (external customer ID, context ID, etc.) to dynamically determine content that may enrich the interaction. Additionally, developers can access external dynamic data sources to see if additional information is available for the agent to assist the customer.

[0019] Upon determining a request for dynamic content, the interruption developer / administrator can return one or many views that are embedded within the agent's user interface (UI). In addition, the application developer / administrator can dictate certain aspects of the view's display, such as layout orientation (horizontal / vertical), the required size, and its location relative to other agent views. Because the view is embedded within the agent's UI and is interaction-specific, custom views can be hyper-focused. Views do not require application headers, search boxes, navigation, etc. Rather, views are embedded right inside the agent's UI and provide focused, detailed, context-relevant information. Finally, views can utilize a command and control Software Development Kit (SDK) to request programmatic actions from the host application, such as calling attention, popping up a toast message, automatically replying to the customer, etc.

[0020] There are several advantages to the embodiments described herein. First, context-sensitive content can be delivered dynamically in an infinite number of ways. Dynamic, context-sensitive add-ons allow for a mechanism for interaction providers to enrich the interaction UI for agents. Dynamic, infinite views can be easily added to interactions, informed by internal and external data. The additional views are focused to suit the specific interaction and help the agent to help the end customer. Multiple providers are available, non-limiting examples include domain-specific language providers and programmatic providers. Domain-specific language providers may be best suited for basic application and administrator level configuration of interactions. Programmatic providers offer a Turing-complete way to dynamically query interactions and any other data sources and determine if an interaction would benefit from an interaction. These providers allow application developers and third-party authorized vendors to build compelling add-ons, allowing full access to conversations, APIs, etc. Providers can be built by third-party developers in new and unexpected verticals. Applications that do not require product development or engineering efforts to enable from developers in contact center environments unlock limitless industry verticals. Addressing multiple use cases allows multiple Interruption Providers to be configured per organization / user to provide multiple types of applications per interaction. An Interruption Provider can provide one or more interrupts per interaction, or none if none are determined to be relevant.

[0021] Second, it provides an unprecedented add-on user experience. Interruption vendors can be given control to build a compulsory add-on suite for every interaction. They can choose to return multiple interrupts with different layouts and sizes. They can build the overall functionality on the platform. Programmatic command and control access (via SDK) is also possible. For example, application developers have access to command and control APIs to deepen integration with the host application. Developers can pop up toast messages, request focus, track focus, auto-fill communications on behalf of agents, and many other things.

[0022] Third, new content delivery mechanisms are enabled. These can be first-party, second-party, and third-party. Interruptions and interruption providers can be built by many parties (contact center staff, the contact center platform provider's developers and / or its professional services organization, third-party vendors, etc.). Delivery mechanisms can be built and maintained by vendors, developers, partners, and SMEs. Interruptions and interruption providers can be built by subject matter experts rather than by a single contact center staff. Delivery mechanisms can also be externally hosted and dynamically updated (SaaS). Because interruptions are externally hosted code, both the providers and the applications themselves can be dynamically built, tested, deployed, and rolled back. Applications can be managed externally from the contact center platform.

[0023] Contact Center Systems

[0024] FIG. 1 is a diagram illustrating one embodiment of a communications infrastructure generally designated 100. For example, FIG. 1 illustrates a system for supporting a contact center in providing contact center services. A contact center can be an in-house facility to a business or enterprise for providing services to the enterprise in performing sales and service functions related to products and services available through the enterprise. In another aspect, the contact center can be operated by a third-party service provider. In one embodiment, the contact center can be operated as a hybrid system in which some components of the contact center system are hosted on the contact center premises and other components are hosted remotely (e.g., in a cloud-based environment). The contact center can be located on equipment dedicated to the enterprise or third-party service provider and / or in a remote computing environment, such as, for example, a private or public cloud environment with infrastructure to support multiple contact centers for multiple enterprises. Various components of the contact center system can also be distributed across various geographic locations and computing environments and not necessarily contained in a single location, computing environment, or even computing device.

[0025] The components of the communications infrastructure, generally designated 100, include a number of end user devices 105A, 105B, 105C, a communications network 110, a switch / media gateway 115, a call controller 120, an IMR server 125, a routing server 130, a storage device 135, a statistics server 140, a number of agent devices 145A, 145B, 145C including work bins 146A, 146B, 146C, a multimedia / social media server 150, a web server 155, an iXn server 160, a UCS 165, a reporting server 170, and a media service 175.

[0026] In one embodiment, a contact center system manages resources (e.g., workers, computers, telecommunications equipment, etc.) to enable the delivery of services over the telephone or other communications mechanisms. Such services may vary depending on the type of contact center and range from customer service to help desk, emergency response, telemarketing, order taking, etc.

[0027] Customers, potential customers, or other end users (collectively referred to as customers or end users) desiring to receive service from the contact center can initiate inbound communications (e.g., telephone calls, emails, chats, etc.) to the contact center via end user devices 105A, 105B, and 105C (collectively referred to as 105). Each of the end user devices 105 may be a communication device conventional in the art, such as a telephone, wireless telephone, smart phone, personal computer, electronic tablet, laptop, etc., to name a few non-limiting examples. A user operating an end user device 105 can initiate, manage, and respond to telephone calls, emails, chats, text messages, web browsing sessions, and other multimedia transactions. For simplicity, three end user devices 105 are illustrated in 100, although any number may be present.

[0028] Inbound and outbound communications from and to the end user device 105 may traverse a network 110 depending on the type of device being used. The network 110 may include communication networks for telephone, cellular, and / or data services, including, by way of non-limiting example, a private or public switched telephone network (PSTN), a local area network (LAN), a private wide area network (WAN), and / or a public WAN such as the Internet. The network 110 may also include wireless carrier networks, including code division multiple access (CDMA) networks, global system for mobile communications (GSM) networks, or any wireless network / technology conventional in the art, including, but not limited to, 3G, 4G, LTE, etc.

[0029] In one embodiment, the contact center system includes a switch / media gateway 115 coupled to the network 110 for transmitting and receiving telephone calls between end users and the contact center. The switch / media gateway 115 may include a telephone switch or a communication switch configured to act as a central switch for agent-level routing within the center. The switch may be a hardware switching system or a soft switch implemented via software. For example, the switch 115 may include an automatic call distributor, a private branch exchange (PBX), an IP-based software switch, and / or any other switch having dedicated hardware and software configured to receive Internet-sourced and / or telephone network-sourced interactions from customers and route these interactions, for example, to an agent telephone or communication device. In this example, the switch / media gateway establishes a voice path / connection (not shown) between the calling customer and the agent telephone device, for example, by establishing a connection between the customer telephone device and the agent telephone device.

[0030] In one embodiment, the switch is coupled to a call controller 120, which may act as, for example, an adapter or interface between the switch and other communication processing components of the contact center, such as routing, monitoring, etc. The call controller 120 may be configured to process PSTN calls, VoIP calls, etc. For example, the call controller 120 may be configured with computer-telephony integration (CTI) software for interfacing with the switch / media gateway and the contact center equipment. In one embodiment, the call controller 120 may include a session initiation protocol (SIP) server for processing SIP calls. The call controller 120 may also extract data regarding the customer interaction, such as the caller's telephone number (e.g., automatic number identification (ANI) number), the customer's Internet Protocol (IP) address, or email address, and communicate with other components of the system 100 in processing the interaction.

[0031] In one embodiment, the system 100 further includes an interactive media response (IMR) server 125. The IMR server 125 may also be referred to as a self-help system, a virtual assistant, and the like. The IMR server 125 may be similar to an interactive voice response (IVR) server, except that the IMR server 125 is not limited to voice, but may also cover a variety of media channels. In an embodiment illustrating voice, the IMR server 125 may be configured with an IMR script to query the customer's needs. For example, a bank contact center may tell a customer via an IMR script that if the customer wants to get their account balance, they should "press 1." Through continued interaction with the IMR server 125, the customer may be able to complete the service without needing to speak to an agent. The IMR server 125 may also ask open-ended questions such as "How can I help you?", and the customer may speak or otherwise input the reason for contacting the contact center. The customer's response may be used by the routing server 130 to route the call or communication to the appropriate contact center resource.

[0032] If the communication can be routed to an agent, the call controller 120 interacts with a routing server (also referred to as an orchestration server) 130 to find a suitable agent to handle the interaction. The selection of a suitable agent to route the inbound interaction can be based, for example, on a routing strategy employed by the routing server 130, and can further be based on information about agent availability, skills, and other routing parameters provided, for example, by a statistics server 140.

[0033] In one embodiment, the routing server 130 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 the contact center to resolve any customer issues. The database may be, for example, Cassandra or any NoSQL database and may be stored on the mass storage device 135. The database may also be a SQL database and may be managed by any database management system, such as, for example, Oracle, IBM DB2, Microsoft SQL Server, Microsoft Access, PostgreSQL, to name a few non-limiting examples. The routing server 130 may query the customer database for customer information via the ANI or any other information collected by the IMR server 125.

[0034] Once a suitable agent is identified as available to handle the communication, a connection may be made between the customer and the identified agent's agent device 145A, 145B, and / or 145C (collectively referred to as 145). Although three agent devices are illustrated in FIG. 1 for simplicity, any number of devices may be present. Information collected regarding the customer and / or customer history information may be provided to the agent device for purposes of assisting the agent in better servicing the communication, as well as to a manager / supervisor device for management of the contact center. In this regard, each device 145 may include a telephone adapted for regular telephone calls, VoIP calls, and the like. The devices 145 may also include a computer for communicating with one or more servers of the contact center, performing data processing associated with contact center operations, and interacting with customers via voice and other multimedia communication mechanisms.

[0035] The contact center system 100 may also include a multimedia / social media server 150 for engaging in media interactions other than voice interactions with the end user devices 105 and / or a web server 155. The media interactions may relate to, for example, email, voicemail (voicemail over email), chat, video, text messaging, web, social media, co-browsing, etc. The multimedia / social media server 150 may take the form of any IP router conventional in the art, with specialized hardware and software for receiving, processing, and forwarding multimedia events.

[0036] The web server 155 may include, for example, social networking site hosts for various known social networking sites to which end users may join, such as Facebook, Twitter, Instagram, to name a few non-limiting examples. In one embodiment, the web server 155 is shown as part of the contact center system 100, but the web server may also be provided by a third party and / or maintained outside the contact center premises. The web server 155 may also provide web pages for businesses supported by the contact center system 100. End users may browse the web pages and obtain information about the products and services of the businesses. The web pages may also provide mechanisms for contacting the contact center via, for example, web chat, voice calls, email, web real-time communications (WebRTC), etc. Widgets may be deployed on websites hosted on the web server 155.

[0037] In one embodiment, deferrable interactions / activities may also be routed to contact center agents in addition to real-time interactions. Deferrable interactions / activities may include back office tasks or tasks that may be performed offline, such as responding to emails, letters, attending training, or other activities that do not require real-time communication with customers. The interaction (iXn) server 160 interacts with the routing server 130 to select an appropriate agent to handle the activity. Once assigned to an agent, the activity may be pushed to the agent or may appear in the agent's work bins 146A, 146B, 146C (collectively 146) as tasks to be completed by the agent. The agent's work bins may be implemented via any data structure conventional in the art, such as, for example, linked lists, arrays, etc. In one embodiment, the work bins 146 may be maintained, for example, in a buffer memory of each agent device 145.

[0038] In one embodiment, mass storage device 135 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 but not limited to, reason for the interaction, processing data, wait times, processing times, etc.), etc. In another embodiment, some of the data (e.g., customer profile data) may be maintained in a CRM database hosted on mass storage device 135 or elsewhere. Mass storage device 135 may take the form of a hard disk or disk array, as is conventional in the art.

[0039] In one embodiment, the contact center system may include a universal contact server (UCS) 165 configured to retrieve information stored in a CRM database and to direct information to be stored in the CRM database. The UCS 165 may also be configured to facilitate maintaining customer preference and interaction histories, capture and store data regarding comments from agents, customer communication history, and the like.

[0040] The contact center system may also include a reporting server 170 configured to generate reports from the data aggregated by the statistics server 140. Such reports may include near real-time or historical reports regarding resource status, such as, for example, average wait times, relaxation rates, agent occupancy, etc. Reports may be generated automatically or in response to a specific request from a requester (e.g., an agent / administrator, a contact center application, etc.).

[0041] The various servers in FIG. 1 may each include one or more processors that execute computer program instructions and interact with other system components to perform the various functions described herein. The computer program instructions are stored in a memory implemented using standard memory devices such as, for example, a random access memory (RAM). The computer program instructions may also be stored on other non-transitory computer-readable media such as, for example, a CD-ROM, a flash drive, etc. Although the functionality of each of the servers is described as being provided by a particular server, those skilled in the art should understand that the functionality of the various servers may be combined or consolidated into a single server, or the functionality of a particular server may be distributed among one or more other servers without departing from the scope of embodiments of the present invention.

[0042] In one embodiment, the terms "interaction" and "communication" are used interchangeably and generally refer to any real-time and non-real-time interaction using any communication channel, including, but not limited to, phone calls (PSTN or VoIP calls), email, vmail, video, chat, screen sharing, text messages, social media messages, WebRTC calls, etc.

[0043] Media services 175 may provide audio and / or video services to support contact center functions such as IVR or IMR system prompts (e.g., playing audio files), music on hold, voicemail / single-party recording, multi-party recording (e.g., audio and / or video calls), speech recognition, dual-tone multi-frequency (DTMF) recognition, fax, audio and video transcoding, Secure Real-Time Transport Protocol (SRTP), audio conferencing, video conferencing, coaching (e.g., support for a coach to listen to an interaction between a customer and an agent, and support for a coach to provide comments to an agent without the customer hearing the comments), call analysis, and keyword spotting.

[0044] In one embodiment, the premises-based platform product may provide access and control of components of the system 100 via a UI present on the agent devices 145A-C. A graphical application generator program may be integrated within the premises-based platform product, allowing users to create programs (handlers) that control various interaction processing behaviors within the premises-based platform product.

[0045] As noted above, a contact center may operate as a hybrid system in which some or all components are remotely hosted, such as in a cloud-based environment. For convenience, aspects of an embodiment of the present invention are described below with respect to providing SaaS from a cloud-based environment to components housed on premises.

[0046] FIG. 2 is a flow diagram illustrating an embodiment of a process, generally designated 200, for configuring providers, displaying interruptions when an interaction is routed to an agent, and optionally handling state changes. The interface platform includes several components, including providers, application configuration, and display. As illustrated in 200, a host application 200A, a provider factory 200B, a dynamic interrupt provider 200C, a SaaS public API 200D, and an external / private application API 200E are shown. Initially, when a developer or administrator wants to create a new provider in the system, the host application 200A sends a request for providers "getProvidersForUser(userContext)" to the provider factory 200B (202). The host application 200A includes a SaaS platform that may be executed in a contact center environment. The provider factory 200B includes multiple interrupt providers that may be configured or installed by an administrator or built into the host application 200A. Providers configured or installed by an administrator may be stored with the dynamic interrupt provider 200C. An interrupt provider consists of a bit of software that utilizes the details of a specified interaction and external factors and data sources to determine if the provider wants to embellish the specified interaction with dynamic content in the form of an interrupt. Interrupt providers may be configured and enabled dynamically / programmatically. Thus, there may be any number of interrupt providers for different organizations, departments, or users. Also, the list of interrupt providers available to a given user may change due to factors such as user access control, licenses, etc. The provider factory 200B sends a create request (204) to the dynamic interrupt provider 200C.The dynamic interrupt provider 200C returns an acknowledgement to the provider factory 200B (206), which sends the array of providers to the host application 200A (208). The list of third-party interrupt providers is updated and executed in a separate execution context (210).

[0047] When an interaction is received within the contact center environment, the third-party provider is invoked via messaging rather than a direct method call (212). Each conversation routed to an agent is passed to one or more interrupt providers. In one embodiment, the DSL provider is not passed any arguments since the DSL grammar is interpreted for them. The host application 200A requests the application's configuration (e.g., interaction ID, callback) from the dynamic interrupt provider 200C. Depending on the provider type, the provider can send the entire interaction object, the interaction ID, or non-interaction data. The dynamic provider also allows the provider to dynamically change the interrupt list at any point in time by sending a callback. The dynamic interrupt provider 200C requests the conversation details using the interaction ID from the SaaS public API 200D (214). The SaaS public API returns (216) the conversation details to the dynamic interruption provider 200C, which then requests (218) the customer record from the external private application API 200E. The external private application API returns (220) the external customer record as an object to the interruption provider 200C. The interruption provider 200C returns (222) the interruption configuration to the host application 200A. In one embodiment, if there is no matching application, no application may be returned. In another embodiment, there may be one or more that apply to the interaction passed.

[0048] The interrupt provider 200C must return 222 a list of interface configuration objects that tell the host application 200A how to render the desired interruptions. Among other data, these configuration objects include the ID, name, icon, URL of the application to load, security settings (iframe sandbox settings), layout and preferred size (e.g., horizontal vs. vertical, 50% vs. 75%), and application type for special host application handling (grouping, ordering, etc.).

[0049] There are several types of interaction providers, including built-in, DSL, and programmatic, to name a few non-limiting examples. Built-in interrupt providers are code reserved for first class code or written by the developers of the SaaS platform to be used within a contact center environment. They provide a complete interaction object and can access any resource within the SaaS platform. These types of providers are not available to third parties. DSL interrupt providers utilize a DSL grammar (or Boolean logic) that can be used to ascertain the details of the interaction to determine if an interrupt should be presented for a given interaction. This interpretation can be done within the sandbox of the host application, since the DSL does not allow for arbitrary code execution. Also, there is no need to transfer data to the developers of the interrupt provider at this stage for evaluation.

[0050] The interruption provider DSL can be specified by the contact center administrator at installation time or can be pre-configured by the application vendor as a managed solution.

[0051] The final and most advanced type of interrupt provider is the programmatic provider. This provider can execute any Turing complete code in an isolated sandbox and make decisions regarding interrupts. This type of interrupt provider can also make calls to any data source available on the Internet to gather more data. Finally, this provider can manually update the list of available interrupts for an interaction at any time. This type of provider is written directly into the UI shell (or web directory). It allows the application developer to be notified of interaction changes, monitor other details of the web directory state such as feature toggles, permissions, and also has access to out-of-band application update callbacks.

[0052] Programmatic interruption providers are best suited for specialist developers who want to build a high quality dynamic integration suite for use in a particular contact center. Upon receiving interrupt configurations from various interruption providers, the host application 200A can display various views to the agent 224 via a tabbed or other layout UI. The host application 200A makes the correct interrupts available for the active interaction selected by the agent, at the location specified by the interruption configuration. The interrupts are loaded lazily (or asynchronously). When the user clicks on a tab in the application, a web browser loads the specified URL for the user in an iframe.

[0053] In one embodiment, the client application SDK can be called to interact with the application lifecycle (bootstrap, blur, focus, stop). Views in the host application 200A can also utilize command-and-control UI commands to request programmatic behavior from the host application (226), such as calling attention, popping a toast message, automatically replying to the customer, etc. The programmatic behavior is returned (228) from the dynamic interrupt provider 200C.

[0054] In one embodiment, the dynamic interrupt provider 200C can use callbacks to update the list of applications within the host application 200A at any time if there is an interaction or external state change (230). The host application's 200A display of interruptions can be refreshed using an LRU algorithm (232). In web-based products, the view itself is created as an inline frame (or "iframe"), allowing for isolation of code execution for third-party applications. The view is cached between interactions, allowing the state of the interruption to be quickly restored. Interruptions can be evicted (e.g., when a maximum number of simultaneous interrupts is reached) based on a configurable maximum size and eviction algorithm (e.g., a Least Recently Used (LRU) algorithm). Applications are pooled to allow iframes to remain in the Document Object Model (DOM) to maintain state, and also to limit the total resources utilized by the DOM. Interrupts are pooled across all active interactions and providers and capped by the web directory. Applications may be evicted from the pool based on an LRU algorithm when they reach a maximum number of simultaneous interrupts (or other threshold). As a result, an application may be discarded at any time except when a user is directly interacting with the application. The application is lightweight to load / reload, reducing the amount of state it maintains.

[0055] In one embodiment, the provider, interaction, and interruption function function as a tuple. Multiple instances (iframes) of an application can run within a web directory. The application developer does not need to manage the state of the current interaction.

[0056] In one embodiment, in addition to when an interaction is initially routed to an agent, conversation changes may also trigger provider flows (regardless of provider type). Providers can respond to conversation (state) changes as well as attached context that may be provided (such as web chat or association with an external contact).

[0057] Computer Systems

[0058] In one embodiment, each of the various servers, controllers, switches, gateways, engines, and / or modules (collectively referred to as servers) of the illustrated figures is implemented via hardware or firmware (e.g., ASICs), as will be appreciated by those skilled in the art. Each of the various servers may be a process or thread running on one or more processors and executing computer program instructions in one or more computing devices (e.g., FIG. 3A, FIG. 3B) and interacting with other system components to perform the various functions described herein. The computer program instructions are stored in a memory that may be implemented in the computing device using standard memory devices such as, for example, RAM. The computer program instructions may also be stored in other non-transitory computer readable media such as, for example, CD-ROM, flash drive, etc. Those skilled in the art should recognize that a computing device may be implemented via firmware (e.g., application specific integrated circuit), hardware, or a combination of software, firmware, and hardware. Those skilled in the art should also recognize that the functionality of the various computing devices may be combined or integrated into a single computing device, or the functionality of a particular computing device may be distributed among 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 that may also simply be referred to as a module. The set of modules in a contact center may include servers and other modules.

[0059] The various servers may be located on on-site computing devices in the same physical location as the contact center agents, or may be located off-site in different geographic locations, e.g., in a remote data center connected to the contact center via a network such as the Internet. Furthermore, some of the servers may be located in on-site computing devices at the contact center while other servers may be located in off-site computing devices, or servers providing redundant functionality may be provided via both on-site and off-site computing devices to provide better fault tolerance. In some embodiments, functionality provided by servers located on off-site computing devices may be accessed and provided via a virtual private network (VPN) as if such servers were on-site, or functionality may be provided using SaaS as a Service to provide functionality over the Internet using various protocols, such as by exchanging data using encoding in extensible markup language (XML) or JSON.

[0060] 3A and 3B are diagrams illustrating an embodiment of a computing device, generally designated 300, that may be used in embodiments of the present invention. Each computing device 300 includes a CPU 305 and a main memory unit 310. As illustrated in FIG. 3A, the computing device 300 may also include a storage device 315, a removable media interface 320, a network interface 325, an input / output (I / O) controller 330, one or more display devices 335A, a keyboard 335B, and a pointing device 335C (e.g., a mouse). The storage device 315 may include, but is not limited to, storage for an operating system and software. As shown in FIG. 3B, each computing device 300 may also include additional optional elements, such as a memory port 340, a bridge 345, one or more additional I / O devices 335D, 335E, and a cache memory 350 in communication with the CPU 305. The input / output devices 335A, 335B, 335C, 335D, and 335E may be referred to collectively herein as 335.

[0061] The CPU 305 is any logic circuit that responds to and processes instructions fetched from the main memory unit 310. For example, the CPU 305 may be implemented in an integrated circuit in the form of a microprocessor, microcontroller, or graphics processing unit, or in a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC). The main memory unit 310 may be one or more memory chips that store data and allow any storage location to be directly accessed by the central processing unit 305. As shown in FIG. 3A, the central processing unit 305 communicates with the main memory 310 via a system bus 355. As shown in FIG. 3B, the central processing unit 305 may also communicate directly with the main memory 310 via a memory port 340.

[0062] In one embodiment, the CPU 305 may include multiple processors and may provide functionality for the concurrent execution of instructions or the concurrent execution of a single instruction on one or more pieces of data. In one embodiment, the computing device 300 may include a parallel processor having one or more cores. In one embodiment, the computing device 300 comprises a shared memory parallel device having multiple processors and / or multiple processor cores that access all available memory as a single global address space. In another embodiment, the computing device 300 is a distributed memory parallel device having multiple processors that each access only local memory. The computing device 300 may have both some memory that is shared and some memory that may only be accessed by a particular processor or subset of processors. The CPU 305 may include a multi-core microprocessor that combines two or more independent processors in a single package, e.g., in a single integrated circuit (IC). For example, the computing device 300 may include at least one CPU 305 and at least one graphics processing unit.

[0063] In one embodiment, CPU 305 provides single instruction multiple data (SIMD) capabilities, e.g., the ability to execute a single instruction on multiple pieces of data simultaneously. In another embodiment, some processors in CPU 305 may provide the ability to execute multiple instructions on multiple pieces of data simultaneously (multiple pieces of data (MIMD)). CPU 305 may also use any combination of SIMD and MIMD cores within a single device.

[0064] 3B shows an embodiment in which the CPU 305 communicates directly with the cache memory 350 via a secondary bus, sometimes referred to as a backside bus. In another embodiment, the CPU 305 communicates with the cache memory 350 using a system bus 355. The cache memory 350 typically has a faster response time than the main memory 310. As illustrated in FIG. 3A, the CPU 305 communicates with various I / O devices 335 via a local system bus 355. Various buses can be used as the local system bus 355, including, but not limited to, a Video Electronics Standards Association (VESA) local bus (VLB), an Industry Standard Architecture (ISA) bus, an Extended Industry Standard Architecture (EISA) bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI Extended (PCI-X) bus, a PCI-Express bus, or a NuBus. For embodiments in which the I / O device is a display device 335A, the CPU 305 may communicate with the display device 335A via an Advanced Graphics Port (AGP). Figure 3B illustrates an embodiment of a computer 300 in which the CPU 305 communicates directly with an I / O device 335E. Figure 3B also illustrates an embodiment in which local bus and direct communication are mixed. The CPU 305 communicates with the I / O device 335D using the local system bus 355 while communicating directly with the I / O device 335E.

[0065] A wide variety of I / O devices 335 may be present in computing device 300. Input devices include one or more keyboards 335B, a mouse, a trackpad, a trackball, a microphone, and a drawing board, to name a few non-limiting examples. Output devices include a video display device 335A, speakers, and a printer. The I / O controller 330 shown in FIG. 3A may control one or more I / O devices, such as, for example, a keyboard 335B and a pointing device 335C (e.g., a mouse or optical pen).

[0066] 3A, computing device 300 may support one or more removable media interfaces 320, 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 FLASH™ 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. I / O device 335 may be a bridge between system bus 355 and removable media interface 320.

[0067] The removable media interface 320 may be used, for example, to install software and programs. The computing device 300 may further include a storage device 315, 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. Optionally, the removable media interface 320 may also be used as a storage device. For example, the operating system and software may be executed from a bootable medium, such as a bootable CD.

[0068] In one embodiment, the computing device 300 may include or be connected to multiple display devices 335A, each of which may be the same or different type and / or form. Thus, any of the I / O devices 335 and / or I / O controllers 330 may include 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 335A by the computing device 300. For example, the computing device 300 may include any type and / or form of video adapter, video card, drivers, and / or libraries for interfacing, communicating, connecting, or otherwise using the display devices 335A. In one embodiment, the video adapter may include multiple connectors for interfacing to the multiple display devices 335A. In another embodiment, the computing device 300 may include multiple video adapters, each video adapter connected to one or more of the display devices 335A. In other embodiments, one or more of the display devices 335A may be provided by one or more other computing devices connected to the computing device 300, for example, via a network. These embodiments may include any type of software designed and constructed to use a display device of another computing device as a second display device 335A for computing device 300. Those skilled in the art will recognize and understand the various ways and embodiments in which computing device 300 may be configured to have multiple display devices 335A.

[0069] The embodiment of a computing device generally shown in Figures 3A and 3B may operate under the control of an operating system, which controls the scheduling of tasks and access to system resources. Computing device 300 may run any operating system, any embedded operating system, any real-time operating system, any open source operating system, any proprietary operating system, any operating system for mobile computing devices, or any other operating system capable of running on a computing device and performing the operations described herein.

[0070] Computing device 300 may be any workstation, desktop computer, laptop or notebook computer, server machine, computer on a steering wheel, mobile phone or other portable telecommunications device, media playback device, gaming system, mobile computing device, or any other type and / or form of computing, telecommunications, or media device capable of communicating and having sufficient processor power and memory capacity to perform the operations described herein. In some embodiments, computing device 300 may have different processors, operating systems, and input devices consistent with the device.

[0071] In other embodiments, computing device 300 is a mobile device. Examples may include a Java-enabled mobile phone or personal digital assistant (PDA), a smartphone, a digital audio player, or a portable media player. In one embodiment, computing device 300 includes a combination of devices, such as a mobile phone combined with a digital audio player or portable media player.

[0072] The computing device 300 may be one of or may include multiple machines connected by a network. A network environment may include one or more local machines, client nodes, client machines, client computers, client devices, endpoints, or endpoint nodes that communicate with one or more remote machines (which may also be generally referred to as server machines or remote machines) over one or more networks. In one embodiment, a local machine has the ability to function as both a client node seeking access to resources provided by a server machine, and a server machine providing access to hosted resources for other clients. The network may be a LAN or WAN link, a broadband connection, a wireless connection, or a combination of any or all of the above. Connections may be established using a variety of communication protocols. In one embodiment, the computing device 300 communicates with other computing devices 300 through any type and / or form of gateway or tunneling protocol, such as Secure Socket Layer (SSL) or Transport Layer Security (TLS). A network interface may include a built-in network adapter, such as a network interface card, suitable for interfacing the computing device to any type of network with which it can communicate and performing the operations described herein. The I / O device may be a bridge between the system bus and an external communication bus.

[0073] In one embodiment, the network environment may be a virtual network environment in which various components of the network are virtualized. For example, the various machines may be virtual machines implemented as software-based computers running on physical machines. The virtual machines may share the same operating system. In other embodiments, different operating systems may run on each virtual machine instance. In one embodiment, a "hypervisor" type of virtualization is implemented in which multiple virtual machines run on the same host physical machine, each functioning as if they had their own dedicated box. Virtual machines may also run on different host physical machines.

[0074] Other types of virtualization are contemplated, such as, for example, the network (e.g., via Software Defined Networking (SDN)). Functions, such as the Session Border Controller function and other types of functions, may also be virtualized, such as, for example, via Network Functions Virtualization (NFV).

[0075] In one embodiment, the use of LSH to automatically discover carrier audio messages within a large set of pre-connected audio recordings can be applied to support processes of media services for contact center environments, for example, this can help support call analysis processes for contact centers and eliminate the need for humans to listen to a large set of voice recordings to discover new carrier audio messages.

[0076] While the invention has been illustrated and described in detail in the drawings and foregoing description, it is to be considered illustrative and not of a limiting character, with the understanding that only the preferred embodiment has been shown and described, and that all equivalents, changes and modifications which come within the spirit of the invention as set forth in this specification and / or the following claims are desired to be protected.

[0077] Accordingly, the appropriate scope of the present invention should be determined only by the broadest interpretation of the appended claims so as to encompass all such modifications and all equivalent relationships as illustrated in the drawings and described herein.

Claims

1. 1. A method for adding content to a received interaction in a contact center environment, comprising: routing the interaction to an agent, the interaction being routed through one or more providers of a client application embedded in a user interface; triggering a user interface by the one or more providers to display one or more specified client applications to the agent; asynchronously loading the one or more client applications, where when the agent selects one of the specified client applications, a web page address is loaded in an inline frame.

2. The method of claim 1 , wherein the client application enables one or more parties to add dynamic content to an interaction.

3. The method of claim 2 , wherein the one or more parties include at least one of an internal party and a third party.

4. The method of claim 1 , wherein the provider, the interaction, and the client application comprise a tuple, and multiple inline frames of the client application are executed.

5. The method of claim 1 , wherein the client applications are pooled.

6. The method of claim 5 , wherein the client applications are evicted from the pool based on at least one of a configurable maximum size and an eviction algorithm.

7. The method of claim 1 , wherein the provider comprises a first party in-code provider that writes directly into the UI Shell and enables notification of interaction changes and state monitoring of the UI Shell.

8. The method of claim 1 , wherein the provider comprises a DSL provider.

9. The method of claim 8 , wherein the provider enables defined Boolean logic to determine whether the client application should be displayed for a given interaction.

10. The method of claim 1 , wherein the provider comprises a programmatic provider.

11. The method of claim 10 , wherein the provider uses any Turing complete code to determine whether a client application should be displayed for a given interaction.

12. A system is presented for adding content to interactions received within a contact center environment, the system comprising: A processor; and a memory in communication with the processor, the memory, when executed by the processor, causing the processor to: routing the interaction to an agent to route the interaction through one or more providers of a client application embedded in a user interface; triggering, by the one or more providers, a user interface that displays one or more designated client applications to the agent; and storing instructions that cause the one or more embedded client applications to asynchronously load and, when the agent selects one of the specified client applications, load an address of a web page into an inline frame.

13. The system of claim 12 , wherein the client application enables one or more parties to add dynamic content to an interaction.

14. The system of claim 13 , wherein the one or more parties include at least one of an internal party and a third party.

15. The system of claim 12 , wherein the provider, the interaction, and the client application comprise tuples, and wherein multiple inline frames of the embedded client application are executed.

16. The system of claim 12 , wherein the client applications are pooled.

17. 20. The system of claim 16, wherein the client applications are evicted from the pool based on at least one of a configurable maximum size and an eviction algorithm.

18. 13. The system of claim 12, wherein the provider includes a first party in-code provider that writes directly into the UI shell and enables notification of interaction changes and state monitoring of the UI shell.

19. The system of claim 12 , wherein the provider comprises a DSL provider.

20. 20. The system of claim 19, wherein defined Boolean logic enables the provider to determine whether the client application should be displayed for a given interaction.

21. The system of claim 12 , wherein the provider comprises a programmatic provider.

22. 22. The system of claim 21, wherein the provider uses any Turing complete code to determine whether a client application should be displayed for a given interaction.

Citation Information

Patent Citations

  • Web-content aware automatic call transfer system and process for mobile users and operators

    US20030187988A1