A QR code waiter call system lets guests reach your staff from the menu on their phone: one tap for a waiter, the bill, water or a custom request. Your team sees who needs what, at which table, on a live board – no buttons to install, no batteries, no wiring.
It uses the table QR code that already opens your menu – nothing extra goes on the table.
The menu opens with the table attached, and the service button sits at the bottom of the screen, within thumb's reach.
Call a waiter, request the bill (and say cash or card), ask for water or type a short custom request such as “an extra chair, please”.
The request appears instantly on the live board with the table name, request type and an optional sound alert. The guest sees “Request sent, we are on our way.” in their language.
A waiter marks the request as acknowledged, then resolved. Everyone on the floor sees who is handling what, so two people don't walk to the same table.
Every guest knows the moment: the plates are cleared, the bill is the only thing left, and nobody is looking your way. Every waiter knows the other side: six tables, one pair of hands and no idea which table has been waiting longest.
A waiter call system closes that gap. Guests say what they need without raising a hand, and your team sees requests in order, with the table name and the type of request. A water refill and a bill request are no longer the same wave across the room.
Hardware call buttons solve part of this, but they need a device on each table, a receiver and batteries. A QR waiter call works with the code that is already on the table for your QR code menu, and it tells you exactly what the guest wants.
Waiter calls are part of the ordering add-on for Qdestera Menu. You can switch them on without taking orders.
Call a waiter, request the bill, ask for water or send a custom request with a short note. The bill request lets the guest say whether they will pay by cash or card, so the waiter brings the card terminal only when it's needed.
Impatient taps happen. Qdestera accepts one request of each type per table within a minute; further taps show the guest a friendly “already sent, please wait a moment” message instead of creating new alerts. A photo of the table code shared online can't flood your board either.
Group your tables into zones such as Terrace, Garden or Upstairs, and assign each team member to their zones. On the live board, the “my zones” view shows a waiter only the tables they look after, while managers can filter by zone or branch.
Requests and orders share one live board that updates on its own. Turn on sound alerts, and each card shows how long it has been waiting; anything older than 15 minutes is highlighted. Every request can also be sent to your own systems as a signed “service requested” webhook.
All three get a waiter to the table eventually. They differ in what they cost to set up and what your team learns before walking over.
| Waving and waiting | Table call button | QR waiter call | |
|---|---|---|---|
| Device on each table | None | Button and receiver | None – uses the table QR code |
| Says what the guest needs | No | Depends on the model | Yes |
| Routes the request to the right waiter | No | Depends on the model | ✓ Staff zones |
| Works in the guest's language | No | No | Yes |
| Guards against repeat calls | No | Depends on the model | Yes |
| Shows up in your menu analytics | No | No | Yes |
A line on the table tent – “Scan to see the menu or call your waiter” – makes the feature visible from the first visit.
Use the names your staff already use on the floor, so nobody has to translate “Zone B” into “the back terrace”.
Browsers only play sound after a click, so tap the sound button when you open the live board.
Decide that the waiter who acknowledges a request also resolves it. The board then shows a clean picture of what is still open.
Many water requests on the terrace? Put a carafe on the table. Long waits for the bill? Bring it with the coffee.
Open the live menu demo on your phone and see how a menu looks and feels to guests at the table.
No. Guests use the QR code on their table, and your team uses the live board in a browser. There is nothing to install on the tables.
No. The call button is part of the menu page that opens in the phone's browser after scanning the table code.
Only one request of each type per table is accepted within a minute. Further taps show the guest that the request has already been sent.
Yes. The bill request lets them say whether they will pay by cash or card, so the waiter comes prepared.
Yes. Waiter calls and ordering are separate switches in your menu settings. Both are part of the ordering add-on – see the pricing page.
Requests appear instantly on the live board with an optional sound alert and a browser notification when the tab is in the background. Staff zones show each waiter their own tables.
The guest buttons and messages are available in Turkish, English, German, French, Spanish, Russian and Arabic. Other menu languages use the English labels.
Waiter calls need a valid table code; the general menu link can't send them. You can deactivate any table's code at any time, and the cooldown filters repeat calls.
Yes. Every request can be sent as a signed webhook to an address you choose, for example your POS or a staff paging tool your developer connects.
Switch on waiter calls in your QR menu and see every request on one live board.