"Closed" Is Not "Resolved": Fixing After-Sales Complaint Governance

Every service dashboard I've ever reviewed looks healthy. Complaints logged, complaints closed, a closure rate north of ninety-something percent. Then you call ten of those "closed" customers and discover a third are still unhappy, a quarter never got a real fix and a few didn't know the case was closed at all. The dashboard wasn't lying. It was measuring the wrong thing.

"Closed" is an internal status. "Resolved" is a customer outcome. They are not the same and the gap between them is where your reputation quietly bleeds.

The closure illusion

In a lot of service operations, a case is closed when the technician or the agent says it's done. Nobody checks with the customer. That single shortcut creates a chain of expensive problems:

• Repeat complaints. The "fix" didn't hold, so the customer calls again, often logged as a fresh case, so the same failure never shows up as a pattern.
• Silent churn. A customer who feels unheard doesn't always complain twice. Sometimes they just don't buy from you again and never tell you why.
• Warranty and safety exposure. A recurring fault that's repeatedly "closed" instead of root-caused can become a far larger and costlier problem in an industrial setting.
• A blind NPS. If you're not systematically asking after resolution, your sense of customer satisfaction is anecdote, not data.

What disciplined complaint governance looks like

A managed service operation treats a complaint as a process with a verified ending, not a ticket to be cleared. The flow we run:

1. 01Registration and routing. Every complaint, from every channel, is logged in one place and routed to the right owner immediately, no enquiry lost in a WhatsApp thread or a personal inbox.
2. 02MTTR monitoring and escalation. Mean time to resolve is tracked against a target and aging cases escalate automatically before they breach, instead of after a customer chases.
3. 03Closure verification. This is the step that changes everything: a case is not closed because the fixer says so. It's closed after an independent check confirms the customer agrees it's resolved.
4. 04Post-resolution feedback (NPS). Satisfaction is captured right after the case closes, while the experience is fresh, turning a vague sense of "service is fine" into a number you can act on.
5. 05Repeat-complaint identification and RCA. Recurring issues are flagged and root-caused, so the operation fixes the cause, not just the tenth instance of the same symptom.

The discipline that matters most

The most important discipline is the separation between fixing and verifying. When the same person who closes the case also reports it as resolved, closure rates always look excellent and customers often don't agree. An independent verification and feedback layer breaks that conflict of interest. It's the difference between a number that flatters you and a number you can trust.

The test to run this week

Pull twenty cases your team closed last month and have someone neutral call the customers. If the answers match your dashboard, you have a genuinely strong operation. If they don't, you've just found the gap between "closed" and "resolved" and that gap, not your technicians' skill, is what your customers actually remember.