Prioritized service delivery based on presence and availability of interruptible enterprise resources with skills

Information

  • Patent Grant
  • 7787609
  • Patent Number
    7,787,609
  • Date Filed
    Thursday, October 6, 2005
    18 years ago
  • Date Issued
    Tuesday, August 31, 2010
    13 years ago
Abstract
The present invention is directed to a contact center using presence information to direct work items to experts. More specifically, a system is provided that includes a feature that allows for subject matter experts, which are individuals other than customer service agents, to assist in incoming calls in at least three different modes: an assist mode, an intercept mode and an overflow mode. Thus, customer service efficiency and customer satisfaction are increased. In addition, it is contemplated that subject matter experts may either selectively accept or deny the request for assistance.
Description
FIELD OF THE INVENTION

The invention relates generally to contact centers and particularly to presence-enabled contact centers.


BACKGROUND OF THE INVENTION

Contact centers, such as Automatic Call Distribution or ACD systems, are employed by many enterprises to service customer contacts. A typical contact center includes a switch and/or server to receive and route incoming packet-switched and/or circuit-switched contacts and one or more resources, such as human agents and automated resources (e.g., Interactive Voice Response (IVR) units), to service the incoming contacts. As used herein, a “call” or “contact” refers to any mode or type of contact between at least two entities, including without limitation voice calls, VoIP, text-chat, instant messaging, e-mail, fax, electronic documents, webforms, voice messages, and video calls, to name but a few. Contact centers distribute contacts, whether inbound or outbound, for servicing to any suitable resource according to predefined criteria. Normally in present-day ACDs when the ACD system's controller detects that an agent has become available to handle a contact, the controller identifies all predefined contact-handling skills of the agent (usually in some order of priority) and delivers to the agent the highest-priority oldest contact that matches the agent's highest-priority skill. Agents with a higher skill are normally preferred over agents with lower skill levels when assigning an agent to a contact. When agents have multiple skills, the controller is more likely to select a contact for which the agent has a high skill level over a contact for which the agent has a lesser skill level. Generally, the only condition that results in a contact not being delivered to an available agent is that there are no contacts waiting to be handled.


Contact-distribution algorithms ultimately seek to maximize contact center performance and profitability. That may involve minimizing cost, maximizing contact throughput, and/or maximizing revenue, among others. Skills-based routing, which allows each agent to be slotted into a number of agent groups based on the agent's skill types and levels, is an attempt to maximize contact center performance and profitability. Skills-based routing systems have been further modified by introducing, as criterion in assigning work items to available agents, the service level associated with each work item.


Traditional contact centers have struggled to maintain and exceed customer service expectations, not only for wait time but also for responding effectively and efficiently to customer questions. To address wait times, contact centers have been “staffed up” by hiring additional resources at the service centers or have implemented reactive and manual processes that would involve having non-traditional resources (back office workers) alerted using manual processes to have them reactively “log in” to the resource pool. It is increasingly difficult to staff a correct number of resources to serve increasingly complex customer requests. Customers still continue to receive sub-optimal resources, busy signals, or excessive delays on IP based interactions over the web. Recently, additional manual approaches appearing in new form factors like instant messaging have been used to try and address this issue.


The fundamental problem of traditional contact centers is that resource pooling of agents and the notion of dedicated or designated call center agents is not always the most effective and efficient way to service incoming calls. Thus, it is often the case that contact centers fail to locate, let alone connect with customers, the optimal enterprise resource at any one instant. Simply put, contact centers fail to aggregate the totality of resources and skills available outside of the service center in a structured and dynamic manner.


SUMMARY

These and other needs are addressed by the various embodiments and configurations of the present invention. The present invention is directed to a presence-enabled contact center using nonagent personnel, such as experts, to service customer work items.


In one embodiment, a contact distribution methodology is employed that is presence-enabled to acquire the optimal or most appropriate skilled resource to serve a customer's immediate needs, for example, if a traditional resource is not immediately available or busy. The embodiment can allow potential skilled resources to make their availability known (e.g., “present”) as either primary or “escalation” resources when the traditional contact center agents are unable or unavailable to service a contact or the skills sets available do not meet the needs of the customer. The “on-demand” resources, which are often other geographic regions, would have a high probability of being engaged in other work activities. They would thus have the option to voluntarily offer to be “interrupted” by either “accepting” or “denying” the escalated service request. An example of an “acceptance” is the following: “Though I am busy, I am interruptible.” An example of a “conditional acceptance” is: “I decline to be interrupted now but I accept the contact if I can address it when I am available in 10 to 15 minutes.” Finally, an example of a “denial” is: “I am busy and unable to be interrupted”.


The acceptance or denial of the “on-demand” resources could be aggregated to provide the invention with an instant “inventory” of resources that can serve the escalated customer request. Customers requiring escalated service could be provided with an audio or HTML message that would inform them of the estimated (predicted) waiting time to locate and connect the best or optimal resource for their call. Customers unwilling to wait could indicate their availability for an “on-demand” conference when the best resource becomes available and would be linked to a mechanism aggregating the cumulative availability of resources that can serve the customer if more than one resource responds with “I am not interruptible now but will be available in X minutes from now”. If the requests extended to the “on-demand” resources do not result in a satisfactory level of real-time or anticipated service, the customer contact could be returned to the traditional queue of agents in the contact center.


Presence-enabled “on demand” expert resources would not need to practice standard agent behaviors, such as logging in to the ACD, using AUX codes to become unavailable to calls, or remain at their desks to take calls. Yet as resources their contributions could be tracked, such as total SIP-enabled and available time, a number of support requests or invitations made to them, number of acceptable offers made by them in response to requests, number of offers accepted by the contact center, time they spend on each customer interaction, etc., so that a variety of charge-back or payment arrangements can be implemented.


The embodiment can take into consideration extended enterprise resources (knowledge worker) outside of the traditional contact center for servicing customer contacts based on the “interruptibility” of extended resources who otherwise may be engaged in other work activities. It can allow the remote worker to self-determine his participation in the escalation process. Rather than having requests “automatically” forwarded to him as in the case of agents with consequent interruption of what may be more valuable work. The embodiment can meet and exceed customer service expectations, expand the pool of available resources to serve customers at any one point in time based on spikes or bursts in demand, locate resources in real time to serve a customer contact demand regardless of the expert's physical location or status within the business, and provide a mechanism under which knowledge workers or experts control when and how they participate in the customer servicing process. As a result, the embodiment can provide reduced contact center operating costs, increased customer satisfaction levels, lower call abandonment rates, and higher levels of resource productivity.


These and other advantages will be apparent from the disclosure of the invention(s) contained herein.


The above-described embodiments and configurations are neither complete nor exhaustive. As will be appreciated, other embodiments of the invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.


As used herein, “at least one”, “one or more”, and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B, or C” and “A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of a call center according to an embodiment of the present invention;



FIG. 2 is a block diagram of a server according to an embodiment of the present invention;



FIG. 3 is a flow chart according to an embodiment of the present invention;



FIG. 4 is a flowchart according to an embodiment of the present invention; and



FIG. 5 is a flow chart according to an embodiment of the present invention.





DETAILED DESCRIPTION

The invention will be illustrated below in conjunction with an exemplary communication system. Although well suited for use with, e.g., a system having an ACD or other similar contact processing switch, the invention is not limited to use with any particular type of communication system switch or configuration of system elements. Those skilled in the art will recognize that the disclosed techniques may be used in any communication application in which it is desirable to provide improved contact processing.



FIG. 1 shows an illustrative embodiment of the present invention. A contact center 100 (or enterprise network denoted by dashed lines 175) comprises a central server 110, a set of data stores or databases 113, 114, and 116 containing contact or customer related information and other information that can enhance the value and efficiency of the contact, and a plurality of servers, namely a voice mail server 118, an Interactive Voice Response unit, or IVR 122, and a presence server 108, a switch 130, a plurality of working agents (not shown) operating packet-switched (first) telecommunication devices 134-1 to N (such as computer work stations or personal computers), and/or circuit-switched (second) telecommunication devices 138-1 to M, all interconnected by a local area network LAN (or wide area network WAN) 142. As will be appreciated, experts may also have circuit switched and/or packet switched telecommunications devices within the enterprise premises that are directly serviced by the switch/server. The servers can be connected via optional communication lines to the switch 130. The switch 130 is connected via a plurality of trunks 150 to the Public Switch Telecommunication Network or PSTN 154 and via link(s) 152 to the second telecommunication devices 138-1 to M. A gateway 158 is positioned between the server 110 and a packet-switched network 162 (such as the Internet) to process communications passing between the server 110 and the network 162.


The term “switch” or “server” as used herein should be understood to include a PBX, an ACD, an enterprise switch, an enterprise server, or other type of telecommunications system switch or server, as well as other types of processor-based communication control devices such as media servers, computers, adjuncts, etc.


External to the enterprise network 175 are the packet-switched network 162, circuit-switched network 154, and wireless network(s) 104. The packet-switched network 162 is in communication with a gateway 178 and packet-switched communication device 174. Circuit-switched network 154 is in communication with a circuit-switched communication device 180. Finally, the wireless network(s) is in communication with a wireless communication device 156 (which may be packet- and/or circuit-switched).


The gateway 158 can be any suitable protocol converter, such as Avaya Inc.'s, G700™, G600™, or MCC/SCC™ media gateway and may be implemented as hardware such as via an adjunct processor (as shown) or as a chip in the server.


The first telecommunication devices 134-1, . . . 134-N are packet-switched and can include, for example, IP hardphones such as the Avaya Inc.'s, 4600 Series IP Phones™, IP softphones such as Avaya Inc.'s, IP Softphone™, Personal Digital Assistants or PDAs, Personal Computers or PCs, laptops, packet-based H.320 video phones and conferencing units, packet-based voice messaging and response units, and packet-based traditional computer telephony adjuncts.


The second telecommunication devices 138-1, . . . 138-M are circuit-switched. Each of the telecommunication devices 138-1, . . . 138-M corresponds to one of a set of internal extensions Ext1, . . . ExtM, respectively. These extensions are referred to herein as “internal” in that they are extensions within the premises that are directly serviced by the switch. More particularly, these extensions correspond to conventional telecommunication device endpoints serviced by the switch/server, and the switch/server can direct incoming contacts to and receive outgoing contacts from these extensions in a conventional manner. The second telecommunication devices can include, for example, wired and wireless telephones, PDAs, H.320 video phones and conferencing units, voice messaging and response units, and traditional computer telephony adjuncts.


The agent and expert information databases 114 and 113 commonly include a profile for each agent or expert, respectively, that includes individual enterprise identifier, individual name, address, communication device information, personal information (e.g., age, sex, hobbies, physical condition, spoken languages, ethnicity, geographic area of expertise, etc.), individual skills and/or areas of expertise, and, in the case of experts, day(s) and time(s) during which and/or areas in which the expert may be contacted to service customer contacts and/or a number of times over a selected period in which the expert may be contacted to service customer contacts.


Presence information database 116 generally includes presence information for each expert available for servicing contacts. “Presence information” means any information associated with a network node and/or endpoint device, such as a communication device, that is in turn associated with a person or identity. Examples of presence information include registration information, information regarding the accessibility of the expert's endpoint device, the endpoint device's telephone number or address, the recency of use of the endpoint device by the expert, recency of authentication by the expert to a network component, the geographic location of the expert's endpoint device, the type of media, format language, session and communications capabilities of the currently available expert's communications devices, the preferences of the expert (e.g., contact mode preferences or profiles such as the communication device to be contacted for specific types of contacts or under specified factual scenarios, contact time preferences, impermissible contact types and/or subjects such as subjects about which the expert does not wish to be contacted, and permissible contact type and/or subjects such as subjects about which the expert does wish to be contacted. In one configuration, presence information includes availability information from an electronic calendar or agenda maintained by the expert in an application, such as Outlook™ by Microsoft, and accessible by the enterprise network. Presence information can be user configurable, i.e., the user can configure the number and type of communications and message devices by which they can be accessed and to define different profiles that define the communications and messaging options presented to incoming contactors in specified factual situations. The presence information can be associated with internal and external endpoints associated with each expert.


It should be noted that the invention does not require any particular type of information transport medium between switch or server and first and second telecommunication devices, i.e., the invention may be implemented with any desired type of transport medium as well as combinations of different types of transport medium.


The wireless network(s) 104 may be any packet- or circuit-switched wireless network, such as a cellular network.


The packet-switched network 162 is in communication with an external first telecommunication device 174 via a gateway 178, the circuit-switched network 154 with an external second telecommunication device 180, and the wireless network(s) 104 with the wireless communication device 156. These telecommunication devices are referred to as “external” in that they are not directly supported as telecommunication device endpoints by the switch or server. The telecommunication devices 174, 180, and 156 are examples of devices more generally referred to herein as “external endpoints.” These devices can be any of the devices referred to above.


An external presence server 171 and associated presence information 173 collect presence information associated with external endpoints. The external presence server 171 may be managed by the enterprise or by a third party. The presence server 108 in the enterprise network 175 periodically queries the presence server 171 for information regarding external endpoints associated with selected experts.


In a preferred configuration, the server 110, network 162, and first telecommunication devices 134 are Session Initiation Protocol or SIP compatible and can include interfaces for various other protocols such as the Lightweight Directory Access Protocol or LDAP, H.248, H.323, Simple Mail Transfer Protocol or SMTP, IMAP4, ISDN, E1/T1, and analog line or trunk.


It should be emphasized that the configuration of the switch, server, user telecommunication devices, and other elements as shown in FIG. 1 is for purposes of illustration only and should not be construed as limiting the invention to any particular arrangement of elements.


As will be appreciated, the central server 110 is notified via LAN 142 of an incoming contact by the telecommunications component (e.g., switch 130, fax server, email server, web server, and/or other server) receiving the incoming contact. The incoming contact is held by the receiving telecommunications component until the server 110 forwards instructions to the component to forward or route the contact to a specific contact center resource, such as the IVR unit 122, the voice mail server 118, and/or first or second telecommunication device 134, 138 associated with a selected agent or expert. The server 110 distributes and connects these contacts to telecommunication devices of available agents and experts based on the predetermined criteria noted above. When the central server 110 forwards a voice contact (or first work item) to an agent or expert, the central server 110 may also forward customer-related information from databases 114 to the agent's or expert's computer work station or other communication device for viewing (such as by a pop-up display) to permit the agent to better serve the customer. The agents and experts process the contacts or work items sent to them by the central server 110. This embodiment is particularly suited for a Customer Relationship Management (CRM) environment in which customers are permitted to use any media to contact a business.


The switch 130 and/or server 110 can be any architecture for directing contacts to one or more telecommunication devices. Illustratively, the switch and/or server can be a modified form of the subscriber-premises equipment disclosed in U.S. Pat. Nos. 6,192,122; 6,173,053; 6,163,607; 5,982,873; 5,905,793; 5,828,747; and 5,206,903, all of which are incorporated herein by this reference; Avaya Inc.'s Definity™ Private-Branch Exchange (PBX)-based ACD system; MultiVantage™ PBX, CRM Central 2000 Server™, Communication Manager™, S8300™, IP600™ or S8700™ media server, and/or Avaya Interaction Center™. Typically, the switch/server is a stored-program-controlled system that conventionally includes interfaces to external communication links, a communications switching fabric, service circuits (e.g., tone generators, announcement circuits, etc.), memory for storing control programs and data, and a processor (i.e., a computer) for executing the stored control programs to control the interfaces and the fabric and to provide automatic contact-distribution functionality. The switch and/or server typically include a network interface card (not shown) to provide services to the serviced telecommunication devices. Other types of known switches and servers are well known in the art and therefore not described in detail herein.


The present invention generally uses agents and experts to service contacts. Agents are individuals connected to agent workstations located in the service center that typically have at least most, and more typically at least 75%, of their working time (or primary job assignment) dedicated or assigned to servicing customer contacts. Agents log in and out of one or more agent queues at the beginning and end of their shifts and have various contact center states, such as AUX for auxiliary, AVAILABLE, UNAVAILABLE or BUSY when servicing a contact, AFTER CALL WORK (ACW), while finishing up work on a completed contact, and analogs thereof. In contrast, subject matter experts or nonagents are individuals not connected to agent workstations that have at least most, and more typically at least 75%, of their working time (or primary job assignment) assigned or dedicated to activities other than servicing customer contacts. As such, they generally do not have contact center states. Unlike agents, contacts are generally not blind transferred or forced upon experts. Experts, for example, are off site sales personnel, design engineers, software developers, research and development personnel, management or supervisory personnel, manufacturing employees, sales personnel, and the like who have an expertise in a desired area, such as product or service expertise, customer expertise, and the like. Customer expertise may include a prior relationship with a customer. Experts are often associated with and reachable via internal and external endpoints while agents are reachable only via internal endpoints. Agents often have limited knowledge of various aspects of a business or subject areas while an expert has deep or extensive knowledge of one or more of these aspects or subject areas.


Subject matter experts 240 may be called upon to service contacts in a variety of situations. For example, subject matter experts 240 may be called upon to service contacts or work items if traditional customer service agents are overloaded with work items and/or to assist an agent when the subject matter of the work item is beyond the expertise of the agent. In addition, the intercept engine 232 may notify the routing agent 220 of an incoming contact originating from high priority clients or containing subject matter of interest to a matter expert 240. Thus, a customer service system is provided where the customer's inquiry is handled by an individual or individuals with the greatest amount of expertise related to the problem, thereby increasing customer satisfaction and allowing the subject matter experts 240 to gain valuable experience or knowledge from handling customer inquiries.


Because experts have job duties other than servicing contacts, experts are generally given the option of whether or not to accept a contact for servicing prior to receiving the contact. A service request or invitation is sent to the expert by any convenient media or media type. The request may include contact and/or customer information, and a reason why the expert was selected to service the contact. “Contact information” commonly includes, for an incoming contact, customer identity, customer needs, contact media type, time stamp, and the like while “customer information” commonly includes customer identity, customer personal information, customer financial information, customer type or membership class, customer sales history, customer service history, and the like. The expert may respond with an unconditional acceptance (e.g., “available to service contact now”), a conditional acceptance (e.g., “currently unavailable to service contact but will be available in 15 minutes” or “currently available to service contact only on media type X”), or a denial. When a subject matter expert declines the request to participate, he or she may be contacted at a later time and re-invited. Re-invitation may be needed when the criticality or status of the work item escalates. For example, after initial subject matter expert denial, a service agreement for the contact may be violated (due to exceeded wait times, etc.), thus the subject matter expert will be re-invited to assist and given the new status of the work item. Depending on the response, the contact routing agent 220 immediately delivers to the contact to the expert, holds, parks or queues the contact until the expert is available, or selects another expert having the appropriate media type capability.


Referring to FIG. 2, one possible configuration of the server 110 is depicted. The server 110 is in communication with a plurality of customer communication lines (not shown) (which can be one or more trunks, phone lines, etc.) and agent and expert communication lines (not shown) (which can be a voice-and-data transmission line such as LAN 142 and/or a circuit switched voice line). Included among the data stored in the server 110 is a set of work item queues 208a-n and a separate set of agent queues 212a-n. Each work item queue 208a-n corresponds to a different set of agent skills, as does each agent queue 212a-n. Conventionally, work items are prioritized and either are enqueued in individual ones of the work item queues 208a-n in their orders of priority or are enqueued in different ones of a plurality of work item queues that correspond to a different priority. Likewise, each agent's skills are prioritized according to his or her level of expertise in that skill, and either agents are enqueued in individual ones of agent queues 212a-n in their orders of expertise level or are enqueued in different ones of a plurality of agent queues 212a-n that correspond to a skill and each one of which corresponds to a different expertise level. As will be appreciated, experts may be placed in one or more agent queues or separate queues using the same criteria. Contacts incoming to the contact center are assigned by a contact routing agent 220 to different work item queues 208a-n based upon a number of predetermined criteria, including customer identity, customer needs, contact center needs, current work item center queue lengths, customer value, and the agent skill that is required for the proper handling of the contact. Agents (or experts) who are available for handling contacts are assigned to agent queues 212a-n based upon the skills that they possess. An agent or expert may have multiple skills, and hence may be assigned to multiple agent (and/or expert) queues 212a-n simultaneously. Furthermore, an agent or expert may have different levels of skill expertise (e.g., skill levels 1-N in one configuration or merely primary skills and secondary skills in another configuration), and hence may be assigned to different agent (and/or expert) queues 212a-n at different expertise levels.


According to the invention, included among the programs executed by the processor of the server 110 are not only the contact routing agent 220 but also the agent selector 224, the expert selector 228, an intercept engine 232, and a filtering engine 236. The contact routing agent 220 directs an incoming contact either to a contact queue 208 or directly to an expert 240 and determines whether the contact is to be routed to an agent in an agent skill queue 212 or an expert 240. The agent selector 224 selects an agent to service the contact based on techniques known to those of skill in the art. The expert selector 228 selects an expert 240 to service the contact as set forth in more detail below. The intercept engine 232 flags incoming contacts, prior to queuing, that need to be directed to an expert 240. Finally, the filtering engine 236 applies predetermined filtering rules and policies to determine a set of eligible experts for consideration by the expert selector 228.


The expert selector 228 selects, from a subset of eligible experts, an expert to service an incoming or enqueued contact or assist an agent. In selecting an expert, the expert selector 228 applies policies and rules to contact, customer and expert information to select the optimal expert under the circumstances to service or assist in servicing the contact. The contact/customer information considered can include the identity of the customer making the contact, the contact type or media type, the maximum wait time tolerable to the customer, the subject area of interest to the customer, the needs of the customer, the predicted, expected or actual wait time of the contact, the customer class membership, customer-specific information, the predicted amount of time required to address the contact, and the like. The expert information considered can include the presence information associated with the selected expert, the expert information for the selected expert, the contact or media types that are available to the selected expert to service the contact, the minimum and maximum times at which the expert will be available to service contacts, and the like. In one configuration, the algorithm used for expert selection is the same as or similar to the algorithm used for agent selection. Both algorithms would employ skills-based routing techniques to direct the contact to an agent or expert.


The expert selector 228 can use a variety of techniques to notify experts of possible selection for servicing a contact. In one configuration, the experts are on a rotating list of availability, and the next listed expert is selected and requested to service the contact. In another configuration, the expert having the highest degree of expertise for the subject matter of interest to the customer or has handled the fewest contacts in a specified time period is selected and requested. In another configuration, each expert in the subset of experts is sent a request. Experts indicating that they are available for contact servicing are then further filtered to select a best fit for the contact. A final service confirmation notification is sent to the selected expert and the contact simultaneously or delivered subsequently. When only one expert at-a-time is selected and requested, the process is repeated until an expert indicates that he is available for servicing the contact. He is then sent a confirmation notification, and the contact delivered to him. In any of the above techniques, the request may be an audio message, a graphical message, or a combination thereof.


When an expert is only available in a set period of time, the customer may be queried whether he is willing to wait for the expert or prefers to be serviced immediately by a less skilled agent. If the customer opts to wait, the contact is queued until the expert is available. Alternatively, the customer may request a call back when the expert is available. In that event, a call back request is placed in a call back queue. In one configuration, the selector 228 toggles back-and-forth between the customer making the contact and one or more experts to determine which expert is best able to service the customer within the customer's time constraints.


The intercept engine maps selected contact information for each incoming contact against a set of target criteria to determine if an incoming contact should be routed directly to an expert rather than an agent. The target criteria can include customer identity, customer class, subject matter area, customer need, and the like. For example, an expert may request that any incoming contact from a specified customer or class of customer be sent directly to him. The expert may request that any incoming contact related to a specific product or product problem be sent directly to him.


The filtering engine 236 maps the customer and/or contact information against expert preferences, presence and/or expert information to exclude ineligible experts from consideration by the expert selector 228. Expert preferences or limitations include, for example, permissible times for servicing contacts, permissible customer membership classes, permissible customer identities, permissible subject matter areas, and the like. If a contact is found to be impermissible based on the expert preferences, the expert is considered to be ineligible to service the contact. In one configuration, the filtering engine 236 and not the selector 228 sends invite messages to possible eligible experts and provides the selector 228 only with those experts indicating a determined degree of availability.


Based upon the foregoing, there are a number of contact center modes of operation.


In a first “work item overflow” mode, the contact center is designed to call in subject matter experts 240 when the time to address work items in one or more queues and/or a number of work items in one or more queues exceeds a predetermined limit. This mode ensures that customer service inquiries are addressed in an acceptable amount of time. For example, when an incoming work item or an enqueued work item is subject to a service escalation such as due to a work overflow condition, the routing agent 220 requests the expert selector 228 to identify subject matter experts 240 that are available to address the work item. The work item is then directed to the available subject matter expert 240 with the highest degree of expertise in that field or, alternatively, is directed to the first available subject matter expert 240 to provide assistance. The work items may be placed in a skill queue to be addressed by the subject matter expert 240 in order of receipt.


In a second “intercept” mode of operation, the subject matter expert 240 is able to intercept work items of a specific nature or from a specific customer. More specifically, some work items are important to subject matter experts 240, because, for example, they originate from a valued customer or are concerned with a certain type of hardware or problem handled routinely by the subject matter expert 240. The subject matter expert 240 can alter his or her expert information to identify the conditions wherein certain work items will be sent directly to him, thereby bypassing any agent interaction. The advantage of this mode is that subject matter experts may provide a high level of customer service to their important clients. In addition, one skilled in the art will appreciate that subject matter experts who develop products may be interested in how a certain product is being used in real world situations. For example, the identification of software problems, i.e. bugs, may be more quickly addressed. The ability to intercept specific product-related questions may also identify the need to create additional frequently asked question hyperlinks on a website, for example.


In yet a third “agent assistance” mode of operation, a servicing agent requests assistance from a subject matter expert when the subject matter of the work item is directed to subject matter outside the expertise of the agent. One skilled in the art will appreciate that this situation may occur when the agent initially addressed the work item but discovers during further investigation of the client's problem, that the problems posed were not accurately characterized by the contact center, thereby creating a situation where the agent is unable to address the problem. Embodiments of the present invention may also include the ability for the agent to provide the subject matter expert a time estimate of how long it will take to rectify the complex work item. More specifically, when a subject matter expert is invited to interrupt his/her current activities to aid an agent, the subject matter expert may be given an estimated duration of the interruption. This duration information will help the subject matter expert decide whether to accept or decline the request for assistance. The estimated duration may be derived from the average handling times of similar work items or from alternate methods known in the art. One skilled in the art will appreciate that this aspect of the invention may be employed in the work item overflow and intercept modes of operation as well.


It is still yet another mode of operation that allows subject matter experts to participate in a follow-up fashion. More specifically, it is often desirable to identify certain clients or work items involving certain issues, for enhanced service, wherein the subject matter expert contacts the customer as a follow-up to ensure that the work item was sufficiently addressed. One skilled in the art will appreciate that again, the follow-up criteria may allow subject matter experts to opt into the system by a volunteer basis, customer basis, problem basis, etc. One advantage of this would be to allow for the subject matter expert to follow up with a particular client, build a rapport with that client, and have a continued relationship with that client wherein future work items generated by that client may be intercepted by the subject matter expert. Thus, the subject matter expert helps build confidence in the company by catering to a certain group of clients.


A volunteer mode is also contemplated that allows subject matter experts to volunteer to address random customer service inquiries, i.e. become “agents”. This mode allows the subject matter experts to increase their customer service skills and to have more customer interaction. In addition, this option is desirable to the company such that the time customers spend in agent queues would be reduced since the amount of agents would increase from time to time. In addition, it should be understood by one skilled in the art that subject matter experts may log in to volunteer to assist agents when the subject matter expert's work load is low, thus increasing employee productivity.


Referring now to FIG. 3, a flowchart is shown that illustrates the “overflow” mode. When a work item initially arrives at step 304, it is characterized in step 308 to identify the subject matter level of difficulty, time to answer, etc. Characterization may be performed by the IVR unit 122, a human agent, content analysis, DNIS or sending address analysis, and the like. Next, the system assesses the availability of agents in decision diamond 312. If there is an agent available to service the work item immediately or a skill queue of agents to service the work item within a predetermined time frame, the work item, in step 314, is assigned to the agent or is placed in the agent queue. If however, an agent is not available immediately or if wait times of the skill queue exceed a predetermined level, the router 220 instructs the selector 228 to select a subject matter expert to service the work item in step 316. More specifically, if the agent is not immediately available, the work item is queued 313. The system next assesses the estimated wait time in decision diamond 315. If the wait time is not acceptable, the work item is routed to the selected expert 316. If subject matter experts are available as identified by the presence information and as described above, individual experts are invited in step 320 to service the work item. Here, embodiments of the present invention utilize a call to the subject matter expert, a pop up screen on the subject matter expert's computer, a page, a call to the subject matter expert's cellphone, or any other similar way to contact the expert to invite them to assist the agents. In decision diamond 324, the invited expert(s) may accept, decline, or accept with a condition. if the invited expert(s) accept unconditionally or conditionally with an acceptable condition, the other requests or invitations for assistance to all other subject matter experts are cancelled or retracted in step 328, and the contact is routed to the accepting expert in step 332. If the invited expert(s) decline or conditionally accept with unacceptable conditions, the selector 228 proceeds to decision diamond 336 and searches for other available experts 240. if no further experts can be identified, the selector 228 proceeds to decision diamond 312. If one or more further experts are identified, the selector 228 proceeds to and repeats step 320. One skilled in the art will appreciate that a parallel approach may be used where many experts are invited at one time as described above. In one configuration, if no experts are available in decision diamond 336, the work item is directed to the appropriate agent queue.


Referring now to FIG. 4, the “intercept” mode is illustrated. The work item arrives in step 404 and is characterized in step 408 to identify the subject matter thereof and other relevant information. In decision diamond 412, the intercept engine 232 compares the contact information of the work item with target criteria that has been identified to initiate re-direction of an incoming work item. If the comparison finds a match, the identified expert is invited in step 416 to service the work item. As noted, the expert in decision diamond 420 may accept conditionally or unconditionally or decline. If the expert accepts unconditionally or with an acceptable condition, the work item is routed to the expert in step 440. If the expert declines or accepts conditionally with an unacceptable condition, the selector 228 proceeds to decision diamond 436. If the condition is a wait time before the expert is available to service the contact, the selector 228 proceeds to decision diamond 432. In decision diamond 432, the customer is queried whether she would like to wait for the expert to be available to service her contact. If so, the work item, in step 433 is parked, held, or placed in a queue or a conference is scheduled with the expert. If however, the customer does not wish to wait to talk to the expert, if the contact is not to be intercepted in decision diamond 412, or if the expert declines to service the contact in decision diamond 436, the contact, in step 433, is queued in a contact queue to await servicing by an agent.


Referring now to FIG. 5, the “agent assistance” mode of operation is shown. Here, as in traditional call center systems, the work item arrives in step 504, is characterized in step 508, and assigned to an agent in step 512. During the course of servicing the work item, the agent decides, in step 516, to ask a subject matter expert for assistance. In step 520, an expert or group of experts is selected based, inter alia, on the subject matter of the work item and the skills of a subject matter expert. Once the subject matter expert is identified, he or she is invited in step 524 to assist the agent in resolving the work item. If, in decision diamond 528, the expert accepts unconditionally or conditionally with acceptable conditions, all other invitations are canceled in step 532, and, in step 536, the contact is routed to the accepting expert. Alternatively, the expert may be conferenced in with the agent and the customer. If, in decision diamond 528, the expert declines or accepts conditionally with an unacceptable condition, the selector 228, in decision diamond 540, determines whether any potentially selectable experts are still available. If so, the selector 228 proceeds to and repeats step 520. if not, the agent continues servicing the contact without assistance.


A number of variations and modifications of the invention can be used. It would be possible to provide for some features of the invention without providing others.


For example in one alternative embodiment, the various components or modules can be implemented as hardware or software or a combination thereof and can be implemented in different ways. For example, the steps noted above for each module can be performed by other modules, depending on the application.


The present invention, in various embodiments, includes components, methods, processes, systems and/or apparatus substantially as depicted and described herein, including various embodiments, subcombinations, and subsets thereof. Those of skill in the art will understand how to make and use the present invention after understanding the present disclosure. The present invention, in various embodiments, includes providing devices and processes in the absence of items not depicted and/or described herein or in various embodiments hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and\or reducing cost of implementation.


The foregoing discussion of the invention has been presented for purposes of illustration and description. The foregoing is not intended to limit the invention to the form or forms disclosed herein. In the foregoing Detailed Description for example, various features of the invention are grouped together in one or more embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate preferred embodiment of the invention.


Moreover, though the description of the invention has included description of one or more embodiments and certain variations and modifications, other variations and modifications are within the scope of the invention, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter.

Claims
  • 1. In a contact center, the contact center comprising at least one work item queue, at least one agent queue for servicing the at least one work item queue, the at least one agent queue being associated with a plurality of agents, a method for servicing contacts, comprising: a processor determining whether an agent is available to service a selected work item;if an agent is available, the processor assigning the selected work item to the agent;if the agent is not available, the processor determining that the selected work item is to be serviced by a selected expert, the selected expert being a third party that is different from the plurality of agents;the processor determining presence information associated with the selected expert, the presence information indicating a current availability of the selected expert for receiving a contact;the processor determining that the selected expert is currently available to receive a contact;the processor inviting the selected expert to service the work item; andthe processor determining if the selected expert has accepted the invitation, wherein determining if the selected expert has accepted the invitation comprises:the processor receiving a conditional acceptance of the invitation from the selected expert, the conditional acceptance indicating that the selected expert will be available to service the contact at a stated period of time and on a specified media type,the processor querying a customer associated with the work item whether or not the customer may wait the stated period of time for the work item to be serviced; andthe processor applying the following rules:when the customer is willing to wait, the processor directing the work item to the selected expert for servicing; andwhen the customer is unwilling to wait, the processor not directing the work item to the selected expert for servicing.
  • 2. The method of claim 1, wherein at least most of the expert's work hours are not dedicated to servicing work items, wherein at least most of each agent's work hours are dedicated to servicing work items, wherein the selected expert does not log into a call center component, and does not use auxiliary codes to become unavailable to calls, wherein the agents log into the call center component and use auxiliary codes to become unavailable to calls, and wherein the selected expert is contacted, when inviting the selected expert to service the work item, via an external endpoint.
  • 3. The method of claim 1, wherein determining that a the selected work item is to be serviced by a selected expert comprises: the processor determining that the selected work item is a type of work item subject to a service escalation condition, wherein the service escalation condition results from a number of work items of the type of work item waiting to be serviced being in excess of a first selected threshold, the type of work item having a wait time in excess of a second selected threshold, and/or the selected work item has a wait time in excess of a third selected threshold; andin response to determining that the selected work item is a type of work item subject to a service escalation condition, the processor determining that the selected work item is to be serviced by the selected expert rather than an agent.
  • 4. The method of claim 1, wherein determining that a the selected work item is to be serviced by a selected expert is performed before the selected work item is queued and wherein the presence information comprises a plurality of registration information, information regarding the accessibility of the selected expert's endpoint device, a recency of use of the endpoint device by the expert, a recency of authentication by the selected expert to a network component, the geographic location of the selected expert's endpoint device, a type of media used by the selected expert's endpoint device, contact preferences of the selected expert, and entries in the selected expert's electronic calendar.
  • 5. The method of claim 1, wherein determining that the selected work item is to be serviced by a selected expert is performed after the selected work item is at least partially serviced by an agent, wherein the invitation comprises contact information associated with the work item, and wherein the contact information comprises customer identity, customer needs, contact media type, and time stamp.
  • 6. The method of claim 1, wherein the invitation comprises contact information associated with the work item, customer information associated with the work item, and a reason why the expert was selected to service the contact, wherein the contact information comprises a plurality of customer identity, customer needs, contact media type, and time stamp, and wherein customer information comprises a plurality of customer identity, customer personal information, customer financial information, customer wait time preferences, customer type or class membership class, customer sales history, and customer service history.
  • 7. The method of claim 1, wherein the presence information comprises a plurality of registration information associated with the selected expert, information regarding the accessibility of an endpoint device associated with the selected expert, a recency of use of the endpoint device by the selected expert, a recency of authentication by the selected expert to a network component, a geographic location of the selected expert's endpoint device, a type of media capability of the selected expert's endpoint device, session and communications capabilities of the endpoint devices associated with the selected expert, one or more preferences of the selected expert, and an electronic calendar maintained by the selected expert.
  • 8. The method of claim 1, wherein determining that the selected work item is to be serviced by a selected expert comprises the sub-steps: the processor determining, by an intercept engine, that the selected work item is to be serviced by an expert rather than an agent, the intercept engine mapping contact information for the selected work item against a set of target criteria;the processor determining, by a filtration engine, a set of experts eligible to service the selected work item, the selected expert being a member of the expert set, wherein the filtration engine maps customer and/or contact information associated with the selected work item against expert preferences, presence information, and/or expert information; andthe processor selecting, by an expert selector, a subset of the set of experts, the subset comprising the selected expert, wherein at least one of the following is used to select the expert subset: a rotating list of availability, a degree of expertise of the members of the expert set, and a level of responsiveness and/or availability of the members of the expert set.
  • 9. The method of claim 1, wherein, in determining that the selected expert is currently available to receive a contact, a plurality of selected experts are simultaneously or substantially simultaneously invited to service the work item and further comprising: the processor selecting the expert based on expert preferences, the preferences comprising at least one of permissible times for servicing contacts, permissible customer membership classes, permissible customer identities, permissible expected handle time duration, and permissible subject matter areas.
  • 10. The processor executing instructions for performing the steps of claim 1.
  • 11. A contact center, comprising: a memory;at least one work item queue;at least one agent queue for servicing the at least one work item queue, the at least one agent queue being associated with a plurality of agents;a processor operable to:determine that a selected work item is to be serviced by a selected expert, the selected expert being different from the plurality of agents, wherein determining that a the selected work item is to be serviced by a selected expert is performed before the selected work item is queued;access a third party presence server, wherein the third party presence server stores presence information for the selected expert;retrieve presence information from the third party presence server;determine presence information associated with the selected expert, the presence information indicating a current availability of the selected expert for receiving a contact;determine that the selected expert is currently available to receive a contact;in response to determining that the selected expert is currently available, invite the selected expert to service the work item; anddetermine if the selected expert has accepted the invitation, wherein determining if the selected expert has accepted the invitation comprises:the processor receiving a conditional acceptance of the invitation from the selected expert, the conditional acceptance indicating that the selected expert will be available to service the contact at a stated period of time and on a specified media type,the processor querying a customer associated with the work item whether or not the customer may wait the stated period of time for the work item to be serviced; andthe processor applying the following rules:when the customer is willing to wait, the processor directing the work item to the selected expert for servicing; andwhen the customer is unwilling to wait, the processor not directing the work item to the selected expert for servicing.
  • 12. The contact center of claim 11, wherein at least most of the expert's work hours are not dedicated to servicing work items, wherein at least most of each agent's work hours are dedicated to servicing work items, wherein the selected expert does not log into a call center component, and does not use auxiliary codes to become unavailable to calls, wherein the agents log into the call center component and use auxiliary codes to become unavailable to calls, and wherein the selected expert is contacted in operation (iv) via an external endpoint.
  • 13. The contact center of claim 11, wherein determining that a selected work item is to be serviced by a selected expert, the selected expert being different from the plurality of agents comprises: determining that the selected work item is a type of work item subject to a service escalation condition, wherein the service escalation condition results from a number of work items of the type of work item waiting to be serviced being in excess of a first selected threshold, the type of work item having a wait time in excess of a second selected threshold, the time to address the work item exceeds a third selected threshold, the predicted time to address the work item exceeds a fourth selected threshold, and/or the selected work item has a wait time in excess of a fifth selected threshold.
  • 14. The contact center of claim 11, wherein the presence information comprises a plurality of registration information, information regarding the accessibility of the selected expert's endpoint device, a recency of use of the endpoint device by the expert, a recency of authentication by the selected expert to a network component, the geographic location of the selected expert's endpoint device, a type of media used by the selected expert's endpoint device, contact preferences of the selected expert, and entries in the selected expert's electronic calendar.
  • 15. The contact center of claim 11, wherein the invitation comprises contact information associated with the work item, and wherein the contact information comprises customer identity, customer needs, contact media type, and time stamp.
  • 16. The contact center of claim 11, wherein the invitation comprises at least one of contact information associated with the work item, customer information associated with the work item, expected handling time of the work item, and a reason why the expert was selected to service the contact, wherein the contact information comprises a plurality of customer identity, customer needs, contact media type, and time stamp, and wherein customer information comprises a plurality of customer identity, customer personal information, customer financial information, customer wait time preferences, customer type or class membership class, customer sales history, and customer service history.
  • 17. The contact center of claim 11, wherein the presence information comprises a plurality of registration information associated with the selected expert, information regarding the accessibility of an endpoint device associated with the selected expert, a recency of use of the endpoint device by the selected expert, a recency of authentication by the selected expert to a network component, a geographic location of the endpoint device, a type of media capability of the selected expert's endpoint device, session and communications capabilities of the various endpoint devices associated with the selected expert, one or more preferences of the selected expert, and an electronic calendar maintained by the selected expert.
  • 18. The contact center of claim 11, in determining that a selected work item is to be serviced by a selected expert, the selected expert being different from the plurality of agents, the processor performs the following instructional modules: an intercept module to determine that the selected work item is to be serviced by an expert rather than an agent, the intercept engine mapping contact information for the selected work item against a set of target criteria;a filtration module to determine that a set of experts eligible to service the selected work item, the selected expert being a member of the expert set, wherein the filtration engine maps customer and/or contact information associated with the selected work item against expert preferences, presence information, and/or expert information; andan expert selector to determine a subset of the set of experts, the subset comprising the selected expert, wherein at least one of the following is used to select the expert subset: a rotating list of availability, a degree of expertise of the members of the expert set, and a level of responsiveness and/or availability of the members of the expert set.
  • 19. The contact center of claim 11, wherein, in determining that the selected expert is currently available to receive a contact, a plurality of selected experts are simultaneously or substantially simultaneously invited to service the work item and wherein the processor is further operable to select the expert based on expert preferences, the preferences comprising at least one of permissible times for servicing contacts, permissible customer membership classes, permissible customer identities, permissible expected handle time duration, and permissible subject matter areas.
  • 20. The contact center of claim 11, wherein time the expert spends addressing the work item is tracked and further comprising re-inviting the selected expert if he or she does not accept the invitation.
  • 21. The method of claim 1, wherein the selected work item is to be serviced by the selected expert for at least one of the following reasons: a time to address work items in one or more queues exceeds a predetermined limit;a number of work items in one or more queues exceeds a predetermined limit;the selected expert has identified conditions requiring the selected work item to be sent directly to the selected expert rather than an agent; andan agent servicing the work item requests assistance from a subject matter expert.
  • 22. In a contact center, the contact center comprising at least one work item queue, at least one agent queue for servicing the at least one work item queue, the at least one agent queue being associated with a plurality of agents, a method for servicing contacts, comprising: a processor receiving a selected work item from a customer;the processor assigning the selected work item to the agent, wherein the agent partially services the selected work item;after the selected work item is partially serviced, the processor determining that the selected work item is to be serviced by a selected expert, the selected expert being a third party that is different from the plurality of agents;the processor determining presence information associated with the selected expert, the presence information indicating a current availability of the selected expert for receiving a contact;the processor determining that the selected expert is currently available to receive a contact the processor inviting the selected expert to service the partially serviced work item; andthe processor determining if the selected expert has accepted the invitation, wherein determining if the selected expert has accepted the invitation comprises:the processor receiving a conditional acceptance of the invitation from the selected expert, the conditional acceptance indicating that the selected expert will be available to service the contact at a stated period of time and on a specified media type,the processor querying a customer associated with the partially service work item whether or not the customer may wait the stated period of time for the partially service work item to be serviced; andthe processor applying the following rules:when the customer is willing to wait, the processor directing the partially service work item to the selected expert for servicing; andwhen the customer is unwilling to wait, the processor not directing the partially service work item to the selected expert for servicing.
US Referenced Citations (347)
Number Name Date Kind
4163124 Jolissaint Jul 1979 A
4510351 Costello et al. Apr 1985 A
4567323 Lottes et al. Jan 1986 A
4737983 Frauenthal et al. Apr 1988 A
4797911 Szlam et al. Jan 1989 A
4894857 Szlam et al. Jan 1990 A
5001710 Gawrys et al. Mar 1991 A
5097528 Gursahaney et al. Mar 1992 A
5101425 Darland Mar 1992 A
5155761 Hammond Oct 1992 A
5164981 Mitchell et al. Nov 1992 A
5164983 Brown et al. Nov 1992 A
5167010 Elm et al. Nov 1992 A
5185780 Leggett Feb 1993 A
5206903 Kohler et al. Apr 1993 A
5210789 Jeffus et al. May 1993 A
5274700 Gechter et al. Dec 1993 A
5278898 Cambray et al. Jan 1994 A
5289368 Jordan et al. Feb 1994 A
5291550 Levy et al. Mar 1994 A
5299260 Shaio Mar 1994 A
5309513 Rose May 1994 A
5325292 Crockett Jun 1994 A
5335268 Kelly, Jr. et al. Aug 1994 A
5335269 Steinlicht Aug 1994 A
5390243 Casselman et al. Feb 1995 A
5436965 Grossman et al. Jul 1995 A
5444774 Friedes Aug 1995 A
5467391 Donaghue, Jr. et al. Nov 1995 A
5469503 Butensky et al. Nov 1995 A
5469504 Blaha Nov 1995 A
5473773 Aman et al. Dec 1995 A
5479497 Kovarik Dec 1995 A
5499291 Kepley Mar 1996 A
5500795 Powers et al. Mar 1996 A
5504894 Ferguson et al. Apr 1996 A
5506898 Costantini et al. Apr 1996 A
5530744 Charalambous et al. Jun 1996 A
5537470 Lee Jul 1996 A
5537542 Eilert et al. Jul 1996 A
5544232 Baker et al. Aug 1996 A
5546452 Andrews et al. Aug 1996 A
5555299 Maloney et al. Sep 1996 A
5577169 Prezioso Nov 1996 A
5592378 Cameron et al. Jan 1997 A
5592542 Honda et al. Jan 1997 A
5594726 Thompson et al. Jan 1997 A
5603029 Aman et al. Feb 1997 A
5604892 Nuttall et al. Feb 1997 A
5606361 Davidsohn et al. Feb 1997 A
5611076 Durflinger et al. Mar 1997 A
5627884 Williams et al. May 1997 A
5642515 Jones et al. Jun 1997 A
5684872 Flockhart et al. Nov 1997 A
5684874 Yagyu et al. Nov 1997 A
5684964 Powers et al. Nov 1997 A
5689698 Jones et al. Nov 1997 A
5703943 Otto Dec 1997 A
5713014 Durflinger et al. Jan 1998 A
5721770 Kohler Feb 1998 A
5724092 Davidsohn et al. Mar 1998 A
5740238 Flockhart et al. Apr 1998 A
5742675 Kilander et al. Apr 1998 A
5742763 Jones Apr 1998 A
5748468 Notenboom et al. May 1998 A
5749079 Yong et al. May 1998 A
5751707 Voit et al. May 1998 A
5752027 Familiar May 1998 A
5754639 Flockhart et al. May 1998 A
5754776 Hales et al. May 1998 A
5754841 Carino, Jr. May 1998 A
5757904 Anderson May 1998 A
5784452 Carney Jul 1998 A
5790642 Taylor et al. Aug 1998 A
5790650 Dunn et al. Aug 1998 A
5790677 Fox et al. Aug 1998 A
5794250 Carino, Jr. et al. Aug 1998 A
5796393 MacNaughton et al. Aug 1998 A
5802282 Hales et al. Sep 1998 A
5802510 Jones Sep 1998 A
5818907 Maloney et al. Oct 1998 A
5819084 Shapiro et al. Oct 1998 A
5825869 Brooks et al. Oct 1998 A
5826039 Jones Oct 1998 A
5828747 Fisher et al. Oct 1998 A
5836011 Hambrick et al. Nov 1998 A
5838968 Culbert Nov 1998 A
5839117 Cameron et al. Nov 1998 A
5864874 Shapiro Jan 1999 A
5875437 Atkins Feb 1999 A
5880720 Iwafune et al. Mar 1999 A
5881238 Aman et al. Mar 1999 A
5884032 Bateman et al. Mar 1999 A
5889956 Hauser et al. Mar 1999 A
5897622 Blinn et al. Apr 1999 A
5903641 Tonisson May 1999 A
5903877 Berkowitz et al. May 1999 A
5905793 Flockhart et al. May 1999 A
5909669 Havens Jun 1999 A
5911134 Castonguay et al. Jun 1999 A
5914951 Bentley et al. Jun 1999 A
5915012 Miloslavsky Jun 1999 A
5923745 Hurd Jul 1999 A
5926538 Deryugin et al. Jul 1999 A
5930786 Carino, Jr. et al. Jul 1999 A
5937051 Hurd et al. Aug 1999 A
5937402 Pandit Aug 1999 A
5940496 Gisby et al. Aug 1999 A
5943416 Gisby Aug 1999 A
5948065 Eilert et al. Sep 1999 A
5960073 Kikinis et al. Sep 1999 A
5963635 Szlam et al. Oct 1999 A
5963911 Walker et al. Oct 1999 A
5970132 Brady Oct 1999 A
5974135 Breneman et al. Oct 1999 A
5974462 Aman et al. Oct 1999 A
5982873 Flockhart et al. Nov 1999 A
5987117 McNeil et al. Nov 1999 A
5991392 Miloslavsky Nov 1999 A
5996013 Delp et al. Nov 1999 A
5999963 Bruno et al. Dec 1999 A
6000832 Franklin et al. Dec 1999 A
6011844 Uppaluru et al. Jan 2000 A
6014437 Acker et al. Jan 2000 A
6031896 Gardell et al. Feb 2000 A
6038293 McNerney et al. Mar 2000 A
6038296 Brunson et al. Mar 2000 A
6044144 Becker et al. Mar 2000 A
6044205 Reed et al. Mar 2000 A
6044355 Crockett et al. Mar 2000 A
6049547 Fisher et al. Apr 2000 A
6049779 Berkson Apr 2000 A
6052723 Ginn Apr 2000 A
6055308 Miloslavsky et al. Apr 2000 A
6064730 Ginsberg May 2000 A
6064731 Flockhart et al. May 2000 A
6084954 Harless Jul 2000 A
6088441 Flockhart et al. Jul 2000 A
6108670 Weida et al. Aug 2000 A
6115462 Servi et al. Sep 2000 A
6128304 Gardell et al. Oct 2000 A
6151571 Pertrushin Nov 2000 A
6154769 Cherkasova et al. Nov 2000 A
6163607 Bogart et al. Dec 2000 A
6173053 Bogart et al. Jan 2001 B1
6175564 Miloslavsky et al. Jan 2001 B1
6178441 Elnozahy Jan 2001 B1
6185292 Miloslavsky Feb 2001 B1
6185603 Henderson et al. Feb 2001 B1
6192122 Flockhart et al. Feb 2001 B1
6215865 McCalmont Apr 2001 B1
6226377 Donaghue, Jr. May 2001 B1
6229819 Darland et al. May 2001 B1
6230183 Yocom et al. May 2001 B1
6233333 Dezonmo May 2001 B1
6240417 Eastwick May 2001 B1
6259969 Tackett et al. Jul 2001 B1
6263359 Fong et al. Jul 2001 B1
6272544 Mullen Aug 2001 B1
6275806 Pertrushin Aug 2001 B1
6275812 Haq et al. Aug 2001 B1
6275991 Erlin Aug 2001 B1
6278777 Morley Aug 2001 B1
6292550 Burritt Sep 2001 B1
6295353 Flockhart et al. Sep 2001 B1
6298062 Gardell et al. Oct 2001 B1
6307931 Vaudreuil Oct 2001 B1
6324282 McIllwaine et al. Nov 2001 B1
6332081 Do Dec 2001 B1
6339754 Flanagan et al. Jan 2002 B1
6353810 Petrushin Mar 2002 B1
6356632 Foster et al. Mar 2002 B1
6360222 Quinn Mar 2002 B1
6366666 Bengtson et al. Apr 2002 B2
6366668 Borst et al. Apr 2002 B1
6389028 Bondarenko et al. May 2002 B1
6389132 Price May 2002 B1
6389400 Bushey et al. May 2002 B1
6411682 Fuller et al. Jun 2002 B1
6424709 Doyle et al. Jul 2002 B1
6426950 Mistry Jul 2002 B1
6427137 Petrushin Jul 2002 B2
6430282 Bannister et al. Aug 2002 B1
6434230 Gabriel Aug 2002 B1
6446092 Sutter Sep 2002 B1
6449356 Dezonno Sep 2002 B1
6449358 Anisimov et al. Sep 2002 B1
6449646 Sikora et al. Sep 2002 B1
6453038 McFarlane et al. Sep 2002 B1
6463148 Brady Oct 2002 B1
6463346 Flockhart et al. Oct 2002 B1
6463415 St. John Oct 2002 B2
6480826 Pertrushin Nov 2002 B2
6490350 McDuff et al. Dec 2002 B2
6535600 Fisher et al. Mar 2003 B1
6535601 Flockhart et al. Mar 2003 B1
6553114 Fisher et al. Apr 2003 B1
6556974 D'Alessandro Apr 2003 B1
6560330 Gabriel May 2003 B2
6560649 Mullen et al. May 2003 B1
6560707 Curtis et al. May 2003 B2
6563920 Flockhart et al. May 2003 B1
6571285 Groath et al. May 2003 B1
6574599 Lim et al. Jun 2003 B1
6574605 Sanders et al. Jun 2003 B1
6597685 Miloslavsky et al. Jul 2003 B2
6603854 Judkins et al. Aug 2003 B1
6604084 Powers et al. Aug 2003 B1
6614903 Flockhart et al. Sep 2003 B1
6650748 Edwards et al. Nov 2003 B1
6704409 Dilip et al. Mar 2004 B1
6707903 Flockhart et al. Mar 2004 B2
6711253 Prabhaker Mar 2004 B1
6735299 Krimstock et al. May 2004 B2
6735593 Williams May 2004 B1
6738462 Brunson May 2004 B1
6754333 Flockhart et al. Jun 2004 B1
6757362 Cooper et al. Jun 2004 B1
6766013 Flockhart et al. Jul 2004 B2
6766014 Flockhart et al. Jul 2004 B2
6766326 Cena Jul 2004 B1
6775377 McIllwaine et al. Aug 2004 B2
6785666 Nareddy et al. Aug 2004 B1
6822945 Petrovykh Nov 2004 B2
6829348 Schroeder et al. Dec 2004 B1
6842503 Wildfeuer Jan 2005 B1
6847973 Griffin et al. Jan 2005 B2
6898190 Shtivelman et al. May 2005 B2
6915305 Subramanian et al. Jul 2005 B2
6947988 Saleh Sep 2005 B1
6981061 Sakakura Dec 2005 B1
6985901 Sachse et al. Jan 2006 B1
6988126 Wilcock et al. Jan 2006 B2
7010542 Trappen et al. Mar 2006 B2
7020254 Phillips Mar 2006 B2
7039176 Borodow et al. May 2006 B2
7062031 Becerra et al. Jun 2006 B2
7076051 Brown et al. Jul 2006 B2
7100200 Pope et al. Aug 2006 B2
7110525 Heller et al. Sep 2006 B1
7117193 Basko et al. Oct 2006 B1
7136873 Smith et al. Nov 2006 B2
7149733 Lin et al. Dec 2006 B2
7155612 Licis Dec 2006 B2
7158628 McConnell et al. Jan 2007 B2
7162469 Anonsen et al. Jan 2007 B2
7165075 Harter et al. Jan 2007 B2
7170976 Keagy Jan 2007 B1
7170992 Knott et al. Jan 2007 B2
7177401 Mundra et al. Feb 2007 B2
7203655 Herbert et al. Apr 2007 B2
7212625 McKenna et al. May 2007 B1
7215744 Scherer May 2007 B2
7257597 Pryce et al. Aug 2007 B1
7266508 Owen et al. Sep 2007 B1
7324954 Calderaro et al. Jan 2008 B2
7340408 Drew et al. Mar 2008 B1
7376127 Hepworth et al. May 2008 B2
7392402 Suzuki Jun 2008 B2
7418093 Knott et al. Aug 2008 B2
7545925 Williams Jun 2009 B2
20010011228 Shenkman Aug 2001 A1
20010019816 Kumar Sep 2001 A1
20010042126 Wong et al. Nov 2001 A1
20010053214 Kleinoder et al. Dec 2001 A1
20010054037 Shapiro et al. Dec 2001 A1
20010056349 St. John Dec 2001 A1
20020002460 Pertrushin Jan 2002 A1
20020002464 Petrushin Jan 2002 A1
20020010587 Pertrushin Jan 2002 A1
20020012186 Nakamura et al. Jan 2002 A1
20020019829 Shapiro Feb 2002 A1
20020021307 Glenn et al. Feb 2002 A1
20020035594 Dreke et al. Mar 2002 A1
20020035605 McDowell et al. Mar 2002 A1
20020038422 Suwamoto et al. Mar 2002 A1
20020055975 Petrovykh May 2002 A1
20020065894 Dalal et al. May 2002 A1
20020076010 Sahai Jun 2002 A1
20020083127 Agrawal Jun 2002 A1
20020085701 Parsons et al. Jul 2002 A1
20020086672 McDowell et al. Jul 2002 A1
20020087630 Wu Jul 2002 A1
20020097856 Wullert, II Jul 2002 A1
20020112186 Ford et al. Aug 2002 A1
20020116336 Diacakis et al. Aug 2002 A1
20020116461 Diacakis et al. Aug 2002 A1
20020118816 Flockhart et al. Aug 2002 A1
20020120687 Diacakis et al. Aug 2002 A1
20020123923 Manganaris et al. Sep 2002 A1
20020181692 Flockhart et al. Dec 2002 A1
20020194002 Pertrushin Dec 2002 A1
20030014491 Horvitz et al. Jan 2003 A1
20030028621 Furlong et al. Feb 2003 A1
20030073440 Mukherjee et al. Apr 2003 A1
20030108186 Brown et al. Jun 2003 A1
20030123642 Alvarado et al. Jul 2003 A1
20030144900 Whitmer Jul 2003 A1
20030144959 Makita Jul 2003 A1
20030152212 Burok et al. Aug 2003 A1
20030174830 Boyer et al. Sep 2003 A1
20030177017 Boyer et al. Sep 2003 A1
20030177231 Flockhart et al. Sep 2003 A1
20030231757 Harkreader et al. Dec 2003 A1
20040008828 Coles et al. Jan 2004 A1
20040015496 Anonsen Jan 2004 A1
20040015506 Anonsen et al. Jan 2004 A1
20040054743 McPartlan et al. Mar 2004 A1
20040057569 Busey et al. Mar 2004 A1
20040103324 Band May 2004 A1
20040138944 Whitacre et al. Jul 2004 A1
20040162998 Tuomi et al. Aug 2004 A1
20040202309 Baggenstoss et al. Oct 2004 A1
20040203878 Thomson Oct 2004 A1
20040210475 Starnes et al. Oct 2004 A1
20040240659 Gagle et al. Dec 2004 A1
20040249650 Freedman et al. Dec 2004 A1
20040260706 Anonsen et al. Dec 2004 A1
20050021529 Hodson et al. Jan 2005 A1
20050027612 Walker et al. Feb 2005 A1
20050044375 Paatero et al. Feb 2005 A1
20050091071 Lee Apr 2005 A1
20050125432 Lin et al. Jun 2005 A1
20050125458 Sutherland et al. Jun 2005 A1
20050138064 Trappen et al. Jun 2005 A1
20050154708 Sun Jul 2005 A1
20050182784 Trappen et al. Aug 2005 A1
20050289446 Moncsko et al. Dec 2005 A1
20060004686 Molnar et al. Jan 2006 A1
20060007916 Jones et al. Jan 2006 A1
20060026049 Joseph et al. Feb 2006 A1
20060056598 Brandt et al. Mar 2006 A1
20060135058 Karabinis Jun 2006 A1
20060178994 Stolfo et al. Aug 2006 A1
20060242160 Kanchwalla et al. Oct 2006 A1
20060256957 Fain et al. Nov 2006 A1
20060271418 Hackbarth et al. Nov 2006 A1
20070038632 Engstrom Feb 2007 A1
20070064912 Kagan et al. Mar 2007 A1
20070083572 Bland et al. Apr 2007 A1
20070112953 Barnett May 2007 A1
20070127643 Keagy Jun 2007 A1
20070192414 Chen et al. Aug 2007 A1
20070201311 Olson Aug 2007 A1
20070201674 Annadata et al. Aug 2007 A1
20070230681 Boyer et al. Oct 2007 A1
20080056165 Petrovykh Mar 2008 A1
Foreign Referenced Citations (25)
Number Date Country
2143198 Jan 1995 CA
2174762 Jun 1995 CA
0 501 189 Sep 1992 EP
0 740 450 Oct 1996 EP
0770967 May 1997 EP
0772335 May 1997 EP
0855826 Jul 1998 EP
0 863 651 Sep 1998 EP
0829996 Sep 1998 EP
0866407 Sep 1998 EP
899673 Mar 1999 EP
998108 May 2000 EP
1035718 Sep 2000 EP
1091307 Apr 2001 EP
1150236 Oct 2001 EP
2 273 418 Jun 1994 GB
2 290 192 Dec 1995 GB
2001-053843 Feb 2001 JP
2006-054864 Feb 2006 JP
WO 9607141 Mar 1996 WO
WO 9728635 Aug 1997 WO
WO 9856207 Dec 1998 WO
WO 9917522 Apr 1999 WO
WO 0180094 Oct 2001 WO
WO 02099640 Dec 2002 WO