|Publication number||US6233332 B1|
|Application number||US 09/089,788|
|Publication date||May 15, 2001|
|Filing date||Jun 3, 1998|
|Priority date||Jun 3, 1998|
|Also published as||US6453038, US6690788, US6704410|
|Publication number||089788, 09089788, US 6233332 B1, US 6233332B1, US-B1-6233332, US6233332 B1, US6233332B1|
|Inventors||Gregory Lane Anderson, Lucinda M. Sanders, Robert W. Donnelly, Eugene Mathews, Mark Landers|
|Original Assignee||Avaya Technology Corp.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (6), Referenced by (120), Classifications (10), Legal Events (12)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates to call processing systems and, in particular, to a rules-based call center routing process that utilizes the identity of the calling party, the call context and media capabilities of the calling party to route the call to a destination that is appropriate to the call in terms of media communications capabilities and type of desired service.
It is a problem in communication systems to extend the basic call management paradigm of voice-based communications to provide the services and capabilities required of “anymedia” communications, wherein the term “anymedia” as used herein refers to the ability of the calling party to use any one or a combination of a number of different media to initiate the call. In particular, in a voice call, as parties are added to the call, a voice path is set up so that the newly added parties can communicate with all of the parties presently on the voice call. If a party drops from the voice call, the voice path between that person and all of the remaining parties to the voice call is dropped. The voice call is spontaneous and does not require the prearranged set up of communication facilities. The voice call model is therefore a one-dimensional model with the voice calls being characterized by their physical call connections. The controlling call processing system simply manages the physical call connections and no information is remembered either about the voice call once the voice call is completed or about a party to the voice call if the party hangs up during the progress of the voice call. The departing party is erased from memory once they depart and, upon call completion, the call connection data is also erased.
In the simplest form, an anymedia call should be an extension of the voice call of today, comprising any combination of audio, video, desktop data, or image services that are transmitted among the parties to the call. If the separate media types are bundled in a single call, the communication facilities for each media type can be handled in a consistent and expected way. For example, if a person drops a call involving audio and video, both types of media facilities are dropped automatically and simultaneously. If other people are conferenced onto the call, they receive all of the presently active types of media for which they are enabled. An anymedia call would ideally be as easy to use as voice calling is today, since it would behave in expected ways, and not require the people involved in the call to perform extra or complex work to establish the anymedia connection. However, this is not the case in existing call management systems. The provision of other than simple voice communications requires that the users expend a significant amount of effort to communicate via a selected set of media types. In addition, the media are not integrated and the communication connections that are established to serve an anymedia call are typically immutable for the call duration, with the ability to release a particular media facility during the call connection being an impossible task.
A further problem with anymedia communications in customer service scenarios, such as a call center, is that many existing information access systems are architected for voice-only access and in a manner to minimize the cost of providing the offered services pursuantto some predefined level of responsiveness to customers' requests. For example, a call center comprises an automated call management system where customers can access information regarding products and services that are offered by the call center operator. The call center is generally staffed by a number of agents who answer queries from the customers, provide information, and take customer orders. In order to increase the efficiency of operation of the call centers, these systems are architected to force a customer's incoming call down a predefined path through an immutable response hierarchy. While this reduces the cost of providing the agents and yet provides a modicum of service to the customers, these call center systems are limited in their ability to truly serve each particular customer's needs. In particular, the incoming call is queued as a function of the type of media, thereby requiring the implementation of multiple disjunct queues, each having different call management parameters and customer wait times. Furthermore, the call connection to a particular agent represents a localized transaction that cannot easily be forwarded to another agent during the processing of the call connection while retaining the call context. For example, the order entry agent cannot easily forward any information regarding the customer if the call is transferred to another agent and the customer must again provide the information requested by the original agent. This process is frustrating to both the agent and the customer. In addition, the call center operator may have extensive information regarding the customer, their existing orders, past orders, preferences, account balance, and the like, but this information is distributed over numerous databases within the organization and cannot easily be used to enhance the level of services provided in the processing of the customer's incoming call.
In summary, existing communications systems are lacking in their simplicity of use and ability to integrate the numerous disjunct information systems that are in use in commerce. As an example, call centers represent a typical instance where anymedia communications, integrated with an information system, would be beneficial to both the customers who access the call center and the call center operator, yet such integrated communications are unavailable for use in this application.
The above described problems are solved and a technical advance achieved by the present system for context based media independent communications processing that functions to provide business useful services to customers with the media resources and customer-specific data, that is stored in a call “context,” that are required to satisfy the customer's request. In particular, the capabilities of this media independent communications processing system are illustrated in the call center example used above. The present media independent communications processing system functions to carry call information across the entirety of a transaction with the call being managed as an anymedia multi-transactional event surrounded by a “context” of customer-specific data.
The architecture used to implement the present media independent communications processing system in the call center application can be modeled with a hallways and rooms paradigm that enables the customer to dynamically navigate their anymedia communications connection to a desired information providing source hence fulfilling their request. The incoming call is processed through a universal work queue for agents, which enables the call center system administrator to adjust the media mix of the incoming call connections for each agent or group of agents while also monitoring call center statistics across all media types. Also, the agents who staff the call center are not dedicated to processing only a single type of media call, but can receive incoming calls of varying media types, as their terminal equipment permits. As the present media independent communications processing system routes the customer's call during the duration of the communication session, the call context information is stored and used by the rules-based call routing process to route the call to a source of information/services that is best adapted to serve the needs of this customer during this and future communication sessions. The present communication session is viewed as one segment of a potentially long-term interaction between customer and service provides with the present media independent communications processing system providing both the customer and serving agent with access to relevant customer and service provider data via the call context. In this example, the customer call context information includes, but is not limited to: customer data, customer profile/preferences/history, environment data; while the corresponding agent call context information includes, but is not limited to: agent skills, agent queue length, fairness of call routing with respect to the agent pool, agent job function, and the like. Furthermore, the anymedia capabilities of the customer are considered in the rules-base call routing process. The various agents and automated information sources available to the present media independent communications processing system are dynamically incorporated into the communication connection on an as needed basis in order to benefit from the anymedia communications potential of the system.
Thus, the present media independent communications processing system implements a rules-based call routing process that utilizes the identity of the calling party, the call context and anymedia content of a communication connection to effect routing the call to a destination that is appropriate to the call in terms of anymedia communications capabilities and information content, via a call context, in a manner heretofore unknown in call processing.
FIG. 1 illustrates diagrammatically the anymedia call model used to manage such communications connections;
FIG. 2 illustrates in block diagram form the preferred embodiment of a call center architecture that uses the anymedia call model of FIG. 1 and a rules-based call management paradigm;
FIG. 3 illustrates in block diagram form the anymedia physical implementation of the call center of FIG. 2, with illustrative call connections;
FIGS. 4 and 5 illustrate in block diagram form the architecture of the rules engine data and the rules engine, respectively, for the call center example of FIG. 3 in the processing of a typical call connection; and
FIG. 6, illustrate in flow diagram form the operation of the rules-based process for the call center example of FIG. 3 in the processing of a typical call connection.
A basic premise of anymedia calling is to bundle various media types into a single call between two or more people, using whatever media specific communication facilities that are necessary to serve the call connection. In the simplest form, a anymedia call is an extension of the voice call of today, with audio service between people being augmented by the provision of video, and/or desktop data, and/or image communications. Because these separate media types are bundled in a single call, each media type can be handled in a consistent and expected way. For example, if a person drops a anymedia call involving audio and video, the facilities that serve both media types are dropped automatically and simultaneously. If other people are conferenced (or transferred, or placed on hold, etc.) onto an existing anymedia call, they receive all media communications in use on the existing anymedia call by the provision of the necessary communication facilities. Anymedia calls can be set up initially with more than one communication facility and media types can be added or dropped at any time during the duration of the anymedia call. An anymedia call should ideally be as easy to use as voice calling is today. It should behave in expected ways, and not require the people involved in the anymedia call to perform extra or complex work to establish the anymedia connections that serve the anymedia call.
Anymedia communication services evolve from both the voice and data worlds and it is important that products that offer anymedia communications be tightly coupled into both the voice and data networks where these services reside. The anymedia communications must be business useful to be effective solutions to customers' communications problems. An example of a anymedia call is illustrated in FIG. 1. A call processing system 100 functions to manage the communication facilities that serve to interconnect the various parties to the call. The facilities that are shown interconnecting the parties can be unique for each of the types of media, or can be shared facilities that function to concurrently provide several types of media communications on the same physical transmission medium. In this anymedia call, two parties 101, 102 are only connected by voice communication facilities V1 while voice, video and data communication facilities V2 and V3 interconnect parties 101, 103 and 102, 103, respectively. Since it is desirable that media can come and go during the progress of the anymedia call, the call processing system 100 must manage call connections as with voice calls: spontaneous call connections with parties and media freely able to be added and removed from the anymedia call. A differentiating factor with the anymedia call is that the call processing system 100 includes a call context management process 112 that stores data indicative of the particulars of the anymedia call, such as customer media capabilities/preferences and customer history data, which data is termed call “context.” Support for this degree of service is implemented in the form of call services system 111 that functions to interconnect the resident operating system of the call processing system 100 and the application software that is used to implement various any media services in the call context management process 112 to enable communications applications to be realized independent of the resident operating system, the network transport, interworking algorithms and the like.
The communications model used herein for anymedia calls is an extension of this well known concept from the voice world. Enhancing the voice calling model for anymedia results in a model for the anymedia customer interface and the integration of anymedia technology. Anymedia calling is an important customer level service and fits in broadband network implementations.
The anymedia calling concept is disclosed in FIG. 1 noted above where there is a need for persistent call data to enable the call processing system 100 to provide business useful services by dynamically managing the associated anymedia communications resources. In this system, call services 111 implements a rules-based call routing process to control the switch/communications fabric as well as content/protocol of the physical interconnections. The rules-based call routing process also maintains the call context information of call context management process 112 to enable the provision of communication services that are appropriate for anymedia and customer-specific transactions in call centers as described below.
FIG. 2 illustrates in block diagram form the preferred embodiment of the present media independent communications processing system in the form of a call center architecture, that uses the anymedia call model of FIG. 1 and a rules-based call management paradigm to provide differentiated customer service. FIG. 3 illustrates in block diagram form the anymedia physical implementation of the call center 310. The present media independent communications processing system of FIG. 2 comprises the controlling hardware and software that function to obtain data from and control the operation of the various communication facilities that serve to implement the anymedia call connections. Calls can be placed to the call center 310 with more than one medium and media can be added to or dropped from the communication connection at any time during a call.
The call center 310 functions to selectively interconnect the plurality of customers with the information and services that are provided by the call center 310. To accomplish this function, the incoming call from a customer must be routed in an appropriate and efficient mannerthrough the call center architecture, modeled in FIG. 2, which comprises a hierarchically organized set of facilities and services. This model divides the call center 310 into suites of “rooms”, with each suite comprising a plurality of alternate embodiments of that particular layer of the hierarchy. Each suite of rooms is separated from the next hierarchically distinct suite of rooms by a “hallway” that enables the customer to navigate among the various selections available at a particular level of the hierarchy. Using this paradigm, the rules-based call routing process 308 operates a rules engine 200 to enable the customer to provide data, either actively or passively, to define the optimal route through the call center 310 to obtain the services desired by this customer in a customer-specific manner. The rules-based call routing process 308 collects data from the various elements used to implement the call center and also provides data to regulate the operation of the call center elements by use of the rules engine 200.
The various levels of the call center architecture illustrated in FIG. 2 comprise: Accessing Layer 201, Connecting Layer 202, Relating Layer 203, fulfilling Layer 204, and Information Layer 205. It is obvious that not all levels of his architecture are necessarily internal to a specific embodiment of a call center 310, but for completeness of the architecture all levels are illustrated to thereby enable the specific implementation to address all of the potential possibilities that can be envisioned. For example the call center 310 does not encompass the customer's communication devices or the common carrier communication facilities that serve to connect these communication devices to the call center 310, but from a call management perspective, the data that defines these communication devices and the communication facilities are important to enable the rules-based call routing process 308 to perform its function in an efficient manner. Thus, the anymedia call model of FIG. 1, when implemented in the call center model of FIG. 2, provides a view of the call relevant data that provides the customer with an organized way of navigating through the maze of choices available in the call center architecture to chart a course through the various levels to reach the desired specific information. The navigation is effected by the rules engine 200 of the rules based call routing process 308, using the call context data that is collected by the call context management process 112.
The Accessing Layer 201 comprises a categorization of a plurality of communication devices that the customer may use to initiate a call connection. Those listed in FIG. 2 are typical examples of communication devices and the various entries listed herein can be divided into different combinations than that illustrated herein, depending on the granularity of the divisions that may be desired for a particular application. The entries illustrated are: wired voice terminal, personal computer, cellular voice/data, anymedia terminal, pay phone. Each of these categories represents a subset of well known communication devices and an associated technology that must be served by the call center 310. For the purpose of illustration, the following example uses a customer who is equipped with a anymedia terminal and who desires to access information, resident in the communication and data processing systems that serve the call center 310.
To effect a communication connection to the call center 310, the customer must initiate a call connection in a conventional manner to a point of presence provided by the call center 310 on the appropriate communication network. In this example, the call center 310 has a plurality of such point of presence embodiments to thereby serve customers with diverse types of communication devices. The second level of the architecture represents the Connecting Layer 202 which comprises a plurality of selections of communication medium that are available to the customer. These are: Terminal Communication Protocol (TCP/IP) on an Local Area Network/Wide Area Network (LAN/WAN), Public Telephone Switched Network (PTSN), Integrated Services Digital Network (ISDN), and Asynchronous Transfer Mode (ATM) on an LAN/WAN. As shown in FIG. 2, the customer at the anymedia terminal traverses the first hallway to enter the “room” noted as ATM, which indicates that the customer call connection is implemented from a anymedia terminal via the physical communication facilities implemented in the Asynchronous Transfer Mode of data communication.
The third layer of the hierarchy comprises the Relating Layer 203 which represents the mode of presenting the point of presence to the customer (and possibly also to the agent) once the customer reaches the physical boundary of the call center 310. These selections are: prompting the user with screen pops, ANI hits with screen pops, hypertext, voice message with user prompts, recorded message, and the like. Each of these call center responses are appropriate for a particular customer communication device and/or communication mode, or are based on a customer preference. Therefore, the rules-based call routing process 308 must collect data from the incoming call connection to determine the particulars of this incoming call to thereby provide an appropriate response. If the incoming call data includes an identification of the customer, the rules-based call routing process 308 can access the data stored in one of the databases 307 resident in the call center 310 to retrieve customer-specific data to enhance the appropriateness of the call handling, as is described in additional detail below.
The fourth layer of the hierarchy comprises the Fulfilling Layer 204 which represents the physical apparatus and business process used by the call center to serve the call connection. These include: interactive response, live agent, Web server, FAX back, voice message. The rules-based call routing process directs the incoming call, absent specific selections by the customer, to an appropriate one of these options to thereby create a pseudo personal connection, where the customer has their incoming call processed in a manner that is of greatest interest to this particular customer. This personalization includes the use of call context information, so the serving agent can provide a personalized response, having had access to the context of this particular customer displayed at the time the incoming call is connected to the agent's terminal.
The final layer of the hierarchy comprises the Information Layer 205 that comprises the associated information processing systems that function to provide the goods and services to the customer. These include: customer database, communication context database, order entry scripts, forms, Web pages, customer billing information, back order fulfilment, call context data input by the agents in response to call context changes occasioned by the customer, and the like. These databases are typically resident in a plurality of independently operational data processors.
FIGS. 4 and 5 illustrate in block diagram form the architecture of the rules engine data 400 and the rules engine 200, respectively, for the call center example of FIG. 3 in the processing of a typical call connection. In FIG. 4, the data 400 typically contained in the rules engine 200 is divided into a number of categories. The first category is the Identification Data 401 that can be used to assist in the identification of the calling customer. This data represents the information that is available as a result of the calling customer creating a physical call connection to the call center system 310 via some selected communication medium, and is contained in the call context. This data can be caller identification if the calling customer is using a voice line connection from a telephone station set TEL1, TEL2, or E-Mail address if accessing the system via a personal computer 300 and a shared communication network such as an Intranet or the Internet. The second category of rules data comprises the Qualification Data 402 that identifies the importance of this calling customer to the operator of the call center 310. Thus, the customer identification data is used to access account information contained in the database 307 to provide further information that relates to the specific needs of this calling customer. Therefore, the calling customer can be identified as a “high value” customer based upon past volume of sales transactions and may also be identified as the recipient of special discount offers. The third category of rules data comprises Circumstances Data 403 that may impact on the processing of this call connection. Thus, the prior call activity for this calling customer may be an important indicator of the type of service that they should receive. The fourth category of rules data comprises the Efficiency Context Data 404 for the call center 310. This data relates to the present state of operation of the call center and provides an indication of length of queue, status of preferred agents which agent would be best adapted to process this call, and the like. Finally, the fifth category of rules data comprises the Entitlement Data 405 that defines the type of call processing that is appropriate or preferred for this specific calling customer. Thus, the calling customer may prefer personalized service from an agent rather than a voice response system, or the calling customer may prefer immediate service. In addition, an anymedia call instance can be processed where for example the customer initiates a voice call and desires an E-Mail response order confirmation. These categories of rules data are maintained in the rules engine 200 to enable the system to efficiently process the calling customer's call connection.
The rules engine 200 itself is illustrated in block diagram form in FIG. 5 and, for the particular call center example, comprises three components. The rules creation language 501 comprises a user interface that enables a system administrator to create and manage the rules that are used to regulate the operation of the rules engine 200 and thereby regulate the operation of the call center 310. The individualized care engine 503 comprises customer-specific data and the processing of this data to adapt the operation of the call center 310 to most effectively match the preferences of a calling customer. Thus data represents a history of past interactions of the particular customer with the call center 310 as well as accounting data and data collected from other sources that is relevant to the provision of the degree of personalized service to the particular customer. The efficiency engine 502 comprises the call center operation control. This efficiency engine 502 maintains data relating to various aspects of operation of the equipment that comprise the call center 310. Thus, the example illustrated in FIG. 5 shows data collection for caller identification, as well as call status: new call received, call transferred, call on hold, and the like. Furthermore, agent data is maintained: identification of the skill set for each agent, the state of each agent position, and level of activity for each agent. There is also a basic call queue management process that provides a universal queue for incoming call connections. This queue identifies the time-ordered sequence of incoming call connections, regardless of the media that is used to serve the call connection. Thus, the calling customer is served in true order of arrival fashion (or any other queuing algorithm desired), rather than being placed in a queue based upon media type. The call center administrator can adjust the call distribution as a function of the number of calls in the queue of a particular media type. It is envisioned that at least some of the agents are equipped with terminals that enable the agents to process call connections of more than a single media type. The mix of media types processed by a particular agent can therefore be adjusted as a function of the mix of call connections in the universal queue. Finally, the efficiency engine 502 is equipped with a set of dynamic predictors and artificial intelligence algorithms to process all of the above-mentioned data to regulate the handling of the call connections.
FIG. 3 illustrates in block diagram form the anymedia physical implementation of the call center 310 of FIG. 2, with illustrative call connections while FIGS. 6A, 6B illustrate in flow diagram form the processing of a typical call connection through this system. The customer initiates the call connection at step 601 from a personal computer 300 which the user connects to the call center operator's Web site 301 via an Asynchronous Transfer Mode (ATM) communication connection. The Web site 301 is managed by the Web server 302 which functions to present the Web page images, transmit same to the customer and respond to customer provided input to redirect the customer to the information requested by the customer. Typically, the Web server 302 cycles the customer through a plurality of screen displays as the user navigates through the Web site 301 and its plurality of information choices provided by the Web server 302. In addition, the Web server 302 functions to collect data relating to the identity of the calling customer and any other customer related data that can be used to process this call in the proper context. The collected data is transmitted at step 603 described below by the Web server 302 to the call routing process 308 for inclusion in the rules data 500 portion of the rules engine 200.
The processing of the initial connection for this calling customer comprises the call connection entering the Accessing Layer 201 of FIG. 2 via the Multi-Media Terminal category and receiving a point of presence on the call center system 310 by the rules engine 200 providing an ATM trunk slot on the local area network, which comprises the ATM LAN/WAN category of the Connecting Layer 202 of FIG. 2. The rules engine 200 performs a relationship building function, which comprises a layer of functionality that is overlaid on the connectivity layer. In the relationship building function, the mode of communication that is deemed appropriate by the rules engine 200 for this type of access is the Hyper Text category of the Relating Layer 203, which interconnects the Web Server category of Fulfilling layer 203 with the calling customer. The Web server 302 thus fulfills the customer request and the hypertext is used to learn more about this customer to thereby enable the call center 310 to more effectively serve the customer. The Web Server category has an embodiment in FIG. 3 as Web server 302, which has access to a predefined series of Web Pages that comprise Web site software 301, which comprise a portion of the Information Layer 205. As this call connection is processed, temporary connections are established among the various layers 201-205 and various categories of these layers 201-205 to exchange call context data among the various participants in the call connection.
For the purpose of this description, assume that the calling customer, via the various selections available on a Web page presented by the Web server 302, elects to access an agent within the call center 310. This is accomplished by the user clicking on a selected icon on the display produced as part of a Web page transmitted to the calling customer by the Web server 302 at step 602 which prompts the Web server 302 to redirect the communication connection from the Web server 302 to the call center gateway 303 which functions as a gateway for communication connection routing. The call center gateway 303 communicates with the rules-based call routing process 308 to direct this communication connection to an appropriate destination. The rules engine 200 portion of the rules-based call routing process 308 at step 603 obtains data relating to the customer (Information Layer 205) as part of the communication connection redirection. In particular, the identity of the customer, the particular pages presented at the Web site 302 that were accessed by the customer, the duration of these accesses, customer query information input to the Web server 302 by the customer as part of the Web site access, and the like are transmitted from the Web server 302 to the rules-based call routing process 308. Thus, the call context data that is associated with this customer's access to the call center 310 via the Web server 302 is retained and passed along with the customer's communication connection to the next link in the call connection. The rules-based call routing process 308 prequalifies this call by generating a customer profile and redirecting the communications connection to a selected category of the Fulfilling Layer 204 in the call center 310 based upon the customer-indicated preferences and passively collected customer data. For the selected example, the rules-based call routing process 308 must route the calling customer to a live agent for the processing of this call connection. The routing is processed in the context of the calling customer using data that was collected on the Web, rather than as an anonymous incoming call.
Assume for the purposes of this description, that the calling customer has attempted to access the call center agents three times in the last 24 hour period and was unsuccessful in all three attempts due to the agents being busy. When the calling customer elects to access an agent at step 602, the rules-based call routing process 308 as part of the call routing process, activates the rules engine 200 which retrieves all relevant data regarding this customer for processing at step 604. The rules engine 200 retrieves customer related data: Customer Data Base data from the Information Layer 205, Customer Profile Info category of the Relating Layer 203, as well as agent related data from the Load Balancing and Availability categories of the Relating Layer 203 in order to process the customer initiated request. The following data is relevant to this call connection:
Identification: Customer account number, telephone number, Internet address, and the like.
Circumstances: Customer has unsuccessfully attempted to reach an agent three times in a 24 hour period
Qualification: Customer is of high value
Efficiency Context: All agents are busy and incoming calls are queued
The rules engine is programmed with a plurality of rules relating to all aspects of call processing and data collection. An example of one such rule can be the following:
Rule: IF the calling customer is of high value and has abandoned their attempts to contact the call center agents via any medium at least three times in a single 24-hour period, THEN quickly connect the calling customer to an agent, EVEN if the call center is overloaded.
Therefore, once the rules engine 200 receives the data relating to this calling customer's call connection, and history of prior attempts, the rules engine 200 executes the above-noted rule and produces the following result:
Entitlement: Place this calling customer's call connection at top of queue for immediate processing.
The rules engine 200 therefore signals the rules-based call routing process 308 to place this call connection at the head of the incoming call queue and to route this call connection via call center switch 303 to the first available agent, such as agent 304. The agent availability, skill level and agent administration data is considered in the agent selection process for the servicing of this call connection.
The rules-based call routing process 308 thus responds to this decision by activating call center switch 303 at step 605 to interconnect the calling customer with available agent 304. The agent 304 receives call context data from the rules-based call routing process 308 to thereby enable the agent 304 to interact with the calling customer in an informed manner. In particular, the customer-specific context data relating to this call connection is presented to the agent 304 as part of the initial call connection. The agent 304 can be informed of the calling customer's failed attempts, Web site browsing, presently shipped orders, back ordered goods, and the like. The agent 304 can thereby be prepared to intelligently discuss the customer's needs. Thus, at step 606 the agent 304 serves the calling customer's request.
Assume for the purposes of this description, that the calling customer has an account that has become overdue. The account balance is $650.45 and this amount has remained unpaid for more than 60 days. Thus, the following data is retrieved at step 607 by the rules engine 200 from the database 307, concurrently with the agent 304 serving the calling customer's request:
Circumstances: Customer's account is overdue for payment (>60 days) and amount owed ($650.45) is in excess of a predetermined allowable delinquent dollar value ($100.00).
As part of the processing of the input order, the rules engine 200 retrieves the calling customer account data and processes the present transaction information, along with the account data to ensure that any open issues regarding this account and the associated customer are resolved in the single call connection. Thus, the rules engine 200 is typically programmed with a rule, such as the following:
Rule: IF the calling customer has an account balance in excess of $100, and this amount is more than 60 past due, THEN route the call connection to a collection agent once order processing is input but not released.
Therefore, once the rules engine 200 receives the data relating to this calling customer's call connection, the rules engine 200 executes the above-noted rule and produces the following result:
Entitlement: Block release of calling customer order and place this calling customer's call connection at top of queue for immediate processing to collection agent.
Therefore, at step 608, the agent inputs order data into the database 307 for order processing and, at step 609 receives an alert from the rules-based call routing process 308 that the calling customer's call connection is to be routed to the collections agent 306 and the present order will not be entered until satisfactory resolution of the collection matter is obtained. The call connection is then rerouted by the rules-based call routing process 308 activating the call center switch 303 to interconnect the call connection to the collections agent 306 at step 610. The collections agent 306 is connected to the calling customer and at step 611 the rules-based call routing process 308 forwards the data retrieved by the rules engine 200 regarding the delinquent nature of this account to the collections agent 306. The collections agent is connected to the database 307 and can access additional customer specific data therefrom. By automatically forwarding the call connection and all of the call context data associated with this call connection and the calling customer, the collections agent can be informed of the present order, past orders, customer identity, overdue account status and the like. The collections agent 306 at step 612 can therefore resolve the account issues and, assuming successful resolution of these issues, signal the rules-based call routing process 308 at step 613 to return the call connection to agent 304 or any other available agent. Again, the call context data is forwarded with the call connection to enable the agent 304 to process the order without requiring further information from the calling customer. Once the order is placed, call processing exits at step 614.
Thus, the present media independent communications processing system implements a rules-based call routing process that utilizes the identity of the calling party, the call context and anymedia content of a communication connection to effect routing the call to a destination that is appropriate to the call in terms of anymedia communications capabilities and information content, in a manner heretofore unknown in call processing. This rules-based call routing process also maximizes the call center efficiency and agent productivity.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5008930 *||Oct 24, 1989||Apr 16, 1991||At&T Bell Laboratories||Customer definable integrated voice/data call transfer technique|
|US5452350 *||Mar 9, 1992||Sep 19, 1995||Advantis||Subscriber call routing processing system|
|US5491742 *||Jan 20, 1995||Feb 13, 1996||Bell Atlantic Network Services, Inc.||Method and apparatus for provisioning a public switched telephone network|
|US5610910 *||Aug 17, 1995||Mar 11, 1997||Northern Telecom Limited||Access to telecommunications networks in multi-service environment|
|US5848143 *||Mar 4, 1996||Dec 8, 1998||Geotel Communications Corp.||Communications system using a central controller to control at least one network and agent system|
|US5946386 *||Mar 11, 1996||Aug 31, 1999||Xantel Corporation||Call management system with call control from user workstation computers|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6690788 *||Sep 15, 2000||Feb 10, 2004||Avaya Inc.||Integrated work management engine for customer care in a communication system|
|US6859529||Feb 25, 2002||Feb 22, 2005||Austin Logistics Incorporated||Method and system for self-service scheduling of inbound inquiries|
|US6865267 *||Nov 27, 2001||Mar 8, 2005||Rockwell Electronic Commerce Corp.||Method and system for routing transactions in an automatic call distribution system based on non-voice dialog agent skill set|
|US7039176 *||Jul 9, 2001||May 2, 2006||Telephony@Work||Call center administration manager with rules-based routing prioritization|
|US7054434||Jun 6, 2003||May 30, 2006||Austin Logistics Incorporated||System and method for common account based routing of contact records|
|US7103173||Mar 12, 2002||Sep 5, 2006||Austin Logistics Incorporated||System and method for preemptive goals based routing of contact records|
|US7103556||Sep 26, 2001||Sep 5, 2006||Jpmorgan Chase Bank, N.A.||System and method for aggregate portfolio client support|
|US7142662||Jul 9, 2001||Nov 28, 2006||Austin Logistics Incorporated||Method and system for distributing outbound telephone calls|
|US7158629||Jun 7, 2006||Jan 2, 2007||Austin Logistics Incorporated||System and method for preemptive goals based routing of contact records|
|US7206402 *||Apr 27, 2001||Apr 17, 2007||Fujitsu Limited||Method of and system for call service system, and computer product|
|US7215757 *||Oct 21, 2004||May 8, 2007||Sbc Services, Inc.||System and method to provide automated scripting for customer service representatives|
|US7215758 *||Dec 15, 2004||May 8, 2007||Aspect Communications Corporation||Generating media-specific interaction control programs|
|US7221752 *||Feb 18, 2003||May 22, 2007||Siemens Aktiengesellschaft||Method and configuration for operation of an operator switching position in a telecommunications system|
|US7239692||Nov 20, 2006||Jul 3, 2007||Austin Logistics Incorporated||Method and system for distributing outbound telephone calls|
|US7324640||Mar 15, 2002||Jan 29, 2008||Rockwell Electronic Commerce Technologies||Transaction outcome state mapping|
|US7401320 *||Oct 11, 2005||Jul 15, 2008||Hewlett-Packard Development Company, L.P.||Operator network that routes customer care calls based on subscriber/device profile and CSR skill set|
|US7415267||Jan 27, 2004||Aug 19, 2008||Jp Morgan Chase Bank||Methods and systems for managing call reports for the financial services industry|
|US7502460||Jun 6, 2007||Mar 10, 2009||Austin Logistics Incorporated||Method and system for distributing outbound telephone calls|
|US7620722 *||Jun 20, 2000||Nov 17, 2009||Alcatel-Lucent Usa Inc.||Method and apparatus for establishing communication|
|US7660764||Aug 24, 2006||Feb 9, 2010||Jpmorgan Chase Bank, Na||Service charge adjustment platform|
|US7676034||Mar 5, 2004||Mar 9, 2010||Wai Wu||Method and system for matching entities in an auction|
|US7707089||Mar 12, 2008||Apr 27, 2010||Jpmorgan Chase, N.A.||Method and system for automating fraud authorization strategies|
|US7715546||Feb 9, 2004||May 11, 2010||Austin Logistics Incorporated||System and method for updating contact records|
|US7716170 *||Sep 17, 2004||May 11, 2010||Wafik Farag||Holistic dynamic information management platform for end-users to interact with and share all information categories, including data, functions, and results, in collaborative secure venue|
|US7769650||Mar 3, 2003||Aug 3, 2010||Jp Morgan Chase Bank||Network-based sub-allocation systems and methods for swaps|
|US7823146 *||Nov 5, 2004||Oct 26, 2010||Computer Associates Think, Inc.||Method and system for software installation|
|US7894595||May 2, 2008||Feb 22, 2011||Wai Wu||Telephony control system with intelligent call routing|
|US7916858||Sep 18, 2006||Mar 29, 2011||Toby Heller||Agent training sensitive call routing system|
|US7962644||Aug 28, 2002||Jun 14, 2011||Oracle International Corporation||Systems and methods for handling a plurality of communications|
|US8015096||Jun 25, 2010||Sep 6, 2011||Jp Morgan Chase Bank||Network-based sub-allocation systems and methods for swaps|
|US8032438||Apr 20, 2010||Oct 4, 2011||Jpmorgan Chase Bank, N.A.||Method and system for automating fraud authorization strategies|
|US8041800||Nov 8, 2005||Oct 18, 2011||International Business Machines Corporation||Automatic orchestration of dynamic multiple party, multiple media communications|
|US8073129||Oct 3, 2005||Dec 6, 2011||Avaya Inc.||Work item relation awareness for agents during routing engine driven sub-optimal work assignments|
|US8116446||Oct 3, 2005||Feb 14, 2012||Avaya Inc.||Agent driven work item awareness for tuning routing engine work-assignment algorithms|
|US8175258||May 18, 2006||May 8, 2012||Austin Logistics Incorporated||System and method for common account based routing of contact records|
|US8228824||Apr 6, 2006||Jul 24, 2012||Microsoft Corporation||VoIP contextual information processing|
|US8238541||Jan 31, 2006||Aug 7, 2012||Avaya Inc.||Intent based skill-set classification for accurate, automatic determination of agent skills|
|US8296160||Dec 28, 2006||Oct 23, 2012||Jpmorgan Chase Bank, N.A.||System and method for integrated customer management|
|US8300798||Apr 3, 2007||Oct 30, 2012||Wai Wu||Intelligent communication routing system and method|
|US8346942||Jun 18, 2009||Jan 1, 2013||Oracle International Corporation||Call centers for providing customer services in a telecommunications network|
|US8351596 *||Jun 24, 2008||Jan 8, 2013||International Business Machines Corporation||Method and system for call to role|
|US8355393 *||Nov 3, 2004||Jan 15, 2013||Rockstar Bidco, LP||Method and apparatus to process a call request by establishing calls among devices|
|US8386381||Dec 16, 2009||Feb 26, 2013||Jpmorgan Chase Bank, N.A.||Method and system for detecting, monitoring and addressing data compromises|
|US8422659||Aug 13, 2009||Apr 16, 2013||Assurant, Inc.||Call processing system|
|US8468515||Dec 12, 2006||Jun 18, 2013||Hewlett-Packard Development Company, L.P.||Initialization and update of software and/or firmware in electronic devices|
|US8472592 *||Aug 9, 2011||Jun 25, 2013||Callwave Communications, Llc||Methods and systems for call processing|
|US8479189||Apr 11, 2003||Jul 2, 2013||Hewlett-Packard Development Company, L.P.||Pattern detection preprocessor in an electronic device update generation system|
|US8509406 *||Dec 15, 2009||Aug 13, 2013||At&T Intellectual Property I, L.P.||Presence enhanced telephony service architecture|
|US8526940||Dec 6, 2004||Sep 3, 2013||Palm, Inc.||Centralized rules repository for smart phone customer care|
|US8533000||Sep 14, 2012||Sep 10, 2013||Jpmorgan Chase Bank, N.A.||System and method for integrated customer management|
|US8549107||May 6, 2011||Oct 1, 2013||Oracle International Corporation||Systems and methods for handling a plurality of communications for different companies|
|US8554631||Dec 13, 2010||Oct 8, 2013||Jpmorgan Chase Bank, N.A.||Method and system for determining point of sale authorization|
|US8555273||Sep 17, 2004||Oct 8, 2013||Palm. Inc.||Network for updating electronic devices|
|US8578361||Feb 27, 2011||Nov 5, 2013||Palm, Inc.||Updating an electronic device with update agent code|
|US8582753||Mar 28, 2011||Nov 12, 2013||Toby Heller||Agent training sensitive call routing system|
|US8583466||Mar 21, 2006||Nov 12, 2013||Oracle International Corporation||System and method for routing workflow items based on workflow templates in a call center|
|US8687790||Feb 7, 2013||Apr 1, 2014||Jpmorgan Chase Bank, N.A.||System and method of intelligent call routing for cross sell offer selection based on optimization parameters or account-level data|
|US8688460||Oct 23, 2012||Apr 1, 2014||Jpmorgan Chase Bank, N.A.||System and method for integrated customer management|
|US8718243||Aug 29, 2012||May 6, 2014||Callwave Communications, Llc||Call processing and subscriber registration systems and methods|
|US8750469||Jun 20, 2013||Jun 10, 2014||Callwave Communications, Llc||Methods and systems for call processing|
|US8752044||Jul 27, 2007||Jun 10, 2014||Qualcomm Incorporated||User experience and dependency management in a mobile device|
|US8781094 *||Jan 16, 2008||Jul 15, 2014||Microsoft Corporation||Contextual call routing by calling party specified information through called party specified form|
|US8831205||Mar 15, 2013||Sep 9, 2014||Wai Wu||Intelligent communication routing|
|US8842660 *||Mar 31, 2006||Sep 23, 2014||Microsoft Corporation||VoIP variable metadata|
|US8848899||Mar 27, 2008||Sep 30, 2014||Qualcomm Incorporated||Operator network that routes customer care calls based on subscriber / device profile and CSR skill set|
|US8885812||Mar 15, 2006||Nov 11, 2014||Oracle International Corporation||Dynamic customer satisfaction routing|
|US8893110||Apr 26, 2012||Nov 18, 2014||Qualcomm Incorporated||Device management in a network|
|US8917857 *||Aug 16, 2012||Dec 23, 2014||International Business Machines Corporation||Method and system for call to role|
|US8918342 *||Apr 29, 2013||Dec 23, 2014||Convergys Customer Management Delaware Llc||System for closed loop decisionmaking in an automated care system|
|US8971519||Oct 30, 2013||Mar 3, 2015||Steven Hoffberg||Agent training sensitive call routing system|
|US8995643||Jan 17, 2014||Mar 31, 2015||Jpmorgan Chase Bank, N.A.||System and method of intelligent call routing for cross sell offer selection based on optimization parameters or account-level data|
|US9001818||Jan 14, 2013||Apr 7, 2015||Rpx Clearinghouse Llc||Method to process a call request|
|US9081638||Apr 25, 2014||Jul 14, 2015||Qualcomm Incorporated||User experience and dependency management in a mobile device|
|US9088654 *||Nov 5, 2013||Jul 21, 2015||Bank Of America Corporation||Communication disposition determination for unified recovery system for payments in arrears|
|US9111278||Oct 7, 2013||Aug 18, 2015||Jpmorgan Chase Bank, N.A.||Method and system for determining point of sale authorization|
|US9124696 *||May 16, 2014||Sep 1, 2015||Genesys Telecommunications Laboratories, Inc.||Customer-enabled evaluation and control of communication center agent contact|
|US9154624||Apr 24, 2014||Oct 6, 2015||Callwave Communications, Llc||Call processing and subscriber registration systems and methods|
|US20020021792 *||Apr 27, 2001||Feb 21, 2002||Hiroko Shimizu||Method of and system for call service system, and computer product|
|US20020046049 *||Jul 10, 2001||Apr 18, 2002||Siegel Rebecca Lynn||System and method for supervising account management operations|
|US20020101979 *||Jul 9, 2001||Aug 1, 2002||Borodow Eli Ben||Call center administration manager with rules-based routing prioritization|
|US20020141561 *||Feb 25, 2002||Oct 3, 2002||Austin Logistics Incorporated||Method and system for self-service scheduling of inbound inquiries|
|US20020188497 *||Jun 12, 2001||Dec 12, 2002||Cerwin Francis Anthony||System and method for customer knowledge respository|
|US20030016812 *||Mar 12, 2002||Jan 23, 2003||Austin Logistics Incorporated||System and method for preemptive goals based routing of contact records|
|US20030074209 *||Oct 15, 2001||Apr 17, 2003||Tobin Christopher M.||User device with service finding and purchasing functionality|
|US20030099343 *||Nov 27, 2001||May 29, 2003||Dezonno Anthony J.||Method and system for routing transactions in an automatic call distribution system based on non-voice dialog agent skill set|
|US20030120660 *||Dec 7, 2001||Jun 26, 2003||Maritzen L. Michael||Consumer-centric context-aware switching model|
|US20030138096 *||Feb 18, 2003||Jul 24, 2003||Siemens Aktiengesellschaft||Method and configuration for operation of an operator switching position in a telecommunications system|
|US20030174831 *||Mar 15, 2002||Sep 18, 2003||Anthony Dezonno||Transaction outcome state mapping|
|US20030198336 *||Jun 6, 2003||Oct 23, 2003||Richard Rodenbusch||System and method for common account based routing of contact records|
|US20040179672 *||Feb 9, 2004||Sep 16, 2004||Austin Logistics Incorporated||System and method for updating contact records|
|US20040205484 *||May 1, 2002||Oct 14, 2004||Pennington Stanford E.||System and method for dynamically generating customized pages|
|US20050053224 *||Oct 21, 2004||Mar 10, 2005||Sbc Services, Inc.||System and method to provide automated scripting for customer service representatives|
|US20050060342 *||Sep 17, 2004||Mar 17, 2005||Wafik Farag||Holistic dynamic information management platform for end-users to interact with and share all information categories, including data, functions, and results, in collaborative secure venue|
|US20050114864 *||Nov 5, 2004||May 26, 2005||Surace Luke A.||Method and system for software installation|
|US20050123124 *||Dec 15, 2004||Jun 9, 2005||Aspect Communications Corporation||Generating media-specific interaction control programs|
|US20050132187 *||Jan 27, 2004||Jun 16, 2005||Scott Malat||Methods and systems for managing call reports for the financial services industry|
|US20050187901 *||Feb 11, 2005||Aug 25, 2005||Maritzen L. M.||Consumer-centric context-aware switching model|
|US20060143058 *||Oct 11, 2005||Jun 29, 2006||Jeffrey Brunet||Operator network that routes customer care calls based on subscriber/device profile and CSR skill set|
|US20060149664 *||Feb 24, 2005||Jul 6, 2006||Jp Morgan Chase Bank||Marketing system and method|
|US20060222165 *||Jun 7, 2006||Oct 5, 2006||Richard Rodenbusch||System and method for preemptive goals based routing of contact records|
|US20070038499 *||Mar 21, 2006||Feb 15, 2007||Margulies Edwin K||Universal workflow-based routing|
|US20070106795 *||Nov 8, 2005||May 10, 2007||Gilfix Michael A||Automatic orchestration of dynamic multiple party, multiple media communications|
|US20070121900 *||Nov 20, 2006||May 31, 2007||Richard Rodenbusch||Method and System for Distributing Outbound Telephone Calls|
|US20070230439 *||Mar 31, 2006||Oct 4, 2007||Microsoft Corporation||VoIP variable metadata|
|US20070239428 *||Apr 6, 2006||Oct 11, 2007||Microsoft Corporation||VoIP contextual information processing|
|US20070253407 *||May 1, 2006||Nov 1, 2007||Microsoft Corporation||Enhanced VoIP services|
|US20070274293 *||May 26, 2006||Nov 29, 2007||Microsoft Corporation||Archiving VoIP conversations|
|US20070280225 *||May 31, 2006||Dec 6, 2007||Microsoft Corporation||Extended services and recommendations|
|US20080247533 *||Jun 24, 2008||Oct 9, 2008||International Business Machines Corporation||Method and system for call to role|
|US20090168989 *||Dec 27, 2007||Jul 2, 2009||Perlmutter S Michael||Customer-Enabled Evaluation and and Control of Communication Center Agent Contact|
|US20090180602 *||Jul 16, 2009||Microsoft Corporation||Contextual call routing by calling party specified information through called party specified form|
|US20100166162 *||Dec 15, 2009||Jul 1, 2010||At&T Intellectual Property I, L.P.||Presence enhanced telephony service architecture|
|US20120307996 *||Dec 6, 2012||International Business Machines Corporation||Method and system for call to role|
|US20130089197 *||Nov 28, 2012||Apr 11, 2013||International Business Machines Corporation||Method and system for call to role|
|US20130097333 *||Jun 12, 2012||Apr 18, 2013||Clearone Communications, Inc.||Methods and apparatuses for unified streaming communication|
|US20140254789 *||May 16, 2014||Sep 11, 2014||Genesys Telecommunications Laboratories, Inc.||Customer-enabled evaluation and control of communication center agent contact|
|US20150124956 *||Nov 5, 2013||May 7, 2015||Bank Of America Corporation||Communication disposition determination for unified recovery system for payments in arrears|
|USRE44979||Nov 5, 2012||Jul 1, 2014||Noble Systems Corporation||System and method for common account based routing of contact records|
|CN100422988C||Oct 31, 2002||Oct 1, 2008||索尼电子有限公司||Consumer-centric context-aware switching model|
|WO2003050719A1 *||Oct 31, 2002||Jun 19, 2003||Sony Electronics Inc||Consumer-centric context-aware switching model|
|U.S. Classification||379/265.09, 379/242, 379/266.02|
|Cooperative Classification||H04M3/5233, H04M2203/551, H04M3/5235, H04M2242/22, H04M3/42059|
|Jun 3, 1998||AS||Assignment|
Owner name: LUCENT TECHNOLOGIES, INC., NEW JERSEY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ANDERSON, GREGORY LANE;SANDERS, LUCINDA M.;DONNELLY, ROBERT W.;AND OTHERS;REEL/FRAME:009491/0587;SIGNING DATES FROM 19980505 TO 19980601
|Feb 13, 2001||AS||Assignment|
|Apr 9, 2002||AS||Assignment|
|Sep 22, 2004||FPAY||Fee payment|
Year of fee payment: 4
|Nov 27, 2007||AS||Assignment|
Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT,NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNORS:AVAYA, INC.;AVAYA TECHNOLOGY LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:020156/0149
Effective date: 20071026
|Nov 28, 2007||AS||Assignment|
Owner name: CITICORP USA, INC., AS ADMINISTRATIVE AGENT,NEW YO
Free format text: SECURITY AGREEMENT;ASSIGNORS:AVAYA, INC.;AVAYA TECHNOLOGY LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:020166/0705
Effective date: 20071026
|Jun 27, 2008||AS||Assignment|
Owner name: AVAYA INC, NEW JERSEY
Free format text: REASSIGNMENT;ASSIGNOR:AVAYA TECHNOLOGY LLC;REEL/FRAME:021158/0300
Effective date: 20080625
|Oct 17, 2008||FPAY||Fee payment|
Year of fee payment: 8
|Dec 29, 2008||AS||Assignment|
Owner name: AVAYA TECHNOLOGY LLC, NEW JERSEY
Free format text: CONVERSION FROM CORP TO LLC;ASSIGNOR:AVAYA TECHNOLOGY CORP.;REEL/FRAME:022071/0420
Effective date: 20051004
|Feb 22, 2011||AS||Assignment|
Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLAT
Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535
Effective date: 20110211
|Sep 28, 2012||FPAY||Fee payment|
Year of fee payment: 12
|Mar 13, 2013||AS||Assignment|
Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE,
Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:030083/0639
Effective date: 20130307