A bad review on a Monday morning

A bad review on a Monday morning is a familiar feeling for anyone who runs a restaurant. The weekend was busy, the team worked hard, and now, over coffee, there it is: one star, a few angry paragraphs, a description of an evening that sounds nothing like the one you remember. The instinct is to reply at once, to explain, to defend the team, to set the record straight. That instinct is almost always wrong.

A bad review is information, a public moment and a chance at service recovery, all at once. Handled calmly, it can reassure future guests, win back the reviewer and reveal a problem worth fixing. Handled badly, it can turn one unhappy guest into a public argument that every future guest reads.

This guide sets out what to do with a bad review, step by step: what to check before replying, how to decide whether the complaint is a one-off or part of a pattern, what to say in public, what to offer in private, and when the wisest public response is very little at all. It also covers looking after the team, and how to stop the same review appearing again.

The first step is to wait. Read the review, then close it. A reply written while you are angry, hurt or defensive will show it, and once posted it stays beneath the review for as long as the review exists. Future guests will read your reply alongside the complaint, and they will judge the venue by the reply.

Give yourself a few hours, or until the end of the day. Use the time to find out what happened. A reply written with the facts in hand, and with a calm head, is almost always better than one written in the first ten minutes.

Waiting does not mean ignoring. Aim to reply within a day or two. A review left unanswered for weeks suggests that nobody is listening.

Before replying, find out what actually happened. Look for the booking, the table, the time and the order. Check the bill. Ask the staff who were working: the host, the server, the kitchen. Read any notes made during service. Look at the kitchen's ticket times for that evening, if you have them.

Often the review and the record agree: the mains were late, the dish was overcooked, the server was rushed. Sometimes they differ in detail, and occasionally the review describes a visit you cannot find at all, which may mean the guest has the wrong venue or the review is not genuine.

Whatever you find, the point is to understand the evening from the guest's side. Even if some details are wrong, the guest's feeling that the evening went badly is real, and that is what the reply needs to address.

Read a bad review twice. The first time, read it as the guest felt it: disappointed, perhaps embarrassed in front of friends, perhaps angry. Notice the emotion, because that is what the reply has to meet. The second time, read it for facts: what exactly does the guest say happened, when, and to whom?

Separating the two makes the reply easier. The emotion calls for acknowledgement and apology. The facts call for checking. A review that says "the worst service I have ever had" may, on the second reading, describe one long wait and a server who did not explain it. That is a specific, fixable problem, and the reply can address it specifically.

List the claims. Each one is either something to check, something to fix, or something that is simply the guest's opinion. Opinions deserve respect, not argument.

A single bad review is one guest's evening. Several bad reviews about the same thing are a pattern, and a pattern is far more important. Before replying, look at recent reviews and private feedback for the same complaint. Is this the third mention of slow mains on a Saturday this month? The second mention of a particular dish being cold?

Complaint patterns tell you where the real problem is. A one-off may need a sincere apology and a private conversation. A pattern needs a change in how the venue works, and the reply should say so honestly.

Keep a simple log of complaints by theme, from public reviews, private feedback and complaints made at the table. Over time, it shows which problems recur and whether changes have worked.

A public reply to a bad review should be short, calm and specific. The four sentence structure works well: thank the guest for telling you, acknowledge what went wrong in your own words, say what you are doing about it, and invite them to get in touch directly. Our guide to responding to reviews in four sentences covers the structure in detail.

Write for the next guest as much as for the reviewer. Future guests want to see that the venue takes problems seriously, does not argue with its guests and puts things right. They do not need the operational details of what went wrong.

Sign with a name and a role. A reply from "Tom, general manager" is a conversation; a reply from "The management" is a statement.

Some things should never appear in a public reply. Do not argue with the guest's account, even if parts of it are wrong. Do not reveal details of their booking, their bill or their behaviour beyond what they shared. Do not blame staff by name, suppliers or the busy night. Do not suggest the guest is lying, exaggerating or trying to get something for free.

Do not offer compensation in public either. A public offer of a free meal invites other guests to complain for the same reward, and it turns a private resolution into a public transaction. Offer to talk privately, and make it right there.

Avoid long explanations. A paragraph about how the kitchen was short-staffed because two cooks were ill reads as an excuse, however true it is.

Sometimes the wisest public reply is very brief. If a review is abusive, contains personal attacks on staff, makes accusations that need investigating, or concerns a serious matter such as an allergy incident or a safety issue, keep the public reply to a sentence or two: thank the guest, say you take it seriously, and ask them to contact a named person directly.

If a review appears to be fake, for a visit you cannot find, or from someone who clearly never ate there, consider reporting it to the platform under its rules rather than replying at length. A short, polite reply saying you cannot find a record of the visit and would welcome contact is often enough.

Saying very little in public is not the same as doing nothing. The private conversation, the investigation and the change still matter.

Service recovery happens in private. When the guest gets in touch, or when you have a way to contact them, start by listening. Let them tell you what happened, without interrupting or correcting. Apologise for what went wrong, specifically and sincerely.

Then explain what you are doing about it, and offer something that fits the problem. A refund for a dish that should not have been on the bill. An invitation to come back as your guest. A personal welcome from the manager on their next visit. The offer should reflect how badly the evening went and what the guest values, not a fixed policy.

Follow through. If you promise to call, call. If you invite them back, make sure the host knows and the visit goes well. Our guide to service recovery covers how to turn a poor evening around.

A bad review can hit the team hard, especially one that criticises a named member of staff. Talk to the people involved privately and calmly. Find out their side of the evening, acknowledge that busy nights are difficult, and focus on what can be learned rather than on blame.

Do not share the review with the whole team in a way that singles anyone out. If the review reveals a training need, address it individually and constructively. If it is unfair, say so to the person concerned, and make sure they know the venue supports them.

Share the lessons with the whole team without naming names. "We had a review about slow mains on Saturday; here is what we are changing" focuses on the system, not the individual.

Some bad reviews name a server, a host or a manager. These need particular care, in public and in private. In the public reply, do not repeat the name, do not blame the person and do not defend them in detail. Acknowledge the guest's experience and say you are looking into it.

In private, talk to the member of staff first, before drawing conclusions. Hear their account of the evening. Often the picture is more complicated than the review suggests: a table that arrived late, a kitchen running behind, a misunderstanding. Sometimes the review is fair, and the conversation becomes a chance to coach.

Either way, make sure the person knows the venue will treat them fairly. A team that sees colleagues blamed publicly for every complaint learns to hide problems rather than raise them.

A bad review that mentions an allergic reaction, food poisoning, an injury or another safety issue is different from a complaint about slow service. Treat it as an incident first and a review second. Investigate immediately: what was ordered, what the kitchen did, what the records show and whether anyone else was affected.

Keep the public reply very short: thank the guest, say you take it extremely seriously, and ask them to contact a named person at once. Do not discuss the details in public, and do not deny or admit anything before you know what happened.

Follow your food safety procedures, and check whether you need to report the incident to your local food safety authority. Our guide to building an allergen matrix that stays correct covers the records that help prevent allergy incidents.

A bad review from a regular guest hurts more, and it matters more. A regular who has visited many times and had one bad evening is telling you something important: the experience they come back for slipped. Check their history before replying, so you know who they are and what they usually enjoy.

Reply publicly as you would to anyone, then contact them personally if you have their permission to do so: a call or a note from the manager, acknowledging their loyalty and apologising properly. Regulars are often the most forgiving guests when they feel recognised, and the least forgiving when they feel taken for granted.

The most important response to a bad review is the change that prevents the next one. If the review describes a real problem, fix it. If it is part of a pattern, the pattern is the priority.

Common causes behind bad reviews include long waits for food, poor communication when things go wrong, mistakes on the order or the bill, a cold or noisy room, and staff who seemed rushed or indifferent. Each has a practical fix, and many come down to how the floor and the kitchen work together on a busy night. Our guide to order management from table to pass covers where orders go wrong.

After making a change, watch whether the complaint stops appearing. That is the real measure of whether the bad review was handled well.

It is tempting to treat a bad review as a crisis to be contained. It is more useful to treat it as part of reputation management: the steady, routine work of listening to guests, replying well and improving the experience. The general idea of reputation management covers much more than replies, but for a venue it comes down to those habits.

A venue with a steady flow of reviews, mostly positive, with calm and specific replies to the occasional critical one, has a strong reputation. One bad review does not change that. A venue with few reviews, defensive replies and recurring complaints is vulnerable, and each bad review does more damage.

Build the routine before the bad review arrives. Our guide to online reviews covers which reviews matter and how to keep them coming.

Many bad reviews come from guests who had a disappointing evening and said nothing at the time. A server who asks genuinely how the meal was, a manager who visits tables on busy nights, and a short feedback form at the end of the meal or the day after all give guests a chance to raise problems while they can still be fixed.

A guest whose cold main was replaced quickly, with an apology, often leaves happy. The same guest, whose cold main was never noticed, may write a bad review that night. Private feedback does not stop guests from posting reviews, and should never be used to discourage them, but it gives the venue a chance to listen first.

Our guide to guest feedback covers how to collect feedback you can act on.

Sometimes a guest who left a bad review takes up the invitation and returns. Treat that visit as one of the most important of the month. Make sure the host knows they are coming, that the table is a good one, that the kitchen is aware and that the manager welcomes them personally.

A guest who returns after a bad experience and has an excellent evening often becomes one of the venue's most loyal guests, and sometimes updates their review. Do not ask them to change it; if the evening is good, many will do so on their own.

Here is an illustrative Monday morning, to show the steps. The details are examples.

servearound does not post or manage public reviews. What it gives you on a Monday morning is the record of the evening. With the Guest CRM, a guest's profile shows each visit with its date and time, party, table, orders and what was spent and paid, with notes from the team and any feedback the guest gave. Kitchen analytics shows ticket times by day and hour, and the slowest tickets with what was on them, so you can see what the kitchen was doing when the review says the food was late.

Private feedback, collected at the table or after the visit, lets guests tell you about a problem before they post it, and you can follow up with the guests who asked for a reply, by email or phone. See the guests module.

Usually, yes, briefly and calmly. For abusive or clearly fake reviews, a very short reply or a report to the platform may be better.

Within a day or two, after checking what happened. Not in the first few minutes.

Possibly, in private, if it fits the problem and the guest. Never in a public reply.

Reply politely without arguing. If it breaks the platform's rules, report it. Future guests usually recognise unfair reviews.

Talk privately to anyone involved, and share lessons with the team without naming names.

You cannot stop every one. You can reduce them by catching problems during service, collecting private feedback and fixing the patterns reviews reveal.

Do not continue the argument in public. Reply once more, briefly, repeating the invitation to talk privately, and then leave it.

A bad review on a Monday morning calls for patience, not speed. Wait, check what happened, and look for complaint patterns before replying. Reply in public briefly and specifically: thank the guest, acknowledge the problem, say what you are changing and invite them to get in touch. Say very little in public about serious matters, and never argue, blame or offer compensation there.

Make it right in private through genuine service recovery, look after the team, and fix the cause so the same review does not appear again. Treat responding to reviews as part of everyday reputation management, and catch problems during service, when they are easiest to put right.