Guest complaints: the first thing to say

Guest complaints are moments that test a venue more than any other. A guest catches a server's eye, or waves a manager over, and says something has gone wrong: the steak is overcooked, they have waited forty minutes, the bill is wrong, the table is in a draught. What happens in the next ten seconds often decides whether the guest leaves forgiving or leaves for good. And the first thing a member of staff says shapes those ten seconds more than anything else.

Most staff mean well, but under pressure many reach for the wrong words. They explain why the problem happened, defend the kitchen, mention how busy the evening is, or say that nobody else has complained. Each is understandable, and each makes the guest feel unheard. The problem is not the words' intention; it is how they land with a disappointed guest.

This guide sets out three openings that calm a table and two that inflame it. It covers what to do before offering anything, how to read what a disappointed guest actually wants, how to handle the rare occasion when the guest is wrong, how guest complaints connect to service recovery and feedback, and how to train a team to respond well without sounding scripted.

A guest who complains is usually already frustrated. They have decided that something is wrong, and they are bracing for the response. If the first words show that they have been heard, the frustration starts to fall. If the first words sound like defence, excuse or doubt, it rises, and the conversation becomes a contest.

First words also set the direction. An opening that acknowledges the problem leads naturally to fixing it. An opening that explains or argues leads to more argument. Once a guest feels they have to prove their complaint, even a generous gesture later may not repair the feeling.

That is why the first words are worth practising. They take a second to say and can save an evening, a guest and a review. Customer satisfaction is shaped as much by how problems are handled as by whether they happen at all.

The first calming opening is simple gratitude: "Thank you for telling me." It may feel strange to thank someone for a complaint, but it does several things at once. It shows that the venue wants to know when something is wrong. It treats the guest as helpful rather than difficult. And it signals that the conversation will be cooperative, not defensive.

Mean it. A guest who raises a problem is giving the venue a chance to fix it before they leave unhappy. Many disappointed guests never say anything; they simply do not come back. A guest who speaks up is doing the venue a favour.

Follow it immediately with attention: stop what you are doing, make eye contact and listen.

The second calming opening is an apology that names the problem: "I am really sorry. That is not what we want for you." Or, more specifically, "I am sorry your steak is overcooked" or "I am sorry you have waited so long." It acknowledges the guest's experience without arguing about whose fault it was.

An apology does not mean accepting blame for everything. It means recognising that the guest's evening has been disappointing, which is true whatever the cause. The investigation can come later.

Avoid adding "but". "I am sorry, but the kitchen is very busy" turns the apology into an excuse. A clean apology, with nothing after it, is far more powerful.

The third calming opening is a commitment to act: "Let me sort that out for you now." It tells the guest that the problem will be dealt with, by this person, immediately. For many guests, that is what they want most: not compensation, not explanation, just the problem fixed.

Be specific where you can: "Let me get the kitchen to make you a fresh one straight away; it will be about ten minutes." Telling the guest what will happen, and when, removes uncertainty, which is often what frustrates them most.

Then do it, quickly. An opening that promises action is only calming if the action follows.

The first opening that inflames is "nobody else has complained", or its cousins: "that has never happened before" and "everyone else loves that dish". It is meant to reassure, but it tells the guest that their experience is unusual, possibly imagined, and that the problem is them. Most guests hear it as an accusation.

Even if it is true, it does not help. The guest is not interested in other guests' meals; they are interested in their own. Saying that the dish is usually fine does nothing to fix the one in front of them.

If you want to understand whether a problem is common, find out afterwards, from the kitchen and the records, not by telling the guest.

The second opening that inflames is the explanation: "we are very busy tonight", "the kitchen is short-staffed", "we have a large party in". It is often true, and it feels like honesty. But to a disappointed guest, it sounds like an excuse, and it suggests that the venue's problems are now the guest's problem.

Guests do not mind a busy restaurant; they mind being forgotten in it. Explaining why they were forgotten does not make them feel remembered.

There is a better way to share context. Instead of explaining at the moment of complaint, communicate early: "the kitchen is running a little behind tonight; your mains are next." Information given before a guest complains feels considerate. The same information given after feels defensive.

When a guest complains, the instinct is often to offer something straight away: a free dessert, a drink, money off the bill. Wait. Offering compensation before listening and apologising can feel like buying the guest off, and it may not address what they actually want.

First, listen fully, so you understand the problem. Second, apologise. Third, fix the problem itself, such as replacing the dish or correcting the bill. Only then consider whether a gesture is appropriate, and what kind. A guest who wanted their steak replaced may be perfectly happy once it arrives, with no further gesture needed.

Our guide to service recovery sets out the four steps in order.

Different guests want different things. Some want the problem fixed and nothing more. Some want to be heard and to know the venue cares. Some want the venue to know so it can improve. A few want compensation. Reading which one you are dealing with makes the response fit.

Listen to what they say and how they say it. A guest who says "I just wanted you to know" is often telling you they want acknowledgement, not a free meal. A guest who says "this has ruined our evening" needs more. A guest who mentions an anniversary or a guest of honour may be embarrassed in front of someone important to them.

When in doubt, ask: "What can I do to put this right for you?" Many guests ask for less than you would have offered.

How you say it matters as much as what you say. Stand or crouch at the guest's level, rather than looming over the table. Keep your voice calm and quiet, especially if the guest is upset or other tables are listening. Make eye contact. Do not cross your arms or glance around the room while the guest is speaking.

Match the guest's seriousness, not their volume. A guest who is upset deserves to see that you take it seriously; a guest who is shouting is best met with calm. Lowering your voice often lowers theirs.

Avoid smiling at the wrong moment. A smile while a guest describes a ruined anniversary can look dismissive, however friendly it was meant to be.

Sometimes the guest is wrong: they ordered the dish they now say they did not, the steak is cooked exactly as requested, the price on the bill is the price on the menu. Even then, the first words should be calm and respectful. Arguing at the table rarely changes the guest's mind and often ends with everyone unhappy.

Acknowledge their disappointment, check the facts gently, and look for a solution that keeps the guest's dignity: "I am sorry it is not what you expected. Would you like me to bring you something else?" Often, putting the guest's experience right costs less than winning the argument.

There are limits. Abusive behaviour, threats or attempts to get a free meal through repeated false complaints should be handled firmly by a manager. But these are rare, and treating every complaint as one of them damages the far more common honest ones.

Some complaints are made loudly, in front of other tables. That raises the stakes: the whole room is watching how the venue responds. Stay calm, keep your voice low and focus entirely on the guest. Do not try to quieten them by telling them to lower their voice; it almost always makes things worse.

If the conversation needs to continue, offer to talk somewhere quieter, framed as a courtesy to them: "Would you like to step over here so I can sort this out properly for you?" Many guests calm down once they feel taken seriously and are no longer performing for the room.

Other guests notice a calm, respectful response. A complaint handled well in public can reassure everyone who saw it.

Complaints about price are different from complaints about food or service. The guest may feel a dish was not worth what it cost, that the bill was higher than expected, or that a drink was priced unfairly. The first words still matter: thank them, acknowledge that it was not what they expected, and check whether anything on the bill is actually wrong.

If the bill is correct and matches the menu, explain gently, without condescension, and consider whether there is something you can do to leave the guest feeling better about the evening. If the bill is wrong, correct it straight away and apologise. Recurring complaints about value are worth taking to the menu review rather than settling table by table.

Guest complaints are one form of feedback, the most urgent kind. Every complaint tells the venue something: about a dish, a station, a process, a member of staff or the room. Recorded and reviewed, complaints and feedback together show patterns that no single complaint reveals.

Keep a simple record of complaints: what was wrong, when, and how it was put right. Review it weekly with the kitchen and floor managers. If the same dish comes back every Saturday, or the same table is always too cold, the fix is in the venue, not in the response.

Our guide to guest feedback you can actually act on covers how to collect feedback from guests who do not complain at the table.

Some guests complain after they have left, by email, phone or review. The first words matter just as much in writing. Begin by thanking them for getting in touch, apologise specifically, and say what you will do. Avoid the same two inflaming openings: "nobody else has mentioned this" and "we were very busy that night" read even worse in an email than they sound at the table.

Respond promptly, ideally within a day. A guest who complained and heard nothing for a week is more upset than when they wrote.

For public reviews, keep the reply short and take the conversation private. Our guide to responding to reviews in four sentences covers how.

Staff can only respond well if they are allowed to. A server who must find a manager before replacing a dish or removing a drink from the bill will hesitate, and the guest will wait. Give servers the authority to fix small problems on the spot, within clear limits, and make sure they know what those limits are.

Bring in a manager for larger problems, for guests who are very upset, for anything involving safety and whenever a server feels out of their depth. A manager's arrival also tells the guest that the venue takes their complaint seriously.

Support staff after difficult complaints. A complaint can feel personal to the server who received it, even when it was not. A quick word from a manager afterwards helps.

Scripts help staff remember the right openings, but recited word for word they sound hollow. Train the principles instead: thank, apologise, act; avoid defending, explaining and doubting. Then let staff practise in their own words.

Role-play is the most effective training. One person plays a disappointed guest with a cold main, a long wait or a wrong bill; another responds. Swap roles. Discuss what felt calming and what did not. A few minutes of practice before service builds confidence that lasts.

Share real examples, good and bad, without naming anyone. A recovery that went well is a better lesson than any manual.

Some complaints are about a member of staff: a server who seemed rude, a host who was dismissive. These need extra care. At the table, do not defend or criticise the colleague. Thank the guest, apologise for their experience and, if appropriate, ask a manager to take over the table.

Afterwards, talk to the member of staff privately, hear their side and look at what happened. Often there is more to the story; sometimes there is a training need. Either way, handle it away from guests and with fairness to the colleague.

The first words open the door; what follows decides whether the guest walks through it. After the problem is fixed, check back: "Is the new dish how you like it?" At the end of the meal, acknowledge it again, briefly. If the problem was significant, the manager might stop by.

Record the complaint and how it was resolved, so the venue can learn from it. If the guest has a profile, a short note helps the next visit go well, for example "long wait for mains on last visit, apologised, drinks removed".

Here is an illustrative complaint, handled two ways. The details are examples.

The guest leaves satisfied, and books again a few weeks later.

In servearound, guests who order from the table's QR code menu can call a server at any time, and the call lands in a live queue for the team, marked as it is dealt with, so a guest who needs help is seen quickly. A dish sent back as a remake arrives in the kitchen marked re-fire, so the guest is not charged twice, and kitchen analytics shows ticket times and the slowest tickets, so you can see where waits happen.

With the Guest CRM, notes from the team and the guest's feedback sit on their profile, so the next booking is taken by somebody who knows how the last visit went. See the guests module.

"Thank you for telling me", followed by a specific apology and a commitment to sort it out.

Not at the moment of complaint. Explanations sound like excuses. Communicate delays early instead.

Stay calm and respectful, look for a solution that keeps their dignity, and save the investigation for later.

Servers for small problems, with clear authority. Managers for larger problems, very upset guests and anything involving safety.

No. Fix the problem first. A gesture may or may not be needed.

With principles and role-play, not scripts recited word for word.

Acknowledge it honestly, apologise for the disappointment and explain what you can do instead. Guests usually accept a limit when they feel they have been listened to.

Guest complaints are decided in the first few seconds. Three openings calm a table: "thank you for telling me", a specific apology with no "but", and "let me sort that out for you now". Two inflame it: "nobody else has complained" and "we are very busy tonight". Listen, apologise and fix the problem before offering anything, and read what a disappointed guest actually wants.

Stay calm and respectful even when the guest is wrong, give staff the authority to act on small problems, record complaints and feedback to find patterns, and train with principles and practice rather than scripts. Handled well, a complaint becomes the first step of service recovery, and often the reason a guest returns.