The present application claims priority from U.S. application Ser. No. 17/363,984, filed on 6/30 of 2021, incorporated herein by reference in its entirety.
Disclosure of Invention
The present disclosure, by one or more of its various aspects, embodiments, and/or specific features or sub-components, is directed to various systems, servers, devices, methods, media, programs, and platforms for reporting metrics related to customer calls in a contact center environment utilizing alternative agents for multiple service applications.
In accordance with one aspect of the present disclosure, a method is provided for reporting metrics related to a customer call in a contact center environment using an alternative agent of a plurality of service applications. The method is implemented by at least one processor. The method includes receiving, by at least one processor, a service request call from a first customer, determining, by the at least one processor, at least one application from a predetermined plurality of applications available to respond to the service request call, monitoring, by the at least one processor, the service request call for information related to a time of the service request call, at least one event occurring during the service request call, and at least one output of the at least one application, determining, by the at least one processor, at least one call-specific indicator based on the information obtained as a result of the monitoring when the service request call is completed, and reporting, by the at least one processor, each of the determined at least one call-specific indicators to a predetermined destination.
The at least one call specific indicator may include at least one of hold time, talk time, average processing time, call intention, call processing, speed of answer, number of dropped calls, number of processed calls, average post-call working time, percentage of calls held, average duration of calls held, percentage of post-call working of average processing time, number and percentage of calls forwarded, number and percentage of conference calls, percentage of forwarded or conference calls combinations, percentage of service levels, number of forwarded, idle time, call count, type of service application for each service request by each team's professionals and team leader during the call, and number of call records.
The at least one call-specific indicator may also include a sum of service levels over a day, an average processing time, an average answering speed, a number of calls provided and a number of calls processed, a sum and/or an average of indicators over a predetermined interval (e.g., 30 minutes, 8 hours per day, one week, or one month). Each call and interval report has a goal and threshold that is also calculated in real-time and displayed to professionals and team leaders to monitor and take appropriate action.
The method may also include generating trends from such aggregations, which are then used for labor management and prediction.
The method may further include identifying an agent assigned to handle the service request call and calculating at least one agent-specific indicator based on the determined at least one call-specific indicator and previously stored agent-specific indicator data.
The method may further include capturing at least one metadata item associated with the service request call. The at least one metadata item may include at least one of telephony data, subscriber profile data associated with the identified agent, an identification of each of the at least one application, and information associated with whether the identified agent performed a search function during the service request call.
The method may further include displaying a user interface on a display associated with the identified agent, the user interface including information related to the service request call and information related to a historical interaction sequence corresponding to the first customer.
The at least one application may include a first application operable to respond to a first aspect of the service request call and at least a second application operable to respond to a second aspect of the service request call.
The at least one call-specific indicator may comprise a first call-specific indicator related to a first aspect of the service request call and at least a second call-specific indicator related to a second aspect of the service request call.
The method may further include monitoring and reporting using a container application designed to facilitate interaction between respective ones of the predetermined plurality of applications.
In addition, the container application may display the customer itinerary in the same call as the customer that the professional assisted, and more than one application matches the customer's intent or consultation with the processing of each application and links it to the historical interaction sequence of the customer itinerary when the customer's intent was achieved.
The at least one call-specific indicator may also include an amount of time spent within the service application of the business transaction and actions taken. These metrics, as well as other data including the customer's device, first use cases, etc., may be collected as part of a clickstream event that may be sent to a post-analysis big data system with business insight visualization.
According to another exemplary embodiment, a computing device for reporting metrics related to a customer call is presented. The computing device includes a processor, a memory, and a communication interface coupled to each of the processor and the memory. The processor is configured to receive a service request call from a first customer via a communication interface, determine at least one application from a predetermined plurality of applications available to respond to the service request call, monitor the service request call for information related to a time of the service request call, at least one event occurring during the service request call, and at least one output of the at least one application, determine at least one call specific indicator based on the information obtained as a result of the monitoring when the service request call is completed, and report each of the determined at least one call specific indicators to a predetermined destination.
The at least one call specific indicator may include at least one of hold time, talk time, average processing time, call intention, call processing, speed of answer, number of dropped calls, number of processed calls, average post-call working time, percentage of calls held, average duration of calls held, percentage of post-call working of average processing time, number and percentage of calls forwarded, number and percentage of conference calls, percentage of forwarded or conference calls combinations, percentage of service levels, number of forwarded, idle time, call count, type of service application for each service request by each team's professionals and team leader during the call, and number of call records.
The processor may be further configured to identify an agent assigned to handle the service request call and calculate at least one agent-specific indicator based on the determined at least one call-specific indicator and previously stored agent-specific indicator data.
The processor may be further configured to capture at least one metadata item related to the service request call. The at least one metadata item may include at least one of telephony data, subscriber profile data associated with the identified agent, an identification of each of the at least one application, and information associated with whether the identified agent performed a search function during the service request call.
The processor may be further configured to display a user interface on a display associated with the identified agent, the user interface including information related to the service request call and information related to a historical interaction sequence corresponding to the first customer.
The at least one application may include a first application operable to respond to a first aspect of the service request call and at least a second application operable to respond to a second aspect of the service request call.
The at least one call-specific indicator may comprise a first call-specific indicator related to a first aspect of the service request call and at least a second call-specific indicator related to a second aspect of the service request call.
The processor may also be configured to monitor and report using container applications designed to facilitate interactions between respective ones of a predetermined plurality of applications.
The container application may pass the reporting metrics collected for each set of applications to the contact center reporting system and append it as metadata for identifying records and analysis and use it as metadata when the customer is switched or contacted the company again to enrich the customer's experience.
According to yet another exemplary embodiment, a non-transitory computer-readable storage medium storing instructions for reporting metrics related to a customer call is presented. The storage medium includes executable code that, when executed by the processor, causes the processor to receive a service request call from a first client, determine at least one application from a predetermined plurality of applications available to respond to the service request call, monitor the service request call for information related to a time of the service request call, at least one event occurring during the service request, and at least one output of the at least one application, determine at least one call specific indicator based on a result of the monitoring when the service request call is completed, and report each of the determined at least one call specific indicators to a predetermined destination.
The executable code may be further configured to cause the processor to identify an agent assigned to process the service request call and calculate at least one agent-specific indicator based on the determined at least one call-specific indicator and previously stored agent-specific indicator data.
The executable code may be further configured to cause the processor to display a user interface on a display associated with the identified agent, the user interface including information related to the service request call and information related to a historical interaction sequence corresponding to the first customer.
The at least one application may include a first application operable to respond to a first aspect of a service request call and at least a second application operable to respond to a second aspect of a service request call.
Detailed Description
The disclosure is directed to one or more advantages particularly described above and below by way of one or more of its various aspects, embodiments, and/or specific features or sub-components.
Examples may also be embodied as one or more non-transitory computer-readable media having instructions stored thereon for one or more aspects of the present technology as described and illustrated herein by way of example. The instructions in some examples include executable code that, when executed by one or more processors, cause the processors to perform the steps necessary to implement the methods in the examples of the technology described and illustrated herein.
FIG. 1 is an exemplary system for use in accordance with embodiments described herein. The system 100 is generally shown and may include a computer system 102, which is generally indicated.
The computer system 102 may include a set of instructions that are executable to cause the computer system 102 to perform any one or more of the methods or computer-based functions disclosed herein, alone or in combination with other described devices. The computer system 102 may operate as a standalone device or may be connected to other systems or peripheral devices. For example, computer system 102 may include or be included in any one or more computers, servers, systems, communication networks, or cloud environments. Further, the instructions may be executed in such a cloud-based computing environment.
In a networked deployment, the computer system 102 may operate in the capacity of a server, or as a client user computer in a server-client user network environment, a client user computer in a cloud computing environment, or a peer computer system in a peer-to-peer (or distributed) network environment. Computer system 102, or portions thereof, may be implemented as or incorporated into a variety of devices, such as a personal computer, tablet computer, set-top box, personal digital assistant, mobile device, palmtop computer, laptop computer, desktop computer, communication device, wireless smart phone, personal trusted device, wearable device, global Positioning Satellite (GPS) device, network device, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while a single computer system 102 is illustrated, additional embodiments may include any collection of systems or subsystems that individually or jointly execute instructions or perform functions. The term "system" shall be taken throughout the present disclosure to include any collection of systems or subsystems that individually or jointly execute one or more sets of instructions to perform one or more computer functions.
As shown in fig. 1, computer system 102 may include at least one processor 104. The processor 104 is tangible and non-transitory. As used herein, the term "non-transitory" should not be construed as a permanent feature of a state, but rather a feature that a state will last for a period of time. The term "non-transitory" specifically denies transitory features such as the features of a particular carrier or signal or other form of carrier or signal that only exists anywhere at any time. The processor 104 is an article of manufacture and/or a machine component. The processor 104 is configured to execute software instructions in order to perform the functions as described in the various embodiments herein. The processor 104 may be a general purpose processor or may be part of an Application Specific Integrated Circuit (ASIC). The processor 104 may also be a microprocessor, microcomputer, processor chip, controller, microcontroller, digital Signal Processor (DSP), state machine, or programmable logic device. The processor 104 may also be logic circuitry including a Programmable Gate Array (PGA), such as a Field Programmable Gate Array (FPGA), or another type of circuit including discrete gate and/or transistor logic. The processor 104 may be a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), or both. Further, any of the processors described herein may include multiple processors, parallel processors, or both. Multiple processors may be included in or coupled to a single device or multiple devices.
The computer system 102 may also include a computer memory 106. The computer memory 106 may include static memory in communication, dynamic memory, or both. The memory described herein is a tangible storage medium that can store data as well as executable instructions and is non-transitory during the time that the instructions are stored therein. Also, as used herein, the term "non-transitory" should not be construed as a permanent feature of a state, but rather a feature that a state will last for a period of time. The term "non-transitory" specifically denies transitory features such as the features of a particular carrier or signal or other form of carrier or signal that only exists anywhere at any time. The memory is an article of manufacture and/or a machine component. The memory described herein is a computer-readable medium from which a computer can read data and executable instructions. The memory as described herein may be Random Access Memory (RAM), read Only Memory (ROM), flash memory, electrically Programmable Read Only Memory (EPROM), electrically Erasable Programmable Read Only Memory (EEPROM), registers, hard disk, cache, a removable disk, magnetic tape, a compact disc read only memory (CD-ROM), a Digital Versatile Disc (DVD), a floppy disk, a blu-ray disc, or any other form of storage medium known in the art. The memory may be volatile or nonvolatile, secure and/or encrypted, unsecure and/or unencrypted. Of course, the computer memory 106 may comprise any combination of memories or a single memory.
Computer system 102 may also include a display 108, such as a Liquid Crystal Display (LCD), an Organic Light Emitting Diode (OLED), a flat panel display, a solid state display, a Cathode Ray Tube (CRT), a plasma display, or any other type of display, examples of which are well known to those of skill in the art.
The computer system 102 may also include at least one input device 110, such as a keyboard, a touch-sensitive input screen or tablet, voice input, a mouse, a remote control device with a wireless keyboard, a microphone coupled to a speech recognition engine, a camera such as a video camera or still camera, a cursor control device, a Global Positioning System (GPS) device, an altimeter, a gyroscope, an accelerometer, a proximity sensor, or any combination thereof. Those skilled in the art will appreciate that various embodiments of the computer system 102 may include a plurality of input devices 110. Moreover, those skilled in the art will also appreciate that the above-listed exemplary input devices 110 are not meant to be exhaustive, and that the computer system 102 may include any additional or alternative input devices 110.
The computer system 102 may also include a media reader 112, the media reader 112 being configured to read any one or more sets of instructions, e.g., software, from any of the memories described herein. The instructions, when executed by a processor, may be used to perform one or more of the methods and processes described herein. In particular embodiments, the instructions may reside, completely or at least partially, within the memory 106, the media reader 112, and/or the processor 110 during execution thereof by the computer system 102.
Further, computer system 102 may include any additional devices, components, parts, peripherals, hardware, software, or any combination thereof, which are well known and understood to be included in computer systems, such as, but not limited to, network interface 114 and output device 116. The output device 116 may be, but is not limited to, a speaker, an audio output, a video output, a remote control output, a printer, or any combination thereof.
The various components in computer system 102 may be interconnected and communicate by a bus 118 or other communication link. As shown in fig. 1, the components may be interconnected and communicate by an internal bus. However, it will be appreciated by those skilled in the art that any of the components may also be connected by an expansion bus. Further, bus 118 may enable communication via any standard or other specification known and understood, such as, but not limited to, peripheral component interconnect express, parallel advanced technology attachment, serial advanced technology attachment, and the like.
Computer system 102 may communicate with one or more additional computer devices 120 via a network 122. The network 122 may be, but is not limited to, a local area network, a wide area network, the internet, a telephone network, a short range network, or any other network known and understood in the art. The short-range network may include, for example, bluetooth, zigbee, infrared, near field communication, ultra wideband, or any combination thereof. Those skilled in the art will appreciate that additional networks 122, which are known and understood, may additionally or alternatively be used, and that the exemplary network 122 is not limiting or exhaustive. Further, although network 122 is shown in fig. 1 as a wireless network, those skilled in the art will appreciate that network 122 may also be a wired network.
The additional computer device 120 is illustrated in fig. 1 as a personal computer. However, those skilled in the art will appreciate that in alternative embodiments of the application, computer device 120 may be a laptop computer, a tablet computer, a personal digital assistant, a mobile device, a palmtop computer, a desktop computer, a communication device, a wireless telephone, a personal trusted device, a network device, a server, or any other device capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that device. Of course, those skilled in the art will appreciate that the devices listed above are merely exemplary devices, and that device 120 may be any additional device or apparatus known and understood in the art without departing from the scope of the present application. For example, the computer device 120 may be the same as or similar to the computer system 102. Furthermore, it will also be appreciated by those skilled in the art that the apparatus may be any combination of individual apparatuses and devices.
Of course, those skilled in the art will appreciate that the above-listed components of computer system 102 are meant to be exemplary only and are not intended to be exhaustive and/or inclusive. Moreover, the examples of components listed above are also meant to be exemplary and are not meant to be exhaustive and/or inclusive as such.
According to various embodiments of the present disclosure, the methods described herein may be implemented using a hardware computer system executing a software program. Further, in an exemplary, non-limiting embodiment, implementations can include distributed processing, component/object distributed processing, and parallel processing. The virtual computer system processing may be configured to implement one or more of the methods or functions as described herein, and the processors described herein may be used to support a virtual processing environment.
As described herein, in various embodiments, an optimization method and system for reporting metrics related to customer calls with alternative agents of multiple service applications in a contact center environment are provided.
Referring to fig. 2, a schematic diagram of an exemplary network environment 200 implementing a method for reporting metrics related to customer calls with an alternative agent of a plurality of service applications in a contact center environment is shown. In an exemplary embodiment, the method may be performed on any networked computer platform, such as a Personal Computer (PC).
A method for reporting metrics related to a customer call in a contact center environment using an alternative agent of a plurality of service applications may be implemented by a Service Application Call Metrics Reporting (SACMR) device 202. SACMR the device 202 may be the same as or similar to the computer system 102 described with respect to fig. 1. SACMR device 202 may store one or more applications that may include executable instructions that, when executed by SACMR device 202, cause SACMR device 202 to perform actions such as sending, receiving, or otherwise processing network messages, and perform other actions as described and illustrated below with reference to the figures. An application may be implemented as a module or component of other applications. Further, applications may be implemented as operating system extensions, modules, plug-ins, and the like.
Further, applications may run in a cloud-based computing environment. The application may be executed within or as a virtual machine or virtual server managed in a cloud-based computing environment. Further, applications, and even SACMR devices 202 themselves, may reside in virtual servers running in a cloud-based computing environment rather than being bound to one or more specific physical network computing devices. Further, the application may run in one or more Virtual Machines (VMs) executing on SACMR devices 202. Further, in one or more embodiments of the technology, the virtual machine running on SACMR device 202 may be managed or supervised by a hypervisor.
In the network environment 200 of fig. 2, SACMR devices 202 are coupled to a plurality of server devices 204 (1) -204 (n) carrying a plurality of databases 206 (1) -206 (n) via a communication network 210, and are also coupled to a plurality of client devices 208 (1) -208 (n). SACMR a communication interface of device 202, such as network interface 114 of computer system 102 of fig. 1, is operable to couple and communicate between SACMR device 204, server devices 204 (1) -204 (n), and/or client devices 208 (1) -208 (n), all coupled together by a communication network 210, although other types and/or numbers of communication networks or systems having other types and/or numbers of connections and/or configurations to other devices and/or elements may also be used.
Communication network 210 may be the same or similar to network 122 described with respect to fig. 1, but SACMR devices 202, server devices 204 (1) -204 (n), and/or client devices 208 (1) -218 (n) may be coupled together by other topologies. In addition, network environment 200 may include other network devices, such as one or more routers and/or switches, which are well known in the art and therefore will not be described herein. The techniques provide a number of advantages, including methods, non-transitory computer-readable media, and SACMR devices that effectively implement methods for reporting metrics related to customer calls with alternative agents for multiple service applications in a contact center environment.
By way of example only, the communication network 210 may include a Local Area Network (LAN) or a Wide Area Network (WAN), and may use Ethernet TCP/IP and industry standard protocols, but other types and/or numbers of protocols and/or communication networks may also be used. The communication network 210 in this example may employ any suitable interface mechanism and network communication technology including, for example, any suitable form of long-distance communication traffic (e.g., voice, modem, etc.), public Switched Telephone Network (PSTN), ethernet-based Packet Data Network (PDN), combinations thereof, and the like.
SACMR device 202 may be a stand-alone device or may be integrated with one or more other devices or apparatuses, such as one or more of server devices 204 (1) -204 (n). In one particular example, SACMR device 202 may include or be carried by one of server devices 204 (1) -204 (n), and other devices may also be present. Further, one or more of SACMR devices 202 may be in the same communication network or in different communication networks, including, for example, one or more public, private, or cloud networks, etc.
The plurality of server devices 204 (1) -204 (n) may be the same as or similar to the computer system 102 or computer device 120 described with respect to fig. 1, including any feature or any combination of features described with respect to fig. 1. For example, any of server devices 204 (1) -204 (n) may include, among other features, one or more processors, memory, and communication interfaces coupled together by a bus or other communication link, although other numbers and/or types of network devices may be used. The server devices 204 (1) -204 (n) in this example may process requests received from SACMR devices 202 via the communication network 210 according to, for example, HTTP-based and/or JavaScript object notation (JSON) protocols, although other protocols may be used.
Server devices 204 (1) -204 (n) may be hardware or software or may represent a system having multiple servers in a pool, which may include an internal network or an external network. Server devices 204 (1) -204 (n) carry databases 206 (1) -206 (n) configured to store data related to agent-specific call service indicators and customer-specific call services.
Although server devices 204 (1) -204 (n) are illustrated as a single device, one or more actions of each server device 204 (1) -204 (n) may be distributed to one or more different network computing devices that together comprise one or more of server devices 204 (1) -204 (n). Further, the server devices 204 (1) -204 (n) are not limited to a particular configuration. Thus, the server devices 204 (1) -204 (n) may contain multiple network computing devices that operate using a master/slave approach, whereby one of the network computing devices of the server devices 204 (1) -204 (n) operates to manage and/or otherwise coordinate the operation of the other network computing devices.
Server devices 204 (1) -204 (n) may operate as multiple network computing devices within, for example, a cluster architecture, a peer-to-peer architecture, a virtual machine, or a cloud architecture. Thus, the techniques disclosed herein should not be construed as limited to a single environment, and other configurations and architectures are also contemplated.
The plurality of client devices 208 (1) -208 (n) may also be the same as or similar to the computer system 102 or computer device 120 described with respect to fig. 1, including any feature or any combination of features described with respect to fig. 1. For example, client devices 208 (1) -208 (n) in this example may include any type of computing device that may interact with SACMR devices 202 via communication network 210. Thus, client devices 208 (1) -208 (n) may be mobile computing devices, desktop computing devices, laptop computing devices, tablet computing devices, virtual machines (including cloud-based computers), and the like, that carry applications such as chat, email, or voice-to-text. In an exemplary embodiment, at least one client device 208 is a wireless mobile communication device, i.e., a smartphone.
Client devices 208 (1) -208 (n) may run interface applications, such as standard web browsers or stand-alone client applications, which may provide interfaces to communicate with SACMR devices 202 via communication network 210 in order to communicate user requests and information. Client devices 208 (1) -208 (n) may include, among other features, a display device (e.g., a display screen or touch screen) and/or an input device (e.g., a keyboard).
Although the exemplary network environment 200 is described and illustrated herein with SACMR devices 202, server devices 204 (1) -204 (n), client devices 208 (1) -208 (n), and communication network 210, other types and/or numbers of systems, devices, components, and/or elements in other topologies may be used. It should be understood that the systems in the examples described herein are for illustrative purposes as many variations of the specific hardware and software used to implement the examples are possible, as will be appreciated by those skilled in the relevant art(s).
One or more devices described in network environment 200, such as SACMR devices 202, server devices 204 (1) -204 (n), or client devices 208 (1) -208 (n), may be configured to run as virtual instances on the same physical machine. In other words, one or more of SACMR devices 202, server devices 204 (1) -204 (n), or client devices 208 (1) -208 (n) may operate on the same physical device, rather than as separate devices communicating over communication network 210. Further, there may be more or fewer SACMR devices 202, server devices 204 (1) -204 (n), or client devices 208 (1) -208 (n) than shown in fig. 2.
Further, in any example, two or more computing systems or devices may replace any one system or device. Thus, the principles and advantages of distributed processing, such as redundancy and replication, may also be implemented as needed to improve the robustness and performance of the devices and systems in the examples. These examples may also be implemented on a computer system that extends over any suitable network using any suitable interface mechanism and communication traffic technology, including, by way of example only, any suitable form of long distance communication traffic (e.g., voice, modem, etc.), wireless communication traffic networks, cellular communication traffic networks, packet Data Networks (PDNs), the internet, intranets, and combinations thereof.
SACMR device 202 is depicted and described in fig. 3 as including service application call metrics reporting module 302, but may include, for example, other rules, policies, modules, databases, or applications. As described below, contact center service structure container module 302 is configured to implement a method for reporting metrics related to customer calls with an alternative agent of a plurality of service applications in a contact center environment.
An exemplary process 300 for implementing a mechanism for reporting metrics related to a customer call for an alternative agent utilizing multiple service applications in a contact center environment using the network environment of fig. 2 is shown as being performed in fig. 3. Specifically, the first client device 208 (1) and the second client device 208 (2) are shown in communication with SACMR devices 202. In this regard, the first client device 208 (1) and the second client device 208 (2) may be "clients" of SACMR devices 202, and are described as such herein. However, it is to be appreciated and understood that the first client device 208 (1) and/or the second client device 208 (2) need not be "clients" of SACMR devices 202, or any entity described in association therewith. Any additional or alternative relationship may or may not exist between either or both of the first client device 208 (1) and the second client device 208 (2) and SACMR devices 202.
In addition, SACMR devices 202 are shown as having access to agent-specific call metrics data store 206 (1) and customer-specific call services database 206 (2). The service application call metrics reporting module 302 may be configured to access these databases to implement a method for reporting metrics related to customer calls with alternative agents of multiple service applications in a contact center environment.
The first client device 208 (1) may be, for example, a smart phone. Of course, the first client device 208 (1) may be any of the additional devices described herein. The second client device 208 (2) may be, for example, a Personal Computer (PC). Of course, the second client device 208 (2) may be any of the additional devices described herein.
The process may be performed via a communication network 210, which communication network 210 may include a plurality of networks as described above. For example, in one exemplary embodiment, either or both of the first client device 208 (1) and the second client device 208 (2) may communicate with SACMR devices 202 via broadband or cellular communications. Of course, these embodiments are merely exemplary and are not intended to be limiting or exhaustive.
Once the service application call metrics reporting module 302 is activated, it performs a process for reporting metrics related to customer calls with an alternative agent of multiple service applications in a contact center environment. An exemplary process for an alternative agent reporting metrics related to a customer call using multiple service applications in a contact center environment is generally shown in flow chart 400 of fig. 4.
In the process 400 of fig. 4, the service application call indicator reporting module 302 receives a service request call from a customer, step S402. In step S404, the call is assigned to an agent, and the service application call indicator reporting module 302 determines the identity of the agent. In an exemplary embodiment, the service application call indicator reporting module 302 may display a user interface at a workstation associated with the agent and may include information related to the call and the customer, for example, information related to a historical interaction sequence with the customer. Such information is commonly referred to as "customer itineraries".
In step S406, the service application call indicator reporting module 302 determines which of the available software applications will facilitate responding to various aspects of the customer' S service request. In an exemplary embodiment, the contact center may use a container application (container application) configured to facilitate interactions between multiple applications for various functions designed to handle customer service consultation. In this regard, the service application call indicator reporting module 302 may select one or more applications integrated into the container application for processing a particular service request made by a customer. Alternatively, the agent handling the call may simply select which applications are most helpful. Importantly, in many cases, customer service request calls may place multiple requests and/or may include several aspects, preferably handled by using different applications.
In step S408, the service application call indicator reporting module 302 monitors the call. In an exemplary embodiment, calls are monitored for time, events, and output of the application for handling each individual aspect of the service request. For example, the start time and end time of the call may be recorded, and any other time-related aspect, such as hold time and/or idle time, may be recorded. As another example, if the client transitions from a first agent to a second agent, the event may be logged. Other events and/or application outputs may vary greatly based on the specifics of the service request.
In step S410, the service application call indicator reporting module 302 determines a set of indicators associated with the customer service request call. The metrics may include call-specific metrics such as hold time, idle time, number of transfers, call count, and/or call records. The metrics may also include agent specific metrics that may be calculated with reference to previously stored agent specific data. For example, as determined in step S408, an agent-specific Average Hold Time (AHT) may be calculated by combining previously stored agent-specific AHT data with the hold time of the current call. In an exemplary embodiment, the metrics may also include metadata items related to the service request call, such as telephone data, user profile data related to the agent, identification of the application used to respond to the service request, and whether a search function was performed during the call.
In step S412, the service application call indicator reporting module 302 reports the indicator to the call center central repository so that all interested parties in the call center environment can access the indicator. In an exemplary embodiment, the container application may be used to route metrics to the appropriate destination.
Fig. 5 is an architecture diagram 500 of a system for implementing a method for reporting metrics related to a customer call with an alternative agent of a plurality of service applications in a contact center environment, according to an exemplary embodiment. As shown in architecture diagram 500, an interactive services architecture (ISF) container technology prototype implements alternative reporting through a container, where the container includes a plurality of service applications.
In an exemplary embodiment, during the same call (1 a), the professional assists the customer with multiple service applications, also referred to herein as micro-front ends, including (2 a) and (2 b) retail accounts, (3) credit card consultation, and (4) requests related to automotive loans. The index is continuously updated in (1 b). The different products may be pushed out by a hot link from one micro front end to another or with (5) an overall view micro front end. The container monitors the activity of each micro front end and sends the raw data to the ISF through the network socket. The web socket notification passes the service application event from the container to the ISF and the computed metrics from the ISF to the container.
The metrics for each service application used during the call may include any one or more of hold time, talk time, average processing time, call intent, call processing, speed of answer, number of dropped calls, number of calls processed, average post-call working time, percentage of calls held, average duration of calls held, post-call working percentage of average processing time, number and percentage of calls forwarded, number and percentage of conference calls, percentage of forwarded or conference call combinations, percentage of service levels, number of forwarded, idle time, call count, type of service application for each service request during the call for each team's professionals and team leaders, and number of call records.
The interval report may include any one or more of the total daily of service level, average processing time, average speed of answer, number of calls provided and processed, total sum and/or average of indicators over an interval (e.g., 30 minutes or 8 hours, one week or one month), targets and thresholds are also calculated in real time and displayed to professionals and team leaders for monitoring and appropriate action.
Trend ISFs can generate trends from this aggregation, which can then be used for labor management and prediction.
Interfaces with other systems-data lakes, traditional reporting systems, and analytics systems-index data and click stream data (i.e., first user access, device type, operating system, time spent, business transaction details, time spent per click stream architecture) are sent to the data lakes for historical analysis, business insight, quality, and dashboard production, as well as to traditional contact center reporting systems. Customer itinerary visualization may also be drawn by combining current calls and historical interactions.
Thus, with this technique, an optimization process is provided for reporting metrics related to customer calls in a contact center environment using alternative agents for multiple service applications.
While the invention has been described with reference to several exemplary embodiments, it is understood that the words which have been used are words of description and illustration, rather than words of limitation. Changes may be made, within the purview of the appended claims, as presently stated and as amended, without departing from the scope and spirit of the various aspects of the present disclosure. Although the invention has been described with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed, but rather extends to all functionally equivalent structures, methods and uses, such as are within the scope of the appended claims.
For example, while a computer-readable medium may be described as a single medium, the term "computer-readable medium" includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store the one or more sets of instructions. The term "computer-readable medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the embodiments disclosed herein.
The computer-readable medium may include one or more non-transitory computer-readable media and/or include one or more transitory computer-readable media. In certain non-limiting, exemplary embodiments, the computer readable medium can comprise a solid state memory, such as a memory card or other package housing one or more non-volatile read-only memories. Furthermore, the computer readable medium may be random access memory or other volatile rewritable memory. Furthermore, the computer-readable medium may include magneto-optical or optical media, such as magnetic disks or tape or other storage devices, to capture carrier signals, such as signals transmitted over transmission media. Accordingly, the disclosure is considered to include any computer-readable medium or other equivalent and successor media, in which data or instructions may be stored.
Although the application describes particular embodiments of computer programs or code segments that can be implemented in a computer readable medium, it should be understood that special purpose hardware implementations, such as application specific integrated circuits, programmable logic arrays, and other hardware devices, can be constructed to implement one or more of the embodiments described herein. Applications that may include the various embodiments set forth herein may broadly include a variety of electronic and computer systems. Accordingly, the present application may comprise software, firmware, and hardware implementations, or combinations thereof. Nothing in this application should be construed as being implemented or realized in software only and not in hardware.
Although the present specification describes components and functions that may be implemented in a particular embodiment with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Such standards are periodically superseded by faster or more effective equivalents having substantially the same function. Accordingly, alternative standards and protocols having the same or similar functions are considered equivalents thereof.
The illustrations of the embodiments described herein are intended to provide a general understanding of the various embodiments. These illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon review of this disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Moreover, these illustrations are merely representational and may not be drawn to scale. Some proportions in the illustrations may be exaggerated, while other proportions may be minimized. Accordingly, the disclosure and figures are to be regarded as illustrative rather than restrictive.
One or more embodiments of the present disclosure may be referred to herein, individually and/or collectively, by the term "application" merely for convenience and without intending to voluntarily limit the scope of this application to any particular application or inventive concept. Furthermore, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent device designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.
The Abstract of the disclosure is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing detailed description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. The following claims are, therefore, to be read in this detailed description, with each claim standing on its own as defining separately claimed subject matter.
The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments, which fall within the true spirit and scope of the present disclosure. Accordingly, to the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.