Customer complaint tracking turns scattered gripes into a pattern you can fix. If you log every complaint with a category, an owner and an outcome, then review them together, you will see root causes instead of repeat symptoms.
This guide builds on how to handle customer complaints by focusing on the record-keeping and analysis side.
| Item | Value |
|---|---|
| Complaints-handling standard | BS ISO 10002:2018 |
| BSI publication date | 31 Jul 2018 |
| Year ISO 10002 was first introduced | 2004 |
| Guidance for small businesses | Annex B of the standard |
| Customers who stop buying after a bad experience | Nearly a third (per surveys cited) |
The figures come from the BSI Knowledge listing and a SafetyCulture topic guide. They can change, so check the sources before you rely on them.
Why does tracking complaints matter?
A single complaint is an anecdote. A logged set of complaints is evidence, and evidence is what lets you fix the cause rather than apologise for the symptom again next week.
The stakes are real. According to surveys cited by SafetyCulture, nearly a third of customers stop doing business with a brand they love after a bad experience. Every complaint you fail to record is a missed chance to find out what went wrong.
The BSI listing for the standard names this aim directly: analysing and evaluating complaints in order to improve products and services, including customer service.
What a complaint record should capture
A useful record is short enough that staff will actually fill it in, and structured enough that you can sort it later. A typical entry holds these fields:
- The date the complaint arrived and the channel it came through.
- A customer reference, so repeat contacts can be linked.
- The product, service, branch or team involved.
- A category, plus a rating for seriousness and urgency.
- The person who owns the case.
- What was done, and how the customer responded.
- The root cause, added once it is known.
Capture matters as much as the fields. SafetyCulture’s guide says that by offering multiple, easy-to-use channels (e.g., email, phone, online forms, in-person), businesses can ensure customers can submit concerns with ease. Whatever the channel, everything should land in the same log.
Triage belongs here too. The same guide advises that you review each concern for validity, seriousness and urgency, then categorise it, prioritise by impact and assign it to the responsible person for a speedy resolution, as described by SafetyCulture.
Moving from a log to a root cause
A log only pays off when somebody reads it as a whole. A simple routine works for most teams:
- Group complaints by category and by the product, process or team involved.
- Look for clusters: the same fault, the same step in a journey, the same shift or supplier.
- For each cluster, ask why it happened, and keep asking until you reach something the business controls.
- Assign a corrective action to a named owner.
- Record the cause in the log, then watch whether that cluster shrinks.
The point of step three is to stop at causes, not at the individual case. As SafetyCulture puts it, by analyzing the root cause of a customer-raised issue, the business resolves it completely and prevents future occurrences.

Be wary of fixes that only treat the person who complained. Refunding one customer closes the ticket, but if the cluster keeps growing, the cause is still there.
What does the complaints standard say about records and review?
The international standard on complaints handling gives guidelines on how a complaints-handling process should be put in place, according to the BSI Knowledge page. As of that page, BS ISO 10002:2018 is listed as current, with a publication date of 31 Jul 2018.
The SafetyCulture guide says the ISO standard was introduced in 2004. Two of the components it lists bear directly on tracking:
- Documentation and reporting: systematically record issues, actions taken and outcomes so no information or evidence is lost.
- Performance monitoring and review: use metrics, audits and customer satisfaction surveys to measure how effective the process is.
Smaller organisations are not left out, because Annex B provides guidance specifically for small businesses. The same page says the revised standard is compatible with BS EN ISO 9001 and BS EN ISO 9004, and that it can also be used independently.
One limit is worth knowing. The BSI note states that the standard doesn’t apply to disputes referred for resolution outside the organization or to employment-related disputes, per the BSI listing.
Keeping the tracking system honest
Tracking drifts when nobody reviews it. Set a regular review slot, put the cluster analysis on the agenda, and check whether last period’s corrective actions actually reduced the complaints they targeted.
The log also shows where your process strains. If many cases end up with senior staff, that is a signal to revisit your customer complaint escalation process so that the right people see the right cases sooner.
Record the remedy you offered as well as the fault. Over time you will see which fixes restored goodwill, which is the practical heart of service recovery.
Finally, tell customers and staff what changed because of complaints. A visible fix shows people that raising a problem leads somewhere, and that encourages the open feedback a tracking system depends on.
Frequently asked questions
Do I need special software to track complaints?
Show answer
Not at the start. A shared spreadsheet with consistent fields and drop-down categories is enough to reveal patterns, and you can move to dedicated tools once the volume or the number of channels makes manual upkeep hard.
How should I choose complaint categories?
Show answer
Base them on things you can change: product, process step, team or supplier. Vague labels such as “service” hide the cause, so split them until each category points to an owner.
Does a complaints standard require a particular tracking tool?
Show answer
The BSI listing describes guidelines for a process, not a specific product, and says the guidance suits any organization regardless of type, size or sector.
What should I do with complaints that turn out to be invalid?
Show answer
Log them anyway, marked as such. Validity is one of the checks in triage, and a run of invalid complaints about the same thing can reveal unclear instructions or misleading marketing.



