Not applicable.
Not applicable.
Many types of restaurants have one or more drive-through lines that enable customers to place an order while staying in their vehicles. Many times, the restaurant utilizes a speaker system that includes a drive-through speaker for each drive-through line and a headset worn by an employee taking orders inside the restaurant. If this technology is not working correctly, communication errors can occur and the customer may not receive the correct food and/or drink products that were ordered. In addition, some customers may not be proficient in the native language spoken by the employee, which can also cause communication errors. Further, while some restaurants reduce communication errors by providing a digital screen adjacent each drive-through line that enables customers to view their orders, there are still many restaurants that have not installed digital screens due to cost considerations or other factors.
Another problem with existing ordering technology is that restaurants must use on-site employees to take orders and payments using point-of-sale terminals. While this may not be a significant issue during peak hours when the drive-through lines are sufficiently staffed, it can lead to problems during slow periods of the day when the restaurant operates with fewer employees. Restaurants often experience unexpected bursts in ordering outside of the normal peak hours due to unforeseen events, such as large groups of people exiting a concert or sporting event or an event drawing unexpected crowds. Most restaurants are not equipped to handle these additional bursts in volume and may lose business due to their inability to provide timely service to additional customers during these times.
Even if the drive-through lines of a restaurant are sufficiently staffed, the existing ordering technology typically requires customers to wait for all the customers in vehicles in front of them to place their orders before they can place their own orders. In some cases, a customer is indecisive when placing an order or places a relatively large order, which delays the ordering process for customers behind that customer's vehicle. Customers must also wait for the customers in vehicles in front of them to pay for their orders once they get to the pick-up window. In some cases, a customer has a credit card and the employee must run the payment on the point-of-sale terminal and wait for the response from the credit card processing gateway, which can take upwards of sixty seconds. The employee then asks if the customer would like a receipt and, if so, requests a printed receipt from the point-of-sale terminal and provides it to the customer. Meanwhile, all of the vehicles behind this vehicle are waiting to pull forward, some of which haven't even had a chance to place their orders.
Thus, there remains a need in the art for ordering technology that overcomes some or all of the drawbacks associated with conventional ordering systems and/or that offers other advantages compared to conventional ordering systems.
The present invention is directed to a system and method for providing real-time order assistance to a customer placing an order at a restaurant or other retail location, or through a website that enables the ordering of various types of products or services. The customer places the order using the customer's own computing device. The customer device may comprise, for example, a mobile phone, an in-vehicle computer, a personal computing tablet, a smart watch, a personal computer, or a laptop computer, or any other type of Internet-enabled device. An order assistant assists the customer with order placement using the order assistant's computing device. The order assistant device may comprise, for example, a mobile phone, a personal computing tablet, a personal computer, or a laptop computer (in embodiments where the order assistant works remotely from home or from a call center), a point-of-sale terminal (in embodiments where the order assistant works at a retail store), or any other type of Internet-enabled device. In some embodiments, the order assistant may not be a person, e.g., it is possible to use a smart automated order assistant via the use of artificial intelligence (AI) technology.
In accordance with the invention, two connections are established between the customer device and the order assistant device— a real-time audio connection and a real-time data connection. The real-time audio connection is established to enable the customer and the order assistant to speak with each other during the order session. The real-time data connection is established to enable the customer and the order assistant to create (i.e., view and/or update) the order on their respective devices during an order session, including the submission of order data and payment data.
An order assistance system in accordance with one embodiment of the invention described herein is programmed to receive an initial order request from a customer device of a customer and, in response, provide a first user interface for rendering by a first Internet-enabled application on the customer device, wherein the first user interface enables selection of a request for order assistance. The system is also programmed to receive the request for order assistance from the customer device and, in response, provide a second user interface for rendering by a second Internet-enabled application on an order assistant device of an order assistant. In addition, the system is programmed to transmit a transaction identifier to each of the customer device and the order assistant device for use in transmitting a plurality of connection requests. The system is also programmed to receive the connection requests from the customer device and the order assistant device and, in response, establish an audio connection and a data connection between the first and second Internet-enabled devices. The system is further programmed to manage an order session by (a) enabling audio communication between the customer and the order assistant via the audio connection and (b) enabling the customer and the order assistant to create an order via the data connection. In addition, the system is programmed to close the order session when the order is complete to enable fulfillment of the order.
An order assistance system in accordance with another embodiment of the invention described herein is programmed to receive a request for order assistance from a customer device of a customer and, in response, identify an order assistant device of an order assistant available to assist with the request for order assistance. The system is also programmed to transmit a transaction identifier to each of the customer device and the order assistant device for use in transmitting a plurality of connection requests. In addition, the system is programmed to receive the connection requests from the customer device and the order assistant device and, in response, establish an audio connection and a data connection between the customer device and the order assistant device. The system is further programmed to manage an order session by (a) enabling audio communication between the customer and the order assistant via the audio connection and (b) enabling the customer and the order assistant to create an order via the data connection. In addition, the system is programmed to close the order session when the order is complete to enable fulfillment of the order.
An order assistance system in accordance with yet another embodiment of the invention described herein is programmed to receive a request for order assistance from a customer device of a customer. The system is also programmed to establish an audio connection and a data connection between the customer device and an order assistant device of an order assistant available to assist with the request for order assistance. The system is further programmed to manage an order session by (a) enabling audio communication between the customer and the order assistant via the audio connection and (b) enabling the customer and the order assistant to create an order via the data connection.
Various other embodiments of the present invention are described in detail below, or will be apparent to one skilled in the art based on the disclosure provided herein, or may be learned from the practice of the invention. It should be understood that the above brief summary of the invention is not intended to identify key features or essential components of the embodiments of the present invention, nor is it intended to be used as an aid in determining the scope of the claimed subject matter as set forth below.
A detailed description of various exemplary embodiments of the present invention is provided below with reference to the following drawings, in which:
The present invention is directed to a system and method for providing real-time order assistance using data and audio connections between Internet-enabled devices of a customer and an order assistant. While the invention will be described in detail below with reference to various exemplary embodiments, it should be understood that the invention is not limited to the specific configuration or methodologies of any of these embodiments. In addition, although the exemplary embodiments are described as embodying several different inventive features, those skilled in the art will appreciate that any one of these features could be implemented without the others in accordance with the invention.
In the present disclosure, references to “one embodiment,” “an embodiment,” “an exemplary embodiment,” or “embodiments” mean that the feature or features being described are included in at least one embodiment of the invention. Separate references to “one embodiment,” “an embodiment,” “an exemplary embodiment,” or “embodiments” in this disclosure do not necessarily refer to the same embodiment and are also not mutually exclusive unless so stated and/or except as will be readily apparent to one skilled in the art from the description. For example, a feature, structure, function, etc. described in one embodiment may also be included in other embodiments, but is not necessarily included. Thus, the present invention can include a variety of combinations and/or integrations of the embodiments described herein.
In general terms, the system and method of the present invention enable a customer to obtain assistance with placement of an order via a real-time order session with an order assistant. The customer may be anyone who wishes to place an order with a company or other seller (such as a retail store). The order assistant may be an employee of the company, a subcontractor of the company, or an employee or subcontractor of a third party hired for the purpose of assisting customers with placing orders with the company. It should be understood that different companies may have different names for the order assistant, such as customer service representative, order taker, order specialist, agent, waiter, server, or the like. The order assistant is preferably trained on the company's products or services so as to be able to answer any questions that the customer may have during an order session. Alternatively, the order assistant may be a smart automated order assistant that uses artificial intelligence (AI) technology to assist customers with placing orders as described herein.
The customer is able to request assistance with placement of an order using the customer's own Internet-enabled device, which is referred to herein as the “customer device.” The customer device may be any type of computing device capable of connecting to the Internet, such as a mobile phone, an in-vehicle computer, a personal computing tablet, a smart watch, a personal computer, or a laptop computer. Of course, other types of Internet-enabled devices may be used within the scope of the present invention.
The order assistant is able to provide order assistance services to a plurality of customers using an Internet-enabled device, which is referred to herein as the “order assistant device.” The order assistant device may vary depending on the location and working arrangement of the order assistant. In some embodiments, the order assistant is located in a retail store (e.g., a restaurant), in which case the order assistant device may be a point-of-sale (POS) terminal of the retailer's POS system. In this case, the order assistant typically assists with order placement for the retail store, but not for any other companies. In other embodiments, the order assistant may work from home or may be located at a call center or other location that provides an Internet connection. In this case, the order assistant device may be any type of computing device capable of connecting to the Internet, such as a mobile phone, a personal computing tablet, a smart watch, a personal computer, or a laptop computer (i.e., the same types of devices as those used by the customer). It can be appreciated that, in these embodiments, the order assistant is not required to use a specialized device (such as a POS terminal) and may provide order assistance services on behalf of one or more companies, including one or more retail stores of a particular company. Alternatively, the order assistant device may be any computing device that uses AI technology to assist customers with placing orders as described herein.
When placing an order, a customer may be able to order directly from a company's website or may have installed an application for placement of the order. In either scenario, the customer may wish to speak with an order assistant for assistance with the order. The user interface may have an option to speak with an order assistant or the customer may be automatically connected to an order assistant. Once the order session is initiated, the customer device is connected to the order assistant device through an order assistance system (such as order assistance system 112 shown in
Referring to
Each of customer devices 1021-102n is used by a customer to request assistance with placement of an order. As noted above, the customer device may be a mobile phone, an in-vehicle computer, a personal computing tablet, a smart watch, a personal computer, a laptop computer, or any other computing device that is capable of communication (wireless or wired) with other network elements via communications network 110. In this embodiment, each of customer devices 1021-102n utilizes an Internet-enabled application 1041-104n (e.g., a web browser or installed application) to communicate with web server 114, as described below.
Each of order assistant devices 1061-106n is used by an order assistant to provide order assistance services to a plurality of customers. As noted above, in cases where an order assistant is located in a retail store, the order assistant device used by that order assistant may be a POS terminal of a retailer's POS system (such as POS system 120 shown in
Order assistance system 112 may comprise any suitable computer hardware known in the art that includes memory in data communication with at least one processor, wherein the memory stores at least one computer program comprising instructions that, when executed by the processor, cause the processor to perform the methods described herein. In this embodiment, order assistance system 112 includes a web server 114 in communication with a database server 116.
Web server 114 is accessible by customer devices 1021-102n and order assistant devices 1061-106n via communications network 110. Specifically, the Internet-enabled application of each customer device sends requests to web server 114, and web server 114 responds by providing data that enables the Internet-enabled application to display various user interfaces on the customer device, as described below. Similarly, the Internet-enabled application of each order assistant device sends requests to web server 114, and web server 114 responds by providing a user interface that enables the Internet-enabled application to display various web pages on the order assistant device, as described below. Web server 114 may communicate with customer devices 1021-102n and order assistant devices 1061-106n via Hypertext Transfer Protocol (HTTP) (e.g., HTTP/1.0, HTTP/1.1 plus, HTTP/2, or HTTP/3), Hypertext Transfer Protocol Secure (HTTPS), or any other network protocol used to distribute data and web pages.
As shown in
It will be seen that web server 114 establishes two connections—a data connection and an audio connection—between one of customer devices 1021-102n and one of order assistant devices 1061-106n during an order session. The data connection may comprise any type of connection that enables creation of the customer's order, such as a WebSocket connection or a Web Real-Time Communication (WebRTC) connection. The audio connection may comprise any type of connection that enables audio (i.e., audio only or audio/video) communication between the customer device and the order assistant device, such as a WebRTC connection, a Bluetooth connection, an Ultra-Wideband (UWB) connection, or a Voice over Internet Protocol (VoIP) connection. Of course, other network protocols may be used to establish these connections within the scope of the present invention.
Referring again to
In this embodiment, web server 114 and database server 116 are co-located in the same geographic location. It should be understood, however, that these servers could be located in different geographic locations and connected to each other via communications network 110. It should also be understood that other embodiments may not include both of the servers shown in
Referring back to
Referring still to
Communications network 110 may comprise any network capable of facilitating the exchange of data among the network elements of system 100, such as those that operate according to the IEEE 802.3 protocol (e.g., Ethernet) and/or the IEEE 802.11 protocol (e.g., Wi-Fi). The communications infrastructure may comprise any medium that allows data to be physically transferred through serial or parallel communication channels (e.g., wireless communication channels, cellular communications, optical fiber, copper wire, etc.). It can be appreciated that communications network 110 will typically comprise the Internet so as to enable access to order assistance system 112 by any Internet-enabled device.
As discussed above, system 100 shown in
Referring to
In step 300, web server 114 receives a registration request from an order assistant device of order assistant (or another computing device being used by the order assistant to complete the registration process). In one embodiment, the order assistant accesses an order registration website on the order assistant device and selects a button that makes a call to a Uniform Resource Locator (URL) associated with web server 114 (e.g., http://myserver.com/Registration). When the URL is received at web server 114, it calls the Register Order Assistant application 200 via API 202. The Register Order Assistant application 200 generates and returns a web page with a user interface that allows the user to enter registration information on the order assistant device. The information collected during the registration process is used to identify the order assistant and may include, for example, data such as Name, Email Address, Employee Id, Username and Password. In step 302, web server 114 collects the registration information for the order assistant and, in step 304, stores the collected information in Order Assistants database 220 on database server 116. Then, in step 306, web server 114 returns a registration acknowledgement via API 202 that is presented on the order assistant device. It can be appreciated that this process is repeated for each order assistant who provides order assistance services through system 100.
Of course, in some embodiments, the registration of order assistants could be performed by a human resources manager or other company personnel who performs the registration process on behalf of a plurality of order assistants. In other embodiments, the order assistant information is downloaded from a company database to Order Assistants database 220, in which the case the method shown in
Referring to
In step 400, web server 114 creates an order session between the customer device and the order assistant device in response to receipt of an initial order request from the customer device. In order to create the order session, web server 114 establishes an audio connection and a data connection between the customer device and the order assistant device. The audio connection enables real-time audio communication between the customer and the order assistant during the order session. The data connection enables the customer and order assistant to create (i.e., view and optionally update) an order in real-time during the order session. An example of these connections is shown in
Referring back to
In step 408, it is determined whether the order is complete. If not, then the process returns to step 402 to look for new order data. If the order is complete, then the customer uses the customer device to submit payment data in step 410. Upon receipt of the payment data, web server 114 transmits the payment data to payment system 120 for further processing. Payment system then returns either a payment authorization or a payment denial to web server 114. In step 412, web server 114 updates the order to include the payment status. In step 414, the order's payment status is transmitted to the customer device and the order assistant device to ensure that the customer and order assistant are able to view the same payment status on their respective devices during the order session. Web server 114 may also transmit the order's payment status to POS system 118 if the order assistant device is not a POS terminal of POS system 118. Finally, in step 416, the order session is closed to enable fulfillment of the order via POS system 118.
Referring to
In step 500, web server 114 receives an initial order request from the customer device. The customer may use the customer device to initiate the order session in a variety of different ways, such as scanning a Quick Response (QR) code or other type of bar code with the customer device, tapping or placing the customer device near a Near-Field Communication (NFC) tag or Bluetooth device, sending a text message from the customer device, opening an application on the customer device, or clicking a button or notification on a website displayed on the customer device. Examples of these initiation methods are described in greater detail below in connection with the exemplary implementations shown in
The initial order request is directed to a URL associated with web server 114 ((e.g., http://myserver.com/CreateOrder) and may include a store identifier that identifies the retail store from which the customer wishes to place an order. For example, the customer may initiate the order session by scanning a QR code that encodes the URL and store identifier, in which case the customer device will open its Internet-enabled application and provide the store identifier to that URL. The store identifier will typically be assigned to the retail store ahead of time, e.g. when the retail store is added to system 100 and the item and pricing information is downloaded to Items and Pricing database 224. Of course, if system 100 is only used to provide order assistance services to a single retail store, then the store identifier would not be required.
When the URL is received at web server 114, it calls the Create Order application 204 via API 206. The Create Order application 204 performs a number of functions. First, in step 502, a new order record is inserted into Orders database 222 and a new order identifier is assigned to the order record. The order record includes a number of data fields, as shown in Table 1 below:
Next, in step 504, the received store identifier is stored in the order record. Then, in step 506, a web page with a user interface that allows placement of an order is generated and returned to the customer device via API 206. The web page includes the items and pricing for the retail store having the received store identifier as retrieved from the Items and Pricing database 224. The web page also includes a “Speak with an Order Assistant” button that can be selected to request order assistance. An exemplary screen shot of a web page with this button is shown in
Web server 114 stores a user interface layout that is used to generate the web page presented on the customer device, i.e., the user interface layout has a predetermined format that allows the inclusion of dynamic values, such as the items and pricing for a particular retail store. In this embodiment, the same user interface layout is used in connection with all of the retail stores that receive order assistance services through system 100 and, as such, the user interface will have the same “look and feel” for all of the retail stores. This will provide a consistent user experience in the event that a customer places orders at more than one retail store. In some embodiments, the user interface may have features that can be turned on and off in accordance with the preference of each retail store. For example, some retail stores may want customers to be able to both view and edit their order, while others may only want viewing rights for the customers (in which case only the order assistants would have editing rights). Of course, in other embodiments, web server 114 may store more than one user interface layout for the customer devices that can be used with different retail stores.
In step 508, when the URL is received at web server 114, it calls the Request Order Assistant application 208 via API 209. In step 510, the Order Assistants database 220 is queried to identify an order assistant that is currently available for assignment to the order, wherein the order assistant is associated with an order assistant identifier. Once an available order assistant has been identified, a notification is transmitted to the order assistant device associated with the order assistant identifier of the identified order assistant, which prompts the order assistant to confirm that he/she is available to provide order assistance to the customer. For example, the order assistant may select an “Accept Request” button that can be selected by the order assistant to accept the request to provide order assistance. Selection of the “Accept Request” button makes a call to a URL associated with web server 114 (e.g., http://myserver.com/AcceptRequest), whereby the order assistant device and the customer device are connected with each other. Next, in step 512, a web page with a user interface that allows placement of an order is generated and transmitted to the order assistant device via API 206. The web page includes the items and pricing associated with the store identifier contained in the order record as retrieved from the Items and Pricing database 224.
Web server 114 stores another user interface layout that is used to generate the web page presented on the order assistant device, i.e., the user interface layout has a predetermined format that allows the inclusion of dynamic values, such as the items and pricing for a particular retail store (similar to the user interface layout for the customer device). In this embodiment, the same user interface layout is used in connection with all of the retail stores that receive order assistance services through system 100 and, as such, the user interface will have the same “look and feel” for all of the retail stores. This will simplify the training process for order assistants (i.e., they will only have to learn a single system). Of course, in other embodiments, web server 114 may store more than one user interface layout for the order assistant devices that can be used with different retail stores.
It should be understood that the user interface layout for the customer device may be the same as or different from the user interface layout for the order assistant device. In some embodiments, the user interface layout for the customer device provides a simple user experience for placing an order, while the user interface layout for the order assistant device provides more advanced features for order placement. Of course, in other embodiments, the user interfaces for both devices are the same or similar.
In step 514, the order identifier and the order assistant identifier are correlated using a transaction identifier. In one embodiment, a record that includes the transaction identifier, the order identifier, and the order assistant identifier are part of a record inserted into a table (e.g., Transaction [transaction_id, order_id, order_assistant_id]). In step 516, the transaction identifier is returned back to the customer device via API 206 in response to the customer's selection of the “Speak with an Order Assistant” button and, similarly, the transaction identifier is returned back to the order assistant device via API 206 in response to the order assistant's selection of the “Accept Request” button. It will be seen that the customer device and the order assistant device both use the transaction identifier to identify themselves to web server 114 during an order session so as to enable the establishment of various connections between the devices.
Of course, it should be understood that the present invention is not limited to the use of a separate transaction identifier to correlate the order identifier and the order specialist identifier. In some embodiments, the order identifier may function as the transaction identifier if the order assistant identifier is stored in the order record. In this case, the order identifier is correlated with the order specialist identifier by virtue of them both being stored in the order record. Other types of transaction identifiers may also be used within the scope of the present invention.
Upon receipt of the transaction identifier, the customer device and the order assistant device each send two connection requests to web server 114—a data connection request and an audio connection request. Alternatively, a single connection request may be made in which data and audio are transmitted on the same connection.
In order to make the data connection request, the user interface of the customer device and the user interface of the order assistant device each make a first call to a URL associated with web server 114, wherein the URL references the transaction identifier. It should be noted that both devices may call the same URL. In this embodiment, each of the calls comprises a Web Socket call (e.g., wss://myserver.com/data/transaction=transaction_id). Of course, other network protocols that enable the creation of a point-to-point data connection could also be used within the scope of the present invention.
In order to make the audio connection request, the user interface of the customer device and the user interface of the order assistant device each make a second call to a URL associated with web server 114, wherein the URL references the transaction identifier. Again, it should be noted that both devices may call the same URL. In this embodiment, each of the calls comprises a WebRTC call (e.g., wss://myserver.com/audio/transaction=transaction_id). Of course, other network protocols that enable the creation of a point-to-point audio connection could also be used within the scope of the present invention.
In some embodiments, the data and audio connection requests may both comprise WebRTC calls. In this case, the customer device and the order assistant device each use a single URL to establish a connection containing both the audio and data in combination.
In step 518, web server 114 receives the data connection request from each of the customer device and the order assistant device and, in step 520, uses the transaction identifier to establish a data connection between the devices. It will be seen that the data connection enables the customer and order assistant to create (i.e., view and optionally update) an order in real-time during the order session. It should be noted that web server 114 will also establish a data connection with POS system 118 if the order assistant device is not a POS terminal of POS system 118, in which case there will be three devices on the data connection, i.e., the customer device, the order assistant device, and POS system 118.
In step 522, web server 114 receives the audio connection request from each of the customer device and the order assistant device and, in step 524, uses the transaction identifier to establish an audio connection between the devices. It will be seen that the audio connection enables real-time audio communication between the customer and the order assistant during the order session.
Referring to
In step 600, web server 114 receives order data during the order session. In some cases, the order data comprises order-related information received in step 404 of the method shown in
For all types of order data, the Update Order application 210 performs a number of functions. First, in step 602, the transaction identifier associated with the received order data is used to determine the order identifier, and then the Orders database 222 is queried to identify the order record associated with the order identifier. Then, in step 604, the order data is stored in the order record. In this embodiment, the order data is used to update the data fields of the order record shown in Table 1 above. For example, when an item is added to or removed from an order, there will be an update to both the order_dates and order_items data fields. Also, when the payment status is changed, there will be an update to the payment_status data field. Other updates to the data fields shown in Table 1 will be apparent to one skilled in the art.
Referring to
In this embodiment, steps 700-706 are performed by Send Order Details application 212, which is triggered whenever new order data is stored in the order record via the function of the Update Order application 210. In step 700, the new order data is identified and, in step 702, it is determined whether the new order data causes a change to one or both of the user interfaces of the customer and order assistant devices. If not, the process ends. This may occur, for example, when the order is picked up. If the new order data causes a change to one or both of the user interfaces, then an order update message is generated in step 704. In step 706, API 214 returns the order update message to one or both of the customer device and the order assistant device over the data connection, as applicable, wherein the device updates its user interface with the new information. Thus, the order may be updated in real-time on the user interfaces of the customer device and the order assistant device so that the order is always synchronized between the devices. Web server 114 may also transmit the order update message to POS system 118 over the data connection if the order assistant device is not a POS terminal of POS system 118.
Referring to
The user interface of the customer device includes a “Finish & Pay” button that can be selected by the customer when the order is complete. An exemplary screen shot of a web page with this button is shown in
When the URL is received at web server 114, it calls the Make Payment application 216 via API 218. The Make Payment application 216 performs a number of functions. First, in step 800, the payment data is received and, in step 812, the payment data is transmitted to the API of payment system 120. In step 804, a payment token is received from the API of payment system 120. In step 806, a new payment record is inserted into Payments database 226 and the payment token is stored in the payment record so the customer can re-use that payment method in the future. The payment token is also stored on the customer device to enable use of the payment token in connection with future orders made via system 100.
In step 808, the payment token along with the total charge of the order is transmitted to the API of payment system 120. In step 810, when the response is received from the API of payment system 120, it is determined whether the payment was approved. If so, in step 812, the “Update Order” application 210 is called to change the payment_status to “authorized” and the order status to “paid” in the order record. This information is then returned to the customer device and the order assistant device (and POS System 118 if the order assistant device is not a POS terminal) via the Send Order Details application 212, as described above.
If the payment was not approved, in step 814, the “Update Order” application 210 is called to change the payment status to “denied” in the order record. This information is then returned to the customer device and the order assistant device (and POS System 118 if the order assistant device is not a POS terminal) via the Send Order Details application 212, as described above. In step 816, it is determined whether the customer entered additional payment data. If so, the process returns to step 800 to repeat the process. Otherwise, in step 818, the order status is changed to “cancelled” in the order record.
It should be noted that web server 114 terminates the audio and data connections between the customer device and the order assistant device once the communications between the customer and order assistant have ended.
Referring to
In step 900, when the order status is changed to “paid,” this information is received by POS system 118 via the Send Order Details application 212 of web server 114. In this embodiment, this change in the order status provides an indication that the order is complete and ready for fulfillment. In step 902, POS system 118 transmits the order details to enable fulfillment of the completed order. For example, if the retail store is a restaurant, the order details (e.g., the order items and an indication of payment, such as the last four digits of the credit or debit card number) may be displayed on a kitchen display screen (KDS) and/or automatically printed by a kitchen printer to enable the staff to start preparing the order. Of course, in other embodiments, the retail store may begin fulfillment of the order prior to completion of the payment process. In step 904, POS system 118 transmits an indication that the order has been picked up to web server 114, at which point the order status is changed to “picked up.” When the order and payment process is complete, the order status may be changed to “complete,” “closed,” or fulfilled,” depending on the process used by the business.
Referring to
In the implementation shown in
In the implementation shown in
It should be understood that the implementation shown in
In the implementation shown in
In the implementation shown in
It should be understood that the implementations shown in
The description set forth above provides several exemplary embodiments of the inventive subject matter. Although each exemplary embodiment represents a single combination of inventive elements, the inventive subject matter is considered to include all possible combinations of the disclosed elements. Thus, if one embodiment comprises elements A, B, and C, and a second embodiment comprises elements B and D, then the inventive subject matter is also considered to include other remaining combinations of A, B, C, or D, even if not explicitly disclosed.
The use of any and all examples or exemplary language (e.g., “such as” or “for example”) provided with respect to certain embodiments is intended merely to better describe the invention and does not pose a limitation on the scope of the invention. No language in the description should be construed as indicating any non-claimed element essential to the practice of the invention.
The use of the terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a system or method that comprises a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such system or method.
The use of relative relational terms, such as first and second, are used solely to distinguish one unit or action from another unit or action without necessarily requiring or implying any actual such relationship or order between such units or actions.
Finally, while the present invention has been described and illustrated hereinabove with reference to various exemplary embodiments, it should be understood that various modifications could be made to these embodiments without departing from the scope of the invention. Therefore, the present invention is not to be limited to the specific systems or methodologies of the exemplary embodiments, except insofar as such limitations are included in the following claims.
This application is based on and claims priority to U.S. Provisional Application Ser. No. 63/195,862 filed on Jun. 2, 2021, which is incorporated herein by reference in its entirety.
Number | Date | Country | |
---|---|---|---|
63195862 | Jun 2021 | US |