Datacat

Insights

2026-11-03 · 6 min

Customer complaints that end in a fix, not a lost account

A complaint handled well can keep a customer. How operators give each one an owner, a reply deadline and a recorded cause, then close it with the customer.

The customer rang to say the crew left a mess and nobody had told them the job would run over. The person who answered was apologetic, promised someone would call back and wrote a note on a pad. The account manager heard about it two days later, from the customer, in an email that started with "Still waiting".

By then the problem was no longer the mess. It was that the customer had complained and felt ignored. A small service failure had turned into a question about whether to keep using you.

Complaints can be some of the most useful information an operator gets. The customer is telling you exactly what went wrong, often while they still want to stay. What decides the outcome is often not the original mistake. It is what happens in the hours after they speak up.

How a complaint gets lost between people

When complaints go badly, the trail often looks like this:

  • It arrived somewhere informal. A phone call, a text to a technician, a comment to a site supervisor or a reply buried in an invoice thread.
  • Nobody owned it. Several people knew about it, and each assumed someone else was handling it.
  • The customer heard nothing. Work may have been happening in the background, but from the outside it looked like silence.
  • It was closed by being forgotten. There was no point where someone confirmed the customer was satisfied.

Each step is small. Together they turn a fixable problem into a reason to leave.

Log it once, wherever it comes in

Every complaint should become a record in your customer relationship management (CRM) system, attached to the customer and, where there is one, the job or order it relates to. It should not matter whether it came through the phone, the website, an email to accounts or a word with a technician on site. Whoever hears it logs it in a minute, with the customer's own words and any photos they sent.

Keep the form short so people actually use it:

  • What happened, in the customer's words.
  • Which job, order or invoice it relates to.
  • How upset they are, on a simple scale the team agrees on.
  • What the customer is asking for, if they said.

Linking the complaint to the customer record means the next person who speaks to them knows about it before the customer has to repeat it. It also stops the awkward moment where sales calls to talk about a renewal while a complaint sits open.

Name an owner and promise a time

A complaint without an owner is just a note. Assign one person to every complaint as it is logged, based on simple rules: service complaints to the operations lead for that area, billing complaints to accounts, anything serious to a manager. The owner does not have to fix everything personally, but they are responsible for the customer hearing back.

Then set a reply deadline the customer is told about, and keep it. Even when the fix will take longer, a prompt call that says what you know, what you are doing and when they will hear next changes how the customer feels about the whole problem. If the deadline is about to pass, the system should warn the owner and their manager, not wait for the customer to ring again.

Fix the problem, then fix the cause

Once the customer's issue is resolved, record two more things before closing it: what was done for this customer, and why it happened. Keep the cause to a short list everyone uses the same way, such as a missed booking, poor communication about delays, workmanship, billing error or a supplier problem.

Close the complaint only after the owner has confirmed with the customer that they are satisfied, or recorded why they are not. That last call is often where trust comes back. Many customers don't expect perfection; they notice whether someone came back to check.

Artificial intelligence (AI) can take some of the load. It can read incoming emails and messages and suggest when one is really a complaint, draft a summary of the history for the owner, and group similar complaints so patterns show up sooner. A person still decides what to offer the customer and how to say it.

Read the causes, not just the count

A report of complaints opened and closed tells you how busy the team was. The causes tell you what to change. If poor communication about delays keeps coming up, the fix may be an automatic message to customers when a job runs over, or a customer portal where they can see status without calling, as covered in customers who see status without calling. If billing errors lead the list, the problem sits upstream in how jobs become invoices.

Look at causes by team, service and customer type. The point is not to find someone to blame. It is to spot the one or two fixes that would prevent the most complaints from happening at all.

Pull your open complaints and call three customers

List every complaint that is still open, wherever it is recorded today, including the notebook and the inbox. For each one, check whether it has an owner, whether the customer has heard back, and whether anyone has written down why it happened.

Then pick three customers who complained recently and call them. Ask how they felt about the way it was handled, not just whether the problem was fixed. Their answers often point straight at the step that needs work.

Complaints that leave customers more loyal

Datacat builds complaint handling into the systems operators already use. That can mean adding a complaint record, owner rules, reply deadlines and cause codes to the CRM you have, or a custom CRM and ops platform where the customer, the job, the invoice and any complaint share one history. Logging from email and phone notes, deadline warnings and cause reporting can run through ops workflow automation. If complaints keep landing on the wrong customer record, start with one customer, one record.

Browse work we have delivered, book paid strategy and discovery to map where complaints go missing in your business, or send us the complaint that nearly lost you a customer and we will help you trace where the handling broke down.