Add to cart, send to the kitchen, and the order is in your POS as a ticket. Guests pay with the server or in-app on your processor. $0 per order, no card ever crosses our system.
Some restaurants want guests ordering from the phone. Some want the waiter to take it, the way they always have. It's one switch, and you still get the numbers either way.
Guests read, browse, like, join the list. They tell the server what they want. We read every sale from your POS, so "ordered 242 times this week" and the For You pairs are real. Zero integration risk; works on every POS on day one.
Add → Send to kitchen. The ticket lands in your POS with the table number. Pay with the server, or pay in-app through your own Square or Clover account. Per-guest history becomes exact — that's the campaign engine.
Every table gets its own QR link, numbered the way your POS numbers it. When a guest scans, the menu shows your floor plan in grey with their table highlighted and asks them to tap the chair they're in. An email is optional. That's it — no table number to type, no app, no login, no extra step for your staff. Chair + table + the POS ticket is who ordered what.
A button on every menu. Tapping it sends a zero-dollar ticket to the pass with the table number. Nobody has to feel forced onto a phone.
"The QR on the table has the whole menu in your language, with stories and the team's picks. Any questions, I'm right here — or I can grab you a paper one." That's the script. Tips don't change.
"I saw you sent in the burger and the wings — anything to drink?" The ticket's already in. Their job gets faster, not smaller.
When a guest pays in-app, the card form is your POS's own tokenised field. The money lands in the account you already have, at the rate you already pay. We never see a card number, which also keeps you — and us — out of PCI scope.
When a guest closes their tab from the phone, the card on file is charged through your processor and the menu asks one question: how was everything? Three faces. A happy face goes straight to your Google review page, in the same tab, no app switch. Anything less opens a box that goes to you — not to Google.
Modifiers, sizes and add-ons carry through. The phone already knows their name and points if they've been before.
Your Square or Clover secure card field; we never see the number. Nothing is charged until they close out. If they forget, the tab closes itself after 12 hours — a switch you control.
Table number attached. On Square it goes to the KDS; on Clover it opens on the device. Where a POS can't accept outside orders, we print or text the ticket to the pass.
No app, no login, no account creation. Their email — given at checkout — now carries everything they did before.
Whether it came from the phone or the waiter, each ticket updates "ordered this week", the For You pairs, and the guest's history.
We poll your POS for availability every minute or two. The kitchen marks the branzino out at 7pm; by 7:02 it's greyed on every table, and nobody orders it, and nobody has to be told "sorry."
No. Zero, on every plan, forever. We're a subscription, not a marketplace.
No. It sits in front of it. Square and Clover connect directly; Toast connects for menu and sales today, and for order push through their partner programme. If a POS can't accept outside orders, the ticket prints or texts to the kitchen and a server keys it in — we'll tell you which applies before you pay for it.
Handled by your processor's own form when paying in-app, exactly as with any card payment; or by the server as today.
Yes. Pickup is a mode on the same cart; the ticket says pickup and carries the name. Phone orders through the voice agent land the same way.
Menu mode, fully: your menu, prices, modifiers and 86 status pulled from Toast, every sale read back so the numbers are real. Ordering mode on Toast needs their partner programme — see Integrations for the honest version.
Twenty minutes, no pressure. You'll be looking at your own menu, in your guests' languages, before we've said hello.