The NFC call waiter button built into every table
Tappflow turns each table's NFC tag into a call waiter button: guests tap to call a waiter, request the bill, or ask for water, and a push notification lands on the assigned waiter's phone instantly. No arm-waving, no wandering laps of the floor, no expensive pager hardware.
Free 30-day trial · No credit card · Cancel any time
- Call waiter, request bill, request water — plus any custom request you configure
- Push alerts go straight to the phone of the waiter assigned to that exact table
- Tap-again confirmation and rate limiting block pranks and accidental triggers
Guests who can't get attention stop spending
The second round of drinks never gets ordered because nobody came back to ask. The table that's been waving for the bill for ten minutes leaves a worse review than the food deserved. Meanwhile your servers burn entire shifts walking laps of the floor just to check who needs something — and on a packed Friday night, the quiet tables in the corner simply get missed. Dedicated pager systems fix some of this, but they cost real money, need charging docks, and add one more gadget to break.
Second drinks and desserts never ordered because no one asked
Guests summon service the moment they want something — while the impulse is still there
Servers doing constant check-in laps instead of serving
Requests come to them, routed by table assignment, so every lap has a purpose
Guests waiting on the bill when they're ready to leave
A bill request from the table starts the checkout before frustration sets in
Pager hardware, charging docks, and central tablets
Runs entirely on the phones your staff already carry
Service requests routed to the right phone, instantly
Each table gets an NFC tag bound to it in your table inventory, organized by zones. A guest's first tap opens a short-lived table session where they can browse the menu and send service requests — call waiter, request bill, request water, or any request type you configure with your own labels, icons, and colors. Every request fires a real-time web push notification to the phone of the staff member assigned to that table, who marks it handled from a mobile-first dashboard. Abuse is designed out: a tap-again confirmation verifies the guest is physically at the table, requests are rate-limited and deduplicated, sessions expire automatically, and repeat offenders can be blocked by device. It's a full table service system with zero extra hardware.
One tap to call, request, or ask
Guests tap the table tag and choose what they need — call waiter, request the bill, ask for water, or anything else you've configured. The request is timestamped with the table number, so staff know exactly where to go and what to bring before they leave the pass.
Push notifications to the assigned waiter's phone
Requests don't blast the whole team. Per-staff table assignments route each alert to the phone of the waiter responsible for that section, with real-time web push delivery. A mobile-first staff dashboard shows open requests, and one tap marks them handled so nothing gets served twice.
Anti-prank protection built in
A tap-again confirmation using short-lived tokens proves the guest is physically at the table before a request fires. Requests are rate-limited, deduplicated, and auto-expired, each table runs one active session at a time, and device-based blacklisting shuts down anyone treating your service button like a toy.
Custom request types for how your floor actually runs
Beyond the built-in call waiter, bill, and water requests, create your own request types with custom labels, icons, and colors — refill the shisha coals, bring the dessert menu, call the manager. The service menu matches your concept instead of forcing your concept into someone's template.
No tablets, no pagers, no new hardware
The whole system runs in the browser on the phones your staff already carry — no central tablet by the pass, no charging docks, no proprietary pagers to buy and replace. Staff clock in, see their assigned tables, and start receiving requests within minutes of joining.
How the call waiter system works
From a guest's impulse to a waiter's phone in seconds — here's the flow on a busy night.
Bind an NFC tag to every table
Set up your table inventory with zones and codes, then bind an NFC tag to each table. The tag's link never changes — the dashboard controls where it points.
Guest taps and opens a table session
The first tap opens the menu and starts a short-lived session for that table. One active session per table keeps requests tied to real, seated guests.
Guest sends a request, confirms with a second tap
They pick call waiter, request bill, water, or a custom request. A quick tap-again confirmation verifies they're physically at the table before anything fires.
The assigned waiter's phone buzzes
A push notification with the table number reaches the staff member assigned to that section. They handle it and mark it done from the mobile staff dashboard.
“Every 'can we get the bill?' answered before it's asked twice — with the staff you already have.”
1
tap for a guest to summon service to their table
0
tablets, pagers, or extra hardware required
2
taps to confirm a request is real — pranks blocked by design
Frequently asked questions
Everything owners ask about real-time table service before switching.
You assign staff to tables (or whole zones), and each request sends a real-time web push notification to the phone of whoever is assigned to that table — with the table number and timestamp. Staff see open requests on a mobile dashboard and mark them handled so the team never doubles up.
Several layers. A tap-again confirmation with short-lived tokens proves the sender is physically at the table. Requests are rate-limited, deduplicated, and expire automatically; each table allows one active session at a time; and device-based blacklisting blocks repeat abusers entirely.
No. Everything runs in the mobile browser on the phones your staff already carry — notifications arrive as web push alerts. There's no app to install, no central tablet to buy, and no pager hardware to charge or replace.
Yes. Alongside the built-in call waiter, request bill, and request water options, you can create custom request types with your own labels, icons, and colors — whatever your floor needs, from coal refills at a shisha lounge to a dessert-menu request at a bistro.
Table sessions are short-lived and expire automatically. Once a session ends, that tag can't send requests until someone at the table taps again — so requests always come from guests who are actually seated, not from someone who scanned earlier.
Works better together
Every Tappflow feature runs on the same tags, tables, and dashboard — turn one on and the rest are a click away.
See it live at your own tables
Set up in an afternoon, test it through a real weekend service, and keep it only if your team does.
Free 30-day trial · No credit card · Cancel any time