Your restaurant just learned to talk.
A guest asks what's in a dish and gets an answer immediately -
with a photo and a price, from your own menu. They order when they're
ready, and it comes to you for approval.
No notepad. No waiting. No app to download.
The same team, more tables
Writing orders down, reading the menu out and answering questions about dishes are most of the walking a waiter does on a busy night. The app takes those. What's left is the part that needs a person - serving, reading the room, looking after whoever needs looking after. And the control stays with you:
Every order stops at a human
It appears on your screen and waits. One tap, and only then does it reach the kitchen.
Allergies and special requests
Swap an ingredient, no onion, something that would make a guest ill - it stays on every ticket to the end of the meal. It doesn't depend on who took the table remembering, and it doesn't vanish at shift change.
"Call a waiter" is a button
Your staff see it with the table number. You answer from there, and the guest sees that.
Sixty seconds, from the table to the kitchen
A guest scans, asks what's in a dish, orders - and the staff approve it before the kitchen sees it. The waiter understands what the guest actually asked for, even half-said, and always checks with them before the order reaches you.
From there most of the work - happens by itself
- The guest scans
A QR on the table, and the waiter opens the conversation. In Hebrew, English or Arabic.
- Asks and requests
What's in a dish, water, cutlery - without ordering anything. They get an answer, and it all stays in the chat.
- Orders, and you approve
The order waits on your screen with the price the till will charge.
- The kitchen gets a ticket
In the house's own language, with the table's sensitivities and notes.
- The table updates itself
Started, ready, served - written into the chat automatically.
Your menu - without typing a single dish
Send us a link to your menu - your site, a PDF, or your ordering page - and we load it: names, descriptions, prices, photographs and serving hours. A breakfast that ends at noon ends by itself. If you publish an English menu, that gets loaded too, in your own words.
Not just ordering. The table's whole evening.
From the moment a guest sits down to the moment they get up and go. It already works - there is nothing here to build.
Paying from the table
The guest pays in the chat without waiting for someone to come over with a terminal. Bills can be split.
A guest who comes back
They come back another evening on the same phone, and the waiter already remembers what they liked and what they react to.
A kitchen screen
Every ticket by table, with how long it has been waiting. The table updates itself at each step.
Requests from the table
Water, cutlery, a question for the staff - it reaches you with the table number, and you answer from there.
A floor board
Every table and what's happening at it right now: free, seated, waiting for approval, in the kitchen, asking for the bill.
A menu that knows the time
Breakfast comes off at noon by itself, and the lunch deal appears and disappears on its own hours.
Closing the day
A table left open at the end of the evening closes itself, without anyone having to remember.
Connecting to the till
Still in development. If your POS allows it, we'll check it with you before the pilot.
Common questions
Does it connect to our POS?
It depends on the till - and we check that with you before we start. Tell us which one you run, and if it can be connected we'll do it as part of the pilot. If it can't, the order lands on a separate screen and your staff key it in the way they would an order given out loud.
What happens if the internet goes down?
The chat stops working and your waiters carry on exactly as they do today. Nothing in the restaurant depends on it: your till, your kitchen and your service don't run through us.
What does the staff have to learn?
One screen with an approve button. That's it. We walk through it with you in ten minutes on the first day, and there's nothing to install on anybody's device.
What about guests who don't want a chat?
They order from a waiter as usual. The QR is an option on the table, not a condition - and the chat itself has a button that calls a waiter.
Who's responsible if it says something wrong?
It answers only from the menu you gave it, and it never promises a guest that a dish is safe for an allergy - it refers them to your staff. And every order passes a human before the kitchen, so a mistake is caught before it becomes a plate.
What does it cost?
The pilot is free. We'll talk about what comes after it, after it.
THE NEXT STEP
A pilot on four or five tables, one month, free
Not the whole restaurant and not forever. One corner, one month, to see how guests take to it and what it does for your waiters at the busy hours.
- ✓No cost - the first month is on us, and no card.
- ✓Nothing to install - a printed QR on the tables, that's all.
- ✓Nothing changes for your staff - one screen, one approve button.
- ✓No commitment - stop whenever you like and take the codes down.
Who we are
We have both spent years building complex systems for clients - large organisations and small businesses alike. We are building this one to the same standard.