The system and method relates to contact centers, and in particular to systems and methods for displaying call flows and call statistics.
Current contact flow analysis systems are capable of displaying a call flow for a call center. In addition, these systems can display statistics for events (e.g. hitting 0 to go to the operator) in the call flow process. For example, U.S. Pat. No. 7,103,158 describes a system for displaying the events of the call flow in an Interactive Voice Response System (IVR). Statistics are generated for events in the call flow as a call flows through the IVR. These statistics are then associated with the events in the call flow.
Likewise, U.S. Patent Application No. 2007/0133777 creates a display of a call flow. Statistical information is then associated with events in the call flow. Statistics are tracked for specific call flows through the call center. A user then can select an event and display information about that particular event in a call flow. The user can also select a specific call flow through the call center and display information about that call flow.
The problem with these and other systems is that they lack the ability to fully utilize the information generated in the call flow process. As statistics are generated, the statistics from various events are not evaluated in relation to other events. This results in less effective management of call center resources.
The system and method are directed to solving these and other problems and disadvantages of the prior art. The system and method identify a plurality of call flow events in a call analysis system. Call statistics are associated with the call flow events. The call flow events are organized into event groups, each of which contains a plurality of call flow events. Once an event group is selected, call statistics for the event group are displayed. In addition, the system and method allow for selection of call flows associated with events in order to display calls associated with the events.
These and other features and advantages of the system and method will become more apparent from considering the following description of an illustrative embodiment of the system and method together with the drawing, in which:
The call analysis system 101 may be any system capable of routing calls, such as a PBX, a server, a SIP proxy server, a router, a gateway, and the like. The server 102 may be a network server, a web server, an application server, and the like. The call flow analyzer 103 may be any system capable of analyzing call flows in a call analysis system, such as server, a computer, a PBX, and the like. The call statistics 104 may be any statistics associated with a call, such as a telephone number, a call duration, a date, call flow events associated with a call, a session Identifier (ID), an indication of whether or not the call was abandoned, and the like. The call statistics 104 may be generated from any type of call such as a voice call, a video call, a text message call, a multimedia call, an email call, a chat call, and the like. The network 105 may be any type of network capable of sending and receiving data such as an Internet Protocol (IP) network, a Time Division Multiplexed (TDM) network, and the like. Telephone 106 may be any type of telephone such as an analog telephone, a digital telephone, a cellular telephone, and the like. The computer 107 may be any device that can display information, such as a Personal Computer (PC), a Personal Digital Assistant (PDA), a telephone, and the like.
As telephone calls are received in the call analysis system 101 from telephone 106 and/or other devices (not shown), call statistics 104 are generated and associated with call flow events and the call flows associated with call flow events. As the calls progress through the call analysis system 101, additional call statistics 104 are generated and associated with the call flow events and the call flows associated with call flow events. For example, if a call is received at an Integrated Voice Response system (IVR), and the caller hits “0” to access the operator, there are several call flow events associated with this call flow. The first call flow event occurs when the IVR asks the caller for input. When the caller hits “0”, the caller may be placed in a hold queue or the caller may go directly to the operator. Being placed in the hold queue is a call flow event. Likewise, having the call routed to the operator is a call flow event. As the call progresses, call statistics 104 (e.g. the time of each event) are generated and associated with the call flow events. This association can be done in either real-time or periodically.
The call flow analyzer 103 organizes a plurality of call flow events into one or more event groups 231-234. Each event group contains a plurality of call flow events. Typically, event groups 231-234 contain call flow events with similar characteristics such as being placed in a queue transferring to a different support group, transferring to an agent group, transferring to a second tier support group, and the like. However, event groups 231-234 may contain any type of call flow events.
An administrator using computer 107 selects an event group. The server 102 receives the selection of one of the event groups 231-234 and renders a display of the call statistics 104 associated with the plurality of call flow events that are included in the selected event group. The rendered display data is sent to computer 107. Computer 107 then displays the call statistics 104 associated with the call flow events in the selected event group. For example, an administrator will open a web browser on computer 107 and login into web server 102. A call flow diagram 200 like the one shown in
The call flow with the darker line that begins at start 201 and flows from consulting 203, to Joe Smith queue 206, to Joe Smith agent 212, and call ends 214 is the most frequently traveled call flow. This is the call flow that is most frequently called in the call flow diagram 200. Other end-to end paths could also be denoted.
In this example, the call flow starts 201 when a call is received in a call analysis system 101. The call flow can proceed to service 202, consulting 203, or dropped 209. If the call is dropped 209, the call is completed and the call flow ends. The call flows from service 202 to either the information queue 204 or the operator queue 205. The call flows from consulting 203 to either the Joe Smith queue 206 or the Sue Black queue 207. The call flow from the information queue 204 can proceed to call ends 214, information agent 210, or abandoned 208. The call flows from the operator queue 205 to either operator agent 211 or abandoned 208. The call flows from the Joe Smith queue 206 to either agent Joe Smith 212 or abandoned 208. The call flows from the Sue Black queue 207 to either agent Sue Black 213 or abandoned 208. The call flows from information agent 210 to call ends 214. The call flows from operator agent 211 to call ends 214. The call flows from agent Joe Smith 212 to call ends 214. The call flows from agent Sue Black 213 to call ends 214.
As an example call flow, a call starts 201 and is directed by an IVR based on a caller selecting consulting 203. Based on availability, the call is placed in the Joe Smith queue 206. The caller is on hold in the Joe Smith queue 206 until agent Joe Smith 212 becomes available. At this point, the call is routed to agent Joe Smith 212. Agent Joe Smith 212 handles the call. When agent Joe Smith 212 completes the call, the call ends 214.
The call statistics 104 for each call flow event 201, 203, 206, 212, and 214 are updated as the call progresses through those events. For example, the number of calls associated with start 201 and consulting 203 is updated to 151. Likewise, the number of calls associated with consulting 203, and the Joe Smith queue 206 is updated to 76. The call statistics 104 for the Joe Smith queue 206 call flow event are updated to indicate how long the caller waited to be serviced by agent Joe Smith 212.
The number of calls associated with the Joe Smith queue 206 and agent Joe Smith 212 is updated to 70. Call statistics 104 for agent Joe Smith 212 are updated to indicate that agent Joe Smith 212 took 14 minutes to handle the call. The number of calls associated with agent Joe Smith 212 and call ends 214 is updated to 70.
The administrator selects one of the event groups (e.g., queue group 232). Responsive to the selection, the web browser identifies the selected event group to web server 102. Web server 102 receives the identifier of the selected event group. Web server 102 renders for display the call statistics 104 associated with the plurality of call flow events included in the selected event group. In this example, the web server 102 could create a message using HTML, Java applets, Java Server Pages, and the like. The message containing the rendered display is then sent to computer 107. Computer 107 displays the call statistics 104 associated with the call flow events in the event group in the computer's web browser. For example, the graphical display 300 of
In this example, the administrator can see that the median wait time for the information queue 204 is 3 minutes. The median wait time for the operator queue 205 is 2 minutes. The median wait time for the Joe Smith queue 206 is 6 minutes. The median wait time for the Sue Black queue 207 is 12 minutes. The statistical information in the graphical display 300 assists the administrator in better allocating resources within the call analysis system 101. For example, the administrator may want to move resources to assist agent Sue Black 213 because the wait time for the Sue Black queue 207 is six times longer than the operator queue 205. Both agent Joe Smith 212 and agent Sue Black 213 have received 75 calls. The graphical display 300 also shows that the wait time for the Sue Black queue 207 is twice as long as the Joe Smith queue 206. This may indicate that that additional staff may be required to handle the calls that come into the Sue Black queue 207.
For example, the call flow diagram for abandoned calls 400 shows that there were twenty calls that were abandoned 208 from the Sue Black queue 207 out of seventy five total calls (27% abandonment rate). On the other hand, there were only six abandoned calls from the Joe Smith queue 206 out of seventy five calls (8% abandonment rate).
The administrator could select other events such as the information agent 210. The information agent 210 could represent a group of agents. Selecting the information agent 210 would display all the agents in the information agent 210.
Call table 600 is displayed to the administrator. The call table 600 shows various call statistics 104 about all of the six calls in the call flow associated with the agent Joe Smith queue 206 and the abandoned 208 call flow events. Call table 600 shows a session ID, the date of the call, the duration of the call, and how many call flow events were traversed during the call. The call statistics 104 in the call table are only a subset of many call statistics 104 that may be displayed in association with a call.
The administrator can further drill down to show the call flow for a specific call. In this example, the administrator selected the “cf” (indicating call flow) in the SESSION ID column next session ID 6. As a result, the call flow 601 for the call with the session ID of 6 is displayed to the administrator. This allows the administrator to view a call flow for a specific call. The administrator can display all the calls for any call flow path. For example, the administrator could have selected the “69” associated with the Joe Smith queue 206 and the agent Joe Smith 212 call flow events in
The administrator selects 704 a caller identifier 706 (the Call Flow (CF) icon associated with origination number (987) 123-4567). The call flow for the specific caller 705 (origination number (987) 123-4567) is displayed. In this example, all eight calls that were started 201 went to consulting 203. Four went to the Joe Smith queue 206 and four went to the Sue Black queue 207. All four calls that went to the Joe Smith queue 206 were handled by agent Joe Smith 212. Of the four calls that went to the Sue Black queue 207, two were abandoned 208 and two were handled by agent Sue Black 213. The call flow for the specific caller 705 contains two event groups 707 and 708. Event group 707 contains the Joe Smith queue 206 and the Sue Black queue 207. The event group 708 contains agent Joe Smith 212 and agent Sue Black 213. The event groups 707-708 could have associated buttons (not shown) similar to those shown in
Of course, various changes and modifications to the illustrative embodiment described above will be apparent to those skilled in the art. For example, modifications include, but are not limited to positioning a pointer over an event can show statistics about the event, only showing portions of a call flow when selecting an event, zooming in and out of level of details, viewing call flows over time, and the like. Other examples include, but are not limited to hosting versus on sight, using various report systems, analysis of call times, and hierarchical viewing. These changes and modifications can be made without departing from the spirit and the scope of the system and method and without diminishing its attendant advantages. It is therefore intended that such changes and modifications be covered by the following claims except insofar as limited by the prior art.
This application claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Application No. 61/072,183, filed Mar. 28, 2008, entitled “Contact Center Providing Integrated Analytics.”
Number | Date | Country | |
---|---|---|---|
61072183 | Mar 2008 | US |