What it means
A complaint gives the business a view of where its promise and the customer's experience diverged. The first response should acknowledge the issue, check any urgent safety or service need and give an owner.
Later, the team can investigate why it happened, and these are separate steps: customers need help now, while managers need learning that reduces recurrence. Define the event accurately by recording what the customer expected, what occurred, dates, order or service reference and the effect, preserving the customer's own account without treating it as the only evidence.
Check dispatch, call, invoice or product records, because a complaint may involve several failures, such as a defective item followed by slow support, and the entire experience should not collapse into the first technical fault found. Trace the chain of causes by asking why the immediate event occurred and what control should have caught it.
For example, a wrong item shipped because the picker scanned an incorrect shelf label, and the label was wrong because a new product was put away without master-data review. The useful corrective action may be at the earlier step, and methods such as a timeline or repeated "why" questions help, but a neat single cause should not be forced when several factors interacted.
Include the customer's context, since a 24-hour delay may have little effect for one order and close a customer's business for another, so check whether the business knew the customer's deadline and made a suitable promise. A root cause can include unclear communication or an unowned handoff even if the physical goods were correct, and another customer's private details should not be shared when explaining the finding.
Test corrective actions, because training alone may not fix a system that permits the same error and better labels, approval checks, capacity rules or supplier changes may be needed. Assign an owner and date, then measure whether the relevant complaints or defects fall, and tell the customer what was done at a level supported by facts without promising that no future error is possible.
A short-term workaround can coexist with a longer process fix. Look for patterns across complaints, since one case may reveal a wider issue in a product batch or site, and categorise causes consistently while allowing revision when evidence changes.
A low complaint count is not proof of happy customers if the reporting route is difficult, so staff should record cases honestly rather than closing them under vague categories to meet a target. For owners, understanding root cause turns a painful complaint into a chance to improve the business.
The aim is fewer repeat failures and a fair response to the person affected, not a polished explanation that leaves the process unchanged.
In practice
Real-world examples.
Example
A customer complains that a delivery arrived two days late. The review finds the sales team promised a date before stock was reserved, so the business changes its order confirmation rule to reserve stock first. The late delivery was the symptom, and the unrealistic promise was the cause.
Example
A wholesaler receives repeated billing complaints from different customers. The pattern points to an outdated price file rather than individual clerk errors, so finance updates the source data and reissues the affected invoices. Retraining the clerks alone would not have stopped the problem.
Example
A customer reports a faulty appliance and then waits ten days for a reply. The product fault and the delayed response are investigated separately because both shaped the customer's experience, and each gets its own owner and corrective action.
Formula
Calculation
Repeat-cause complaint rate = Complaints linked to a previously identified cause / Complaints investigated in the period x 100
Worked example. An invented business investigates 80 complaints in a quarter; 20 stem from causes identified in earlier reviews.
- Repeat-cause rate = 20 / 80 x 100 = 25%.
- The team checks whether earlier corrective actions were completed and effective, rather than simply reopening each customer case.
Consistent classification is needed, and some complaints can have multiple causes.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Maple Meals, an invented food delivery business. Customers complained about missing side dishes. Customer service refunded individual items, but the same complaint kept appearing. Managers first assumed packers were inattentive. A review of orders, menus and packing screens found that one promotion listed the side dish in customer-facing copy but not in the warehouse pick ticket.
Packers followed the ticket they received. Maple corrected the product setup, checked other promotions and gave affected customers an appropriate remedy. It also added a test order before launch of complex offers. Refunds had addressed individual losses, but the source-data fix stopped the repeat failure. The owner learned to look at the whole chain rather than blaming the last employee who touched the order.
Watch out
Common mistakes.
- Delaying customer recovery until a full investigation is complete.
- Stopping at the person nearest the mistake instead of checking process and source data.
- Calling a corrective action complete without testing whether recurrence falls.
Questions
People also ask.
Can a complaint have several root causes?
Yes. Product, process and communication failures may each contribute and need separate actions.
Should the customer receive the full internal analysis?
Share supported facts and relevant remedies without exposing private details or unverified speculation.
How is the fix checked?
Track implementation and relevant repeat complaints or defects over a suitable period.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%