Your Complaints Are Free Process Analysis
Most businesses handle complaints one at a time. Somebody is unhappy, a person sorts it out, the customer is placated, and everyone moves on. That is good service and it is also where the useful information gets thrown away.
A complaint is the only free diagnostic your business receives. Somebody has taken the time to tell you exactly where your process broke, and in most companies nobody writes it down.
Fix the case, then look at the cause
These are two separate jobs and they get conflated. The immediate one is to make the customer whole, quickly, without a lot of internal process. The second is to work out why it happened and whether it will happen again.
Businesses that only do the first get very good at recovery and never get better. The same issue comes back every few weeks, handled well each time, at a cost nobody adds up.
Record four things, not a form
Heavy complaint forms do not get filled in. Four fields, captured at the time, are enough to be useful.
- What the customer experienced. In their words, not translated into internal language.
- Where in the process it went wrong. Order taking, scheduling, delivery, invoicing, communication.
- What we did about it. Including anything it cost, in refunds, rework or time.
- Whether we have seen this before. A yes or no, and a link if there is one.
Thirty seconds per complaint. That is the whole overhead.
One complaint is an incident. The same complaint three times is a process that is working exactly as it was built to work.
Read them together, once a month
Individually, complaints look like bad luck. In a batch, patterns appear quickly, and they are usually not what people assumed.
Sit down once a month with the list and sort it by where in the process it went wrong. You are looking for the two or three that keep recurring, and for the ones that cost the most, which are often not the same items.
Most businesses find that a small number of causes account for most of the trouble, and at least one of them is something everyone had learned to live with.
The usual culprits
The causes repeat across very different businesses.
Expectations set differently by two people, usually sales and delivery. A handover where information was lost between teams. A step that depends on one person being available. Silence during a normal delay, which customers experience as something going wrong. A rule the customer was never told about until it applied to them.
Almost none of those are effort problems. They are design problems, and they are fixable once they are visible.
Pay attention to what never gets said
Formal complaints are the visible layer. Underneath are the customers who did not bother, and the staff who work around the same friction every week without calling it a problem.
Two cheap sources help here. Ask the people who deal with customers what they get asked to apologise for most often. And look at what customers ask before they buy, because a repeated question is usually a gap in how something is explained.
Close the loop where it counts
When a change comes out of a complaint, tell the customer who raised it. It takes one short message, it is unusual enough to be remembered, and it turns a bad experience into a reason to trust you.
Tell your team as well. People stop reporting problems when reporting appears to change nothing.
Track whether it worked
The point of the record is not the record. Once you have changed something, watch the same category for the next couple of months and see whether it recurs.
If it does, the fix addressed the symptom rather than the cause, which is worth knowing early rather than a year later.
Where this fits
Complaint handling is a process like any other, and the useful version has an owner, a light record, a monthly review and a way of turning findings into changes to how the work runs.
That is the kind of thing we help businesses set up. Not a quality department, just a habit that turns the same information you are already receiving into a list of things worth fixing.
Your unhappy customers are doing your process analysis for free. The only decision is whether anybody writes it down.
If the same issue keeps coming back, it is usually a design problem rather than an effort problem. Book a consultation, or visit www.expertechsolution.com.
