A table of four finished eating ten minutes ago. The plates are gone, a card is already on the cloth, and one of them has turned in their seat with a hand half up, waiting for anyone in an apron to look over. The kitchen did its job. This is the wait that ends up in the review.
Waiting in a restaurant isn't only about how fast food leaves the pass. A seated guest also waits for attention: to order, to say a plate came out wrong, to pay and leave. Those minutes get shorter two ways, by changing how the room is run and by giving the table a way to ask for something without catching anyone's eye. You can test both without new equipment: a tally sheet through one busy service, and the seating and order times your own records hold.
The Waits That Start After Seating
A digital waitlist measures how long a party stands at the door. It ends when they sit down, and nothing takes its place. From there on, everything runs on a particular person being free at an unpredictable moment: taking the order, spotting a plate that came out wrong, bringing the bill.
Adding staff helps up to a point. In the middle of a rush the server covering that section is at another table, and a guest three tables away has no route to them at all.
What the Floor Can Change Without Buying Anything
Section size is the first lever. Take a table or two off the busiest station for the two hours that actually squeeze, and hand them to a station that is quiet at that hour. If the same station keeps producing raised hands at the same hour, count how many tables it covers before you change anything else.
Move the first order forward. Water and drinks taken at the greeting mean the table has been served once before anyone has decided on food, and that order puts the first timestamp on the visit.
Give the runner a line to say. Setting a plate down with "the sea bass, and the pasta without chili, yes?" catches a wrong order at the table instead of after the table has to flag it.
Then decide when the bill gets prepared. If it is only started once someone asks, that ask turns into two waits. Preparing it as the dessert plates clear works in some rooms and reads as rushing in others, so pick one for your service style and tell the team which one they're running. If what limits you is the shape of the room, which stations can see which tables and how far a runner walks, that is a table management question.
What the Phone Does After the Order Is Sent
All of that shortens the wait while somebody is free to notice. It does nothing for the table that has already tried and has nothing left to do but signal. That is why it matters whether the menu on the guest's phone is still useful once the order has gone through.
A service request is a short, defined message a guest sends from the menu already open on their phone, picked from a set list rather than typed out. Two of them can be sent today: asking for the bill, and reporting an order that came out wrong. They run on the same table code as ordering and payment, so if the wait that bothers you most sits at the front of the meal, our guides to QR code ordering and to table ordering cover that end.
What the set list buys you is a request that arrives already stated, so the person watching for it can pick up the card machine and close the table in one trip.
Before You Switch It On
Dine-in ordering has to be live for any of it to appear. With ordering switched off, the guest side of the menu shows the menu, item detail, allergen icons and reviews, and no cart. The requests come in with the ordering channel, so a display-only QR menu has nothing to enable yet. Once ordering is live, the path is Settings > Operations and the Service Options tab, where you choose which requests a guest can send. Don't assume Service Options arrives switched on either; its default state varies by account, so check it rather than plan around it. Which capabilities your account includes depends on your subscription, and the pricing page is where that stays current.
Then look at your codes. Dine-in codes can be unique per table or one code shared across the whole room, and a bill request is only worth having when it arrives with a table on it. If your tables share a code today, start there. Settle ownership before the first service: nothing chases an unopened request for you, so name the person watching for requests through service and write down who takes over when they go on break.
Which Asks Still Need a Person
A set list covers the predictable asks and stops there. A complaint, an allergy question, moving a table around for a birthday: those want someone standing at the table, and a list of options only puts a step in front of them. Some guests won't scan anything either, and they will signal the way they always have, so your service standard has to hold for both. Our tips to improve customer service cover that half of the floor.
How to Tell Whether It Worked
Start with a count that costs nothing. Take one tally sheet through a single busy service and mark every time a guest has to signal for something: a raised hand, a called-out "excuse me", a runner stopped mid-walk. That number is your baseline, and you can compare against it later without any software at all.
If you want a threshold rather than a count, build it from your own room instead of importing a figure. Hand-time five or six tables across two comparable services, from the moment they sit to the moment their first order is in, then take the median of those times rather than the average, since one table that spends twenty minutes on the wine list will drag an average up on its own. The median is what a normal service looks like in your dining room, and it is the number to watch after you change something.
| What to measure | What it tells you | Where it comes from |
|---|---|---|
| Guest signals counted through one busy service | How often people have to ask to be noticed | Tally sheet, kept by hand |
| Time from seating to the first order submitted | How long the front of the meal takes | Floor process log, if it records both times |
| Mentions of waiting in recent reviews and feedback | Which wait guests actually noticed | Recent reviews and feedback responses |
The middle one may already sit in your records, but only if your floor process records both the seating time and the order time. If it holds the order alone, use first-order time as a rough proxy and pair it with a manual seating tally. For the third, read your recent reviews and feedback responses and count how many mention waiting and where in the meal it happened.
Compare like with like. Two Friday dinner services before the change against two Friday dinner services after tells you something about the change; a Friday against a Tuesday tells you about days of the week. If your reports are in FineDine, the comparison windows are already built: 7, 14, 28 or 90 days, or a custom range, each against the previous period and refreshed hourly. The Timing tab breaks that same hourly data down by time of day. The Real-time tab is the one built to be watched while a service is running; the hourly refresh on the other tabs means a mid-service check may not reflect the last few minutes yet.
Questions About Wait Times and Service Requests
- What is the 30/30/30 rule for restaurants?
- It is a floor-training shorthand for the checkpoints at the very start of a visit: a greeting within the first 30 seconds at the table, a drink order soon after, and a third checkpoint that different versions define differently, some count it from the order going in, others from the drinks arriving. It circulates in more than one version and no standards body defines it, so write down which three checkpoints your own team runs and keep them meaning the same thing on every shift.
- How long is too long to wait for service at a restaurant?
- Tasting menus and lunch counters do not run on the same clock, so a single published figure will not fit either one. Track it separately by meal period if your lunch and dinner services move at different speeds - the median from one rarely applies to the other.
- How long is too long to wait for food?
- That is a ticket-time question and it is measured on the kitchen side, from order fired to plate up. A request sent from the guest's phone doesn't touch it, though it does keep a slow ticket from turning into a second wait while the table tries to ask about it.
- How do you make waiting feel shorter?
- We can't measure perception for you, but two things are within your control: give a specific number when a party asks how long, and update it yourself when it changes rather than waiting to be asked again. An estimate that gets revised once is easier to plan around than an optimistic one that quietly expires.
- Do guests need to download an app to send a request?
- No. The QR menu opens as a web page in the phone's browser, and the request goes from the same screen the guest is already reading the menu on.
- Is this the same as a table buzzer?
- A table buzzer is separate hardware to buy, charge, maintain and keep track of. A QR service request runs on the guest's own phone, so there is less equipment on the table and nothing to collect at the end of service.
