The field of the invention relates to communication systems and more particularly to automatic call distributors.
Automatic call distributors (ACDs) are known. Such systems are typically used by organizations to serve large numbers of callers. Typically, calls are directed to a common telephone number and distributed to agents based upon some criteria (e.g., agent idle time).
ACDs can typically process both inbound and outbound calls. Typically, a controller monitors a workload of its agents. Where a workload of received calls fall below some threshold value, the controller may begin to initiate outbound calls.
In addition to placing and distributing calls, an ACD may also identify and display documents on agent terminals as an aid to processing the calls. In the case of incoming calls, the calls may be received along with dialed number identification service (DNIS) and/or automatic number identification (ANI) information. ANI may be used to identify a caller at the same instant as the call is delivered to the ACD. The controller of the ACD may use the ANI information to retrieve and display customer records on a terminal of the agent selected to handle the call at the same instant that the call is delivered to the agent.
In addition, textual information may be displayed on a terminal of the agent that guides the agent through a sales presentation. DNIS information may be used to identify an intended call target and to select an appropriate sales presentation for use by the agent based upon the intended call target.
While automatic call distributors work relatively well, they are not particularly well suited to the Internet environment. Further, the processes that are used for handling switched circuit calls within the PSTN cannot be used within the Internet where processing elements may be widely separated. Because of the widely separated nature of Internet call processing, a need exits for a method of handling calls at agent workstations that is adaptable to the Internet environment.
A method and apparatus are provided for controlling a plurality of calls with respective clients on a terminal of an agent of an organization. The method includes the steps of setting up the plurality of contacts with the respective clients under an Internet protocol and simultaneously displaying a respective line softkey of each contact of the plurality of contacts on a terminal of the agent where the respective line softkey depicts a status of the contact.
In general, the system 10 may be used by any of a number of different enterprise organizations (e.g., commercial, environmental, political, etc.) to advance the agenda of the enterprise. In order to advance the agenda of the organization, the organization may publish (by advertising or otherwise) one or more universal resource locators (URLS) or universal resource indicators (URI) that allow clients 12, 14 to contact the organization through the internet. The URLs or URIs may be an e-mail address, an instant messaging (IM) address or an identify of a website 24 through which clients 12, 14 may download information.
As each contact arrives at (i.e., is established with) the website 24, a contact processor 28 may open a contact file to track a history of the contact. The contact processor 28 may retrieve a source URL or URI that identifies the client 12, 14 from the website access request. As the client 12, 14 browses the website 24, the contact processor 28 may add identifiers of any webpages visited to the contact file.
Included on some or all of the webpages provided by the website 24 may be a SPEAK WITH AGENT softkey. Activation of the SPEAK WITH AGENT softkey may cause the contact distributor to connect the contact with an agent 20, 22.
Alternatively, the organization may purchase lists of URLs or URIs that allow the organization to contact the clients 12, 14 directly. Direct contact in this case may mean sending e-mails to the client 12, 14, posting ads to the client 12, 14 or sending instant messages (IMs) to the client 12, 14 soliciting a response.
In the case of outgoing contacts, the contact processor 28 may open a file that includes a URL or URI of the client. The content of any message sent to the client 12, 14 may also be included within the file.
Contacts may be determined to be active when a response is received to an outgoing contact or a SPEAK WITH AGENT softkey is activated. In either case, the host 18 may assign the contact to an agent 20, 22.
In order to assign active contacts to agents 20, 22, the host 18 may transfer the contact file to an agent selection application 26. As a first step in selecting an agent 20, 22, the agent selection application 26 may determine a subject matter of the contact. Determination of the subject matter of the contact may be made based upon the content of the contact file.
Selection of an agent 20, 22 may be based upon a comparison of the content of the contact file with a skills list associated with each agent 20, 22. In this regard, when the content of the contact file substantially matches the skills list of one or more agents 20, 22, the contact may be assigned to one or simultaneously to all of the agents that meet the skills requirements of the contact.
Turning now to the agents 20, 22, each agent 20, 22 may be provided with a messaging application 30, 32, 34 for each message type (Internet protocol) that the agent 20, 22 will handle. A first application 30 may be provided for exchanging audible information with a client 12, 14 under a voice-over-Internet-protocol (VoIP) format. An OUTLOOK application 32 may be provided for processing e-mails and an IM application 34 may be provided for instant messaging.
As each contact is assigned to a selected agent 20, 22, the contact file may be sent to the agent 20, 22. The contact file may be stored in a contact list in memory of the terminal 20, 22.
A PROPOSED CONTACT window 106 may be provided that summarizes the contact to the agent 20, 22 based upon the information in the contact file before the agent 20, 22 accepts the contact. As shown, a name 108 of the client 12, 14, a subject matter 112 and a format 110 of the contact may appear to the agent 20, 22 in a respective window 106 before acceptance of the contact. The proposed contact window 106 may allow the agent 20, 22 to screen contacts for a desirable subject matter or to select a communication format 110 that the agent 20, 22 is most comfortable with at that instant of time.
When the agent 20, 22 accepts a contact by activating the ACCEPT CONTACT softkey 102, the information from the contact may be transferred by a connection processor 38 from the PROPOSED CONTACT window 106 to a PENDING CONTACT display and softkey combination (hereinafter a display/softkey or line softkey) 114. In addition to indicating acceptance by the agent 20, 22 of the contact, the PENDING CONTACT display/softkey may also be highlighted with an appropriate color (e.g., red, green, etc.) by the connection processor 38 to indicate an open channel status (active contact) with the client 12, 14. The highlighting of the PENDING CONTACT display/softkey 114 may alert the agent 20, 22 that any client information appearing in the interactive window 124 relates to the client 12, 14 identified within the name field (window) 116. The subject window 118 and format window 120 may also confirm the format of use within the interactive client information window 124 (e.g., IM, e-mail, etc.). In addition to highlighting the active PENDING CONTACT display 114, 122, the connection processor 38 may also cause the softkey 114, 122 to flash under control of a timer 40.
An open channel in this context means that any message sent by the agent 20, 22 may be communicated through the open channel to the client 12, 14. For example, if the channel is VoIP, then any words spoken by the agent 20, 22 during that time period will be heard by the client 12, 14.
Once a contact has been accepted, the agent 20, 22 may converse with the client 12, 14 under any appropriate format (e.g., VoIP, e-mail, IM, etc.). If the client 12, 14 is somewhat slow in responding to the agent's messages or the agent 20, 22 should find that he/she can handle more than one contact at a time, then the agent 20, 22 may activate the ACCEPT CONTACT softkey 102 (while the first contact is still in progress) to accept another contact. When the agent 20, 22 accepts another contact, the contact that formerly occupied the first PENDING CONTACT display/softkey 114 (now an inactive contact) may be moved down one position. It should be noted in this regard that any number of PENDING CONTACT display/softkeys 114, 122 may be provided limited only by the agent's abilityto handle multiple contacts. It may also be noted in this regard that the agent 20, 22 may switch back and forth between contacts (to make a formerly inactive contact active and visa versa) by manually activating a PENDING CONTACT display/softkeys 114, 122.
In order to control operation of the contacts, the connection processor 38 monitors the PENDING CONTACT softkeys 114, 122. When the connection processor 38 detects activation of a PENDING CONTACT softkey 114, 122 that is not the currently open channel, the connection processor 38 closes the previously open channel and opens the channel (i.e., activates the contact) that is associated with the softkey 114, 122 that has been most recently activated.
To help the agent 20, 22 in the case of multiple contacts, a flashing MESSAGE RECEIVED status display 121 may be provided. In this case, a message received processor 36 may monitor each pending (inactive) contact for activity. If a message is received or a voice is detected on an incoming voice channel the MESSAGE RECEIVED display 121 is activated to prompt the agent 20, 22 that this contact needs attention. A received message memory may save any spoken words until the PENDING CONTACT display/softkey 114, 122 is again activated, at which time the spoken words are repeated from memory or the text is displayed in the box 124. In this regard, the connection processor 38 within the agent terminal 20, 22 may monitor the respective PENDING CONTACT display/softkeys 114, 122 and switch the open connection among clients 12, 14 as directed by the agent.
In addition, the highlighting of the PENDING CONTACT display/softkey 114, 122 may be time and color coded based upon a relative priority of a call. The PENDING CONTACT display/softkey 114, 122 of the open channel may be time encoded by causing the highlighting to flash at a predetermined rate determined by the priority of the call. The PENDING CONTACT display/softkey 114, 122 may be color coded with a priority indicator.
In addition, the priority of the individual contacts may require service at certain minimum rates. For example, VoIP contacts may require frequent service (e.g., every five seconds) while IMs may require service less frequently (e.g., every ten seconds). E-mails may require service even less frequently (e.g., once every one-h hour).
A priority processor 42 may track activation of each contact to ensure that each contact is serviced in accordance with its relative priority level. When a contact has not been serviced within the required predetermined time period, the message light 121 may be activated to prompt the agent 20, 22.
A specific embodiment of method and apparatus for controlling a plurality of contacts with respective clients on a terminal of an agent of an organization has been described for the purpose of illustrating the manner in which the invention is made and used. It should be understood that the implementation of other variations and modifications of the invention and its various aspects will be apparent to one skilled in the art, and that the invention is not limited by the specific embodiments described. Therefore, it is contemplated to cover the present invention and any and all modifications, variations, or equivalents that fall within the true spirit and scope of the basic underlying principles disclosed and claimed herein.
Number | Name | Date | Kind |
---|---|---|---|
5014303 | Velius | May 1991 | A |
5555179 | Koyama et al. | Sep 1996 | A |
5765033 | Miloslavsky | Jun 1998 | A |
5784452 | Carney | Jul 1998 | A |
5832451 | Flake et al. | Nov 1998 | A |
5841854 | Schumacher et al. | Nov 1998 | A |
5926539 | Shtivelman | Jul 1999 | A |
5940496 | Gisby et al. | Aug 1999 | A |
5946387 | Miloslavsky | Aug 1999 | A |
5953332 | Miloslavsky | Sep 1999 | A |
5953405 | Miloslavsky | Sep 1999 | A |
5987115 | Petrunka et al. | Nov 1999 | A |
6002760 | Gisby | Dec 1999 | A |
6021428 | Miloslavsky | Feb 2000 | A |
6044145 | Kelly et al. | Mar 2000 | A |
6044368 | Powers | Mar 2000 | A |
6067357 | Kishinsky et al. | May 2000 | A |
6108711 | Beck et al. | Aug 2000 | A |
6138139 | Beck et al. | Oct 2000 | A |
6167395 | Beck et al. | Dec 2000 | A |
6170011 | Macleod Beck et al. | Jan 2001 | B1 |
6175563 | Miloslavsky | Jan 2001 | B1 |
6175564 | Miloslavsky et al. | Jan 2001 | B1 |
6185292 | Miloslavsky | Feb 2001 | B1 |
6345305 | Beck et al. | Feb 2002 | B1 |
6373836 | Deryugin et al. | Apr 2002 | B1 |
6389007 | Shenkman et al. | May 2002 | B1 |
6393015 | Shtivelman | May 2002 | B1 |
6408064 | Fedorov et al. | Jun 2002 | B1 |
6574331 | Forsythe et al. | Jun 2003 | B1 |
6704404 | Burnett | Mar 2004 | B1 |
6732156 | Miloslavsky | May 2004 | B2 |
7000019 | Low et al. | Feb 2006 | B2 |
7085367 | Lang | Aug 2006 | B1 |
20030174831 | Dezonno et al. | Sep 2003 | A1 |
20040054743 | McPartlan et al. | Mar 2004 | A1 |
20040057570 | Power et al. | Mar 2004 | A1 |
20050238162 | Dezonno | Oct 2005 | A1 |
20060023866 | Dezonno | Feb 2006 | A1 |
Number | Date | Country | |
---|---|---|---|
20060115073 A1 | Jun 2006 | US |