How Diners Order

A guest at the table scans the QR code and lands in a chat. There's no app to install and nothing to download. From that chat they browse your menu, ask questions, and place the order in their own words. This guide walks you through what your guests see, so you know what's happening on the other side of the table.

The first screen

When a guest scans, the chat opens right away. They can enter a phone number, and they can also add a name, a preferred language, and a diet preference if they want to.

The phone number matters most. It becomes the order's identifier at checkout, so you can tie the order to the table and the guest.

Browsing the menu

Guests browse your menu by category, the same categories you set up. Each item shows:

• Its name and price.
• A short description of the dish.
• Diet tags, like veg or vegan.

Only the items you've marked available show up in the chat. When you mark a dish unavailable on the menu page, it simply drops off the guest's menu and they can't order it. There's no automatic "sold out" badge tied to a stock count, and your inventory counts never change what a guest sees. You decide what's on the menu by hand.

Adding to the cart

A guest adds items to a cart and sets the quantity for each. The cart shows a running total as they go, so they always know what the bill is shaping up to be before they confirm.

Chatting in their own language

Here's the part guests tend to love. They can chat naturally in English, Hindi, Kannada, Tamil, or Telugu. Mixed phrasing works too, so a guest who types half in Hindi and half in English still gets a clear answer.

The AI answers questions about the menu, applies any active offers, and suggests a pairing to go with the order. You set up both of those behind the scenes. See offers and discounts for how the discounts work, and pairings and upsell for how the suggestions are built.

Checking out

When the guest confirms, the phone number they entered earlier is used as the order's identifier. The order then moves straight to your kitchen board, ready for your staff.

If you've turned on the optional Require waiter confirmation before the kitchen setting (it's off by default), a new order waits in the waiter app instead. A waiter checks the table has a real guest and taps Confirm, and only then does the order reach the kitchen board. It's there to block fake remote orders from someone who scans your QR off-site. See settings and branding for how to turn it on.

FAQ

Do guests need an app to order?

No. A guest scans the QR code on the table and a chat opens in their phone's browser. There's nothing to install and nothing to download. They browse the menu, add items, and order right there in the chat.

Is a phone number mandatory?

The phone number is the order's identifier at checkout, so it's the key detail a guest enters. A name, preferred language, and diet preference are optional extras they can add if they want a more tailored chat.

Which languages can guests use?

Guests can chat in English, Hindi, Kannada, Tamil, or Telugu. Mixed phrasing is fine too, so someone typing part of a sentence in Hindi and part in English still gets a clear, useful reply from the AI.

What if a dish is unavailable?

Items you've marked unavailable on the menu page simply don't show in the chat, so a guest can't add them. There's no automatic "sold out" badge driven by a stock count, and inventory counts never change the diner menu. You decide what's on by toggling each item's availability yourself.

Can an order be held before it reaches the kitchen?

Only if you turn on the optional "Require waiter confirmation before the kitchen" setting, which is off by default. With it on, a new order waits in the waiter app until a waiter taps Confirm, then it lands on the kitchen board. A waiter can also reject an order that looks fake, and a rejected order never reaches the kitchen.

What to do next

Now that you know what guests see, set up the things the AI uses to sell. Start with offers and discounts so active deals show up in the chat.