Hundreds of complaints, no pattern
The complaints log is full. Each one was handled: someone apologised, sent a replacement, issued a credit. But when the operations meeting asks what customers are complaining about most, the answer is a shrug. The category field says "Other" for a large share of them, "Delivery" for a lot more, and the real detail sits in free-text notes nobody has time to read in bulk.
So the same problems keep coming back. A packaging fault on one product line, a courier that keeps leaving parcels in the wrong place, a website instruction that confuses people. Each complaint is dealt with on its own, and the cause behind the pile is never fixed.
Why the categories do not help
Complaint categories are usually a short dropdown set up years ago. They describe the symptom at a high level, such as delivery, quality or billing, and say nothing about the cause. Staff under pressure pick the first plausible option or "Other", because choosing carefully takes time and nobody seems to use the field anyway.
The useful information is in the words: what the customer said, what the agent found, what fixed it. Reading a few complaints tells you a lot. Reading thousands is impossible by hand, so the text is effectively lost as a source of insight.
What hidden complaint patterns cost
| Hidden pattern | What it costs |
|---|---|
| Repeated product fault | Returns, replacements and credits that keep coming |
| Supplier or courier problem | Complaints you absorb for someone else's failure |
| Confusing process or instructions | Contacts that should never have happened |
| Slow rise in one issue | Spotted only when it becomes a crisis |
| No evidence for decisions | Arguments about priorities based on anecdote |
There is also a regulatory side in some sectors, where complaint handling and root cause analysis are expected to be demonstrable. A log full of "Other" is hard to defend.
How we categorise complaints at volume
- We export complaint history from wherever it lives, such as Zendesk, Freshdesk, a CRM like HubSpot or Salesforce, a shared inbox or a spreadsheet, together with order, product and site details where they can be linked.
- We work with your team to define a category structure that is actually useful: the issue, the likely cause, and the part of the business responsible, at a level of detail people will act on.
- Your team labels a sample of complaints against that structure. We use the sample to train a classification model, and where labelled data is thin, we use a language model to suggest labels for people to confirm.
- The model then categorises the full history and every new complaint as it arrives, with a confidence level, sending uncertain ones to a short review queue.
- We link categorised complaints to product, supplier, courier, site and time, and build a dashboard that shows volumes and trends by cause, with alerts when an issue rises faster than normal.
- Corrections from the review queue feed back into training, and the category structure is revisited when new kinds of problem appear.
Agents do not need to change how they log complaints to begin with. The model works from what they already write, and a better dropdown can come later once you know which categories matter.
What the business sees
A clear view of what customers complain about, why, and where it comes from, updated as complaints arrive. The operations meeting starts with the issues that are growing, the products or suppliers behind them, and example complaints to read.
Fixing causes becomes possible. A supplier conversation can come with a count of complaints linked to their deliveries. A product change can be judged by whether the related complaints fall afterwards.
The customer service team benefits too. When a problem is spotted early and fixed at source, the calls and emails it would have generated never arrive, and agents spend less of their day apologising for the same thing.
Is this your situation?
- A large share of complaints are logged as "Other" or a vague category.
- The detail is in free-text notes that nobody analyses.
- The same problems seem to come back again and again.
- Nobody can say which complaint types are growing.
- You handle enough complaints that reading them all is not realistic.