The present invention is directed generally to telephony systems and specifically to managing contact queues.
Contact centers 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. Contact centers distribute contacts, whether inbound or outbound, for servicing to any suitable resource according to predefined criteria. In many existing systems, the criteria for servicing the contact from the moment that the contact center becomes aware of the contact until the contact is connected to an agent are customer-specifiable (i.e., programmable by the operator of the contact center), via a capability called vectoring. Normally in present-day Automatic Call Distribution (ACD) systems when the ACD system's controller detects that an agent has become available to handle a contact, the controller identifies all predefined contact-handling queues for 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 queue. 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.
When the contact is in the form of a call, often enqueued callers are placed on hold and ACD resources are used to play announcements or other audio programs (e.g., songs, commercials, etc.) to the callers while the caller waits. The audio programs are commonly referred to as “music-on-hold.” These types of wait treatments are limited in that the callers' in-queue experience is limited and the potential for the caller becoming bored and hanging up increases as the caller continues to wait.
During high contact center volume times there is an increase in the number of lost contacts due to extensive wait times. This is because the contactor tends to get bored with the generic “music-on-hold” types of wait treatments. There is a potential to turn this wait time into a productive time for both the customer and the contact center. For example, in U.S. Pat. No. 6,820,260 to Flockhart et al., the entire contents of which are hereby incorporated herein by this reference, a customized applet is provided that can be downloaded by a customer's communication device or terminal. The applet can be customized based on known customer information and customer location. When a contact is put on hold an applet is provided to the customer for execution by the customer's terminal. When the terminal's communication is taken off hold (e.g., when an agent becomes available), the execution of the applet stops and the agent begins servicing the contact.
Although some solutions have been provided to customize wait treatments for customers on hold, many of these solutions abruptly take the customer out of waiting when an agent is available. This action is based on the assumption that the customer wants to be on hold for the smallest amount of time possible. However, the abrupt interruption of a customer during wait treatment may give some customers the perception that they are being passed between an agent and hold in a haphazard manner. If the wait treatment corresponded to some type of advertisement or even survey it would be imprudent to interrupt the customer during such a wait treatment. However, since it is assumed that the customer does not want to be on hold, the customer is typically not allowed to finish a portion of the wait treatment which may result in the customer becoming annoyed or the contact center foregoing valuable customer feedback.
These and other needs are addressed by various embodiments and configurations of the present invention. The present invention is directed generally to a contact management during wait treatment. More specifically, a graceful transfer out of active wait treatment is provided herein.
In accordance with one embodiment of the present invention, a method of handling one or more contacts in a contact queue is provided. The method generally comprises the steps of:
(a) receiving a contact in a contact queue;
(b) assigning an agent to the contact;
(c) after assigning the agent to the contact one of:
(d) after waiting, connecting the agent to the contact.
As can be appreciated by one skilled in the art, a “contact” is understood herein to include voice calls, chats, video calls, and combinations thereof. Embodiments of the present invention are particularly well suited for use with any type of known real-time or interactive contacts such as those listed above.
While a contact is in a contact queue often a contact will be provided with some sort of wait treatment. One embodiment of the present invention is to create and automatically provide the customer with a meaningful wait treatment that gives the customer a sense of appreciation and usefulness even though they are on hold. Wait treatments may be chosen for a particular contact depending upon the type of contact and/or a state of the queue. The wait treatment may be provided in accordance with the automated service logic.
The wait treatment, in accordance with embodiments of the present invention, includes one or more predetermined exit points that help increase the enjoyment of interacting with the wait treatment. Since the contact is not connected to an available agent until the assigned wait treatment has reached one of the exit points, the agent does not interrupt the wait treatment. Interrupting a wait treatment may seem somewhat rude, especially when useful information is being provided to and/or received from the customer. In these situations an abrupt transition from a wait treatment to connection with a contact center agent can be avoided by waiting until a graceful transfer time indicated by the exit point.
The use of exit points for contacts in a contact center can also be advantageous to agents of the contact center. In one embodiment, while an agent is assigned to a contact but before the agent is connected to the contact (i.e., the agent is waiting for the wait treatment to reach an exit point), the agent may be provided with information pertinent to the customer of the assigned contact. The agent can review the customer information while the customer is finishing up with the wait treatment. In other embodiments, the assigned agent can begin servicing the contact prior to being connected to the contact. Thus when the customer is finally connected with the agent, the agent will have more knowledge about the customer and will be able to provide the customer with more personalized and efficient customer service.
A contact may be received in a contact queue from a number of different locations. Often times contacts are initially received in a contact center or similar contact receiving architecture where they are initially placed in a contact queue until an agent becomes available to service the contact. In other examples, a servicing agent can transfer the contact to a different agent, which may also place the contact in a contact queue until the different agent becomes available. When an agent is transferring the contact to another agent, the contact can be considered resident in a queue during the interim. In still other embodiments, an agent may place a contact on hold. During such a wait time, the customer associated with the contact may be provided with a wait treatment in accordance with embodiments of the present invention. When the agent is ready to take the contact back off of hold, the agent may have to wait until the wait treatment reaches a predetermined time typically corresponding to a predefined exit point in the wait treatment.
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.
The invention will be illustrated below in conjunction with an exemplary communication system. Although well suited for use with, e.g., a system using server(s), the invention is not limited to use with any particular type of communication system 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 a graceful transfer out of active wait treatment.
The term “switch” or “server” as used herein should be understood to include a PBX, an ACD, an enterprise switch, or other type of communications system switch or server, as well as other types of processor-based communication control devices such as media servers, computers, adjuncts, etc.
Referring to
The switch 130 and/or server 110 can be any architecture for directing contacts to one or more communication devices. In some embodiments, the switch 130 may perform load-balancing functions by allocating incoming or outgoing contacts among a plurality of logically and/or geographically distinct contact centers. 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™ 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 communication devices. Other types of known switches and servers are well known in the art and therefore not described in detail herein.
As can be seen in
Referring to
The first communication 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, packet-based traditional computer telephony adjuncts, and any other communication device.
The second communication devices 138-1, . . . 138-M are circuit-switched. Each of the communication 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 communication device endpoints serviced by the switch/server, and the switch/server can direct incoming calls to and receive outgoing calls from these extensions in a conventional manner. The second communication devices 138 can include, for example, wired and wireless telephones, PDAs, H.320 videophones and conferencing units, voice messaging and response units, traditional computer telephony adjuncts, and any other communication device.
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 communication devices, i.e., the invention may be implemented with any desired type of transport medium as well as combinations of different types of transport channels.
The packet-switched network 162 can be any data and/or distributed processing network, such as the Internet. The network 162 typically includes proxies (not shown), registrars (not shown), and routers (not shown) for managing packet flows.
The packet-switched network 162 is in communication with an external first communication device 174 via a gateway 178, and the circuit-switched network 154 with an external second communication device 180. These communication devices are referred to as “external” in that they are not directly supported as communication device endpoints by the switch or server. The communication devices 174 and 180 are an example of devices more generally referred to herein as “external endpoints.”
In a preferred configuration, the server 110, network 162, and first communication 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 communication devices, and other elements as shown in
As will be appreciated, the central server 110 is notified via LAN 142 of an incoming contact by the communications 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 communications 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 communication device 134, 138 associated with a selected agent. The server 110 distributes and connects these contacts to communication devices of available agents based on the predetermined criteria noted above. When the central server 110 forwards a voice contact to an agent, the central server 110 also forwards customer-related information from databases 114 to the agent's computer work station for previewing and/or viewing (such as by a pop-up display) to permit the agent to better serve the customer. The agents process the contacts sent to them by the central server 110.
Reverting back to
The wait treatment data store 236 may be implemented as a portion of memory containing one or a number of various wait treatments. The memory may be volatile and/or non-volatile memory depending upon the types of wait treatments employed.
When an agent becomes available in an agent queue that is capable of servicing a contact on hold, the agent and contact selector 220 assigns the agent to the contact. Although the agent and contact selector 220 assigns the agent to the contact, the wait treatment agent 232 controls the connection of the agent to the corresponding contact. If the wait treatment agent 232 determines that it is okay to connect the agent with the contact (e.g., because the wait treatment has reached a predefined exit point), then the wait treatment agent 232 connects the agent to the contact. However, if the wait treatment agent 232 determines that it is not okay to connect the agent to the contact, then the agent assigned to the contact may be provided with customer data either from the agent and contact selector 220 or the wait treatment agent 232. The agent and contact selector 220 generally provides the assigned agent with data relating to past interactions with a customer as well as other known customer information whereas the wait treatment agent 232 provides the assigned agent with data received from the customer while they are interacting with the current wait treatment.
The types of wait treatments employed in accordance with embodiments of the present invention may be any suitable wait treatment that can be either presented to a customer from the server 110 or sent to the customer's communication device 174, 180 and executed thereon. The wait treatments may either be one-way communications from the contact center to the customer or interactive communications that can collect feedback from the customer. The wait treatment may be any presentation of information (e.g., music, entertainment, education, product and/or service information, advertising, survey, etc.) to the customer associated with the contact. In one embodiment, the communication device 174, 180 and/or a user of the device may be identified (e.g., through an email address, a customer number, an IP address, a phone number, etc.), and the wait treatment can be customized for use by the customer and/or the customer's communication device 174, 180. One example of customization of a wait treatment may include the variation of product offerings based upon a customer's type. That is a platinum level customer may be provided with a wait treatment that discusses high-end technologies for large businesses whereas a gold level customer may be provided with a wait treatment that discusses small business technologies.
Referring now to
In one embodiment, the data structure 300 includes a treatment number field 304 or a similar type of wait treatment identifier field. The treatment number field 304 includes an identifier for a given wait treatment. A unique number, name, or similar type of identification mechanism can be used to identify wait treatments in the treatment number field 304.
The data structure 300 may also include a length field 308 that identifies the length of a particular wait treatment. Some wait treatments may be designed for short wait times and thus may not be interactive. Other wait treatments may be designed for longer estimated wait times and those wait treatments may be interactive since an interactive wait treatment may have a better chance of keeping a customer satisfied even though they are on hold. Of course, all longer wait treatments are not necessarily interactive and some short wait treatments may be interactive.
The data structure 300 may further include an exit point identifier field 312. The exit point identifier field 312 may store information relating to the location of a particular exit point in a wait treatment. In some embodiments, a wait treatment will have an exit point at the end of the wait treatment. Thus the length of the wait treatment may correspond to at least one of the exit point's locations within the wait treatment. Many wait treatments further comprise exit points within the body of the wait treatment. In other words, exit points are interspersed within the wait treatment. For example, the second wait treatment depicted in
Another field included in the data structure 300 may include a contact type field 316. The contact type field 316 can be referenced by the wait treatment agent 232 to determine what wait treatment should be assigned to a particular contact. For example, the first wait treatment depicted is suitable for transmission to any one of a phone, chat, and video contact. Thus the first wait treatment may optionally include images or web URLs that can be presented to a customer via a web page or through video. The first wait treatment may also be perceivable through audio only and thus can be provided to a phone contact. Other wait treatments may only be suitable for one or a couple types of contacts and therefore the wait treatment agent 232 can reference the contact type field 316 prior to assigning a wait treatment to a contact.
The data structure 300 may also include a customer type field 320. The customer type field 320 may identify the types of customers a particular wait treatment is suitable for. As an example, the third wait treatment may include introductory questions designated for new customers such as, “how did you hear about us” and “what is your name.” On the other hand, the fourth wait treatment may be very specific to a particular product that only platinum customers have or may have an interest in. Accordingly, the fourth wait treatment may be designated for only platinum customers in the customer type field 320.
Referring now to
In step 416, it is determined if the estimated wait time is substantially long (e.g., warrants placing the contact in a queue and providing the contact with a wait treatment). If the estimated wait time is substantially small (e.g., a few seconds) or an agent is already available, then the contact may be placed in a queue without being assigned a wait treatment or the contact is connected with the available agent (step 444). However, if the wait time is significant enough to justify providing the customer of the contact with a wait treatment, then the method continues and the wait treatment agent assigns the contact a wait treatment (step 420). The assigned wait treatment may be selected from a set of available wait treatments based upon the estimated wait time, customer data, and context of the wait treatment as well as other properties of the contact. The assigned wait time may also be selected based upon specific questions raised by the contact. For example, if the contact is related to help questions for a particular computer, then a wait treatment may be chosen that provides an introduction to troubleshooting such a computer.
Also, as a part of the assignment step, the selected wait treatment is provided to the customer associated with the contact via the customer's communication device 174, 180. As noted above, a wait treatment may also be assigned to a contact on hold that is not necessarily on hold but is still waiting for an agent to become available again.
While the contact is waiting, either on hold or in a queue, and is being provided with a wait treatment, the contact is considered to be in WAIT mode (step 424). The contact remains in WAIT mode at least until it is determined that an agent has become available (step 428). If it is determined that an agent is available to service the contact, then the available agent is assigned to the contact (step 432). In embodiments where the contact was on hold, the assignment of the agent to the contact may not. When the agent becomes assigned to a particular contact, the assigned agent is provided with customer information via a user interface on their communication device 134, 138 (step 436). The information provided to the assigned agent may include customer data that was retrieved from the database 114 and other data relating to previous contacts initiated by the same customer. The customer information provided to the agent may also include any information gleaned from the customer by the wait treatment. For example, if the wait treatment corresponded to a customer survey, then the assigned agent may be provided with the customer's answers to the survey questions. This allows the agent to become more familiar with the customer prior to the initiation of service of the contact.
At step 440, the wait treatment agent 232 determines if the assigned wait treatment has reached an exit point. In other words, the wait treatment agent 232 determines if it is a good time to transition the contact from the contact queue 208 where a wait treatment is being provided to the assigned agent. The wait treatment agent 232 may reference a timer associated with the wait treatment and compare the value on the timer to exit point locations in the exit point identifier field 312. Alternatively, the wait treatment may send out a signal or similar type of exit point identifier when an exit point is reached. The wait treatment agent 232 can realize that the wait treatment has reached an exit point when such a signal is received.
If the customer is in middle of a wait treatment and the position of the wait treatment does not correspond to an exit point, then the agent stays in an assigned but waiting state. During this state, the agent may be provided with more customer information that has been gleaned from the wait treatment or from other sources. By providing the contact center agent with further information relating to the customer, the agent can make efficient use of the time while waiting for the contact to reach an exit point in the wait treatment. It may be true that requiring an agent to wait for a contact could decrease contact center performance. However, if the contact center agent is making use of the waiting time by reviewing the customer's information, then the agent may be capable of servicing the contact in a more efficient manner once the agent and contact are connected. In some embodiments, part of the customer information may include preliminary or general questions that the customer has and during the wait time an assigned agent may begin finding answers to the contact questions and may also begin servicing the contact without actually being connected to the contact.
Once the contact reaches an exit point in the wait treatment the agent is connected to the contact (step 444). The connection of an agent to a contact may include establishing a communication link between the agent communication device 134, 138 and the customer communication device 174, 180. The link may be made via the server 110 and/or the switch 130 depending upon the functionality of the customer and agent's communication devices. During the connecting step, the wait treatment may be removed from the customer's communication device 174, 180 if the wait treatment was being executed thereon. In accordance with one embodiment, the wait treatment may be provided to the contact while the agent is connected to the contact. This may allow the agent to ask the customer if he/she is interested in a product or service associated with the wait treatment while the customer is receiving the wait treatment.
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.
Number | Name | Date | Kind |
---|---|---|---|
4163124 | Jolissaint | Jul 1979 | 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 |
5164983 | Brown et al. | Nov 1992 | 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 |
5291550 | Levy et al. | Mar 1994 | A |
5299260 | Shaio | Mar 1994 | A |
5309513 | Rose | May 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 |
5469503 | Butensky et al. | Nov 1995 | A |
5469504 | Blaha | Nov 1995 | A |
5473773 | Aman et al. | Dec 1995 | A |
5479497 | Kovarik | Dec 1995 | A |
5500795 | Powers et al. | Mar 1996 | A |
5504894 | Ferguson et al. | Apr 1996 | A |
5506898 | Constantini 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 |
5592378 | Cameron et al. | Jan 1997 | A |
5592542 | Honda et al. | Jan 1997 | A |
5594726 | Thompson et al. | Jan 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 |
5724092 | Davidsohn et al. | Mar 1998 | A |
5740238 | Flockhart et al. | Apr 1998 | A |
5742675 | Kilander et al. | 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 |
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 |
5818907 | Maloney et al. | Oct 1998 | A |
5825869 | Brooks et al. | Oct 1998 | A |
5828747 | Fisher et al. | Oct 1998 | A |
5838968 | Culbert | Nov 1998 | A |
5839117 | Cameron et al. | Nov 1998 | 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 |
5915012 | Miloslavsky | Jun 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 | Pandilt | 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 |
6038293 | Mcnerney 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 |
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 |
6115462 | Servi et al. | Sep 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 |
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 |
6240471 | Schlueter et al. | May 2001 | B1 |
6256773 | Bowman-Amuah | Jul 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 |
6353810 | Pertrushin | Mar 2002 | B1 |
6356632 | Foster et al. | Mar 2002 | B1 |
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 |
6424709 | Doyle et al. | Jul 2002 | B1 |
6425125 | Fries et al. | Jul 2002 | B1 |
6426950 | Mistry | Jul 2002 | B1 |
6427137 | Pertrushin | Jul 2002 | B2 |
6430282 | Bannister et al. | Aug 2002 | B1 |
6434230 | Gabriel | Aug 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 |
6496977 | Hamilton et al. | Dec 2002 | B1 |
6523166 | Mishra et al. | Feb 2003 | B1 |
6535600 | Fisher et al. | Mar 2003 | B1 |
6535601 | Flockhart et al. | Mar 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 |
6597685 | Miloslavsky et al. | Jul 2003 | B2 |
6614903 | Flockhart et al. | Sep 2003 | B1 |
6650748 | Edwards et al. | Nov 2003 | B1 |
6675204 | De Boor et al. | Jan 2004 | B2 |
6697457 | Petrushin | Feb 2004 | B2 |
6704409 | Dilip et al. | Mar 2004 | B1 |
6707903 | Burok et al. | Mar 2004 | B2 |
6754333 | Flockhart et al. | Jun 2004 | B1 |
6766013 | Flockhart et al. | Jul 2004 | B2 |
6766014 | Flockhart et al. | Jul 2004 | B2 |
6820260 | Flockhart et al. | Nov 2004 | B1 |
6947543 | Alvarado et al. | Sep 2005 | B2 |
7035927 | Flockhart et al. | Apr 2006 | B2 |
7170991 | Shaffer et al. | Jan 2007 | B2 |
20020194002 | Pertrushin | Dec 2002 | A1 |
20030174830 | Boyer et al. | Sep 2003 | A1 |
20030177017 | Boyer et al. | Sep 2003 | A1 |
20040203878 | Thomson | Oct 2004 | A1 |
20060239442 | Shaffer et al. | Oct 2006 | A1 |
20070291922 | Matteo et al. | Dec 2007 | A1 |
20080037723 | Milstein et al. | Feb 2008 | A1 |
Number | Date | Country |
---|---|---|
2143198 | Jan 1995 | CA |
2174762 | Mar 1996 | CA |
0501189 | Sep 1992 | EP |
0740450 | Oct 1996 | EP |
0772335 | May 1997 | EP |
0829996 | Mar 1998 | EP |
0855826 | Jul 1998 | EP |
0863651 | Sep 1998 | EP |
0866407 | Sep 1998 | EP |
899673 | Mar 1999 | EP |
998108 | May 2000 | EP |
1091307 | Apr 2001 | EP |
1150236 | Oct 2001 | EP |
2273418 | Jun 1994 | GB |
2290192 | Dec 1995 | GB |
WO 9607141 | Mar 1996 | WO |
WO 9728635 | Aug 1997 | WO |
WO 9856207 | Dec 1998 | WO |