The Complaint That Never Reached You
For every guest who complains, several leave without saying anything. What the silent ones have in common, where complaints get absorbed before management hears them, and the arithmetic that decides what a resolution is worth.
A guest complains at the door. It gets handled, they leave reasonably happy, and management never hears about it.
That is usually described as good service. It is also a complaint that never reached anyone who could fix the cause.
Two separate problems
They get discussed as one and they are not.
Resolution — the guest in front of you leaves satisfied. The floor is usually good at this.
Signal — the venue learns that the thing happened. Most venues are bad at this, and it is the one that compounds.
⚠️ A room can be excellent at the first and learn nothing for years. Every incident gets absorbed, and the same cause produces the same incident every week.
Where complaints get absorbed
Three places, all of them well-intentioned:
Handled on the floor and not mentioned. The person fixed it, considers it closed, and does not think of it as information. This is the largest category by far.
Not escalated because it reflects on someone. Including the person handling it. Nobody wants to file a report about their own section.
Told to a member of staff who is not the manager. The guest mentions it to whoever is nearest. That person is not sure it counts, so it goes nowhere.
None of the three is anyone behaving badly, which is why exhortations to "report everything" fail. The fix has to be structural.
The silent ones
For every guest who says something, several just stop coming. They are the larger group and they are invisible by definition.
But they are not undetectable. A guest who came regularly and stopped is a guest with a reason, and the reason is frequently a specific night.
⚠️ The overlap worth checking: guests who stopped coming, and nights something went wrong. If the same night appears repeatedly, you have found a complaint nobody made.
What the recovery is worth
Worth doing the arithmetic once, because it changes how much authority you give the floor.
Take a regular's annual spend. That is what is at stake in a bad night — not the value of the one visit.
Against that, the cost of resolving it on the spot — a comped round, a discount, a replacement — is almost always small. Frequently an order of magnitude smaller.
⇒ This is the argument for pushing the authority down. A member of staff who must find a manager to comp a drink will, at 01:00 on a Saturday, do neither.
Set the limit deliberately, tell people it exists, and expect it to be used. An unused authority is a policy nobody believed.
The one-line report
The reason complaints do not get recorded is that recording them feels like an incident report.
Make it one line, from anyone, in the moment. What happened, which table, roughly when. No form, no blame field, no follow-up required from the person writing it.
⚠️ A blame field guarantees under-reporting. If the record can be read as evidence against the person writing it, it will not be written — and you lose the signal to protect a feeling that was never at risk.
What to do with a month of them
Not review them individually. Look for the repeat.
One incident is a night. The same incident four times is a cause — a station that is always understaffed at the same hour, a system that fails the same way, a step in the process where guests are consistently misinformed.
The individual complaints were never the point. The pattern is.
Three to hold
Complaints recorded per month. ⚠️ If this number is very low, that is a reporting problem, not a quality one. Rising is usually good news.
Share resolved on the spot without escalation. Tells you whether the authority is real.
Regulars who stopped within thirty days of a recorded incident. The overlap that finds the silent ones.
Where the record has to sit
If an incident lives in a member of staff's memory and the guest's history lives in a different system, the overlap that matters cannot be computed and the pattern never appears.
tasteck keeps notes against the guest and the visit, so a one-line note on a Saturday is still there when the same guest has not been back in two months.
They did complain. It just stopped at the first person who could not fix the cause.
Related articles
Your Pour Cost Is a Schedule Problem
Most venues chase pour cost with tighter counts and better jiggers. The variance usually tracks who was behind the bar, not what they were pouring. How to read pour cost by shift, and why the fix is often on the roster.
Your Coat Check Is a Queue Problem
In cold markets the coat check decides how your night starts and how it ends. What the queue costs in unbought first drinks and in clearance time at close, and the three changes that move it without new staff.
Your Best Night Was Not Your Best Night
The night with the highest take is rarely the night that earned the most. What has to be subtracted before a night can be ranked, and why the answer usually reorders the whole week.
Map out your operations in 5 minutes
Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.
Your answers are not stored. The assessment runs entirely in your browser.
Try tasteck free for 30 days
No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.
- No card required
- Free data migration support
- All features unlocked for 30 days