The three channels so far all have a delay built in: by the time you read the review, the survey or the post, the customer is gone and the meal cannot be fixed. This one has no delay at all. Someone is sitting in your dining room, right now, with an opinion about the plate in front of them, and a member of your staff is standing two metres away. It is the oldest feedback tool in the trade, it costs nothing, and most restaurants run it so badly that it collects almost nothing.
🗣️ "Everything okay?" collects nothing
The standard table check is designed, without anyone meaning it to be, to produce a yes. It is asked while the server is already half-turned away, it is vague enough that "fine" answers it completely, and it puts the customer in the position of having to start a confrontation to say anything real. So they say fine, and you learn nothing, and a third of them do not come back.
Small changes to the question change the odds a lot, because they make it easy and specific to say something true.
| Instead of | Try |
| "Everything okay?" | "How is the lamb — is it how you like it?" |
| "Any problems?" | "Is there anything we could have done better tonight?" |
| Asking as you walk past, mid-turn | Stopping, making eye contact, and waiting three seconds |
| Asking after two bites, before they know | Asking once they are properly into the dish |
| Clearing a half-eaten plate in silence | "I noticed you left the risotto — was it not right?" |
That last row is the highest-yield question in the restaurant and it is almost never asked. A plate coming back half full is feedback that already happened; the customer has decided something and is planning to say nothing. Asking gently at that exact moment gets you the honest answer, and often the chance to fix it before they pay.
👥 Your staff already know
Here is the uncomfortable part. If you ask any server what customers complain about most, they will answer instantly and without hesitating, because they hear it every shift. That information already exists inside your business. It simply has no route from the floor to the person who could act on it — so it evaporates at the end of every shift, night after night, for years.
Building that route is mostly about removing the reasons not to use it.
- Ask specifically, at a fixed moment. "What did you hear tonight?" in the pre-shift or the closedown, every day, until it is routine.
- Make it thirty seconds to record. A notebook by the pass, a shared note on a phone. If it takes a form, it will not happen.
- Never punish the messenger. If reporting a complaint about the kitchen starts an argument, the reporting stops that week and never restarts. This is the single thing that kills these systems.
- Close the loop with the team, too. "You told me the bar was too slow on Fridays; we moved a person" is what proves it is worth telling you.
- Give servers room to fix small things themselves. A remade dish decided at the table, without a manager hunt, turns a bad night into a story about how well you handled it.
Do this and the effect compounds. Staff start noticing on purpose instead of just overhearing, and you get a stream of ground-level detail — which table is always cold, which dish gets sent back on Sundays, what regulars ask for and never get — that no survey would ever have surfaced.
🃏 Cards, boxes and the quiet channel
Some people will never say it out loud and will never fill in an online form either, and for them the old paper channel still works. A comment card left with the check, or a box by the door, catches a specific type of person: the one who wants to say something but does not want a conversation about it.
They are worth having if you keep them honest. Leave the card with the bill rather than handing it over and hovering, because standing there turns it back into a face-to-face question. Keep it to two lines, the same shape as your survey — one score, one open box. Put the box somewhere private enough that using it is not a public act. And empty it: nothing kills a comment box faster than customers noticing that it is dusty and full.
The other quiet channel is the one nobody writes anything on at all. Half-eaten plates, a table that always gets refused, the same dish coming back, people asking for the music down three times a week, regulars whose faces you have stopped seeing. Behaviour is feedback that was never spoken, and a manager who walks the room reading it will know things about the restaurant that no channel in this course would have told them.
🚑 Fixing it while they are still in the building
Most of the value of in-person feedback is not the information — it is the timing. A problem you learn about at the table can still be fixed; the same problem discovered in a review a week later can only be apologised for. A customer whose bad experience is handled well often ends up more loyal than one whose evening was simply uneventful, because you have shown them what happens when something goes wrong.
The recovery is simple and the order matters: listen without interrupting, apologise plainly without excuses or explanations of how busy the kitchen is, fix the actual thing — remake it, take it off the bill, whatever fits — and then thank them for telling you, because they did you a favour that the silent ones did not. Do it quickly and at the table; a complaint that has to wait for a manager to appear has already doubled in size.
Then write it down. This is the step that gets skipped: the problem gets solved for that guest and never reaches the pile where patterns live. The dish that was sent back and comped is a happy customer and a data point — and if it is the fourth time this month, it is not a bad night, it is a recipe or a station that needs attention. Which is exactly what the last topic is for.