A complaint is a test of a service business. The customer has paid, something is still wrong, and they want to know someone cares. Handled well, a complaint turns into loyalty and a renewal. Handled badly, it becomes a lost contract and a poor review. Most of the difference comes from a simple routine.

Who wrote this guide

This guide is written by the EZ Solutions team. We build ServicePilot, field service software for businesses such as pest control, RO, AC, CCTV and lift service. The routine below works with any system.

What does complaint management involve?

Complaint management covers four steps: logging the complaint against the right customer and job, getting a technician there quickly, deciding whether the visit is free, and confirming with the customer that the problem is gone. Each step fails in a familiar way when it lives only in phone calls.

The four steps and where they break
StepCommon failure
Log itThe call is taken by someone who forgets to write it down
Send someoneNo technician is free, and nobody tells the customer
Decide the chargeA repeat problem is billed, and the customer feels cheated
Close the loopNobody asks whether the fix held

1. Log every complaint in one place

Complaints arrive by phone, WhatsApp, a message to a technician, or a word to the owner at a function. Every one of them needs to reach the same list. The record should show:

  • The customer, found by mobile number, and the site.
  • The unit or service the complaint is about.
  • The original job it relates to, if any.
  • When it came in, and who took it.

Morning is the busiest time for this. Many owners check WhatsApp before anything else, since complaints often arrive overnight.

2. Respond quickly, even before the visit

Customers mind silence more than waiting. A quick reply with a visit time, even if the visit is tomorrow, calms most complaints. Then the dispatch board shows the nearest technician with room in the day; the technician dispatch guide explains how to keep that room free.

3. Apply clear free re-visit rules

Many service businesses offer a free re-visit when the same problem returns soon after a service. Pest control is the classic case: cockroaches seen again a week after treatment. Set the rule once and apply it every time:

  1. Same problem, within the window: free re-visit, linked to the original job.
  2. Same problem, after the window: a new job, charged as usual.
  3. A different problem: a new job.
  4. Covered by a contract: handled under the contract’s terms.

Writing the window into each service type removes arguments between staff and customers. The AMC management guide covers complaints under a maintenance contract.

4. Close the loop with feedback

When the technician marks the complaint done, the job is not quite finished. A short call or WhatsApp message a day or two later asks whether the problem is gone. A yes is a good moment to mention the renewal; a no goes straight back on the list, without the customer having to complain twice.

5. Learn from the pattern

Each complaint linked to its original job builds a record over months. Reading it once a month shows what to fix:

  • Technicians whose jobs come back more often than others, who may need training.
  • Services or products that fail repeatedly, which may need a different method or supplier.
  • Areas with slow response times, which may need another technician.

That is where complaint management stops being a cost and starts improving the business.

How ServicePilot handles complaint management

ServicePilot treats complaints as part of the job history:

  • Complaints and free re-visits tied to the original job, with customer feedback recorded.
  • Customers found by mobile number, with every site and installed unit on the record.
  • The Dispatch Board to fit complaints into a technician’s day.
  • Maintenance contracts whose terms apply to complaints during the contract period.
  • Reports and a day summary for the owner, shareable on WhatsApp.

The result is a complaint list that is always complete, and a clear view of what causes repeat calls.

Explore ServicePilot