Quality systems
Customer complaints: the two clocks that keep you honest
Ask a customer what made them leave and it is rarely the defect. Products fail; everyone knows it. What customers do not forgive is what happened next: the complaint that vanished into a shared inbox, the three chasing emails, the resolution that arrived after they had already chosen a new supplier. The complaint was survivable. The silence was not.
Which means complaint handling is a speed problem before it is a quality problem - and speed is exactly what most complaint logs fail to measure. They record what went wrong in loving detail and say nothing about how fast anyone responded. A list of grievances with no clocks is a diary, not a system.
Two clocks, not one
Every complaint needs two timers running against two targets you set:
- The acknowledge clock - from the day the complaint arrived to the day the customer heard a human voice say "we have it, here is your reference, here is who owns it". This clock should be short: two or three working days at most, same-day for serious complaints. Acknowledgement costs nothing and buys more goodwill per pound than any other act in the process, because it converts silence into progress.
- The close clock - from arrival to a resolution the customer has actually received. The right target varies by business - ten working days is a common start - but what matters is that a target exists and breaches are visible.
Both clocks must compute from dates, and a breach must flag itself red without human intervention. And the close clock has a subtlety that catches most spreadsheets: a complaint can be late while still open. If the target is ten days and day eleven arrives with no close date, that row is late now - not on the day someone eventually closes it and the formula notices. Open-past-target complaints are precisely the ones becoming escalations this week; a log that only flags lateness retrospectively is a post-mortem tool.
Justified or not - and why you record both
Investigate honestly and some complaints turn out to be unjustified: the product met the specification, the damage happened in the customer's warehouse, the "defect" was a feature nobody explained. Record the verdict either way, for two reasons. Your improvement effort should follow justified complaints - they are the real process failures that deserve root cause work and a CAPA. And a rising unjustified share is its own signal: expectations are being set wrong somewhere - by the sales pitch, the datasheet, the packaging - and that is fixable too, just not by the factory.
Unjustified never means unanswered. The verdict changes what you fix, not whether you respond well.
From individual complaints to patterns
Handling each complaint well is table stakes; the register earns its keep in aggregate. Three views do the work. The category Pareto - complaints by type - tells you where the next improvement project lives, because complaint categories are never evenly distributed. The severity split keeps one critical complaint from hiding among twenty minor ones. And the monthly trend answers the management review's only real question: is this getting better? Add the two SLA hit rates - acknowledged on time %, closed on time % - and average days to close, and you have the complete complaints slide for your KPI dashboard, generated rather than assembled.
Serious complaints also need a document the register cannot be: a one-page complaint form for the single case - the complaint in the customer's own words, the immediate action, the root cause, the resolution, the sign-off. The register holds the patterns; the form holds the story. Manufacturing complaints will usually spawn an NCR for the nonconforming product itself; keep the reference on the complaint row so the trail survives.
ISO 9001 treats complaints as a required input to customer-satisfaction monitoring and to management review; run the two clocks honestly and the compliance takes care of itself. But the better argument is commercial: complaint handling is one of the few quality processes your customers experience directly, personally and at an emotional moment. It deserves better instrumentation than a diary.
The complaint log with the clocks built in
Two SLA clocks with automatic LATE flags - including complaints still open past target - justified verdicts, a category Pareto and monthly trend dashboard, and a printable one-page complaint form. Works for manufacturing, services and e-commerce.