The call, on the waiter's lock screen.
A guest calls the waiter from the table — the notification drops onto every active waiter's phone, tablet, and watch. The first to accept, owns it. Simple, fast, easy for anyone to use.
It works in five steps
Customer calls → notification to active waiters → appears on lock screen → someone accepts → served, call closed.
Customer calls
"Call Waiter" from table QR
To the active ones
Only waiters active right now
Lock screen
Phone · tablet · watch alert
Accepts it
A waiter taps and owns it
Resolved
Served, call closes
In the waiter's pocket
The moment that matters: the notification appearing on the active waiter's lock screen. When the app opens, every pending call is on the live list.
Same alert, one tap on the wrist.
Paired Apple Watch and Wear OS watches buzz the call on your wrist — you see it while walking the floor, without pulling the phone out.
The operator's single control
No complex shifts or roles. A simple list: who receives notifications? Active/passive with one tap — instant effect. Set a waiter on leave, on break, or off-shift to passive; that's it.
Waiters
Simple — with every scenario thought through
"Simple" doesn't mean incomplete; it means avoiding unnecessary complexity. Every critical situation has a straightforward answer.
| Scenario | How it's handled |
|---|---|
| Waiter on leave / off-shift | The operator sets them passive from the list → no notification. One tap, instant. |
| On a break | Same instant active/passive toggle. Back to active with one tap when they return. |
| No active waiter | safety net The call still appears in the panel (live console) — the operator always sees it. |
| Device offline / notification missed | When the app opens, the live list shows what's waiting. Multiple active waiters = redundancy. |
| Two waiters open it at the same time | single owner The first to accept owns it; others see "Mehmet accepted." No double service. |
| One waiter, multiple devices | Phone + tablet + watch alert simultaneously; whichever accepts first is authoritative. |
| Waiter left the job | The operator removes them → device subscription drops, no more notifications. |
Frequently asked
Do I need extra hardware?
No. If your QR menu is live, activating the module is enough. No bells, tablets, buttons — none required. Staff phones or a counter tablet can open the console.
Do staff need a new account for this?
Yes, but this account only sees the Calls Console. It cannot access menus, prices, settings, or reports. A separate permission tier for menu safety.
How is it protected from trolls?
Repeat calls from the same table merge into one card. A per-device reasonable cap. Long-waiting calls auto-close. A problem table can be silenced with one tap — without disturbing the guest experience.
Can we really measure our service speed?
Yes. Your average response time appears live in the console. Track weekly averages, compare across shifts. Answer "Is our service quality improving?" with a number.
Does it appear for takeaway orders?
No. Only dine-in guests see it. For takeaway you have WhatsApp/phone flows; a waiter call makes no sense there and is hidden.
Related features
Your menu now calls for service.
See the panel demo, watch the flow live. If you like it, it opens in 1 hour and works in your QR menu right away.
Screens are illustrative — real data are the business's own waiters and tables. · QrMenum design studio
