Patent Grant
7912205
The field of the invention relates to telephonic communication systems and more particularly to automatic call distributors that route calls based in part on timely business information.
Automatic call distribution systems are known, such systems are typically used in an organizational context as a means of distributing telephone calls among agents of the organization. To improve the consistency and quality of call handling, agents are typically segregated into groups to serve particular call targets of the organization.
Often the organization disseminates a single telephone number to its customers and to the public in general as a means of contacting the organization. As calls are directed to the organization from the telephone network, the automatic call distribution system directs the calls to its agents based upon some algorithm, typically based upon availability. For example, where all agents are considered equal, the automatic call distributor may distribute the calls based upon which agent position or telephone has been idle the longest.
Previous solutions that route transactions or calls based on contact center performance statistics such as service level, agent occupancy, and average speed of answer are limited in that they can not be programmed effectively to simulate or route transactions based on timely business key process indicators (KPI) information. Another disadvantage is that existing solutions, although referencing a profit business indicator, do not disclose the usage of a simulation model to determine impacts on KPIs, assignment of routings across multiple business objectives, nor address the overall business cost process in assigning routes to calls. Furthermore, the relationship to business operational objectives, such as a goal to increase sales by a certain percentage, are not directly driven as part of the contact center routing operation such that the results from the contact center could not be automatically calculated together or in combination with information from the business systems.
Determining KPI metrics for a business objective are well known, but their incorporation as a factor in the routing of calls is a previously unexplored field. The article, A Standard for Business Architecture description, IBM SYSTEMS JOURNAL, VOL 38, NO 1, 1999, discusses in general terms the relationships between various business concepts to show how these can be used in an information technology environment but does not teach implementing or incorporating the concepts into equipment for routing transactions. The article, An analytic approach for quantifying the value of e-business initiatives, IBM SYSTEMS JOURNAL, VOL 42, NO 3, 2003, shows the following as meaningful business operational metrics but fails to disclose how these can or should be coupled with contact center call statistics to create call routing decisions: “shareholder value added”, “operating income”, “return on net assets”, “cash to cash cycle time”, “operating profit margin”, “inventory turnover”, “days receivables outstanding”, “days payables”, “on time delivery”, “order to delivery lead time”.
The present invention addresses these and other deficiencies inherent in existing automatic call distribution systems. In one embodiment, there is provided a call distribution system and method that incorporates a simulation model to determine impacts on KPI, assignment of routings across multiple business objectives and addresses the overall business cost process in assigning routes to calls. Another embodiment provides a system for a closed loop simulation of contact center business KPIs objectives and operational objectives by allowing stand alone modeling and scenario analysis to be used indirectly in production and allowing use of true production feedback to improve the model. In another form, a model is provided to simulate or route transactions (calls) based on timely business (KPI) information.
Other variations include, simulation models to account for the relationship to business operational objectives, such as a goal to increase sales by a specific percentage, directly driven as part of the contact center routing operation such that the results/path from the contact center can be automatically calculated together or in combination with information from the business systems. In one form, it is desirable that a programmable model be used that has two modes. One mode that allows entry of a model and one that allows only for altering simulation values to prevent changes to the structure of the model. As the model that can be created may be unique for each business structure, a variety of model configurations are possible.
A system and method are provided for distribution of calls using a simulation model to process information used for routing the calls. In one embodiment, the invention comprises inputting information to the simulation model from select business sources, calculating and generating information from the model, and determining key process indicators information. Then decisions are generated for routing a call based on the information from the model and key process indicators information, and a call is routed based on the generated decisions.
While the present invention is susceptible of embodiments in various forms, there is shown in the drawings and will hereinafter be described some exemplary and non-limiting embodiments, with the understanding that the present disclosure is to be considered an exemplification of the invention and is not intended to limit the invention to the specific embodiments illustrated. In this disclosure, the use of the disjunctive is intended to include the conjunctive. The use of the definite article or indefinite article is not intended to indicate cardinality. In particular, a reference to “the” object or “a” object is intended to denote also one of a possible plurality of such objects.
One embodiment of the invention is shown in
Once the simulator 24 calculations are completed and accepted, the output from the simulator may be sent directly to the routing engine for directing the processing of transactions. It is also desirable that the simulator 24 collects information from the router so that simulator parameters can be adjusted to match the current router conditions for optimal transaction routing against the business objectives. Further, information such as sales, forecast, orders, cost, expense, and income data may be collected from a business system as a key process indicator (KPI) input for altering the behavior of the modeler simulation model to give differing outputs to the simulator 24 as business results change. Each of the oval shape represents a simulation process objective in the business model in
As an example of a screen view of a modeler 50 KPI result shown in
After a simulation completion, the information generated by the simulator may be sent to the Business Systems 20, a recommendation engine, and a router engine to alter the routing of transactions either singularly or in an associated group. It is often desirable that a programmable model be used that has 2 modes—one that allows entry of a model and one that allows only for altering simulation values to prevent changes to the structure of the model. As the model that can be created may be unique for each business structure, a variety of model configurations are possible. Some of the contact center specific solutions that may be presented to the model to represent the contact center include, but are not limited to, the equations shown below (developed at Purdue University):
The metrics above represent possible KPI values for the contact center and some of them involve collecting transaction information across multiple business systems such as the final metric on the list—“Once and Done”. One benefit of this approach is that not only does it allow for such conglomerated statistics to be created, but it also allows for the metric to be used as part of the determination of the routing of additional transactions. Each device in a contact center, such as an automatic call distributor (ACD), may provide its own set of KPI values that can be used in the modeling. Various devices (e.g., an Email processing system) may also be combined in the contact center to provide KPI metrics that can be combined with other contact center KPI statistics to provide an overall simulation of the effectiveness of the contact center. It is often desirable that these and other metrics be available directly to the simulator to create a model for doing contact routing decisions. Values may also be monitored, collected, or calculated from analyzing a data depository to be used within the simulation model from other equipment. Additionally, statistics available from reporting systems such as agents call handling time, application service levels or average speed of answer may be used for the calculations.
In certain embodiments, it is desirable that models for other contact center equipment, such as a voice response system be fabricated and used within the model to allow for systems that do not directly offer KPI statistics in order to calculate an optimum route decision. Also, models within the simulator for this equipment may also then present a more realistic view of the operation of the overall system of components.
Collecting information from the router is similar to collecting information from other contact center systems. Information such as the number of agents available or signed in are examples of statistical information that can be used within the model to direct the routing of transactions. Routing of call transactions may be accomplished generally as described in: U.S. Pat. No. 5,335,269 to Steinlicht; U.S. Pat. No. 5,365,581 to Baker et al.; and U.S. Pat. No. 5,384,841 to Adams et al., all incorporated herein by reference.
Upon completing the simulation, the simulator may also provide a recommended output based on the results seen in the simulation. The simulator may, for example, be programmed with a threshold that determines when a recommendation should be made, for instance, when a cost has exceeded 10% of a target business objective value. It may also display a probabilistic measure of the likelihood of meeting a business objective and further may use the probability measure as a means for making routing decisions in the model. For instance, if the likelihood that the caller has a DTMF phone based on the geographic location of the call origination is greater than 90%, the call could be routed to a device, such as an IVR, that can process the DTMF signals. The application of various technology solutions and their effect on the contact center can also be calculated and made available to a user. It is also desirable that the contact center be able to evaluate its performance automatically against metrics representing other contact centers within a specific industry. Creating a gap analysis involves comparing a contact center performance metric against the metric for a suitable peer group.
The recommendation engine may further compare the simulated output against the required objective showing reasons why the objective cannot be met and what, if any, corrective action can be taken to meet the objective. Reasons may include various combinations of cost, equipment, staffing, or time based justifications. Alternative recommendations may include resource or configuration considerations including adding additional agents or moving agents between particular applications to achieve the required performance objective dependant on the equipment which is included as part of the model. The engine may also display calculations, such as, for example, Return on Investment (ROI) that can be programmed into the model. The results of these calculations may also be shown with a probabilistic measure of achieving the goal within a given range.
Specific embodiments of novel methods and apparatus for construction of novel contact center business modelers have been described for the purpose of illustrating the manner in which the invention is made and used. It should be understood that the implementation of other variations and modifications of various possible embodiments of the invention and its various aspects will be apparent to one skilled in the art, and that the alternative possible embodiments of the invention is not limited by the specific embodiments described. Therefore, it is contemplated to cover any and all modifications, variations, or equivalents that fall within the true spirit and scope of the basic underlying principles disclosed and claimed herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5410586 | Davies | Apr 1995 | A |
| 5555179 | Koyama et al. | Sep 1996 | A |
| 5765033 | Miloslavsky | Jun 1998 | A |
| 5926539 | Shtivelman | Jul 1999 | A |
| 5946387 | Miloslavsky | Aug 1999 | A |
| 5953332 | Miloslavsky | Sep 1999 | A |
| 5953405 | Miloslavsky | Sep 1999 | A |
| 6002760 | Gisby | Dec 1999 | A |
| 6021428 | Miloslavsky | Feb 2000 | A |
| 6044145 | Kelly et al. | Mar 2000 | A |
| 6044368 | Powers | Mar 2000 | A |
| 6067357 | Kishinsky et al. | May 2000 | A |
| 6108711 | Beck et al. | Aug 2000 | A |
| 6138139 | Beck et al. | Oct 2000 | A |
| 6163607 | Bogart et al. | Dec 2000 | A |
| 6167395 | Beck et al. | Dec 2000 | A |
| 6170011 | Macleod Beck et al. | Jan 2001 | B1 |
| 6175563 | Miloslavsky | Jan 2001 | B1 |
| 6175564 | Miloslavsky et al. | Jan 2001 | B1 |
| 6185292 | Miloslavsky | Feb 2001 | B1 |
| 6345305 | Beck et al. | Feb 2002 | B1 |
| 6373836 | Deryugin et al. | Apr 2002 | B1 |
| 6389007 | Shenkman et al. | May 2002 | B1 |
| 6393015 | Shtivelman | May 2002 | B1 |
| 6697858 | Ezerzer et al. | Feb 2004 | B1 |
| 6732156 | Miloslavsky | May 2004 | B2 |
| 7376227 | Anisimov et al. | May 2008 | B2 |
| 7783513 | Lee | Aug 2010 | B2 |
| 20010011228 | Shenkman | Aug 2001 | A1 |
| 20010032120 | Stuart et al. | Oct 2001 | A1 |
| 20020038217 | Young | Mar 2002 | A1 |
| 20020067821 | Benson et al. | Jun 2002 | A1 |
| 20020143599 | Nourbakhsh et al. | Oct 2002 | A1 |
| 20020165757 | Lisser | Nov 2002 | A1 |
| 20020184069 | Kosiba et al. | Dec 2002 | A1 |
| 20030081757 | Mengshoel et al. | May 2003 | A1 |
| 20030095652 | Mengshoel et al. | May 2003 | A1 |
| 20030177082 | Buckwalter | Sep 2003 | A1 |
| 20030187675 | Hack et al. | Oct 2003 | A1 |
| 20030225591 | Clay et al. | Dec 2003 | A1 |
| 20040034543 | Bartsch | Feb 2004 | A1 |
| 20040073441 | Heyns et al. | Apr 2004 | A1 |
| 20040073442 | Heyns et al. | Apr 2004 | A1 |
| 20040083116 | Joyce | Apr 2004 | A1 |
| 20050013428 | Walters | Jan 2005 | A1 |
| 20050041796 | Joseph et al. | Feb 2005 | A1 |
| 20060098583 | Baker et al. | May 2006 | A1 |
| 20060147025 | Dezonno et al. | Jul 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20060147025 A1 | Jul 2006 | US |
