Voice and context recognition for bill creation
US-2015348144-A1 · Dec 3, 2015 · US
US10762484B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-10762484-B1 |
| Application number | US-201514871640-A |
| Country | US |
| Kind code | B1 |
| Filing date | Sep 30, 2015 |
| Priority date | Sep 30, 2015 |
| Publication date | Sep 1, 2020 |
| Grant date | Sep 1, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Techniques and arrangements for analyzing previous tickets of a customer at different merchants—specifying interactions of the customer at the different merchants—to determine subsequent recommendations to send to a particular merchant in real-time when the customer is located at the particular merchant. Other techniques and arrangements facilitate annotation of merchant tickets by the merchants to enrich the data maintained by the tickets and, in some instances, to enhance the described real-time recommendations. Still other techniques and arrangements create a merchant ticket for recording interactions between a merchant and customer upon the customer creating a reservation at the merchant for a specified future time, or being added to a waitlist of the merchant. Upon the customer arriving at the merchant proximate to the specified future time, the merchant may use the created ticket to track items ordered by the merchants, track tenders used to pay for items, and the like.
Opening claim text (preview).
What is claimed is: 1. A method comprising: obtaining, by one or more servers associated with a payment service, a first open ticket data structure generated by a first instance of a merchant application executing on a computing device of a first merchant, contents of the first open ticket data structure indicating: (i) a set of items ordered by a particular customer from the first merchant, (ii) for each item of the set of items, a time at which the particular customer ordered the respective item from the first merchant, and (iii) a start time of an engagement between the first merchant and the particular customer, wherein the first instance of the merchant application configures the computing device as a first point-of-sale (POS) device for obtaining payment information associated with a first payment instrument via an associated payment reader and transmitting the first open ticket data structure to the one or more servers; receiving, at the one or more servers, an indication that a second open ticket data structure has been generated by a second instance of the merchant application executing on a second POS device of a second merchant that is different than the first merchant, wherein the second open ticket data structure is generated in association with an engagement between the second merchant and the particular customer, and wherein the second open ticket data structure includes an indication of a start time of the engagement between the second merchant and the particular customer; analyzing, by the one or more servers, the contents of the first open ticket data structure; estimating, by the one or more servers and based at least in part on the analyzing, a future time at which the particular customer is likely to request a particular item from the second merchant, wherein the future time is prior to an end of the engagement between the second merchant and the particular customer, and wherein the future time comprises at least one of a time of day or an amount of time after the start time of the engagement between the second merchant and the particular customer; and sending, by the one or more servers and to the second POS device of the second merchant and prior to the future time, a recommendation that the second merchant offer the particular item to the particular customer at the future time, the recommendation for display on the second POS device as an annotation as part of the second open ticket data structure. 2. The method as recited in claim 1 , wherein the analyzing comprises analyzing the first open ticket data structure to determine that the particular customer ordered the particular item from the first merchant a certain amount of time after: (i) beginning the engagement with the first merchant, or (ii) ordering another particular item from the first merchant. 3. The method as recited in claim 1 , wherein the recommendation comprises a first recommendation, the method further comprising: estimating, based at least in part on the analyzing, another future time prior to the end of the engagement between the second merchant and the particular customer, at which the particular customer is likely to request a bill for a cost of items ordered from the second merchant, wherein the other future time comprises at least one of another time of day or another amount of time after the start time of the engagement between the second merchant and the particular customer; and sending, to the second POS device of the second merchant and prior to the other future time, a second recommendation that the second merchant offer the bill to the particular customer at the other future time, the second recommendation being for display on the second POS device as another annotation as part of the second open ticket data structure. 4. The method as recited in claim 1 , wherein the recommendation comprises a first recommendation, the method further comprising: receiving, by the one or more servers, current contents of the second open ticket data structure; determining, from the current contents of the second open ticket data structure, that the particular customer has ordered another particular item from the second merchant; estimating, based at least in part on the analyzing, another future time prior to the end of the engagement between the second merchant and the particular customer, at which the particular customer is likely to request another instance of the other particular item from the second merchant, wherein the other future time comprises at least one of another time of day or another amount of time after the start time of the engagement between the second merchant and the particular customer; and sending, to the second POS device of the second merchant, a second recommendation that the second merchant offer another instance of the other particular item to the particular customer at the other future time, the second recommendation being for display on the second POS device as another annotation as part of the second open ticket data structure. 5. A method comprising: obtaining, by one or more servers associated with a payment service, a first data structure generated by a first instance of a merchant application executing on a computing device of a first merchant, contents of the first data structure indicating at least one of: (i) a set of items ordered by a particular customer from the first merchant, (ii) for each item of the set of items, a time at which the particular customer ordered the respective item from the first merchant, and (iii) a start time of an engagement between the first merchant and the Particular customer, wherein the first instance of the merchant application configures the computing device as a first point-of-sale (POS) device for obtaining payment information associated with a first payment instrument via an associated payment reader and transmitting the first data structure to the one or more servers; receiving, at the one or more servers, an indication that a second data structure has been generated by a second instance of the merchant application executing on a second POS device of a second merchant that is different than the first merchant, wherein the second data structure is generated in association with an engagement between the second merchant and the particular customer, and wherein the second data structure includes an indication of a start time of the engagement between the second merchant and the particular customer; analyzing, by the one or more servers, the first data structure; determining, by the one or more servers and based at least in part on the analyzing, that the particular customer is likely to make a request to the second merchant; estimating, based at least in part on the analyzing, a future time at which the particular customer is likely to make the request to the second merchant, wherein the future time is prior to an end of the engagement between the second merchant and the particular customer, and wherein the future time comprises at least one of a time of day or an amount of time after the start time of the engagement between the second merchant and the particular customer; and sending, by the one or more servers and to the second POS device of the second merchant and prior to the future time, a recommendation that the second merchant initiate a communication with the particular customer related to the request, the recommendation for display on the second POS device as an annotation as part of the second data structure. 6. The method as recited in claim 5 , wherein: the request comprises a request for a particular item; and the recommendation comprises a recommendation that the second merchant initiate a communication regarding whether the particular customer would like to order the particular item.
Establishing or using transaction specific rules · CPC title
involving fraud or risk level assessment in transaction processing · CPC title
Keeping log of transactions for guaranteeing non-repudiation of a transaction · CPC title
specially adapted for electronic shopping systems · CPC title
replenishment orders; recurring orders · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.