In most small companies a complaint arrives wherever the customer happens to write: the sales manager's inbox, the shared mailbox, a phone call taken by whoever picked up. Each one is handled by someone, often well. But nobody can say how many complaints came in last quarter, which ones are still open, or whether the same problem keeps coming back.
A complaint log solves this without any special software. It is one page, one list and one routine.
Why a log, and not just good intentions
Handling a single complaint well is a matter of attention. Handling complaints as a pattern is a matter of records. Without a log you lose three things:
- Speed. A complaint sitting in one person's inbox during their holiday is a complaint nobody answers.
- Memory. The customer calls again, and the second person asks them to explain everything from the beginning.
- Learning. Five complaints about late delivery notes look like five bad days until they are counted in one place.
The log does not make anyone's work harder. It replaces the question "who was dealing with this?" with a line in a list.
Step one: name the owner
Pick one person who owns the log. This person does not have to resolve every complaint, but they make sure each one has a handler, a date and a status. In a small company this is often the operations manager or the office manager, with a named deputy for absences.
If your team already triages a common inbox, the same rules can carry complaints; our article on moving a shared mailbox to a ticket queue describes owners and triage rules that fit well here.
Step two: decide what counts as a complaint
Keep the definition short and write it at the top of the page. For example: "Any message in which a customer says that something we did, delivered or invoiced did not meet what was agreed or expected." Questions and feature requests are not complaints. If you are unsure, log it; a log with a few extra lines is better than one with gaps.
Step three: the fields
One row per complaint. The fixed set below is enough for most small companies:
- ID and date received.
- Channel: e-mail, phone, meeting, review site.
- Customer and contact person.
- What happened, in one or two plain sentences, in the customer's words where possible.
- Category: delivery, quality, invoice, communication, service, other. Keep the list to six or fewer.
- Handler: the person doing the work.
- First reply sent: date.
- Status: open, waiting for customer, resolved, closed.
- Resolution and date.
- Cause: one line, filled in at closing.
- Fix: what changes so it does not happen again, or "no change, because..."
Resist adding more columns. Each extra field is a reason to skip the row.
Step four: agree on response times
Two numbers matter, and they are different.
First reply. The customer should hear from a human quickly, even if the answer is only "we have it and will come back by Thursday". One working day is a reasonable target for a small team. Write it down and check it in the log: the date received and the date of first reply give you the figure.
Resolution. This depends on the type of problem. Set a target per category, for example three working days for invoice errors and ten for quality issues, and treat them as starting points to be adjusted after the first quarter. If a complaint will take longer, the handler tells the customer the new date.
Do not promise numbers you cannot keep. A realistic target met every time builds more trust than an ambitious one missed twice a month.
Step five: close every complaint properly
A complaint is closed when three things are written down: what we did for the customer, what caused the problem and what, if anything, will change. "Apologised and sent a replacement" is a resolution. It is not yet a cause and a fix.
Sometimes the honest answer is that nothing should change, for instance when the customer's request was outside the agreed terms. Write that down with the reason. A conscious "no change" is a decision; a blank cell is just forgotten.
Step six: the monthly pattern review
Once a month, the owner spends twenty to thirty minutes with the log and one or two colleagues. This fits naturally into an existing meeting; see our piece on a twenty-minute weekly operations meeting for a simple structure. Look at four things:
- Count. How many complaints came in, compared with the previous month?
- Categories. Which category has the most rows? Which has grown?
- Timing. How many first replies were within the target? How many complaints are still open and for how long?
- Repeats. Do the same cause, product, supplier or process step appear more than once?
Pick at most one or two repeating causes and assign each an owner and a date. Do not try to fix everything. The point of the review is to turn the log into a short list of changes that someone is responsible for.
Complaints are also a good source of content. Questions customers ask repeatedly can become public answers, as described in our article on turning customer questions into web answers.
Common mistakes
- Keeping the log in several places, such as one sheet per person.
- Counting only formal written complaints and ignoring phone calls.
- Recording the handler's explanation but not what the customer actually said.
- Measuring only the speed of the first reply and never the resolution.
- Using the log to find who is to blame, which teaches people to stop logging.
- Never reviewing it, so it becomes an archive instead of a tool.
Personal data
A complaint log contains names and contact details. Keep it where only the people who handle complaints can open it, record only what you need, and delete or anonymise old rows according to your own retention rules and local data protection requirements.
Summary
A useful complaint log is one list with a named owner, a short fixed set of fields, a target for the first reply and for the resolution, and a monthly review of repeating causes. It takes little time to start, and after a quarter it shows you which two or three changes would remove the most complaints.
Sources
- Our related articles linked above.
- The fields, response times and review routine are a working practice for small companies, not a legal or industry standard; adjust them to your size, sector and local rules. No client results or market figures are claimed in this article.
