This invention relates to technology for managing shopping carts. More particularly, it relates to a software module for administering call center orders.
A call center is a centralized office used for the purpose of receiving and transmitting a large volume of requests, usually by telephone. A call center is operated by a company to administer incoming product support or information inquiries from consumers. Outgoing calls for telemarketing, clientele, and debt collection are also made. In addition to a call center, collective handling of letters, faxes, and e-mails at one location is known as a contact center.
Additionally, a call center is often operated through an extensive open workspace for call center agents, with work stations that include a computer for each agent, a telephone set/headset connected to a telecom switch, and one or more supervisor stations. It can be independently operated or networked with additional centers, often linked to a corporate computer network, including mainframes, microcomputers and local area networks (LAN). Increasingly, the voice and data pathways into the center are linked through a set of new technologies called computer telephony integration (CTI).
Most major businesses use call centers to interact with their customers. Examples include utility companies, mail order catalogue firms, and customer support for computer hardware and software. Some businesses even service internal functions through call centers. Examples of this include help desks and sales support.
A call center can be viewed, from an operational point of view, as a queuing network. The simplest call center, consisting of a single type of customers and statistically-identical servers, can be viewed as a single-queue. There is operations research of call centers as well, such as forecasting of calls, determining shift-structures, and for analyzing customers' impatience while waiting to be served by an agent.
The centralization of call management aims to improve a company's operations and reduce costs, while providing a standardized, streamlined, uniform service for consumers, making this approach ideal for large companies with extensive customer support needs. To accommodate for such a large customer base, large warehouses are often converted to office space to host all call center operations under one roof. Centralized offices mean that large numbers of workers can be managed and controlled by a relatively small number of managers and support staff. They are often supported by computer technology that manages, measures and monitors the performance and activities of the workers. Call center staff are closely monitored for quality control, level of proficiency, and customer service. Typical contact center operations focus on the discipline areas of workforce management, queue management, quality monitoring, and reporting. Reporting in a call center can be further broken down into real time reporting and historical reporting. The types of information collected for a group of call center agents typically include: agents logged in, agents ready to take calls, agents available to take calls, agents in wrap up mode, average call duration, average call duration including wrap-up time, longest duration agent available, longest duration call in queue, number of calls in queue, number of calls offered, number of calls abandoned, average speed to answer, average speed to abandoned and service level, calculated by the percentage of calls answered in under a certain time period.
Many call centers use workforce management software, which is software that uses historical information coupled with projected need to generate automated schedules. This aims to provide adequate staffing skilled enough to assist callers. The relatively high cost of personnel and worker inefficiency accounts for the majority of call center operating expenses, influencing outsourcing in the call center industry.
Inadequate computer systems can mean staffs take one or two seconds longer than necessary to process a transaction. This can often be quantified in staff cost terms. This is often used as a driving factor in any business case to justify a complete system upgrade or replacement. For several factors, including the efficiency of the call center, the level of computer and telecom support that may be adequate for staff in a typical branch office may prove totally inadequate in a call center.
Call centers need to use a wide variety of different technologies to allow them to manage the large volumes of work that need to be managed by the call center. These technologies ensure that agents are kept as productive as possible, and that calls are queued and processed as quickly as possible, resulting in good levels of service.
Customer service representatives need a faster and more efficient way to place orders on behalf of a caller, instead of using normal order flow. The present invention provides a solution to these needs and other problems, and offers other advantages over the prior art.
The present invention is related to a software system that solves the above-mentioned problems. In a preferred embodiment, call center order system and process allows a customer service representative (representative) to make remote calls to a server to perform shopping cart actions, all on one web page. Historically, representatives would need to enter client information and product information on several different web pages to satisfy a purchase. For example, a customer would contact a call center and speak to a representative. The representative, in turn, would first select a product in either a web page or dialog box. Next, the representative would move to several different pages to enter customer information such as address and shipping data. Eventually, the representative would have “loaded” several different pages to enter product and customer information. This method resulted in a high amount of errors and increased the risk of fraud, affecting company sales and customer satisfaction.
Call center order system and process, on the other hand, utilizes AJAX technology to perform the shopping cart actions. These shopping cart actions may be for several different types of products such as physical goods, electronically downloadable software, video or music, as well as services such as conference registrations, repair requests, reservations, or the like. AJAX, shorthand for Asynchronous JavaScript and Extensible Markup Language (XML), is a web development technique for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user, or representative, requests a change. This is meant to increase the web page's interactivity, speed, and usability.
Again in a preferred embodiment of call center order system and process, all products are initially loaded into dropdown lists when the page is first loaded. When the user changes product categories, the dropdowns are re-built using JavaScript to filter the list for only that selected category. The representative is able to manipulate the shopping cart (e.g., add, update, or remove products in the shopping cart) without waiting for the page to “refresh” after every action. Furthermore, all cart actions are flagged with a “ticking” indicator bar for the split-second that the request goes to the server and back. In this way, product orders and requests may be placed in a “queue” instead of loading and refreshing a different page for each product. Finally, call center order system and process enables the site to switch to Mild Fraud mode and allows multiple orders to be placed from a single IP address. A storefront is used in this process and all products and promotions present within the store are available for the representative to make a purchase on behalf of the customer.
Additional advantages and features of the invention will be set forth in part in the description which follows, and in part, will become apparent to those skilled in the art upon examination of the following or may be learned by practice of the invention.
In a preferred embodiment, call center order system and process allows a customer service representative (representative) to make remote calls to a server to perform shopping cart actions, all on one web page. Historically, representatives would need to enter client information and product information on several different web pages to satisfy a purchase. For example, a customer would contact a call center and speak to a representative. The representative, in turn, would first select a product in either a web page or dialog box. Next, the representative would move to several different pages to enter customer information such as address and shipping data. Eventually, the representative would have “loaded” several different pages to enter product and customer information. This method resulted in a high amount of errors and increased the risk of fraud, affecting company sales and customer satisfaction.
Call center order system and process, on the other hand, utilizes AJAX technology to perform the shopping cart actions. AJAX, shorthand for Asynchronous JavaScript and Extensible Markup Language (XML), is a web development technique for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user, or representative, requests a change. This is meant to increase the web page's interactivity, speed, and usability.
Again in a preferred embodiment of call center order system and process, all products are initially loaded into dropdown lists when the page is first loaded. When the user changes product categories, the dropdowns are re-built using JavaScript to filter the list for only that selected category. The representative is able to add, update, or remove products in the shopping cart without waiting for the page to “refresh” after every action. Furthermore, all cart actions are flagged with a “ticking” indicator bar for the split-second that the request goes to the server and back. In this way, product orders and requests may be placed in a “queue” instead of loading and refreshing a different page for each product. A storefront is used in this process and all products and promotions present within the store are available for the representative to make a purchase on behalf of the customer.
Call center order system and process relies on the domain to remain the same throughout the purchase process. In many instances a storefront may have hard coded URLs which switch the representative to an incorrect domain. Ultimately the representative is inadvertently placing orders outside of the test site. Thus the representative will be in a high fraud mode just like any regular customer and will encounter may fraud errors. Accordingly, call center order system and process enables the site to switch to Mild Fraud mode and allows multiple orders to be placed from a single internet protocol (IP) address.
Referring again to
The next step in the overview diagram of call center order system and process is an “Order Screen” 106 section. Here, a product is selected, a shopping cart is managed, and an authorization page is edited. Next, in an “Order Confirmation” 130 step, the representative confirms the information entered in “Country and Language Selection” 100, “Login” 104, and “Order Screen” 106. Thereafter, if the information is correct 132, the customer service representative will be directed to an “Order Completion and Thank You” 134 page. If the information is not correct, then the representative may re enter and re-submit the items listed in the above steps.
Referring now to
When the representative clicks on a category under “Currency/Product Selector” 108, the next drop down menu, such as product, will be repopulated with items specific to that category. Categories may include but are not limited to: retail, upgrade, subscription, compact disk (CD) replacement, and default items. The same repopulation applies to a deliver drop down menu. It will be understood by one of ordinary skill in the art that selecting an item in one drop down menu filters the next drop down menu.
Next, the representative may select a “Cart Action” 110. Here a currency type, campaign ID, and coupon code may be applied. Under “Pending Cart Actions” 112, the items that are pending completion are shown. All cart actions are flagged with a “ticking” indicator bar for the split-second that the request goes to the server and back. In this way, product orders and requests may be placed in a “queue” instead of loading and refreshing a different page for each product. For example, a representative may add several products together very quickly as the customer requests. The products will thus be lined up in a queue in the “Pending Cart actions” 112 section. This way the shopping cart will not “freeze” and the representative may safely and securely order several products without any need to refresh and reload pages. Conversely, if the representative attempts to delete an item in queue, the shopping cart will automatically lock. This ensures that the representative will not make any mistakes in updating or deleting orders and forces the representative to wait until the orders have gone through the queue. The system displays a message that the product is being added to the cart and locks the cart from further action. Once the item has been added to the cart, the message is removed, the cart is unlocked, and order IDs and representative name fields are populate. It will be understood by one of ordinary skill in the art that product are often bundled together, thus if a representative attempts to delete a product in queue, the related products may also be affected.
Furthermore, under “Shopping Cart” 114, the product(s) are listed along with quantity, delivery method, price, and ability to remove the item. It will be understood that “Shopping Cart” 114 is the actual cart where orders are placed once they move through the “Pending Cart Actions” 112 section. “Shopping Cart” 114 is continually refreshed without the representative needing to manually refresh the page. The representative also does not have to click or load another page to see the shopping cart with the current ordered products. Here, AJAX technology and also dynamic HTML may be used. Also, the representative may click on a trash can to dispose of an item. “Shipping” 116 menu allows the customer service representative to choose the destination and method of shipment. The method will be limited based on the selected product.
Referring now to
It is to be understood that even though numerous characteristics and advantages of various embodiments of the present invention have been set forth in the foregoing description, together with details of the structure and function of various embodiments of the invention, this disclosure is illustrative only, and changes may be made in detail, especially in matters of structure and arrangement of parts within the principles of the present invention to the full extent indicated by the broad general meaning of the terms in which the appended claims are expressed. For example, the particular elements may vary depending on the particular application for the web interface such that different dialog boxes are presented to a user that are organized or designed differently while maintaining substantially the same functionality without departing from the scope and spirit of the present invention.
The present application is a divisional of U.S. patent application Ser. No. 11/694,884, filed 30 Mar. 2007, entitled “Web-Based Product Ordering Method”, which claims the benefit of U.S. Provisional Application No. 60/787,937, filed 31 Mar. 2006, entitled “Call Center Order Tool,” all of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5960411 | Hartman et al. | Sep 1999 | A |
6281517 | Burkhardt et al. | Aug 2001 | B1 |
6378075 | Goldstein et al. | Apr 2002 | B1 |
6823359 | Heidingsfeld et al. | Nov 2004 | B1 |
7106850 | Campbell et al. | Sep 2006 | B2 |
7110521 | Lambrigts et al. | Sep 2006 | B2 |
7181418 | Zucker et al. | Feb 2007 | B1 |
7184539 | Colson et al. | Feb 2007 | B2 |
7461134 | Ambrose | Dec 2008 | B2 |
7805670 | Lipton et al. | Sep 2010 | B2 |
20020055878 | Burton et al. | May 2002 | A1 |
20040225922 | Susarla et al. | Nov 2004 | A1 |
20040254855 | Shaw | Dec 2004 | A1 |
20060136564 | Ambrose | Jun 2006 | A1 |
20070058793 | Li et al. | Mar 2007 | A1 |
20070143672 | Lipton et al. | Jun 2007 | A1 |
20070198494 | Vadon et al. | Aug 2007 | A1 |
20070226613 | Tandriono et al. | Sep 2007 | A1 |
Entry |
---|
“Google Gets the Message, Launches Gmail.” Google Press Center. Datasheet [online]. Google Inc. 2007. [retrieved on Apr. 11, 2007]. Retrieved from the Internet: <URL:http://www.google.com/press/pressrel/gmail.html>. |
“AJAX: Not about technology at all.” Robert Hoekman, Jr. Blog. Datasheet [online]. Rober Hoekman 2005. [retrieved on Apr. 11, 2007]. Retrieved from the Internet: <URL:http://www.rhjr.net/blog/2005/03/ajax-not-about-technology-at-all.html>. |
“Where can you find Flickr and Apple in the same Room? At the AJAX Summit of Course.” Boutelle, Jonathan. Datasheet [online]. Silicon Valley Watcher 2005. [retrieved on Apr. 11, 2007]. Retrieved from the Internet: <URL:http:// www.siliconvalleywatcher.com/mt/archives/2005/05/where—can—you—f—2.php>. |
“Web Standards Project Announces the DOM Scripting Task Force.” Webstandards Press Release. Datasheet [online]. Webstandards Inc. 2005. [retrieved on Apr. 11, 2007]. Retrieved from the internet: <URL:http://www.webstandards.org/press/releases/20050718/>. |
“Why AJAX Matters Now.” OK/Cancel Archive. Datasheet [online]. Okay/Cancel 2005. [retrieved on Apr. 11, 2007]. Retrieved from the Internet: <URL:http://www.ok-cancel.com/archives/article/2005/09/why-ajax-matters-now.html>. |
“World's first AJAX Development Environment with JavaScript Synthesis.” AJAX Magazine 2005. Datasheet [online]. PHP Magazine Network 2005. [retrieved on Apr. 11, 2007]. Retrieved from the Internet: <URL:http://ajax.phpmagazine.net/2005/09/worlds—first—ajax—development.html>. |
AJAX Programming. Datasheet [online]. Wikipedia Inc. 2007 [retrieved on Apr. 4, 2007]. Retrieved from the internet; , URL:http//en.wikipedia.org/wiki/Ajax—%28programming%29>. |
Number | Date | Country | |
---|---|---|---|
20120173386 A1 | Jul 2012 | US |
Number | Date | Country | |
---|---|---|---|
60787937 | Mar 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11694884 | Mar 2007 | US |
Child | 13419950 | US |