The phone rings during the rush
Everyone is plating. It rings out.
Customers ask about the menu, allergies, delivery and prices at the worst possible moment. Answer all of them, recommend the right dish, and take the order — without anyone stopping what they are doing.
No self sign-up: we create the restaurant with you.
They lose them when nobody is free to answer, help, or take the order.
None of these customers said no. Nobody was free to say yes.
Everyone is plating. It rings out.
Nobody sees it for forty minutes.
There is no one to recommend anything.
Nothing was wrong with the food.
The same conversation, answered. Watch where it goes.
One question. Six turns. An order that is €9 bigger than the one they came for.
It sits between your customers and your restaurant. It knows your menu, your hours and your rules, answers in the language the customer wrote in, and hands the order to your kitchen the same way your own staff would.
Channels marked “coming soon” are not connected yet. Nothing here is sold before it works.
A message, a call, your ordering page. Whichever door they use.
Not keywords — the actual request, in the language they wrote it.
What is on, what ran out, how far you deliver, what you charge.
The dish that fits the question, then the side that fits the dish.
On the same board your team already works from.
Answering is the floor. Everything below it is what turns an answered question into a bigger order — and none of it asks your team for a minute.
“Is the lasagne gluten free?” gets an answer, not a PDF to scroll through at the till.
Someone undecided is someone about to leave. A recommendation is the difference between browsing and ordering.
Offered once, after they chose — the moment a waiter would ask, not before it.
Drinks with the burger, dessert with the table. Your combinations, not generic ones.
An order abandoned mid-conversation is a customer who was already buying.
A conversation that ends in a question ends. One that ends in an order reaches your kitchen.
Nobody was upsold. They were asked one question at the moment a waiter would have asked it.
An illustration, not a measurement. The figures come from this page's demo basket — see config/demo.json — and describe no real restaurant.
Every answer, every order and every suggestion that landed — on one screen, in your restaurant's own numbers.
The figures on this screen are demonstration data. No customer's results are shown anywhere on this page.
Whichever door a customer uses, the order lands on the same board, against the same menu, in the same numbers.
Not by charging more. By answering the customers nobody had time for.
The reply goes out while the question is still fresh, not after service.
Nobody stops plating to read a message or repeat the opening hours.
The side gets offered every time, not only when someone remembers.
The message at 19:43 gets an answer at 19:43.
What they ask, what they order, what they order again.
There are no customer stories on this page yet because there are no customers yet. These are the terms for being one of the first.
10 placesYou reach the people building it, not a ticket queue. There are few enough of you that this is a promise rather than a slogan.
Your restaurant is created for you and the first menu is entered with you, so the work on your side is a conversation rather than a form.
Nothing about the roadmap is fixed. What the first restaurants ask for is what gets built first — phone, WhatsApp and the rest are in that order for a reason.
No price is attached to this, because no price has been set. It is not a discount — it is who you talk to and how much say you have.
The plans below are the shape it will take. The numbers are not decided, and inventing one here would be the first thing on this page that is not true.
One restaurant, taking orders.
One restaurant, answering and selling.
Several units under one brand.
Every answer below describes what the platform does today, not what is planned.
No — and you do not need to do anything with it yet, because the platform does not answer calls at the moment. It works through your ordering page and online orders. When calls are connected, the intention is that your number stays yours.
Yes. The customer writes in theirs and you read the order in the language you set for the restaurant. That is the part that works today across every channel that is connected.
Not yet. There is no hand-over to a person, so anything it cannot resolve stops with an honest answer rather than being passed along.
Your menu lives in the panel — name, price, photo, what is out of stock, extras. There is no import from a till system today, so the first entry is typed in.
Yes, in three ways. It answers from documents you upload, it follows a tone you write, and it can only do a small fixed set of things: read the menu, take an order, give your hours. It cannot invent a discount.
It says so. It does not guess, and — see above — it cannot hand the conversation to a person yet, which is the honest limit of it today.
Yes. A live board that moves from new to accepted to ready, with the ones running late marked.
There is no contract, because there is no price yet. When there is, cancelling will be a button in the panel.
Your restaurant is created for you. The work on your side is the menu — a short one is an afternoon.
Not today. There are no till or delivery-app integrations, and orders live on the platform's own board.
Give every conversation a chance to become a sale.