Handling customer complaints in hospitality: the playbook we wrote after the bad ones
A woman rang Harbourside one Tuesday morning to say her partner had been in the night before, eaten our crab linguine, and was now in bed with what she was sure was an allergic reaction. Throat tight, chest heavy, the lot. We took it seriously, we apologised, we told her we'd look into it. Then we tried to look into it and realised we had almost nothing to work with.
Who took the order? Probably Beth, but she'd been covering two sections. Did anyone ask about allergies at the table? Maybe. Was the linguine off the standard menu or a special? Special, but we couldn't find the prep notes. By the time her partner was diagnosed with a chest infection three days later, our insurer had already asked us a dozen questions we couldn't answer properly. The complaint went nowhere. The lesson stuck.
What follows is the playbook we wrote after that one, and after the two or three others that went the same way before we got serious about it. It is not glamorous. It is mostly about writing things down on the night, when you really don't feel like it.
Why this matters
The boring answer is that under the Food Safety Act 1990 and the Consumer Rights Act 2015 you have legal duties when someone says your food made them ill or that you served them something they're allergic to. The less boring answer is that a single complaint, handled badly, can trigger an EHO re-inspection, a public review storm, an insurance claim, or all three at once. The cost of a serious complaint is never the refund. It is what the complaint sets in motion afterwards.
The other thing nobody tells you when you open a café is that complaints are not really about the food. Most of them are about how the person felt when they raised the issue. If they felt heard, half of them never escalate. If they felt brushed off, even a minor complaint can end up on TripAdvisor, on the council's desk, or in your inbox six weeks later as a solicitor's letter. The procedure below is designed to make the brush-off impossible.
The three tiers, and why they need different procedures
Not every complaint is the same beast. We tried, for a while, to have one process for all of them, and it failed in both directions. Tiny issues got over-escalated and serious ones got handled by an 18 year old on a busy Saturday. The fix was to be honest that there are three different kinds of complaint and they need three different procedures.
- Tier 1, in-the-moment. The coffee is cold. The toast came out burnt. The kids' pasta took 25 minutes. These are fixed on shift by whoever is closest, usually with a remake, a comp drink, or a sincere apology. They get a single line in the shift log.
- Tier 2, next-day callback. The customer left unhappy but the issue is not something a remake can solve. A birthday meal that went wrong. A booking that was lost. A bill dispute. The duty manager rings the next day, listens properly, and decides on a remedy.
- Tier 3, serious. Suspected food poisoning. Suspected allergic reaction. An injury on the premises. Anything that could be reported to the council, an insurer, or the FSA. These have a written procedure and the owner or general manager runs them, not the shift lead.
The tier system matters because it tells your team what to do without them having to think. The cold coffee gets sorted. The Tier 3 phone call gets escalated within the hour, with notes, to someone senior. We had complaints sit in someone's head for three days before anyone told me, and that delay alone made one of them ten times harder to handle.
Tier 1: fix it on shift, log it in one line
The team needs permission to fix small problems without asking. At Welsh Back we set a soft budget of about £15 per shift that any team member could spend on remakes, free drinks or knocked-off items without checking. That sounds loose but it costs almost nothing and it stops the situation where a customer is waiting at the till while someone tries to find the manager.
The only rule was that every Tier 1 fix got a single line in the end-of-shift log. Table, what happened, what we did. Not a novel. Just enough that if it came back the next day, we had a starting point. The log lived on the same clipboard as the fridge temperatures, by the pass, and if it was empty at the end of a busy Saturday I knew people had stopped bothering.
Tier 2: the next-day call is the one that saves you
Tier 2 is where most operators lose customers and lose them for good. Someone emails on Sunday night about a botched Saturday lunch. It sits in the inbox till Wednesday. By Wednesday they have written the review.
The rule we settled on was simple. Any Tier 2 complaint gets a phone call (not an email) within 24 hours, made by a manager, not the owner. The manager has the authority to offer up to a full refund of the bill plus a return visit, and they don't have to ring me first. The call follows a loose script: listen, repeat back what happened so they know you heard it, apologise specifically, explain what you'll change, offer the remedy. Don't argue, even when they're wrong about something small. You are not in court.
The cost of a complaint is never the refund. It is what the complaint sets in motion afterwards.
Tier 3: the paper trail that actually protects you
This is the one the Harbourside story is about. When someone phones to say they think your food made them ill, or that they had an allergic reaction, the first 30 minutes is not about the customer. It is about reconstructing the previous service before the memories fade. You will not remember in three days. The kitchen will not remember. The till will, but only if you know what to ask it.
What you need to capture, that day, while it is fresh:
- Who was on shift, in the kitchen and front of house, with start and end times.
- The exact order from the till or POS, with timestamps.
- Whether the booking note flagged any allergies, and what was said at the table.
- The prep notes and supplier batch for any high-risk ingredient (shellfish, eggs, dairy, nuts).
- Fridge and hot-hold temperature logs for the relevant period.
- Whether anyone else on the same shift, on the same dishes, complained.
- A written summary of the call: what the customer said, what you said, what you offered.
We now do this in Paddl, but for years we did it on a printed incident form kept in a drawer by the office phone. The format doesn't really matter. What matters is that the form gets filled out the same day, by the person who took the call, and that someone senior reads it within 24 hours and decides whether it needs to go further.
When the council and the FSA come into it
Most Tier 3 complaints stay between you, the customer and possibly your insurer. Some do not. If a customer suspects food poisoning, they can phone the local council's environmental health team directly. The EHO is then obliged to investigate, and that usually means a phone call to you, a request for your records, and sometimes an unannounced re-inspection.
You are not legally required to ring the council yourself for a single suspected food poisoning case (the customer's GP will notify if it is confirmed and notifiable under the Health Protection Regulations 2010). But if you have a cluster, two or more people from the same service, you should ring the EHO proactively. They would much rather hear it from you. The same applies to a serious allergic reaction where someone needed medical treatment, and to any incident that might be reportable under RIDDOR.
The thing to understand about an EHO re-inspection triggered by a complaint is that they are not coming to look at the complaint. They are coming to look at everything. Your cleaning schedule, your training records, your allergen matrix, your temperature logs, your pest control file. If your paperwork is good, a complaint-triggered visit usually ends with a friendly chat and no change to your hygiene rating. If your paperwork is thin, the complaint becomes the least of your problems.
Common mistakes
- Letting the shift lead handle a Tier 3 call. A duty manager on a Saturday should not be the person managing a suspected food poisoning report. Their job is to take details, be calm, and escalate within the hour. Anything else and you are setting up a 22 year old to make decisions that involve your insurer.
- Apologising in writing without thinking. A heartfelt email at 11pm admitting it was probably your fault is exactly what a solicitor will quote back at you. Apologise for the experience, never admit liability in writing, leave that to your insurer.
- No record of what was offered. "We offered a refund and they refused" is worth nothing if it is in your head. Write down what was offered, when, and what they said. Email confirmation is gold.
- Tidying the kitchen before the EHO gets there. If you know they are coming back because of a complaint, the temptation to do a deep clean is enormous. Don't. They want to see what it normally looks like on a Tuesday, and an unusually shiny kitchen is its own red flag.
- Treating reviews as the complaint. A bad review is the symptom. The complaint is what happened in the room. Replying to the review without finding out what actually happened is how the same problem occurs twice.
- Forgetting to close the loop with the team. Tier 2 and Tier 3 complaints should be discussed at the next team brief, anonymously, with what you changed. Otherwise the lesson sits in a folder and the same thing happens in three months.