Asking customers for feedback is the easy part. What you do next decides whether it was worth asking.
When people hear nothing back, they assume nobody read what they wrote, and they stop writing. When they get a quick, human reply and later see their problem fixed, they keep telling you what’s wrong, and they’re more likely to stay.
This guide covers eleven ways to respond to customer feedback and act on it. The first seven are about replying, to praise and to complaints. The last four are about turning feedback into changes.
The short version: acknowledge every piece of feedback quickly, thank people for praise, reply to complaints calmly and specifically, and sort everything you receive into bugs, feature requests and other comments. Act on what’s specific, repeated and fits your plans. Then tell customers what you changed.
- How to respond to customer feedback
- 1. Acknowledge every piece of feedback quickly
- 2. Thank people for positive feedback, and be specific
- 3. Ask to turn praise into a testimonial
- 4. Take a breath before you reply to negative feedback
- 5. Make sure you understand the problem
- 6. Move public complaints to a private conversation
- 7. Own the mistake and say what happens next
- How to act on customer feedback
How to respond to customer feedback
Before the specifics, two things help with every reply.
First, agree who handles feedback. Feedback that lands in a shared inbox nobody owns tends to sit there. Decide who reads it, who replies, and who passes bugs and ideas on to the people who can act on them.
Second, write a few reply templates for the feedback you get most often. Templates keep replies fast and consistent, but always edit them so they mention what the person actually said. A reply that’s obviously copied and pasted can feel worse than no reply at all.
Your feedback tool can take care of the first step. Saber Feedback, for example, shows a thank-you message as soon as someone sends feedback, and its Zendesk integration turns each report into a ticket your support team can reply to.
1. Acknowledge every piece of feedback quickly
Reply to everything except abuse and spam, even when you have no plans to act on it. The person took the time to write, and a short reply shows that someone read it.
Speed matters more than polish. An automatic “thanks, we’ve got this” straight away, followed by a personal reply within one working day, is a good standard for most businesses. Bug reports and complaints from paying customers deserve a faster reply than general comments.
Example acknowledgement: “Thanks for getting in touch. We’ve received your feedback and someone from our team will reply within one working day.”
2. Thank people for positive feedback, and be specific
Praise is easy to skip because nothing needs fixing. Reply anyway. Thank the person and mention what they liked, so it’s clear you read their message.
Positive feedback is also useful information. It tells you which features and moments customers value, which helps you decide what to protect, and what to do more of. Keep a log of it and share it with the team.
Example reply to positive feedback: “Thanks so much, Anna. We’re really glad the new export saved you time. The team who built it will be very happy to hear that. If there’s anything else that would make your reports easier, just reply to this email.”
3. Ask to turn praise into a testimonial
If the feedback came in privately, ask whether you can quote it on your website, in a case study or on social media. Most happy customers say yes, and a real quote from a real customer is more convincing than anything you can write yourself.
If the person isn’t a customer yet, a happy visitor is also a warm lead. With their permission, pass their details to whoever handles sales.
4. Take a breath before you reply to negative feedback
It’s tempting to reply to criticism straight away, especially when it feels unfair. Don’t. Send the acknowledgement, then take time to look into the problem before you write a full reply.
If you’re not sure how to respond, ask a colleague to read the feedback and your draft reply. A second opinion helps you avoid sounding defensive.
5. Make sure you understand the problem
You can only fix a problem you understand. If the feedback is vague, ask a specific question rather than guessing: which page were they on, what did they expect to happen, and what happened instead?
This is much easier when feedback arrives with context. A website feedback tool such as Saber Feedback attaches a screenshot, the page URL, browser and screen size to each report, so you often don’t need to ask at all.
Example clarifying reply: “Sorry the checkout isn’t working for you. So we can fix it quickly, could you tell us which payment method you chose, and what you saw after you clicked Pay? A screenshot would help a lot.”
6. Move public complaints to a private conversation
When someone complains in a public review or on social media, reply publicly and quickly, then offer to continue privately. The public reply shows other customers that you take problems seriously. The private conversation lets you sort out the details without an audience.
Example public reply: “We’re sorry about this, James, and we’d like to put it right. Could you email us at [email protected] with your order number? We’ll look into it today.”
7. Own the mistake and say what happens next
When the customer is right, say so plainly and apologise. Don’t hide behind formal language or blame the system. Then tell them exactly what happens next: that you’ve fixed it, that it’s on the list to fix, or, honestly, that you don’t plan to change it and why.
Example reply to negative feedback: “You’re right, and I’m sorry. The discount code should have worked, and it didn’t because of a bug on our side. We’ve fixed it today and refunded the difference to your card. Thanks for telling us. Other customers would have hit the same problem.”
A reply that admits a mistake and fixes it often leaves a customer happier than if nothing had gone wrong.
How to act on customer feedback
Replying keeps customers on side. Acting on feedback is what improves your product or website. These four steps turn a pile of comments into a short list of changes.
8. Sort feedback into categories
Start by sorting each piece of feedback into a category. These five work for most websites and web apps:
- Major bugs: something important doesn’t work, such as sign-up, checkout or a core feature. Fix these first.
- Minor bugs: small problems that don’t stop people using your product, such as a broken link or a layout glitch on one browser.
- Feature requests: ideas for something new or different.
- Questions: signs that something is unclear, which you can often fix with better wording or help content.
- Praise: what people like, to keep and build on.
Tag feedback as it arrives, so the categories stay up to date. Many teams send bugs straight to their issue tracker, for example with Saber Feedback’s Jira or Trello integrations, and ideas to a separate list.
If you get a lot of feedback, AI tools can help here. They’re good at grouping similar comments and summarising the main themes. Check the groups yourself before you act on them, because a summary can hide the details that matter.
9. Decide which feedback to act on
You can’t act on everything, and you shouldn’t try. Feedback pulls in different directions, and acting on every request leads to a cluttered product. Before you spend time on a change, check that the feedback:
- Describes a specific problem. “Your site is rubbish” gives you nothing to work on. “I can’t find the cancel button on mobile” does.
- Comes from more than one person. One complaint might be a one-off. The same complaint from several customers is a pattern worth fixing.
- Comes from the people you serve. Long, detailed, polite feedback usually comes from people who care about your product. Weigh it more heavily than drive-by comments.
- Fits your plans. If a suggestion would change what your product is for, it’s probably not for you, however loudly it’s made. You can’t please everyone.
Bugs are the exception. If a bug is real, fix it, even if only one person reported it.
10. Prioritise and plan the work
For everything that passes step 9, compare the impact with the effort. How many customers does it affect, and how much? How long will it take to fix or build? Quick fixes with a big impact go first. Big changes with a small impact may never be worth doing.
Put the work into your normal plan or roadmap, with someone responsible for it. Feedback that isn’t owned by anyone rarely turns into a change.
Review feedback on a regular schedule, too, such as weekly for bugs and monthly for feature requests. That keeps small problems from piling up and shows you how feedback changes over time.
11. Close the loop with your customers
When you fix a problem or ship a feature someone asked for, tell them. A short message is enough:
Example follow-up: “Hi Priya, a few weeks ago you asked if you could export reports to CSV. You can now, from the Reports page. Thanks for the suggestion, and let us know what you think.”
Closing the loop is the step most businesses skip, and it’s the one that makes customers keep giving feedback. It shows that their time made a difference. Share what you’ve changed more widely too, in release notes, a changelog or your newsletter.
Finally, pass on praise inside your team. Tell the people who built a feature when customers love it. Feedback isn’t only a list of problems to fix.
Collect better feedback to start with
Responding and acting is much easier when the feedback you collect is clear and complete. For more on collecting it, see our guide to collecting website feedback, our ready-to-use feedback form templates, and our feedback rate benchmarks to see how much feedback to expect.
Saber Feedback adds a feedback button to your website. Each report includes a screenshot and the visitor’s browser details, and goes straight to your inbox and the tools your team already uses, such as Jira, Slack, Trello, Asana and Zendesk. Plans start at $49 a month, with screenshots and integrations from $99.