A hotel guest feedback form and what to do when a score comes back low

Most hotels already collect guest feedback. The form exists, the link goes out in the checkout email, and the answers land in a spreadsheet or a dashboard that someone opens on Monday. The weak point is rarely the form. It is the hour after a guest submits a 3 out of 10 with a comment about a broken air conditioner, when nobody is sure whose job it is to answer. This guide covers the questions worth asking, the moment to ask them, and, at more length than most guides on hotel guest feedback, what the team should do with a low score in the first day after it arrives.

What hotel guest feedback is for, and the two jobs it does

Feedback from guests does two separate jobs, and treating them as one is the most common reason a feedback programme feels busy but changes little.

The first job is recovery. A single guest had a bad experience and may still be in the building, or left this morning. The value of their answer decays by the hour. If someone contacts them today, the stay can sometimes be rescued, a refund or a goodwill gesture can be decided, and the guest is less likely to take the complaint to a public review site.

The second job is pattern finding. Over weeks, the answers show which rooms, shifts, seasons or services keep producing the same complaint. This work is slow and statistical, and a few days of delay do no harm.

The two jobs pull the design of the form in different directions. Recovery needs an email address, permission to follow up, a named owner, and a clock. Pattern finding needs consistent questions that do not change every month, a room number or stay date, and enough responses to compare. A form can serve both, but the handling has to be split. Low scores go to a person straight away. Everything else goes into the weekly count.

The hospitality software vendors that rank for this topic, such as Cloudbeds, Stay and Chekin, put most of their attention on collection: in-stay messaging, QR codes, post-stay surveys. That is reasonable, because they sell the collection channel. The handling step is where a small team can make the biggest difference without buying anything new.

When to send the form

Timing changes both the response rate and the kind of answer that comes back.

• During the stay. A short check-in question, sent on the first evening or shown on a QR code in the room, catches problems while they can still be fixed. Responses are fewer, but each one is actionable today.
• At checkout or within a few hours of it. Memory is fresh and the guest is often waiting for a taxi or a train with a phone in hand. This is where the main survey belongs.
• Several days later. Response rates fall and answers become more general. A late survey suits questions about booking, value for money and whether the guest would return.

Many hotels run the first two together: one question in the stay ("Is everything in your room working as it should?") and a longer form after checkout. The in-stay question should route to the front desk on duty, not to the person who reads the survey results on Monday.

Mobile matters more here than in most survey work. A guest in a lobby is answering on a phone with one hand, and a long single page of radio buttons will be abandoned halfway. Forms that show one question per screen with a progress bar are easier to finish on a phone, and the hotel ends up with complete answers rather than fragments.

What to ask a guest who has a minute to spare

The guest is doing the hotel a favour. Each extra question costs completions, so every question should be one the team will act on.

A workable post-stay form looks like this:

1. Overall satisfaction, on a 1 to 5 or 0 to 10 scale. Required.
2. Likelihood to recommend, on a 0 to 10 scale. This is the Net Promoter question.
3. One rating per department the hotel can actually change: room cleanliness, front desk, breakfast, noise. Three or four at most.
4. What could be better? Long text, optional.
5. May someone from the hotel contact you about your answers? Yes or no.
6. Email address, prefilled from the booking where possible.
7. Room number and stay date, prefilled or hidden, never typed by the guest.

The recommend question has a defined method. Bain & Company, which created the Net Promoter System, describes asking "How likely are you to recommend us to a friend or colleague?" on a zero-to-ten scale and calculating the score as the percentage of promoters (9 or 10) minus the percentage of detractors (0 to 6), with 7 and 8 counted as passives. The method is explained on the Net Promoter System site. Using the standard scale lets the hotel compare its numbers over time and against published benchmarks.

The permission question is the one most templates leave out, and it decides whether recovery is possible at all. A guest who says no should not be contacted, and the form should make that answer easy to see in the list of responses.

Routing a low score to a person, not an inbox

This is the step that most hotel guest feedback programmes skip. The form sends an email notification to a shared address, several people receive it, each assumes someone else will handle it, and the guest hears nothing.

A routing rule needs three parts:

A threshold. Decide what counts as low. A common choice is an overall score of 2 or below on a 5-point scale, or 6 or below on the recommend question, which matches the detractor band in the Net Promoter method.

An owner. Each low score is assigned to one named person. In a small property it may be the duty manager. In a larger one it may depend on the department rated lowest: housekeeping for cleanliness, food and beverage for breakfast.

A status that moves. The response should carry a stage that everyone can see, for example New, Read, Needs a follow up, Handled. A notification in a chat channel says that a low score arrived. A stage on the response says whether anyone dealt with it.

Here is how the same low score travels under two common setups.

The right-hand column does not need special hotel software. Several general form tools now keep an owner, a stage and a history on each response; the features page of one of them shows a board where each response sits under its stage and can be filtered by owner, tag or date.

The first 24 hours after a low score

When a low score lands, a short, repeatable sequence keeps the response consistent across shifts.

1. Read the whole response before contacting the guest. The comment often changes what the score means. A 2 for breakfast with "no gluten free options" calls for a different answer than a 2 with "found hair on the plate".
2. Check the permission answer. If the guest declined contact, record the issue for the weekly review and stop there.
3. Contact the guest within one business day. If they are still in the hotel, a call or a visit from the duty manager beats an email. If they have left, a short, specific email works better than a template apology.
4. Name what will change, if anything. "The air conditioning in room 412 has been repaired" is more credible than "Your feedback has been passed to the relevant team."
5. Record what was offered. Refunds, upgrades or vouchers should be written on the response, so the next shift can see them and finance can reconcile them.
6. Move the stage to Handled only when the guest has been contacted or the decision not to contact has been recorded.

The record from step 5 also protects the hotel from offering the same guest compensation twice, which happens when two staff members reply separately.

Public review sites and what the form must not do

A private feedback form and a public review site are different channels, and the rules for the second one affect how the first can be used.

Google's policy for user contributions on Maps lists, among things merchants should not do, to "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." The same page says that when soliciting reviews, merchants "should not require or pressure users to leave ratings or write reviews while on the premises." The full text is in Google's Maps user contributed content policy, checked for this guide on October 8, 2026.

That rules out a pattern some hotels have used: send the private survey first, and invite only the guests who scored 9 or 10 to post a public review. If the hotel asks for public reviews, the request should go to every guest in the same way, regardless of score. Google's policy also prohibits offering incentives such as discounts in exchange for a review or for removing a negative one.

What the private form can legitimately do is give an unhappy guest a direct route to the hotel. A guest whose problem is solved within a day may still leave a review, and may mention that the hotel fixed it.

Counting across rooms, shifts and seasons

Once recovery is handled, the weekly and monthly counts become useful rather than decorative. A few counts tend to produce decisions:

• Low scores by department. If housekeeping produces half of the low scores in a month, that is where the conversation starts.
• Low scores by room or floor. Repeated noise or temperature complaints from the same rooms point to a building issue, not a staff issue.
• Time from arrival to Handled. If low scores take three days to reach a guest, the routing rule is not working.
• The share of low scores with permission to contact. If it is very low, the permission question may be worded in a way that discourages a yes.
• Recommend score by month, using the promoter minus detractor method above.

All of these depend on two things: a stay date and room number attached to each response, and a stage that records whether it was handled. Without the first, counts cannot be split. Without the second, the team cannot measure how fast it responds.

What to change first

Write down the threshold for a low score and the name of the person who owns each one this week, then make sure the form asks for permission to follow up. If the current setup cannot show who owns a response and what stage it is at, try a form tool that keeps both on the response; the customer feedback use case for Halict shows a satisfaction form with those stages built in.

Q1. How many questions should a hotel guest feedback form have?

Seven or fewer for a post-stay form works well on a phone: overall satisfaction, likelihood to recommend, three or four department ratings, one open comment, and a question asking permission to follow up. Room number and stay date should be filled in from the booking, not typed by the guest.

Q2. When is the best time to send a hotel guest survey?

Send the main survey at checkout or within a few hours of it, while the stay is fresh. A single question during the stay catches problems that can still be fixed. Surveys sent several days later get fewer responses and more general answers.

Q3. Can a hotel ask only satisfied guests to leave a Google review?

No. Google's Maps user contributed content policy says merchants should not discourage negative reviews or selectively solicit positive ones. If the hotel requests public reviews, it should ask every guest the same way, whatever their private survey score.

Q4. What counts as a low score in a guest feedback survey?

Each hotel sets its own threshold, but a common choice is 2 or below on a 5-point overall rating, or 0 to 6 on the 0 to 10 recommend question. The second matches the detractor band in Bain's Net Promoter method.

Q5. Who should respond to a negative guest survey?

One named person per response, often the duty manager or the head of the department rated lowest. Assigning it to a shared inbox tends to mean either no reply or two separate replies, so the owner and the outcome should be recorded on the response itself.