Waiter — the floor seen from your home page
You walk in two hours before service. You need to know what’s on tonight, who’s booked, and what to say if a guest asks about nuts.
The rule
Your home page answers “what do I need before this table sits down?” The kitchen’s answers a different question, the owner’s another. Open the one that matches what you’re about to do.
What your role shapes
- Your home page leads with tonight’s service — what’s on, who’s booked, and the assistant.
- Your assistant knows the menu. “Is the pistacchio pizza nut-free?” returns the actual answer from the recipe and the allergen card: no, it has Bronte pistachios and pistachio cream, and the dough has gluten. “What pairs with the wagyu burger?” gives you three options across price tiers from your own wine list.
- Your alerts are the floor’s. You don’t get the supplier ping or the cash reconciliation. The phone stays quiet for things that aren’t yours.
That’s the difference between a confident waiter and one who disappears into the kitchen every time a guest asks something.
Asking mid-service
The floating Ask button sits on every screen, so you can answer a guest without losing your place. It opens a small panel; close it and you’re exactly where you were.
If the question is genuinely outside the menu — a custom request, an undeclared dietary need — it routes you to the kitchen rather than guessing. That’s the right behaviour: it knows what it knows.
Related features
- Roles and capabilities — the permissions under the persona
- How the AI thinks about your menu — where those answers come from
- Head chef — the same data, framed for the kitchen