Closed-loop feedback

Closed-loop feedback is the practice of responding to the people who gave feedback: you follow up with each customer who reported a problem, fix what you can, tell them what changed, and feed recurring issues back into the product or process. It turns a score such as NPS or CSAT into actions customers can see.

The term became common with the Net Promoter System. Fred Reichheld and Rob Markey describe it in The Ultimate Question 2.0 (2011) as two loops working together: an inner loop with individual customers and an outer loop with systemic fixes.

Inner loop and outer loop

Teams that only run the inner loop keep apologizing for the same issue. Teams that only run the outer loop fix things but leave individual customers feeling unheard. You need both.

How closing the loop works, step by step

1. Collect feedback with a reason. A score alone tells you who is unhappy, not why. Ask a follow-up open question after the NPS, CSAT or CES question.
2. Route it. Send each low score, with the comment, to the person who will act on it. Set a response deadline your team can keep, for example two business days.
3. Contact the customer. Thank them, ask what happened, and listen before explaining. The goal is to understand and to fix, not to change the score.
4. Resolve and record. Solve the case where possible, then log the root cause with a short, consistent category so that patterns can be counted.
5. Review patterns. In a regular meeting, rank root causes by how many customers they affect and pick owners for the top ones. This is the outer loop.
6. Tell customers what changed. A short "you told us, we did" note to the people who raised an issue, and in release notes, shows that feedback has an effect.

Worked example

An online store sends an NPS survey after delivery. In one month, 1,000 customers answer: 520 promoters, 280 passives, 200 detractors, so NPS = 52% − 20% = 32. Support contacts 170 of the 200 detractors within two business days, an 85% contact rate. Root-cause tags show that 90 detractors mention late delivery in one region. The outer loop moves that region to another courier. Three months later the share of detractors mentioning delivery has dropped, and the team can show the change in the same survey.

The numbers worth tracking are the contact rate, the time to first contact, the share of cases resolved, and the trend of each root cause. You can check NPS itself with the NPS calculator.

Common mistakes

• Asking without capacity to answer. If nobody can follow up, low scores pile up unread. Start with a volume your team can handle, for example one segment or one touchpoint.
• Only calling detractors. Passives often name the one thing that would make them promoters, and promoters can say what to keep.
• Arguing with the customer or sending a scripted apology. Both confirm that nobody read the comment.
• Asking for a better score. "Please give us a 10 next time" distorts the metric and annoys people.
• No outer loop. Without root-cause categories and owners, the same complaints return every month.
• Promising follow-up in an anonymous survey. You can only contact people you can identify, and they should know that when they answer. In an anonymous survey, close the outer loop and share the changes publicly.

Closing the loop with SurveyNinja

• The NPS question can ask for the reason behind the score, with its own follow-up text for detractors, passives and promoters. This works on every plan, including Free, and the report counts NPS and the three groups.
• Email notifications about new responses work on every plan, so the right person sees a low score with its reason as it arrives.
• From the Basic plan, webhooks, Zapier and Google Sheets send each response to a help desk, CRM or task list, and filters show only low scores. Telegram notifications come with Standard.
• From the Basic plan, hidden variables pass a customer or order ID in the survey link, so the person who follows up knows who answered without asking the customer again.

Closed-loop feedback is part of a wider voice of the customer program. For the delivery side, see email notifications and webhooks; for the business result, see customer retention.