KjerrThe customer feedback loop,
and how to close it.
A customer feedback loop is the cycle of collecting feedback, acting on it and telling the people who gave it what happened. Most teams collect well and reply badly. This guide explains the four stages, where loops break, and how to close them every time.
What a customer feedback loop is
A customer feedback loop has four stages: collect, acknowledge, act and follow up. Feedback enters, the team makes a decision, and the decision travels back to the person who spoke. When the last stage is missing, customers experience a suggestion box: things go in and nothing comes out.
The loop matters because feedback is a relationship, not a dataset. A customer who asked for an export and later reads that the export shipped has learned that asking works. A customer who never hears back has learned the opposite, and stops asking.
The four stages
- 1. Collect in one place. Requests arrive by email, chat, calls and support tickets. Give them one public home, a feature request tool where users can post, search and vote, and have your team add the ones that arrive elsewhere on the customer's behalf.
- 2. Acknowledge and organise. Read everything, merge duplicates so demand adds up on one request, and give each request a status. An idea with no status is a question nobody answered. A feedback tracking tool with a personal inbox shows each teammate what they have not read yet.
- 3. Decide and act. Use the votes and who is asking to choose. Move the request to planned, in development, shipped or declined as the work happens, so the public roadmap stays true.
- 4. Follow up. Tell everyone who asked what happened, at the moment it happens. This is the step that closes the loop.
Where feedback loops break
Feedback loops rarely break at gathering customer feedback. They break between the decision and the reply, because that step depends on memory.
- Requests live in five tools, so nobody knows how many people asked for the same thing.
- The people who asked are in a spreadsheet, or in nobody's head.
- Shipping is announced to everyone, and to no one in particular.
- Declined requests get silence, so they are asked again every quarter.
Closing the customer feedback loop, step by step
Closing the customer feedback loop takes three habits. First, keep the request and the list of people who want it in the same record, so the audience for the reply already exists. Second, reply on the request itself, in public, so one answer serves everyone who finds it later. Third, make the reply automatic: a status change should send the message, because a message that depends on someone remembering will not be sent.
When the answer is no, say so with the reason. A declined request with one honest sentence closes the loop as surely as a shipped one.
How Kjerr automates the loop
Kjerr is customer feedback software built around the fourth stage. The reply is a side effect of work the team already does.
- A status change emails the idea's author and every voter, within seconds.
- When a change is only housekeeping, a teammate can make it without the email.
- An admin reply does the same, so an answer reaches everyone who asked.
- Emails go out under your workspace name, each with one-click unsubscribe.
- Votes alone never send email, so people are only written to when something changed.
- Reports counts the requests still awaiting a response, and for how many days.
- For everyone who did not vote, publish a post with the release notes tool.
Two loops: the person and the product
It helps to see two loops inside the one. The inner loop is with a person: someone asked, and that someone gets an answer. The outer loop is with the product: many requests point at the same problem, and the product changes. Teams that only run the outer loop ship good things and tell nobody. Teams that only run the inner loop reply politely and change nothing.
A public board joins them. Votes gather the inner loops into one visible request, the decision on that request is the outer loop, and the reply to everyone who voted closes both at once.
Customer feedback loop examples
Three short customer feedback loop examples, each ending in a reply.
A request that ships
Forty people vote for CSV export. The team marks it planned, then in development, then shipped. Each change emails all forty. The last email is the release announcement they actually open, because they asked for it.
A request that is declined
Six people ask for a dark theme in exported PDFs. The team declines it and writes one sentence on why. Six people stop waiting, and the next person who searches for it finds the answer instead of posting it again.
A request that arrived by phone
A customer asks for two-factor sign-in on a call. A teammate posts it on their behalf and adds their vote. When it ships, the customer hears about it like every other voter, without anyone remembering the call.
Five mistakes that keep the loop open
Most open loops come from the same few habits, and each has a small fix.
- Collecting without a status. Give every request a state within days, even if the state is under consideration.
- Replying in private. An answer in one inbox helps one person. The same answer on the request helps everyone who finds it.
- Announcing only to everyone. A release post is not a reply. Tell the people who asked, specifically.
- Avoiding no. Silence reads as maybe, and maybe brings the request back.
- Emailing too much. Write when something changed, never for a vote, and let people unsubscribe in one click.
How to tell whether your loop is closed
Two numbers tell you. The first is how many requests have no status or reply; Kjerr's Reports page calls these awaiting response and shows the oldest. The second is time to ship: how long a request takes from posted to shipped. Neither needs a survey. If the first number is near zero and people keep posting, the loop is closed. The other numbers worth watching are in the guide to customer feedback analytics.
Questions, answered plainly.
What is a customer feedback loop?
A customer feedback loop is the cycle in which a company collects feedback from customers, decides what to do about it, acts, and tells the customers who spoke up what happened. The last step is what makes it a loop: without the reply, feedback only travels one way.
What does closing the customer feedback loop mean?
Closing the customer feedback loop means going back to the people who gave feedback and telling them the outcome: planned, shipped, or declined and why. It turns a request into a conversation and gives people a reason to give feedback again.
What are the stages of a feedback loop?
Four: collect the feedback in one place, acknowledge and organise it, decide and act, then follow up with everyone who asked. Most teams do the first three and skip the fourth.
Why do feedback loops stay open?
Because the reply is manual. Someone has to remember who asked, find their addresses and write to them, months after the request. Unless the tool that holds the request also sends the reply, it rarely happens.
How do you close the feedback loop when the answer is no?
Say no in public, on the request itself, with the reason. A declined status with one honest sentence is better than silence; people stop waiting and the same request stops coming back.
How does Kjerr close the loop?
A status change or an admin reply emails the idea's author and every voter, under your workspace name, with one-click unsubscribe. Votes alone never send email. Nobody has to keep a list of who asked.
Related pages
Give your users an answer.
Kjerr is free during early access, with every feature included and no credit card. When paid plans arrive they will be priced per workspace, never per admin seat and never per tracked user, so the number of people who post, vote or comment never changes the bill.