Guest feedback you can actually act on

Guest feedback is what guests tell you about their visit, in their own words and on their own scale. It is one of the most valuable things a venue can collect, and one of the most often wasted. Many venues ask for it, few read it carefully, and fewer still change anything because of it. Survey forms go out with ten questions, a handful of guests answer, the scores are averaged into a single number, and the number is admired or worried about without anyone knowing what to do next.

Feedback you can act on looks different. It asks fewer questions, at the right moment, in a way that guests are happy to answer. It collects enough replies to show patterns rather than isolated opinions. It connects each answer to the visit it describes, so a comment about slow mains can be read against the night, the table and the dishes. And it ends in a decision: something the venue will change, keep or look into.

This guide sets out how to collect guest feedback you can actually act on: the survey questions worth asking, when and where to ask them, feedback at the table and after the visit, how many replies you need, how to read feedback scores without being misled, and how to turn what guests say into changes the team can see. It also covers replying to guests, privacy and the mistakes that turn feedback into noise.

Guest feedback has three jobs. The first is to catch problems: a dish that has changed, a section that is slow, a member of staff who needs support, a room that is too cold. The second is to understand what guests value, so you can protect it. The third is to put things right with guests who had a poor experience, before they decide not to come back.

Each job needs something slightly different. Catching problems needs enough replies to see patterns and enough detail to know where to look. Understanding what guests value needs open comments, not just scores. Putting things right needs to know who the guest was and how to reach them, which means asking permission.

A feedback system designed with those three jobs in mind will look quite different from a generic survey. It will be shorter, more focused and connected to the rest of what the venue knows about each visit.

The most common mistake is asking too much. A ten-question survey feels thorough to the venue and tiresome to the guest. Fewer guests finish it, those who do rush the later questions, and the venue ends up with more data and less insight.

Two questions are often enough to start. The first asks for an overall rating of the visit, on a simple scale. The second asks an open question: "What is one thing we could have done better?" or "Tell us about your visit." The rating gives a number to track; the comment tells you why the number is what it is.

If you want more, add a small number of specific ratings for the parts of the visit you most want to understand, such as food, service and atmosphere, and make them optional. Every extra question should earn its place by answering something you will actually use.

Good survey questions are short, specific and easy to answer honestly. "How was your visit overall?" with a five-point scale from very poor to excellent is clear. "How likely are you to recommend us to a friend?" measures something slightly different, willingness to recommend, and is the basis of the Net Promoter Score used by many businesses.

Avoid questions that lead the guest, such as "How much did you enjoy our delicious food?", and questions that combine two things, such as "How was the food and service?". Avoid jargon and internal terms. A guest does not know what "the pass" is, and should not need to.

Open questions are where the most useful feedback comes from. Ask them in a way that invites specifics: "Was there anything that would have made your visit better?" tends to produce more useful comments than "Any other comments?".

Timing changes both the number and the quality of replies. Ask too soon and the guest has not finished the experience; ask too late and they have forgotten the details or stopped caring. For most venues, the best moments are at the end of the meal or within a day of the visit.

At the end of the meal, guests remember every detail and are still in the room, so a problem can sometimes be fixed on the spot. The day after, guests have had time to reflect, and are often more willing to write a considered comment. Both work; many venues use both, for different guests.

Avoid asking during the meal itself, except in the gentlest way. A server checking that the food is good is service; a survey in the middle of dinner is an interruption.

Feedback at the table captures the visit while it is fresh. It can be a short form on the digital menu the guest ordered from, a tablet handed over at the end of the meal, or a card with a QR code left with the bill. The advantage is immediacy: guests answer while they still feel the experience, and the reply arrives before they leave.

Keep it very short at the table, because guests are about to leave. One rating and an optional comment is plenty. Make it clear that it is optional and that the team will read it.

Feedback at the table also gives the team a chance to act straight away. A low rating from a table that is still seated can prompt a manager to go over, listen and put things right. That can turn a poor visit into a story the guest tells for the right reasons.

Feedback after the visit is usually collected by email, with a link sent after the booking is completed. It reaches guests who left quickly, guests who would not fill in a form at the table, and guests who want time to think. Replies tend to be longer and more considered.

Send it soon, ideally the same evening or the next morning, while the visit is still clear. Make the email short and personal, from the venue rather than a generic system, with one clear link. Do not combine it with a marketing offer, which makes the request feel like a sales message.

Link each reply to the visit it describes: the date, the table, the party and what was ordered. A comment that the fish was overcooked means much more when you know which fish, on which night, from which station.

A handful of replies is a handful of opinions. They may be useful as individual stories, but they cannot tell you whether a problem is common or rare. To act on feedback with confidence, you need enough replies to see patterns.

How many depends on your volume and what you want to know. A venue serving 1,000 covers a week that receives five replies has very little to go on; one unhappy guest changes the average sharply. The same venue with 60 replies a week can see whether a complaint about slow service is a one-off or a trend, and can compare one week with another.

To raise the number of replies, make the questions fewer, the timing better and the request more personal. Tell guests that their feedback is read and acted on, and show them, for example by mentioning a change that came from feedback. Guests who believe their answers matter are more likely to give them.

Feedback scores are useful for tracking change over time, but they are easy to misread. An average rating hides the spread: a venue with mostly excellent ratings and a few very poor ones may have the same average as a venue where everything is just good, yet the two need very different actions.

Read the distribution, not just the average. How many guests rated the visit excellent, good, okay, poor and very poor? Are the poor ratings concentrated on certain nights, sections or dishes? Is the share of excellent ratings rising or falling?

Compare like with like. A Saturday's scores should be compared with other Saturdays, and a month's with the same month last year. Watch for changes in the number of replies too, because a sudden change in who responds can move the score without any change in the experience.

An overall rating tells you how the visit felt; ratings for each part of it tell you where to look. Many venues ask for optional ratings of the food, the service and the atmosphere alongside the overall score. When the overall score falls, the part-scores show whether the problem is in the kitchen, on the floor or in the room.

Keep the parts few and broad. Three is usually enough; ten turns a short form back into a long survey. Make them optional, so guests who only want to give an overall rating are not put off.

Read the part-scores against each other. A visit rated excellent for food and poor for service points to the floor, not the kitchen. A month where atmosphere scores fall while food and service hold steady may point to music, lighting, temperature or noise.

Not all feedback needs a form. A server who asks, at the right moment, "How was everything tonight, honestly?" and listens to the answer collects feedback that no survey will. Guests often tell a person things they would never write down, especially small things: the table was wobbly, the music was loud, the dessert was too sweet.

Train the team to ask genuinely, not as a reflex. "Is everything okay?" asked while walking past invites "fine". A question asked while stopping at the table, with eye contact, invites an honest answer. Make sure what servers hear reaches the manager, through a short note or the briefing the next day.

Comments are where the useful detail lives. Read every one, at least at first. Group them by theme: food, service, speed, atmosphere, value, booking, cleanliness, specific dishes or staff. Count how often each theme appears, and note whether it is praise or criticism.

Look for patterns across comments. One guest saying the music was too loud is an opinion; ten guests saying it in a month is a finding. Look also for surprises, things guests mention that the team did not know about, such as a broken chair, a confusing entrance or a server who goes out of their way.

Share the comments with the team, good and bad. Praise for a named member of staff matters to them, and criticism shared constructively helps the whole team improve.

Acting on feedback is the step most often skipped. A useful routine is a short weekly review: read the comments, look at the scores and their spread, list the themes, and choose one or two things to act on. Write them down, assign them to someone, and check the following week whether they have been done.

Prioritise problems that are frequent, fixable and important to guests. A recurring complaint about slow mains on Fridays deserves more attention than a single comment about the font on the menu. Our guide to ticket times covers how to investigate slow service in the kitchen.

Close the loop. When a change is made because of feedback, tell the team, and where appropriate tell guests. A note on the menu or in an email saying "you told us the room was too cold, so we have fixed the heating" shows guests that feedback works.

Some guests want a reply; many do not. Ask, as part of the feedback form, whether the guest would like the venue to follow up, and how: by email or by phone. Respect the answer. A guest who chose to keep their feedback private should not be contacted, and should not be identified to the team.

When a guest does want a reply, reply quickly and personally. Thank them, acknowledge what they said, explain what you will do, and, where they had a poor experience, offer to put it right. Our guide to service recovery covers how to turn a poor visit around.

Keep replies human. A reply that sounds like a template undoes the value of asking.

Feedback is most useful when it sits on the guest's record, next to their visits, what they ordered and any notes from the team. The next time the guest books, whoever takes the booking can see how the last visit went, and the host can make sure this one goes better.

That only works with the guest's permission and with care for their privacy. Feedback given anonymously should stay anonymous. Feedback given with consent to follow up can be linked to the guest's profile, so the team can recognise them and respond. Our guide to guest data covers what to collect and keep.

Private feedback and public reviews are different channels, and both matter. Private feedback reaches the venue directly and gives it a chance to fix problems before they become public. Public reviews on review platforms are read by guests deciding where to eat.

A good private feedback system often reduces the number of poor public reviews, because guests with a complaint have a direct way to be heard and a venue that listens. It does not replace public reviews, and it should never be used to stop guests from posting them. Our guide to online reviews covers the public side.

Guests are not the only source of feedback. Servers, hosts and cooks hear what guests say during the meal, see where service breaks down and know which dishes come back. Ask them regularly, in the pre-service briefing or a short weekly conversation.

Compare what the team says with what guests write. Where they agree, you have a clear finding. Where they disagree, there is something to investigate: a problem guests notice that the team does not, or one the team sees that guests have not mentioned.

Here is an illustrative month of guest feedback for a venue, to show the method. The figures are examples.

Actions: the head chef investigates Friday and Saturday ticket times, the heating near the door is adjusted, and the praised server is thanked at the team briefing. Next month, the venue checks whether the comments about waiting fall.

In servearound, guest feedback is collected from a link after a completed booking, from the digital menu at the end of a table's visit, or on a tablet handed over at the table. Guests give an overall rating from very poor to excellent, can rate the food, service and ambience, and can leave a comment. They choose whether the venue may follow up, and how, by email or by phone; a guest who keeps their feedback private is never identified to you.

The team sees the responses, the average rating and which guests are happy to be contacted, and can send a follow-up email to the guests who asked for one. With the Guest CRM, what a guest said sits on their profile next to what they ate, so the next booking is taken by somebody who knows how the last visit went. See the guests module, or get in touch.

As few as possible: an overall rating and an open question, with a few optional ratings if you will use them.

They reach different guests. Table feedback is immediate; email reaches guests who left quickly. Many venues use both.

The useful comparison is your own scores over time, read as a distribution rather than an average.

Within a day for guests who asked for a reply, and sooner for serious complaints.

Be careful. Incentives can raise response rates but may bias answers. A personal request and visible action usually work better.

Weekly, with a short list of actions, and monthly for trends.

Guest feedback is only useful if it leads to action. Ask fewer survey questions, an overall rating and an open question, at the right moment, through feedback at the table and a short email after the visit. Collect enough replies to see patterns, read feedback scores as a distribution rather than an average, and read every comment.

Review the feedback weekly, choose one or two things to change, and close the loop with the team and with guests. Reply personally to guests who asked for a reply, respect those who did not, keep feedback with the guest's record where they allow it, and remember that acting on feedback is the whole point of asking.