How Restaurants Should Respond to Bad Reviews (Food Safety, Allergies, Waits, Staff)

Restaurants should reply to bad reviews quickly, calmly and specifically: thank the guest, acknowledge the exact issue, avoid arguing about facts in public, and move the details to a private channel. Treat food safety and allergy claims differently from service complaints. Check with the kitchen first, never dismiss an illness report, and fix the underlying problem before you promise anything.

This guide covers the situations restaurants face most often: food poisoning claims, allergy complaints, long waits and complaints about staff. For each one you get a reply you can adapt and a follow-up step for the kitchen or the floor. For a general process that works for any business, see our step-by-step guide to responding to negative Google reviews.

Why restaurant reviews need their own playbook

A restaurant review is often about something that can't be checked later. The plate is gone, the table has turned and the shift has ended. That makes the reply about how you handle uncertainty, not about proving who was right.

Restaurant complaints also carry different levels of risk. A cold side dish is a service issue. A claim that someone got sick or had an allergic reaction is a possible health issue, and future guests reading the review will judge whether you take it seriously. Your reply should match the weight of the complaint.

Remember who reads your reply. On Google, the reviewer is notified when you reply, your reply appears publicly under the review, and it carries your business name rather than your personal name. You must verify your Business Profile before you can reply. You are writing for the guest and for everyone deciding where to eat tonight.

A five-step process for any bad restaurant review

1. Read it twice and sort it. Is it about food quality, food safety, an allergy, wait time, staff, price or something else? Is the visit date or order clear?
2. Check internally before replying. Look at the reservation book, POS records, tickets and the shift schedule. Ask the manager on duty what they remember. For safety or allergy claims, talk to the kitchen lead the same day.
3. Reply publicly within a day or two. Keep it short: thank them, name the issue, say what you are checking or changing, and give a direct contact.
4. Continue privately. Use a named contact such as [manager's email] or a phone number. Don't ask for order details or personal information in the public thread.
5. Log it and fix the cause. Record the complaint type, date and what you changed. Patterns are more useful than single reviews; analyzing your reviews by theme shows which fixes matter most.

Your reply is not a place to tell the guest they are wrong. If facts conflict, say you see things differently in one neutral sentence at most, then offer to talk.

Food poisoning and food safety claims

Illness claims are the most serious review a restaurant can get and the easiest to handle badly. Don't deny it outright (“nobody else got sick”), don't diagnose (“that can't be from our food, it takes days”) and don't ignore it.

What to do in the kitchen first

Before you write anything, pull the details you can verify: what was ordered, which items were on that shift, temperature and cooling logs, deliveries and any other complaints from the same day. Check whether any staff member was ill on that shift. If you have a food safety lead or consultant, involve them now.

Write down what you checked and when. If a health inspector later contacts you, a dated internal record is more useful than anything in a public reply.

Reply wording

Example (illustrative): Hi [Name], I'm sorry to hear you felt unwell after your visit. We take any report like this seriously and have already reviewed that day's kitchen records with our team. I'd like to hear more about what you ordered and when you visited. Please contact me directly at [manager's email] or [phone]. – [First name], General Manager

This reply shows concern, describes a real action, and moves the conversation to a private channel. It doesn't admit fault or argue about the cause, and it doesn't ask for medical details in public.

When the health department comes in

The CDC asks people who think they have food poisoning to report the illness to their local health department. According to the CDC, prompt reports help local and state health departments identify foodborne outbreaks, and investigators may ask for receipts or leftover food for testing.

In your private conversation, it is reasonable to mention that the guest can report the illness to their local health department. Present it as helpful information, not a challenge. If you receive several similar complaints, or a guest reports a serious illness, contact your local health department yourself to ask how they want restaurants to handle illness complaints. Requirements vary by state and county, so check the rules where you operate. This article is general information, not legal advice; for questions about your obligations, consult a qualified lawyer in your jurisdiction.

Allergy complaints

Allergy complaints need the same care as illness claims. Federal law defines nine major food allergens: milk, egg, fish, crustacean shellfish, tree nuts, wheat, peanuts, soybeans and sesame. Sesame was added most recently. Your team should know which dishes contain each one.

Internally, check how the allergy was communicated (verbally, on the ticket, on the reservation) and where the process failed: order entry, kitchen prep, shared equipment, or a recipe change the front of house didn't know about.

Example (illustrative): Hi [Name], thank you for telling us, and I'm very sorry. An allergy should never be missed, and I've gone through what happened with our kitchen and floor teams. I'd like to understand exactly what went wrong so we can fix it. Please reach me at [manager's email]. – [First name], Owner

Don't explain your cross-contact procedures at length in public, and don't suggest the guest should have warned you more clearly. If the review reveals a real gap, fix it first: update the allergen matrix, add a ticket flag, and brief every shift.

Wait times and slow service

Wait-time complaints are the most common and the easiest to answer honestly. Check the timestamps: when the order was entered, fired and served. If there was a real delay, say so briefly without listing excuses.

Example (illustrative): Hi [Name], you're right that your mains took far too long on Saturday. We were short in the kitchen that night, but that's our problem to solve, not yours. We've changed how we pace large tables on weekends. I hope you'll give us another try. – [First name]

If the wait was within normal range for a busy night, you can still acknowledge the frustration and mention, without arguing, what helps: reservations, quieter times, or a call-ahead option. Avoid quoting exact minutes from your system in public; it reads as a rebuttal.

Complaints about staff

When a review describes a rude server or a host who handled a situation badly, handle it in two separate tracks. In public, apologize for the experience and say you are looking into it. In private, talk to the staff member, hear their side and decide on coaching.

Never name the employee in your reply, discuss discipline in public, or defend the employee by attacking the guest. If the reviewer names a staff member, don't repeat the name. Google's content policy prohibits posting personal information without consent and harassment; if a review goes beyond a service complaint into a personal attack on an employee, it may be worth reporting. A plain complaint that a named server was slow or unfriendly usually won't qualify.

Example (illustrative): Hi [Name], I'm sorry the service at your table fell short. That isn't how we want anyone to be treated, and I've followed up with the team on that shift. If you're willing to share more, please email me at [manager's email]. – [First name], General Manager

Reviews that may break platform rules

Some bad reviews aren't about a real visit: a review from someone who never ate with you, a post about a different restaurant, or a rant about a political issue. Google's policy covers content that is not based on a real experience and off-topic content, among other categories.

On Google you can report a review from your Business Profile or the Reviews Management Tool. Google is explicit that you should not report a review just because you disagree with it or dislike it, and that negative reviews aren't always a sign of poor service. Google, not the business, decides. A truthful bad review about a slow night or a disappointing dish will stay up, so put your effort into the reply and the fix. Our guide to what violates Google's review policy covers the categories in detail, and how to respond to a review you believe is fake covers the public reply while a report is pending. Other platforms such as Yelp and Tripadvisor have their own rules; check their current business help pages before reporting.

Close the loop with the kitchen and the floor

A reply without a fix means the next review will say the same thing. A short weekly routine keeps the two connected:

Share a few anonymized reviews in pre-shift meetings, good and bad. Staff respond better to real guest words than to general reminders. If you want an outside view of patterns across your profiles, a free review audit at BRANDprotecto's audit page is one option.

Mistakes to avoid

• Arguing in public. Even if you are right, a long rebuttal makes readers side with the guest.
• Copy-paste replies. The same sentence under every review signals you aren't reading them. See negative review response examples for varied wording.
• Sharing guest details. Don't mention what they ordered, who they were with or their visit history unless they posted it themselves, and even then keep it minimal.
• Offering compensation in exchange for an edit. You can invite a guest back, but don't make it conditional on changing or removing the review.
• Replying angry. Draft, wait an hour, and have a second person read it. You can edit or delete your reply on Google later, but the reviewer may already have been notified of the first version.