Closed-loop feedback is a management approach that ensures customer feedback does not remain a line in a report, but reaches the relevant person, leads to a follow-up with the customer and has its outcome measured. Collecting surveys is only the beginning of the loop; the loop closes when the customer confirms that the issue has been resolved.
Inner Loop and Outer Loop
According to the framework defined in Bain & Company's Net Promoter approach and published in Harvard Business Review, a closed loop works on two levels:
- Inner loop: Responds to the feedback of an individual customer. The customer who had a negative experience is followed up with, the issue is resolved and the resolution is confirmed with the customer. The owner is usually the branch or team manager.
- Outer loop: Draws structural improvements from recurring feedback. If the same root cause recurs across different branches and periods, a change in process, product or policy is needed. The owner is usually the head office teams.
When the two do not work together, the same problems are solved over and over again.
Setup: Step by Step
1. Detection
Which feedback requires action should be defined in advance. For example, a CSAT of 2 or below on a 1-5 scale, an NPS of 0-6 or the selection of a particular root cause (damaged product, safety issue) can automatically open a case. Clear rules ensure that no negative experience goes unnoticed.
2. Assignment
The case is assigned to the person responsible for the unit where the experience took place. When assignment is done automatically based on the organization structure, ambiguity about ownership disappears: an issue at the Kadıköy branch goes to the Kadıköy branch manager.
3. Prioritization and Deadlines
Every case should have a priority and a resolution deadline. Critical cases (experiences involving health, safety or legal risk, or very low scores) are handled in a shorter time. When the deadline is exceeded, the case is escalated to the next level; this tiered escalation keeps pending cases visible.
4. Following Up With the Customer
The responsible person contacts the customer, listens to the issue and offers a solution. The speed of the follow-up often noticeably affects how the customer perceives the resolution. The action taken (call, product exchange, refund, compensation) is recorded.
5. Closure and Root Cause
When the case is closed, what was done and the source of the problem are recorded with standard codes. Using closure codes instead of free text makes the analysis needed for the outer loop possible.
6. Resolution Satisfaction
The last step of the loop is to ask the customer whether the issue has been resolved. A short resolution satisfaction question ("Has the issue you reported been resolved?" Yes / Partially / No) both shows the customer that they matter and measures whether the closed case was actually resolved.
Metrics to Track
- Share of cases handled on time: The share of cases where the first response was made within the defined time.
- Average first response and resolution time: When compared by unit and region, it reveals operational differences.
- Overdue open cases: The most critical indicator for real-time monitoring.
- Resolution satisfaction: The share of closed cases in which the customer confirms that the issue has been resolved.
- Root cause distribution: The priority list for the outer loop.
Common Mistakes
- Notifying everyone. Sending every negative response to all managers dilutes ownership. A case should be assigned to a single responsible person.
- Not defining deadlines. A case without a deadline gets put on hold and forgotten.
- Not asking the customer about closure. Not every case the organization marks as resolved is resolved for the customer.
- Skipping the outer loop. Solving only individual cases leads to the same problems recurring.
For handling complaints as a structured organizational process, see the complaint management process guide, and for metrics, see the NPS, CSAT and CES comparison guide.