Floor intelligence guides
Staff paging and alerts: buzz one person, not the whole floor
Most restaurant alerting fails the same way: a radio call or group message goes to everybody, everybody assumes somebody else has it, and the one time it mattered is buried under thirty times it did not. Good paging is a design problem, and the rules are known.
Why group alerts breed silence
When an alert reaches five people, responsibility divides by five. Each person reasonably assumes someone closer or less busy will take it, and often everyone is right about someone else. Add volume, and staff learn that most alerts are not theirs, so they tune all of them out. The fix is not louder paging; it is narrower paging.
Five rules for alerts that get answered
- One owner per alert. The server whose section it is, or the busser whose zone it is. Named, not “whoever”.
- Escalate on silence, do not broadcast. If the owner has not responded in a set time, the alert moves up to the manager, alone.
- Close alerts automatically. If arriving at the table clears the alert, nobody has to remember a confirmation tap mid-rush.
- Cap alerts per person per hour. A device that buzzes rarely gets answered always.
- Screen first, buzz second. Most states belong on a silent display; only the time-critical ones deserve a vibration.
Pick the right trigger, not just the right device
Guest pagers, kitchen bump bars and call buttons all answer narrow questions. The trigger that covers the whole floor is table state: seated too long without a visit, or empty and dirty while there is a wait. Those two conditions catch most of the money, and neither requires a guest to press anything or a cook to remember anything. Phones and smartwatches your staff already carry are better receivers than dedicated pagers: nothing new to buy, charge or lose.
How TableWave applies the rules
TableWave watches table states through your existing CCTV and applies all five rules out of the box: the alert goes to the one person covering that table, escalates to the manager only on silence, clears itself when the camera sees someone arrive, respects a per-person hourly cap, and leaves everything else on the silent host screen. The first nights run in quiet mode, logging alerts without sending them, while thresholds are tuned to your floor. Alert rules are included in every plan on the pricing page, and a 30-day pilot lets your team feel the difference on a real weekend.
Questions owners ask
Will phones buzz all night?
No. The host screen absorbs everything silently; only a table crossing your attention or cleaning threshold buzzes one person, once, with an hourly cap per person. Most shifts, a server feels a handful of buzzes, each one genuinely theirs.
What devices do staff need?
The phones or smartwatches they already carry. Starter supports alerts to up to 5 devices and Pro up to 6. The host screen is any TV or tablet; it needs no internet to keep working.
What if someone just ignores their alerts?
The escalation answers that operationally: unanswered alerts reach the manager, with the table and the elapsed time. It creates accountability per table without per-employee scoring, which TableWave deliberately does not do.
Do alerts work if the internet drops?
The floor map, timers and host screen keep running, because everything is processed on the computer inside your restaurant. Push alerts to phones need internet to travel; the screen does not, so the stand always has the truth.
Prove it on your own floor
The 30-day pilot is paid, on purpose: you cover your plan’s setup fee, we install in person, and you read your own payback report before any monthly billing starts.
The install is $1,500. If it earns its keep in 30 days, your first month’s on us. If it doesn’t, we take it out and you owe nothing more.
Prices in USD, before tax. Setup is non-refundable once installed; monthly starts only if you continue.