Waving doesn't scale
Booths, patios, a pool table on the far side. The guest is out of eyeline and stays that way until someone walks past.
A little signal. A better service.
Water. A coal change. The check.
One little tap. Everything starts moving.
Actual product screens · isolated sample venue
Made for rooms like these
The actual problem
Booths, patios, a pool table on the far side. The guest is out of eyeline and stays that way until someone walks past.
It tells a server that table 12 wants something. They walk over, ask, walk back, and return with it. Two trips for one glass of water.
The table that waited eleven minutes doesn't complain. They just don't come back, and you never learn which table it was.
How it works
Actual OnCue screens · sample venue
A chip under the table edge, or a printed code. It opens a page — no app, no download, no wifi login. Two seconds.
Coal change. Water. The check. Your list, your words. Specific, so the server arrives with it instead of arriving to ask.
It goes to whoever is covering that section right now. If nobody acknowledges it, it climbs — to another server, then to a manager.
The service loop
One screen asks, the other answers — the path every request takes in the room. It reaches whoever is covering that section, the table is told somebody is coming, and the clock runs from the tap to the moment it is closed.
Actual product screens · isolated sample venue
Against the alternatives
$199/month
$300–600 once
$5,000+
What it does
The tag verifies a real tap at the table. A copied link won’t do. Each seating lasts an hour; another tap keeps it going.
Coal change. Chai refill. Extra roti. Write your own request buttons and add a price when there is one — the guest sees it before asking.
Assign sections and requests find the person covering them. If nobody comes, the guest can raise it to another server, then a manager.
Chai $3.00
Extra roti $2.00
Tax $0.65
ONE ORDER. ALL TOGETHER.Switch on menu ordering when you need it. Items, prices and tax arrive as one order. Table history keeps the requests and running total together.
Four taps stay one request. Guests can cancel before pickup; staff confirm before dismissing. Lose signal? The request waits on the phone, then sends when it returns.
See median answer times by hour and which tables waited. Counts and durations that help you run service — without scores or staff rankings.
Illustrations of the OnCue experience. Names, orders and chart shapes are examples.
For whoever runs the room
Every request is timed from the moment it is sent to the moment it is finished. You get medians by hour, which tables waited, and what escalated — enough to move a server at 8pm instead of reading about it on Google a week later.
There are no scores and no rankings. It reports counts and durations, and draws no conclusion about any individual server.

The actual Reports screen · sample service data
Your venue is set up with you, tags printed and coded on the day. One flat price per room, cancel whenever it stops earning its place.