How to Respond to a Food Poisoning Review (Carefully)

"Ate here Saturday. Up all night being sick. Avoid."

Of every review in this guide, this is the one that can genuinely damage a restaurant beyond repair. It carries legal exposure, insurance implications, potential environmental health involvement, and the kind of public fear that stops people booking.

This is general guidance, not legal advice. For any allegation of illness, involve your insurer and take proper advice before responding.

Before you write anything: investigate for real

Not to build a defence — to find out whether something actually went wrong. Do this the same day.

1. Identify the visit. Date, time, table, orders, who cooked and served.
2. Check for other reports. Same day, same dishes, other reviews, phone complaints, staff who felt unwell. A single isolated report and a cluster are completely different situations.
3. Pull your records. Temperature logs, delivery notes, cleaning records, supplier batches, staff illness records. Save them now — these are what protect you if this escalates.
4. Check whether staff were unwell. Norovirus in a kitchen spreads through a service.
5. Notify your insurer if there's any suggestion of a claim. Most liability policies require prompt notification and prohibit admitting liability.
6. Know your local reporting duties. In many jurisdictions, suspected foodborne illness linked to your premises must be reported to the local authority. Check yours.

Worth knowing: most incubation periods for common foodborne illnesses are longer than people assume, so "I was ill three hours after eating" frequently points to a meal earlier in the day. That is a useful thing for you to understand internally. It is not something to say in your public reply.

The reply

Three things it must do: take the illness seriously, show you have a real food safety operation, and move it offline. Three things it must not do: accept that your food caused it, dispute their account, or lecture anyone about incubation periods.

Thank you for letting us know, and I'm sorry to hear you've been unwell — that's a horrible thing to go through. We take reports like this extremely seriously. We've reviewed our records and kitchen procedures for that date and have had no other reports, but I'd still like to understand your experience properly. Please contact me directly at [email] or [phone]. — [Name], Owner

Read what that does:

• "Sorry to hear you've been unwell" — sympathy for the illness, not an admission it came from you
• "We take reports like this extremely seriously" — the only sentence most readers need
• "Reviewed our records and procedures" — demonstrates a real system exists
• "No other reports" — a fact, stated neutrally, not a rebuttal
• "I'd still like to understand" — no brush-off

If your investigation did find a problem

Thank you for telling us, and I'm sorry you've been unwell. We took this seriously enough to review everything from that day, and we've made changes to [general area] as a result. I'd like to speak with you directly — please contact me at [email].

Note it acknowledges a change without specifying a failure. Speak to your insurer before going further than this.

If several reports arrive at once

Stop replying individually and escalate immediately — owner, insurer, environmental health if required. A cluster is an incident, not a review problem, and the priority order is public health first, legal second, reputation third.

Never write these

• "Nobody else got sick." Reads as dismissive and, in a cluster, ages terribly.
• Anything about incubation periods. Correct, and it reads as a business arguing that a sick customer is wrong.
• "We have a 5-star hygiene rating." Fine as background; as a rebuttal it sounds like hiding behind a certificate.
• "This is defamatory." Never. It travels, and it looks like intimidation.
• Any suggestion they ate elsewhere. Even gently.
• An apology for making them ill. That is an admission of causation. Be sorry they're unwell, not sorry you caused it.

"I'm sorry you've been unwell" and "I'm sorry we made you ill" look almost identical and are completely different sentences. Use the first one.

Can it be removed?

Not usually. A customer describing their genuine experience doesn't breach Google's content policies, even if you're confident they're mistaken.

You have a case if it's clearly not a customer, if it's part of a coordinated attack, or if it contains personal information or harassment. See removing fake reviews and reviews from former employees, which is a surprisingly common source of illness allegations during disputes.

Afterwards

Assume the review stays. What determines the damage is what surrounds it.

• Keep collecting reviews. An illness allegation followed by twenty recent positive reviews reads as an outlier. The same allegation as your most recent review reads as a warning.
• Reply to everything else too. A profile where the owner engages consistently makes the careful reply on this one look like character rather than crisis management.
• If it resolves, update your reply with a single neutral line — cleared with your insurer first.
• Fix anything the investigation found, and document that you did.

Reploi flags high-risk reviews — illness, injury, legal threats — so they reach the owner immediately instead of being answered by whoever happens to check the notifications. Start free — 5 replies/month →