The co-pending and co-owned U.S. patent application Ser. No. 10/327,360, filed Dec. 20, 2002, and entitled “REMOTE AGENT ACCESS METHOD TO A VOIP CONTACT CENTER WHERE HIGH QOS IS NOT SUPPORTED” is also hereby incorporated by reference in its entirety.
The co-pending and co-owned U.S. patent application Ser. No. 10/327,348, filed Dec. 20, 2002, and entitled “SCHEDULED RETURN TO QUEUE WITH PRIORITY (SRQP)” is also hereby incorporated by reference in its entirety.
The co-pending, co-owned and co-filed U.S. patent application Ser. No. 10/633,018 entitled “HIGH AVAILABILITY VOIP SUBSYSTEM” is also hereby incorporated by reference in its entirety.
The co-pending, co-owned and co-filed U.S. patent application Ser. No. 10/632,649 entitled “ESCALATED HANDLING OF NON-REALTIME COMMUNICATIONS” is also hereby incorporated by reference in its entirety.
The co-pending, co-owned and co-filed U.S. patent application Ser. No. 10/632,617 entitled “GRAPHICAL CONTROL FOR SIMULTANEOUSLY EDITING AN ARRAY OF VALUES THAT SUM TO A FIXED VALUE” is also hereby incorporated by reference in its entirety.
The present invention relates generally to the field of graphical user interfaces. More particularly, the present invention relates to the field of automatic graphical user interface management.
In the latest multi-channel Contact Centers, the Agent's personal computing (PC) desktop, particularly the graphical images present of the Agent's graphical user interface has become a very congested space. Programs to control the presentation of customer contacts, agent status controls, agent performance data, and media specific controls must all compete with the Customer Relationship Management (CRM) applications for space on the desktop. Some media channels such as email and web collaboration with chat, take substantial desktop space to run. Although it is possible to expand and contract windows and/or to overlay one window with another when needed, these extra manual steps take valuable agent time and slow down call handling.
Also, many multi-channel Contact Centers currently utilize multiple CRM Applications in order to manage separate voice, e-mail, chat, etc. applications. Having multiple CRM Applications can severely clutter an Agent's PC desktop. An Agent may also be required to utilize more than one CRM Application at one time. Requiring the Agent to manually launch and use independent applications at various points within a task flow requires agent training, and introduces an opportunity for user error. Even the mental operations of deciding to launch or not launch an application introduces a mental operation that takes measurable time for an agent to perform. Further, modern Contact Center graphical user interface arrangements utilizing multiple CRM Applications tend to crowd an Agent's PC desktop so that the desktop does not include space for applications that are separate and unmanaged by the Contact Center such as a corporate e-mail and/or calendar application such as Outlook™, or any other application that is not managed by the Contact Center.
What is needed is a Graphical User Interface having a feature of visual space management that exposes a single CRM Application at the appropriate time to efficiently manage an Agent's PC desktop while also allowing the Agent access to applications not managed by the Contact Center. What is also needed is a Graphical User Interface having a feature of visual management space that exposes a CRM Application at the appropriate time that it is needed in an Agent's Workflow.
A graphical user interface and method for displaying on an agent's desktop. The graphical user interface of the present invention being capable of automatically displaying, in a designated area, a managed application according to a workflow. The graphical user interface of the present invention also includes the ability to control the display of managed applications manually. Further, the graphical user interface and method of the present invention allows an Agent access to non-managed applications without restricting the agent's access to the managed applications.
In one aspect of the present invention, a graphical user interface for displaying on an agent desktop in a contact center comprises a SHUTTERS managed display having a task bar, wherein the task bar includes at least one managed application, at least one SHUTTERS icon corresponding to each one of the at least one managed applications and a managed application display area, wherein a predetermined set of rules determines the size, placement and visibility of the at least one managed application in the managed application display area. The graphical user interface also includes an agent workflow having at least one step corresponding to each one of the at least one SHUTTERS icon, wherein one of the at least one SHUTTERS icon is selected according to the corresponding step of the agent workflow, and the managed application corresponding to the selected SHUTTERS icon is displayed in the managed application display area, a quick start bar, wherein the quick start bar includes at least one non-managed application and a contact center control panel illustrating current contact information. The graphical user interface is displayed on the agent desktop having a display and an input device. The input device is used to selectively input data in to any one of the at least one managed applications. When the agent selects any of the at least one SHUTTERS icon, the corresponding managed application is displayed in the managed application display area.
In another aspect of the present invention, a method of managing a visual space of a customer relations management application comprises displaying a SHUTTERS managed display having a task bar, wherein the task bar includes at least one managed application, displaying at least one SHUTTERS icon corresponding to each one of the at least one managed applications and displaying a managed application display area, wherein a predetermined set of rules determines the size, placement and visibility of the at least one managed application in the managed application display area. The method also includes displaying an agent workflow having at least one step corresponding to each one of the at least one SHUTTERS icon, wherein one of the at least one SHUTTERS icon is selected according to the corresponding step of the agent workflow, and the managed application corresponding to the selected SHUTTERS icon is displayed in the managed application display area, displaying a quick start bar, wherein the quick start bar includes at least one non-managed application, displaying a contact center control panel illustrating current contact information, selectively inputting data in to any one of the at least one managed applications and selecting any of the at least one SHUTTERS icon thereby displaying the corresponding managed application in the managed application display area.
In yet another aspect of the present invention, a system having a central processor, a display, a memory and an input device, a graphical user interface for displaying an agent desktop in a contact center comprises a SHUTTERS managed display having a task bar, wherein the task bar includes at least one managed application, at least one SHUTTERS icon corresponding to each one of the at least one managed applications and a managed application display area, wherein a predetermined set of rules determines the size, placement and visibility of the at least one managed application in the managed application display area. The system also includes an agent workflow having at least one step corresponding to each one of the at least one SHUTTERS icon, wherein one of the at least one SHUTTERS icon is selected according to the corresponding step of the agent workflow, and the managed application corresponding to the selected SHUTTERS icon is displayed in the managed application display area, a quick start bar, wherein the quick start bar includes at least one non-managed application and a contact center control panel illustrating current contact information. The graphical user interface is displayed on the agent desktop having a display and an input device. The input device is used to selectively input data in to any one of the at least one managed applications. When the agent selects any of the at least one SHUTTERS icon, the corresponding managed application is displayed in the managed application display area.
In yet another aspect of the present invention, a graphical user interface for displaying on an agent desktop in a contact center comprises a quick start bar, wherein the quick start bar includes at least one non-managed application, a contact center control panel illustrating current contact information, a SHUTTERS managed display having a task bar, wherein the task bar includes at least one managed application, at least one SHUTTERS icon corresponding to each one of the at least one managed applications, a managed application display area, wherein a predetermined set of rules determines the size, placement and visibility of the at least one managed application in the managed application display area and an agent workflow having at least one step corresponding to each one of the at least one SHUTTERS icon, wherein one of the at least one SHUTTERS icon is selected according to the corresponding step of the agent workflow, and the managed application corresponding to the selected SHUTTERS icon is displayed in the managed application display area. The graphical user interface is displayed on the agent desktop having a display and an input device. The input device is used to selectively input data in to any one of the at least one managed applications. When the agent selects any of the at least one SHUTTERS icon, the corresponding managed application is displayed in the managed application display area.
Referring to
Referring to
In this implementation, applications such as the customer's CRM are put on a list of managed applications or “CRM Applications”, each CRM Application's visual experience is controlled by the Task bar 212, and its corresponding SHUTTERS Icon 210. The Task bar 212 sends messages to the windowing system to reveal, hide and reposition SHUTTERS Managed Applications 208, and intercepts and reinterprets all windowing messages sent via the windowing system that would otherwise control the size, visibility and location of the SHUTTERS Managed Applications 208. The Task bar 212 may or may not have a visual representation on the Desktop 204. In a preferred embodiment, when a contact arrives to the corresponding Contact Step 306 in the Contact Workflow 301, the Contact Workflow 301 can specify which SHUTTERS Managed Application 208 is to be opened for viewing and positioned to the current contact's records in the SHUTTERS Managed Display Area 206. This combines a traditional CRM “screen pop” with the management of the Graphical User Interface 200 at the same time. In alternative embodiments, when the Agent 150 arrives to the corresponding Agent Step 305 in the Agent Workflow 300, the Agent Workflow 300 can specify which SHUTTERS Managed Application 208 is to be opened for viewing and positioned in the SHUTTERS Managed Display Area 206. Also in alternative embodiments, SHUTTERS Managed Applications 208 can also be configured by the contact center administrator to open in a separate window. Such a configuration is often desired when a contact center utilizes a high number of managed applications. Any number of the managed application may be configured in this manner as desired by the contact center administrator. When a SHUTTERS Managed Application 208 is launched in or opened either manually or by an Agent or Contact Workflow 300, 301, a corresponding SHUTTERS Icon 210 appears in the Task bar 212. When a SHUTTERS Managed Application 208 is closed, either manually or by an Agent or Contact Workflow 300, 301 its corresponding SHUTTERS Icon 210 disappears from the Task bar 212.
Still referring to
Still referring to
Referring now to
Still referring to
The Desktop 204 presents the non-managed applications that may be accessed by an Agent 150 while using the Graphical User Interface 200. Preferably the Desktop 204 is located on the left edge of the Graphical User Interface 200 with a strip extending along the bottom of the Graphical User Interface 200 as depicted in
Referring still to
The SHUTTERS Managed Display Area 206 illustrates the current Agent or Contact Step 305, 306 of the Agent or Contact Workflow 300, 301 of the Agent 150 and, if one is being accessed, the current CRM Application. In a preferred embodiment, the SHUTTERS Managed Display Area 206 is typically about 1024 pixels wide and 768 pixels tall as depicted in
Still referring to
In a preferred embodiment, SHUTTERS Managed Applications 208 will “share” the space of the SHUTTERS Managed Display Area 206. Each SHUTTERS Managed Application 208 is allocated all of the required horizontal space, and the remaining vertical space is split up and shared between them as described below. Application focus may be directed to a specific SHUTTERS Managed Application 208 according to the Contact Workflow 301, or manually specified by the Agent 150 by whatever focus shifting mechanisms the windowing system provides. Typically, this includes clicking with the mouse, or by using keyboard shortcuts. In this way, the Agent 150 has simultaneous access to all of the SHUTTERS Managed Applications 208. Such an embodiment allows an Agent 150 to work on multiple CRM Applications at the same time.
The percent of utilization of the SHUTTERS Managed Display Area 206 may be automatically allocated on an even percentage basis or it may be specifically controlled such as one-third given to email and two-thirds given to a CRM Application. When multiple applications appear, the SHUTTERS Icons 210 still allow an Agent 150 to fully expand or contract any SHUTTERS Managed Applications 208 within the SHUTTERS Managed Display Area 206. Furthermore, when multiple applications appear, an Agent 150 may assign a minimum vertical space for each SHUTTERS Managed Application 208 such that when any particular SHUTTERS Managed Application 208 is selected, the non-selected SHUTTERS Managed Applications 208 will resize to allow the selected SHUTTERS Managed Application 208 to be displayed with the assigned minimum vertical height. It should also be noted that any managed application may include a standard scroll bar when the managed application is larger than the allotted space given to that managed application in the SHUTTERS Managed Display Area 206.
Referring now to
Alternatively, when an Agent 150 becomes available to handle contacts of a particular media type, the Contact Workflow 301 sends a message to the Task bar 212 to open a SHUTTERS Managed Application 208 in the SHUTTERS Managed Display Area 206, that allows the Agent 150 to communicate via the appropriate medium. The Task bar 212 determines the size, and placement of the window for the SHUTTERS Managed Application 208, and sends the appropriate messages to the Windowing System. When the Agent 150 is presented with a new contact, the Contact Workflow 301 sends a message to the Task bar 212 to open a SHUTTERS Managed Application 208 to display the detailed contact information. If the Agent 150 accepts the Contact 314, the Contact Workflow 301 sends a message to the Task bar 212 to open a SHUTTERS Managed Application 208 to best process the issues of that contact.
Still following the Contact Workflow 301 in
The present invention has been described in terms of specific embodiments incorporating details to facilitate the understanding of the principles of construction and operation of the invention. Such reference herein to specific embodiments and details thereof is not intended to limit the scope of the claims appended hereto. For example this concept can be implemented in any task-based environment that uses a graphical user interface. It will be apparent to those skilled in the art that modifications can be made in the embodiment chosen for illustration without departing from the spirit and scope of the invention.
This Patent Application claims priority under 35 U.S.C. §119(e) of the co-pending U.S. Provisional Patent Application Ser. No. 60/404,076, filed Aug. 16, 2002, and entitled “YOSEMITE ARCHITECTURE SPECIFICATION”. The Provisional Patent Application Ser. No. 60/404,076, filed Aug. 16, 2002, and entitled “YOSEMITE ARCHITECTURE SPECIFICATION” is also hereby incorporated by reference in its entirety. This Patent Application claims priority under 35 U.S.C. §119(e) of the co-pending U.S. Provisional Patent Application Ser. No. 60/435,974, filed Dec. 20, 2002, and entitled “YOSEMITE ARCHITECTURE SPECIFICATION II”. The Provisional Patent Application Ser. No. 60/435,974, filed Dec. 20, 2002, and entitled “YOSEMITE ARCHITECTURE SPECIFICATION II” is also hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5282243 | Dabbaghi et al. | Jan 1994 | A |
5390295 | Bates et al. | Feb 1995 | A |
5459780 | Sand | Oct 1995 | A |
5530744 | Charalambous et al. | Jun 1996 | A |
5613068 | Gregg et al. | Mar 1997 | A |
5825357 | Malamud et al. | Oct 1998 | A |
5848143 | Andrews et al. | Dec 1998 | A |
5903642 | Schwartz et al. | May 1999 | A |
5986657 | Berteig et al. | Nov 1999 | A |
6046762 | Sonesh et al. | Apr 2000 | A |
6049603 | Schwartz et al. | Apr 2000 | A |
6072486 | Sheldon et al. | Jun 2000 | A |
6094479 | Lindeberg et al. | Jul 2000 | A |
6122364 | Petrunka et al. | Sep 2000 | A |
6141341 | Jones et al. | Oct 2000 | A |
6144667 | Doshi et al. | Nov 2000 | A |
6188673 | Bauer et al. | Feb 2001 | B1 |
6188761 | Dickerman et al. | Feb 2001 | B1 |
6201804 | Kikinis | Mar 2001 | B1 |
6212565 | Gupta | Apr 2001 | B1 |
6219648 | Jones et al. | Apr 2001 | B1 |
6289001 | Smyk | Sep 2001 | B1 |
6298383 | Gutman et al. | Oct 2001 | B1 |
6301480 | Kennedy, III et al. | Oct 2001 | B1 |
6330326 | Whitt | Dec 2001 | B1 |
6337858 | Petty et al. | Jan 2002 | B1 |
6366577 | Donovan | Apr 2002 | B1 |
6377568 | Kelly | Apr 2002 | B1 |
6400804 | Bilder | Jun 2002 | B1 |
6434143 | Donovan | Aug 2002 | B1 |
6445695 | Christie, IV | Sep 2002 | B1 |
6448986 | Smith | Sep 2002 | B1 |
6493695 | Pickering et al. | Dec 2002 | B1 |
6529499 | Doshi et al. | Mar 2003 | B1 |
6542475 | Bala et al. | Apr 2003 | B1 |
6574218 | Cooklev | Jun 2003 | B1 |
6577726 | Huang et al. | Jun 2003 | B1 |
6584191 | McPartlan et al. | Jun 2003 | B1 |
6600735 | Iwama et al. | Jul 2003 | B1 |
6611590 | Lu et al. | Aug 2003 | B1 |
6614902 | Rizzetto | Sep 2003 | B1 |
6615235 | Copeland et al. | Sep 2003 | B1 |
6639982 | Stuart et al. | Oct 2003 | B1 |
6665395 | Busey et al. | Dec 2003 | B1 |
6674713 | Berg et al. | Jan 2004 | B1 |
6678265 | Kung et al. | Jan 2004 | B1 |
6678718 | Khouri et al. | Jan 2004 | B1 |
6687251 | Mousseau et al. | Feb 2004 | B1 |
6697858 | Ezerzer et al. | Feb 2004 | B1 |
6704409 | Dilip et al. | Mar 2004 | B1 |
6704412 | Harris et al. | Mar 2004 | B1 |
6724884 | Jensen et al. | Apr 2004 | B2 |
6741698 | Jensen | May 2004 | B1 |
6766377 | Grabelsky et al. | Jul 2004 | B1 |
6771765 | Crowther et al. | Aug 2004 | B1 |
6778494 | Mauger | Aug 2004 | B1 |
6781959 | Garakani et al. | Aug 2004 | B1 |
6823382 | Stone | Nov 2004 | B2 |
6850599 | Yoshitani | Feb 2005 | B2 |
6850613 | McPartlan et al. | Feb 2005 | B2 |
6868059 | Jones et al. | Mar 2005 | B1 |
6937715 | Delaney | Aug 2005 | B2 |
7035252 | Cave et al. | Apr 2006 | B2 |
7036087 | Odom | Apr 2006 | B1 |
7080327 | Bartz et al. | Jul 2006 | B1 |
7085263 | Fitzgerald | Aug 2006 | B1 |
7167899 | Lee et al. | Jan 2007 | B2 |
20010024997 | Sugano et al. | Sep 2001 | A1 |
20010035882 | Stoakley et al. | Nov 2001 | A1 |
20020071541 | Cheung et al. | Jun 2002 | A1 |
20030018702 | Broughton et al. | Jan 2003 | A1 |
20030133558 | Kung et al. | Jul 2003 | A1 |
20030184583 | Lim | Oct 2003 | A1 |
20030195753 | Homuth | Oct 2003 | A1 |
20040054743 | McPartlan et al. | Mar 2004 | A1 |
20040066923 | Robinson | Apr 2004 | A1 |
20040141508 | Schoeneberger et al. | Jul 2004 | A1 |
20040221053 | Codella et al. | Nov 2004 | A1 |
20040254465 | Sano et al. | Dec 2004 | A1 |
20060136843 | Shafron | Jun 2006 | A1 |
20060293942 | Chaddha et al. | Dec 2006 | A1 |
20070016915 | Mukundan et al. | Jan 2007 | A1 |
20070050340 | von Kaenel et al. | Mar 2007 | A1 |
20070094230 | Subramaniam et al. | Apr 2007 | A1 |
20070106638 | Subramaniam et al. | May 2007 | A1 |
20070118504 | Subramaniam et al. | May 2007 | A1 |
20070204280 | Mukundan et al. | Aug 2007 | A1 |
20070208697 | Subramaniam et al. | Sep 2007 | A1 |
20070214145 | Subramaniam et al. | Sep 2007 | A1 |
20070214463 | Mukundan et al. | Sep 2007 | A1 |
20070220039 | Waldman et al. | Sep 2007 | A1 |
20070226168 | Mukundan et al. | Sep 2007 | A1 |
20070226709 | Coker et al. | Sep 2007 | A1 |
Number | Date | Country |
---|---|---|
1 016 998 | May 2000 | EP |
WO 9965214 | Dec 1999 | WO |
WO 0135601 AI | May 2001 | WO |
WO 0161529 | Aug 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20040032431 A1 | Feb 2004 | US |
Number | Date | Country | |
---|---|---|---|
60404076 | Aug 2002 | US | |
60435974 | Dec 2002 | US |