To close the customer feedback loop, tell every customer who gave feedback what happened to it. It takes five steps: collect feedback from every channel, organise it into requests linked to the customers who asked, decide what to build and what to decline, build it, and tell each customer at every status change, including when the answer is no. Acknowledge new feedback within two business days, then send an update when an idea is planned, started and shipped. Murmur automates the last step by emailing every voter when an idea's status changes.
Most companies are good at asking for feedback and bad at answering it. Customers post an idea, vote, mention it on a call, and then hear nothing. A few months later they stop bothering. Closing the feedback loop is how you keep them talking.
What is a customer feedback loop?
The cycle of collecting feedback from customers, deciding what to do about it, making changes, and telling customers what changed.
A product feedback loop is the same cycle focused on your product: feature requests and bug reports go in, decisions and releases come out, and the customers who asked hear about it.
What does closing the feedback loop mean?
Closing the feedback loop means going back to the customers who gave feedback and telling them what happened to it. Not a general announcement, but a message to the specific people who asked: we heard you, here is what we decided, here is what changed. An automatic "thanks for your feedback" email does not close the loop; it only opens it.
This is also called closed-loop feedback. In survey programs the term usually means following up on NPS responses; for product teams it means following up on feature requests. The steps below cover both.
Why closing the loop matters
- Customers keep giving feedback when they can see it leads somewhere.
- Shipped work gets used. The people who asked for a feature are its most likely first users, if they know it exists.
- Support load drops. Fewer "any update on this?" tickets when updates arrive on their own.
- A no keeps trust. A clear reason beats silence, which customers read as being ignored.
How to close the customer feedback loop in 5 steps
1. Collect feedback from every channel
Feedback arrives through support tickets, sales calls, emails, Slack, reviews and your feedback board. Capture all of it, with the customer's own words and who said it. If you only count what customers post on a board, you miss most of what they ask for. Our voice of the customer guide covers the main sources.
2. Organise it into requests linked to customers
Group feedback into requests and merge duplicates, keeping every customer attached. This is the step that makes closing the loop possible: if you do not know who asked, you cannot tell them. Murmur's Autopilot does this for you, extracting requests from forwarded emails and matching each one to an existing idea with the customer linked.
3. Decide what to build, and what to decline
Rank requests by the number of customers who asked, how important it is to them, and the revenue they represent. Then make a call and set a status: planned, under review, or closed with a reason.
4. Build it
Move the idea to in progress and ship. If you build with coding agents, keep the customers' words with the work: Murmur's MCP server lets Claude Code or Cursor read the request and its comments, and Fix with Claude can turn an approved idea into a pull request for you to review.
5. Tell every customer who asked
When the status changes, email everyone attached to the request. When it ships, publish it to your changelog too. This is the step that closes the loop, and the one teams most often skip because it relies on someone remembering. Send from a real address people can reply to, never a no-reply.
A few weeks after a release, ask the people who requested it one question: did this solve the problem you had? Their answers feed straight back into step 1.
The inner loop and the outer loop (small loop and big loop)
| Inner loop | Outer loop | |
|---|---|---|
| Scope | One customer, one piece of feedback | Patterns across many customers |
| Who owns it | Support, success, sales | Product and leadership |
| Typical action | Reply, fix an account, explain a workaround | Ship a feature, change a policy |
| Closed when | The customer hears back | Everyone affected hears what changed |
A healthy program runs both. The inner loop (also called the small loop) keeps individual customers happy this week; the outer loop (the big loop) is how their feedback changes the product. Some teams add a third, broader update: a regular "you asked, we built it" changelog post or newsletter for every customer, not just the ones who voted.
Closing the loop on NPS feedback
- Detractors (0 to 6): reach out personally within one to two business days. Ask what went wrong and fix what you can.
- Passives (7 and 8): ask what one change would make the product a 10 for them. These answers are often feature requests.
- Promoters (9 and 10): thank them, then invite them to a beta, a review site or a case study.
Closing the loop: email templates
Short, specific and signed by a person. Copy these and change the words in brackets.
Feedback received
Subject: We got your request: [request]
Hi [name],
Thanks for telling us about [request]. I've added it to our feedback board, where [number] other customers have asked for the same thing. You'll get an email when its status changes.
[Your name]
Planned
Subject: [Request] is on the roadmap
Hi [name],
You asked for [request], and it's now planned. We expect to start in [timeframe]. If you'd like to try an early version, reply to this email.
[Your name]
Shipped
Subject: Shipped: [request]
Hi [name],
You asked for [request] back in [month], and it's live today. Here's how to use it: [one line or link]. Thank you for taking the time to tell us.
[Your name]
Declined
Subject: An update on [request]
Hi [name],
We've decided not to build [request] for now, because [one-sentence reason]. In the meantime, [workaround]. If [condition] changes, we'll look at it again and let you know.
[Your name]
A feature request template
Closing the loop is much easier when every feature request is captured the same way. Ask for, or record, these fields:
| Field | Example |
|---|---|
| What do you want to do? | Pull data from Google Sheets |
| Why? What are you trying to get done? | Our weekly report lives in a sheet |
| How do you do it today? | Export a CSV every Monday and upload it |
| How important is it? | Nice to have, important, or must have |
| Who is asking? | Grace, Fieldnote, $2,400 MRR |
Murmur's portal and widget collect the first and fourth fields as customers post, and the signed-in widget fills in the last one. Read more about feature request management.
How to measure your feedback loop
- Time to acknowledge: hours from feedback to first reply. Aim for under two business days.
- Loop closure rate: share of shipped or declined requests where every voter was told. Aim for 100%, sent within one or two business days of the release or decision.
- Repeat feedback: customers who give feedback again within 90 days.
- Adoption by requesters: how many people who asked for a feature use it in its first month.
How to automate closing the loop with Murmur
- Customers post and vote on your portal or in-app widget, and Autopilot adds requests from forwarded email.
- Every request keeps its voters, their company and their revenue.
- You change an idea's status to planned, in progress or shipped.
- Murmur emails every voter about the change. For shipped ideas, publish a changelog entry, which a Murmur Assist assistant can draft for you.
Voter emails are on Solo ($19 a month) and Team ($49 a month), and new workspaces get Team free for 14 days. See pricing or try the live demo.
Frequently asked questions
What is a customer feedback loop?
A customer feedback loop is the cycle of collecting feedback from customers, deciding what to do about it, making changes, and telling customers what changed, so they keep giving feedback.
What does it mean to close the feedback loop?
Closing the feedback loop means following up with the customers who gave feedback to tell them what happened to it: that it was received, planned, built, shipped or declined, and why.
How do I close the feedback loop?
Link every piece of feedback to the customer who gave it, group it into requests, and send an update to everyone attached to a request whenever its status changes. A feedback tool that emails voters automatically, such as Murmur, makes this happen without anyone remembering to do it.
What are the 5 steps of a feedback loop?
Collect feedback from every channel, organise it into requests linked to customers, decide what to build and what to decline, build it, and tell every customer who asked what happened.
What is closed-loop feedback?
Closed-loop feedback is the practice of following up with each customer who gave feedback, acting on it, and telling them the outcome. In NPS programs it means contacting respondents, especially detractors; for product teams it means telling everyone who requested a feature what happened to it.
How quickly should you respond to customer feedback?
Acknowledge new feedback within two business days, ideally the same day. After that, update customers whenever the request changes status rather than on a fixed schedule.
What is a product feedback loop?
A product feedback loop is a customer feedback loop focused on the product: feature requests and bug reports flow to the product team, decisions are made, changes ship, and the customers who asked hear about it, often through a changelog and status emails.
How do you close the loop when the answer is no?
Tell the customer directly, explain the reason in one or two sentences, suggest a workaround if there is one, and leave the door open by saying what would change your mind. A clear no keeps more trust than silence.
What is the difference between the inner and outer feedback loop (small loop and big loop)?
The inner loop is the follow-up with an individual customer about their feedback. The outer loop is the company-level change that feedback from many customers leads to, such as a new feature or a changed policy.
Collect it, rank it, ship it, tell everyone
Murmur is customer feedback software for small SaaS teams: a feedback portal and widget, AI that captures requests from email, revenue on every vote, and emails to every voter when you ship. Free for one board with unlimited voters.