How to close the feedback loop with customers

Asking for feedback creates an expectation. A customer who takes two minutes to tell you the shower was cold assumes someone will read it. If nothing happens, and nothing ever seems to happen, they stop answering, and the ones who keep answering are the ones angry enough to do it anyway.

Closing the feedback loop means making sure something does happen, and that the customer can tell. This guide covers the two loops involved, which follow-ups to automate, and how to check whether your fixes worked.

Two loops, not one

There are two separate jobs here, done by different people on different timescales.

The inner loop is about the individual. One customer said something; someone responds to that customer. A reply to an unhappy guest, a thank-you to a happy one, a quick call to resolve a specific problem. It happens in hours or days.

The outer loop is about the cause. Many customers said similar things; someone fixes the underlying problem and then tells customers it has been fixed. It happens over weeks.

Most teams do some of the inner loop and very little of the outer one. They apologise to every guest who complains about breakfast, month after month, and breakfast never changes. The apologies become a ritual. Both loops are needed.

The inner loop: respond to each customer

Who gets a response

You can't phone everyone, and you don't need to. A practical rule set for a hypothetical 40-room hotel might look like this:

Adjust the thresholds to your business. The point is to decide in advance, so responses don't depend on who happens to be reading that week.

What a good response says

• Use their words. If they mentioned the cold shower, mention the cold shower. A reply that could have been sent to anyone reads as if it was.
• Apologise once, plainly. "I'm sorry the shower in your room ran cold." Not "we apologise for any inconvenience you may have experienced."
• Say what you did or will do. "Our maintenance team has replaced the valve in that room." If you don't know yet, say when you'll know.
• Give a way to reply. A name and a direct email, not a no-reply address.
• Keep it short. Four or five sentences.

Public reviews follow the same principles, with a few differences, since future customers read your reply too. Our guide to responding to negative reviews covers those.

Don't forget the happy customers

Thanking people who liked you is easy to skip and worth doing. It costs little, it tells them their reply was read, and it is a natural moment to ask for a public review, since they have already said something good in private.

Automate the routine parts

Much of the inner loop follows simple rules, which makes it a good candidate for automation. The aim isn't to remove people; it's to make sure nothing is missed and that people spend their time on the replies that need a human.

Some example rules:

1. Low rating → apology email and team alert. When someone rates 1 or 2, send a short, sincere acknowledgement straight away ("Thank you for telling us. I'm sorry it wasn't right. I'll be in touch personally by tomorrow.") and notify the manager with the full reply. The manager then follows up in person.
2. High rating → thank-you. When someone rates 4 or 5, send a thank-you. If you want reviews, include a link to your listing.
3. Specific topic → specific person. When a reply mentions a broken item in a room, alert maintenance. When it mentions a food allergy, alert the kitchen.
4. Free-text only → review queue. Replies with a comment but a middling score go to a short daily list for someone to read and decide.

Two cautions. First, an automatic apology must be followed by a real person, or it does more harm than none. Second, write automated messages in the same plain voice as a personal one, and never pretend an automatic message was typed by hand.

The outer loop: fix the cause

Replying to individuals doesn't stop the next guest having the same problem. For that you need to look across all replies, find what keeps coming up, and change it.

Find the patterns

Group every reply and review into topics, record whether each mention is positive or negative, and track each topic's share of conversation: the percentage of replies that mention it. Rank the negative topics by how many customers they touch, how strongly they are linked to low ratings, and whether they are growing. Our guide to analysing open-ended survey responses explains the method.

Then pick one or two to fix. Not ten.

Make the change, with an owner

For each fix, write down:

• What will change. "Add a second person at reception from 2pm to 6pm on Fridays and Sundays."
• Who owns it. A named person, not "the team".
• When. A date.
• What should move. "Negative mentions of check-in waiting time should fall."

A monthly customer feedback report with an actions table is a simple way to keep this visible.

Tell customers what changed

This is the step most often skipped, and it is what makes customers feel heard. Ways to do it:

• In replies. When someone mentions a problem you have since fixed, say so: "You're right that check-in used to be slow on Sundays; we've added staff at those times."
• In public review responses. Future customers see that you act on what people say.
• To the people who raised it. A short note to customers who complained about something, telling them it has changed, is rarely sent and often appreciated.
• On the form itself. A line at the top of your survey ("Last season you told us the lake was too crowded; we've added a second swim session") shows people their answers matter, and can make them more willing to answer.

Check whether the fix worked

A fix isn't done until the feedback shows it. After making a change, keep watching the topic for the following weeks.

What to look for:

Use share of replies, not raw counts. If you made the fix just before your busy season, raw complaint numbers may rise even though the problem has eased.

When a fix doesn't work, go back to the replies. Read ten recent ones on that topic. Often the original reading was slightly off: the complaint was never about the queue at reception, it was about the room not being ready at check-in time.

Making it a habit

The loops only work if they run every week, not once after a bad month. A simple rhythm:

• Daily: automated replies go out; someone reads the alerts and the review queue.
• Weekly: a quick look at which topics are moving.
• Monthly: pick fixes, check last month's fixes, tell customers what changed.

Doing this with Userforms

Userforms has journeys for the inner loop: automatic follow-ups that can apologise to a low rating, thank a happy customer or alert your team by email, with webhooks, WhatsApp and Telegram actions on Pro. Email notifications let the right person see a reply as it arrives.

For the outer loop, every reply and review is filed into topics with a tone per mention, and the dashboard shows which topics grew or shrank in share and turned better or worse against the previous period, so you can see whether a fix moved anything. Each form also writes a report you can issue as the month's record.

You can start for free, or see what each plan includes on the pricing page.