A system and method of changing entity configuration information in a call center is disclosed. By automatically monitoring entities in a call center, selecting an entity in the call center, and modifying configuration information of the selected entity, keeping track of entities in a call center is automated. Agents and consoles are examples of entities monitored in the call center. When agents or consoles change physical location, the electronic floor plan is automatically updated to reflect the new physical location information for the agents and consoles. Further, a supervisor of a call center can change entity configuration information by selecting an entity on the electronic floor plan.
|
22. A system of changing entity configuration in a call center, such system comprising:
means for monitoring a database of the call center for log ons and log offs by entities of the call center to identify consoles being used by entities of the call center, said identified consoles being used by the means for monitoring to determine physical location information of entities of the call center based upon the log ons and log offs of the entities with respect to the call center to provide an electronic floor plan;
means for producing defined versions of the electronic floor plan containing pictorial images of the entities on a supervisor workstation;
means for updating the electronic floor plan to provide and reflect the changes in physical location information of the entities based upon the log ons and log offs of the entities
means on the supervisors workstation for selecting a pictorial image of an entity of the entities; and
means for displaying entity configuration information of the selected entity on the supervisors workstation in response to selection of the entity.
43. A system of changing entity configuration in a communication system, such system comprising:
an entity monitor which monitors a database of the communication system for log ons and log offs by entities of the call center to identify consoles being used by the entities, said identified consoles being used by the entity monitor to determine physical location information based upon the log ons and log offs of the entities with respect to the communication system to provide an electronic floor plan that contains pictorial images of the entities;
a supervisors workstation that displays the electronic floor plan; and
an informer within the supervisors workstation that automatically updates the electronic floor plan displayed on the supervisors workstation to provide and reflect changes in physical location information of the entities based upon the log ons and log offs of the entities;
a selection device for selecting a pictorial image of an entity of the entities displayed on the electronic floor plan; and
an entity configuration information table that is displayed on the supervisors workstation in response to selection of the pictorial image of the entity.
1. A method of changing entity configuration information in a call center comprising the steps of:
monitoring a database of the call center by an application within a supervisors workstation for log ons and log offs by entities of the call center to identify consoles being used by the entities;
detecting log ons and log offs of the entities with respect to the call center by the application;
modifying configuration information of the entities within a lookup table by the application based upon the detected log ons and log offs of the entities;
monitoring physical location information of entities within the lookup table by an event handler within the supervisors workstation based upon the configuration information within the lookup table to provide an electronic floor plan;
displaying the electronic floor plan containing pictorial images of the entities by the event handler on the workstation of the supervisor;
automatically updating the electronic floor plan by the event handler to provide and reflect a change in physical location information of the entities based upon the automatic monitoring of the log ons and log offs of the entities;
the supervisor selecting a pictorial image of an entity of the entities displayed on the electronic floor plan; and
displaying entity configuration information of the selected entity on the supervisors workstation in response to the selection.
2. The method of changing entity configuration information as in
3. The method of changing entity configuration information as in
4. The method of changing entity configuration information as in
5. The method of changing entity configuration information as in
6. The method of changing entity configuration information as in
7. The method of changing entity configuration information as in
recording physical location information; and
retrieving the recorded physical location information.
8. The method of changing entity configuration information as in
9. The method of changing entity configuration information as in
10. The method of changing entity configuration information as in
retrieving the recorded physical location information;
translating the recorded physical location information to graphical form; and
drawing the graphical form on the electronic floor plan.
11. The method of changing entity configuration information as in
12. The method of changing entity configuration information as in
13. The method of changing entity configuration information as in
14. The method of changing entity configuration information as in
15. The method of changing entity configuration information as in
16. The method of changing entity configuration information as in
17. The method of changing entity configuration information as in
18. The method of changing entity configuration information as in
19. The method of changing entity configuration information as in
20. The method of changing entity configuration information as in
21. The method of changing entity configuration information as in
23. The system of changing entity configuration as in
24. The system of changing entity configuration as in
25. The system of changing entity configuration as in
26. The system of changing entity configuration as in
27. The system of changing entity configuration as in
28. The system of changing entity configuration as in
29. The system of changing entity configuration as in
30. The system of changing entity configuration as in
means for reading the recorded physical location information;
means for translating the recorded physical location information to graphical form; and means for drawing the graphical form on the electronic floor plan.
31. The system of changing entity configuration as in
32. The system of changing entity configuration as in
33. The system of changing entity configuration as in
34. The system of changing entity configuration as in
35. The system of changing entity configuration as in
36. The system of changing entity configuration as in
37. The system of changing entity configuration as in
38. The system of changing entity configuration as in
39. The system of changing entity configuration as, in
40. The system of changing entity configuration as in
41. The system of changing entity configuration as in
42. The system of changing entity configuration as in
44. The system of changing entity configuration as in
45. The system of changing entity configuration as in
46. The system of changing entity configuration as in
47. The system of changing entity configuration as in
48. The system of changing entity configuration as in
49. The system of changing entity configuration as in
a recorder for storing physical location information; and
a retriever for getting the stored physical location information.
50. The system of changing entity configuration as in
a reader which retrieves the recorded physical location information;
a translator for relating the recorded physical location information to graphical form; and
a drawer which places the graphical form on the electronic floor plan.
51. The system of changing entity configuration as in
|
This invention relates to communications systems and, more particularly, to call centers.
Communications systems with call centers are known. Such systems are typically used as a means of distributing telephone calls among a group of call center agents of an organization. As calls are directed to the organization from the public switch telephone network (PSTN), the communications system directs the calls to its call center agents based upon some algorithm. For example, a communications system such as an automatic call distributor (ACD), a public branch exchange (PBX), or a central office exchange service (centrex) may recognize a call target based upon an identity of an incoming trunk line and route the call accordingly.
In call centers where many calls are received and handled by many call center agents, the call center may contain a large number of agents. Agents are responsible for servicing customers. Call center agents may provide product support, take sales orders, and handle inquires. In essence, the call center agents provide the wide array of services that the companies that use them require. Thus, the effectiveness and efficiency of a call center depends on the call center agents. Call center supervisors manage call center agents, including scheduling their tasks and duties, and are responsible for monitoring their whereabouts.
To manage the call center efficiently, it is important for a call center supervisor to have ready access to the location of the call center agents. Currently, monitoring of the call center is performed manually by a paper or electronic floor plan image of the call center depicting the consoles that the agents sit at. To monitor the whereabouts of agents, tags representing agents are placed on the floor plan in the console position occupied by the agent.
Such manual solutions may be inaccurate and may misrepresent an agent's physical location. For example, many call centers operate in hotdesking mode where agents sit at different seats according to availability and preference on a shift by shift basis. Thus, the floor plan may not represent the current agent and console locations. When an agent moves from one console to another, the call center supervisor must make note of the change by moving the tag representing the agent either on the paper or electronic floor plan. This requires the supervisor to constantly update the floor plan. If the supervisor looses track of agent positions, then some consoles identified as occupied may be mismarked. By not adequately tracking agents or consoles, the call center becomes underutilized and inefficient. Also, by being unaware of agents' whereabouts, the call center supervisor is unable to estimate the call center's capability.
Further, even if the supervisor where to maintain an accurate floor plan, the supervisor is not able to reassign agents and make other configuration changes from the supervisor's desk. The supervisor must physically walk over to an agent's console and re-assign or re-configure the agent's console. Having the supervisor walk to each agent's console and perform the necessary changes is time consuming and inefficient.
The existing method of monitoring physical locations of call center agents and consoles of communications systems requires the supervisor to manually track agents and consoles. As a consequence, many agents may be undetected or many unused consoles may be unused, and thereby, the quality of service provided by the call center may degrade. Further, the supervisor must physically walk to each and every console to perform the necessary changes to console configuration so that the call center is optimally performing. Accordingly, a need exists for a better way of changing agent and console information while automatically monitoring and displaying such information in a call center.
The present invention, accordingly, provides a system and method of changing entity configuration information that overcomes or reduces the disadvantageous and limitations associated with prior agent monitoring methods and systems. Illustrated embodiments reduce the disadvantage of manually tracking agents and consoles in a call center by automatically monitoring entities in a call center, selecting an entity in the call center, and modifying configuration information of the selected entity. An electronic floor plan that depicts the locations of the entities, displays the entity configuration information and is automatically updated when changes occur is disclosed. In an exemplary embodiment, call center supervisors are able to view accurate physical location information for call center agents and consoles on a two-dimensional or three-dimensional electronic floor plan. Further, the call center supervisors are able to change entity configuration information by selecting an entity from the electronic floor plan.
The foregoing advantageous features of the invention will be explained in greater detail and others will be made apparent from the detailed description of the preferred embodiment of the present invention which is given with reference to the several figures of the drawing, in which:
Shown in
Further, although the present invention is described in reference to the PSTN 10, a packet-switched voice network or other equivalent network where voice calls are relayed to a call center may be used. For example, where voice calls are transmitted over a global network, such as the Internet using Internet Protocol (IP) a packet-switched communications network may be used to implement the system of transmitting the call.
In addition to the agent telephone (3, 6, or 11), the agent has a computer workstation consisting of a terminal and an input device, such as a keyboard or mouse. The agent telephone (3, 6, or 11), terminal and input device are collectively termed a “console.” A console is one type of physical entity in a call center. The term entity is used to refer to physical objects in a call center. For example, it may refer to an agent, console, supervisor, printer, or facsimile. In the illustrated embodiment, the term entity refers to a call center agent or a call center console; however, other physical objects may be monitored and displayed as described by the present invention.
In addition to the agent telephones (3, 6, 11), the ACD 9 also interfaces with a server computer 8. The server 8 functions to provide agent workstations (2, 5, 12) and supervisor workstation 14 with information from the ACD 9 and a database 7. For example, as calls are received from the PSTN 10, call associated information (e.g., ANI, DNIS, etc.) may be delivered to the agent along with the call. The database 7 maintains performance statistics, customer information, and dial lists of the ACD 9 system. Server computer 8 may relay statistics and performance information maintained in database 7 to the supervisor workstation 14.
In accordance with an embodiment of the present invention, a method for changing entity configuration information in a call center comprising the steps of:
In an exemplary embodiment, entity configuration information includes data such as staff ID, class of service, agent group, directory number, supervisor staff ID, schedule adherence threshold group, secondary agent group, agent information group, message queue, major class, and name. For example, agent Bob having a staff ID of 1111 sitting at console 1234 would have the following related configuration information.
Configuration Name
Description
Value
staff ID
Sign-in Number associated with a Person
1111
class of service
AGENT, SUPV, MASTER, MAINT,
AGENT
VRU, VMAIL, FAX, PHONE, or TRUNK
agent group
Sales, Service, Management, etc.
Widget Sales Telephone Lines, 1–200
directory number
Staff member's phone extension
5455
supervisor staff ID
Supervisor for Staff
Carol Smith
schedule adherence
Associates Staff with certain thresholds
1
threshold group
secondary agent group
Sales, Service, Management, etc.
Gizmo Sales Telephone Lines, 1–220
agent information group
Collection of organized agents, LINRs, or VRUs
message queue
ACD mail message queue to which agent is assigned
0
major class
Type of staff, e.g. AGENT, SUPV, MASTER,
AGENT
and MAINT
name
Name of staff
Bob Jones
console
Number of physical console unit
1234
The step of automatically monitoring entities functions to provide an updated electronic floor plan of the call center to the supervisor of the call center. The step further comprises the steps of: (a) monitoring physical location information of entities to provide an electronic floor plan (see block 22 of
The step of monitoring physical location information of entities functions to provide an automatic trigger for changes in the physical location information. Monitoring means detecting physical location information for each entity in the system and noting changes when an entity moves. The step of updating an electronic floor plan means providing a call center supervisor with current entity configuration information regarding the entity within call center. Updating an electronic floor plan requires retrieving the recorded physical location information, translating the recorded physical location information into graphical form, and drawing the graphical form on an electronic floor plan.
In one embodiment the physical location information is stored in the database 7 without meaning. The application that uses the physical location information dictates the meaning of the coordinates. For example, in a VRML representation of the call center, the physical location information is represented in Cartesian x, y, z coordinates. A call center console projected onto a 2-dimensional device in the direction of the positive z axis has a positive x axis to the right and a positive y axis up.
Referring now to
Further, an event handler routine is initiated to execute whenever agent physical location information is changed (see block 36). The event handler runs in the background on the supervisor workstation 14 and is triggered by a change in x, y, z physical location information. If a change does occur, then the event handler executes software to update the electronic floor plan (see blocks 38–42).
When a new entity or an existing entity is modified (see block 44), the new x, y, z physical location information is updated in the server computer 8 (see block 46). For example, when an agent moves from console 51 to console 52, the agent logs off console 51 and logs on to console 52. Thus, the agent's physical location has changed from (0, 3, 4) to (1, 3, 4). In one embodiment, the new physical location information (1, 3, 4) is stored in the server computer 8. Then, the new x, y, z physical location information is copied to the database 7 (see block 48). In the above example, the new physical location information for the agent sitting at console 52 is (1, 3, 4) and is stored in the database 7.
In one embodiment, an application running on the supervisor workstation 14 may have a look-up table that keeps track of relationships between agents and consoles. In such an embodiment, the application running on the supervisor workstation would copy the physical location information from the server computer 8 or from the database 7 and maintain a look-up table of agents and consoles.
After the change is made in the database, Entity RTEvent Handler is triggered (see block 50) to perform an update of the electronic floor plan (blocks 38–42). Triggering or raising RTEvent for the new physical location information (see block 50) requires sending a signal to inform RTEvent that a change has occurred. When RTEvent receives the signal, it takes specified actions, namely updating the electronic floor plan (see blocks 38–42).
In an alternative embodiment, the new physical location information is compared with the physical location information in the database 7 before RTEvent Handler was triggered. If the two are the same, then RTEvent Handler is not triggered. For example, the supervisor may delete an agent from the system and then immediately add the same agent to the same console. In such a situation, there is no need to redraw the electronic floor plan to reflect the change.
Updating of the electronic floor plan is performed by reading the recorded physical location information, translating the recorded physical location information to graphical form, and drawing the graphical form on the electronic floor plan. Reading the recorded physical location information occurs when RTEvent is triggered (see block 36). Translating the recorded physical location information occurs by first verifying that the information contains x, y, z Cartesian coordinates (see block 38). If it does not, then the entity is placed in a list of entities with no location and displayed on the electronic floor plan as not having a location (see block 40). If the information contains x, y, z information, then the electronic floor plan is drawn to reflect this change (see block 42). In an exemplary embodiment, a symbol representing an agent is placed at the console position that the agent is sitting at. For example, in
Under an illustrated embodiment, the electronic floor plan may be drawn in a two-dimensional projection of the call center. Referring now to
Under another illustrated embodiment, the electronic floor plan may be drawn in a three-dimensional projection of the call center. A three-dimensional floor plan representing a specific call center may be created using virtual reality modeling language (VRML) and JavaScript code. By accessing the physical location information in either the server computer 8 or the database 7, the VRML electronic floor plan is updated with call center agent and console information. The VRML specification provides for taking Cartesian coordinates and performing a visual representation. Referring now to
In an alternative embodiment, the method may employ learning as a method of increasing the detection of changes in physical location. The method recognizes and learns agent location pattern regularities that appear over time. For example, agents assigned to consoles (55–60) regularly break for lunch during the noon hour. The method may recognize this pattern and learn that during such a time, the location of the agent is in the break room. The ability to predict physical location information may allow the call center supervisor to better predict agent absences and more efficiently manage the call center.
At the end of an application session, the physical location information may be copied to the database 8 for use at a future date. Further, the physical location information may be archived so that the call center supervisor may perform historical analysis of the data to determine efficiencies of the call center and more particularly, call center agents.
A specific embodiment of a system and method of monitoring entities according to the present invention 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, any and all modifications, variations, or equivalents that fall within the true spirit and scope of the basic underlying principles disclosed and claimed herein.
Patent | Priority | Assignee | Title |
10178473, | Sep 05 2014 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Collection and analysis of muted audio |
10652652, | Sep 05 2014 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Collection and analysis of muted audio |
7421072, | Oct 04 2002 | AVAYA Inc | Location-based bridging in call centers |
7599861, | Mar 02 2006 | CONCENTRIX CVG CUSTOMER MANAGEMENT DELAWARE LLC | System and method for closed loop decisionmaking in an automated care system |
7809663, | May 22 2006 | CONCENTRIX CVG CUSTOMER MANAGEMENT DELAWARE LLC | System and method for supporting the utilization of machine language |
8379830, | May 22 2006 | CONCENTRIX CVG CUSTOMER MANAGEMENT DELAWARE LLC | System and method for automated customer service with contingent live interaction |
8452668, | Mar 02 2006 | CONCENTRIX CVG CUSTOMER MANAGEMENT DELAWARE LLC | System for closed loop decisionmaking in an automated care system |
8619968, | Apr 14 2010 | Avaya Inc. | View and metrics for a queueless contact center |
8670550, | Apr 14 2010 | Avaya Inc. | Automated mechanism for populating and maintaining data structures in a queueless contact center |
8965878, | Apr 06 2012 | Avaya Inc. | Qualifier set creation for work assignment engine |
9105013, | Aug 29 2011 | Avaya Inc. | Agent and customer avatar presentation in a contact center virtual reality environment |
9179784, | Sep 09 2011 | P&W SOLUTIONS CO., LTD. | Apparatus, method and program for designing seating arrangement |
9251504, | Aug 29 2011 | Avaya Inc. | Configuring a virtual reality environment in a contact center |
9349118, | Aug 29 2011 | Avaya Inc. | Input, display and monitoring of contact center operation in a virtual reality environment |
9549065, | May 22 2006 | CONCENTRIX CVG CUSTOMER MANAGEMENT DELAWARE LLC | System and method for automated customer service with contingent live interaction |
9571654, | Apr 14 2010 | Avaya Inc. | Bitmaps for next generation contact center |
Patent | Priority | Assignee | Title |
5465286, | May 24 1994 | Wilmington Trust FSB | Apparatus for supervising an automatic call distribution telephone system |
5493692, | Dec 03 1993 | UBICOMM, LLC | Selective delivery of electronic messages in a multiple computer system based on context and environment of a user |
5742675, | Sep 26 1995 | Telefonaktiebolaget L M Ericsson | Method and apparatus for automatically distributing calls to available logged-in call handling agents |
5822418, | Feb 28 1994 | Hill-Rom Services, Inc | Telephone communication system having a locator |
6026153, | Sep 14 1984 | Wilmington Trust, National Association, as Administrative Agent | Personal communicator telephone system |
6268872, | May 21 1997 | LINE CORPORATION | Client apparatus, image display controlling method, shared virtual space providing apparatus and method, and program providing medium |
6577726, | Mar 31 2000 | Oracle America, Inc | Computer telephony integration hotelling method and system |
Date | Maintenance Fee Events |
Jul 27 2009 | REM: Maintenance Fee Reminder Mailed. |
Aug 27 2009 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Aug 27 2009 | M1554: Surcharge for Late Payment, Large Entity. |
Mar 08 2013 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Jun 08 2017 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Jan 17 2009 | 4 years fee payment window open |
Jul 17 2009 | 6 months grace period start (w surcharge) |
Jan 17 2010 | patent expiry (for year 4) |
Jan 17 2012 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jan 17 2013 | 8 years fee payment window open |
Jul 17 2013 | 6 months grace period start (w surcharge) |
Jan 17 2014 | patent expiry (for year 8) |
Jan 17 2016 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jan 17 2017 | 12 years fee payment window open |
Jul 17 2017 | 6 months grace period start (w surcharge) |
Jan 17 2018 | patent expiry (for year 12) |
Jan 17 2020 | 2 years to revive unintentionally abandoned end. (for year 12) |