A missed PM visit. A callback job that did not fix the problem. A technician who arrived late and left without completing the work. These things happen in field service — not often, but enough that every business will face a complaint at some point.

How you handle it matters more than the fact that it happened. A customer whose complaint is resolved quickly and fairly is often more loyal than one who never had a problem at all. In Thai field service, where referrals travel through LINE groups and word-of-mouth in building committees, an unresolved complaint has reach beyond the customer themselves.

Why Field Service Complaints Are More Predictable Than You Think

Complaints in installation and maintenance businesses cluster around a predictable set of failures:

Missed or shortened PM visits. The most common source of formal complaints on MA contracts. A customer whose quarterly visit was skipped or completed in fifteen minutes feels they paid for something they did not receive.
The same fault returns. A repair that does not hold leads to a callback within days. Even if the return visit is free, the experience damages confidence.
Billing surprise. The customer expected 3,000 baht and received an invoice for 7,500. If additional work was done without prior sign-off, the complaint is legitimate.
Technician conduct. Lateness without notification, leaving debris on site, or dismissing the customer’s questions. These complaints are often not about the technical work — they are about the experience of having someone on site.
Warranty dispute. The customer believes recent work should cover the current fault. Your team disagrees. Without a clear written record, this becomes a credibility contest.

Knowing which category a complaint falls into tells you how to approach it. Billing and warranty complaints respond to documentation. Conduct complaints require an acknowledgment and a process change. Missed-visit complaints usually need both.

What Should You Do in the First Five Minutes?

The opening of a complaint conversation almost always determines the outcome. The worst response is defensiveness — telling the customer why your team was correct, before you know what actually happened. Even if your team was entirely right, arguing first costs you the customer’s goodwill before you have had a chance to investigate.

A structured first five minutes looks like this:

Step 1: Acknowledge without admitting. “Thank you for letting us know. We take this seriously and will look into it today.” This is not an admission of fault. It is a professional signal that you are engaged and not dismissing the issue.

Step 2: Ask one clear question. What does the customer want? Sometimes they want a technician back on site. Sometimes they want an explanation of what was found. Sometimes they want a partial refund. Asking directly prevents you from offering more than necessary — or less than they need.

Step 3: Set a specific follow-up time. “I’ll call you back before 5 PM today with an update.” A specific time is more reassuring than “soon” — and it holds your team accountable to a deadline that the customer can hold you to.

In Thai field service businesses that communicate primarily through LINE, the first response often happens in writing. A LINE message that acknowledges the issue calmly and gives a specific follow-up time does significant work before any investigation takes place. Customers who receive a professional LINE response within the first hour are far less likely to escalate.

Using Service History to Resolve a Dispute

The majority of field service complaints can be resolved — or refuted — using the job record. What was scheduled? What was completed? Who signed off? What was photographed?

A concrete example: a customer contacts you claiming their quarterly aircon service was not completed last month. Without documentation, this is one person’s recollection against another’s. With a digital service record, you can show the technician check-in timestamp, the before-and-after photos taken during the visit, and the customer’s digital sign-off. The claim either holds up or it does not — and both parties can see why without anyone having to take anything on faith.

Where disputes involve additional work billed on the day, the conversation changes significantly if there is a photo of the technician showing the fault to the customer before starting the additional repair, or a timestamped LINE message requesting approval before work began.

A customers and assets record that tracks the full service history per site — every visit, every photo, every completed report — becomes the reference document for any complaint. Businesses that rely on handwritten forms and fragmented LINE chat history are negotiating from memory. Businesses with structured service records are negotiating from evidence.

How Do You Stop the Same Complaint from Recurring?

The most expensive complaint is one that returns every quarter from different customers for the same root cause. When that happens, the problem is not the customers — it is a gap in your operational process.

If your team receives repeated complaints about technicians arriving late without notification, the problem is not any individual technician. It is the absence of an automated notification step in your dispatch workflow. If customers regularly complain about unexpected charges, the issue is not unreasonable customer expectations. It is a missing approval step for additional work before it starts.

After each resolved complaint, identify one concrete process change:

Complaint: missed or shortened PM visit. Does your scheduling system flag overdue visits automatically before the customer has to call you?
Complaint: billing surprise. Is the additional-work sign-off step built into the job workflow before work begins — not added to the invoice afterward?
Complaint: callback within 30 days. Is the same technician assigned to the return visit, and is there a documented root-cause review before they go back?

A complaint log does not need to be complex. A shared record with the date, complaint category, root cause, and resolution is enough for a team of ten or fewer technicians. Review it monthly and you will quickly see whether you are resolving complaints or only quieting them temporarily.

Handling B2B Complaints from Property Managers and Juristic Persons

Corporate and property management clients add a layer to complaint handling that individual customers do not. The person calling is rarely the person who signed the contract — and is almost never the person whose operations are affected.

When a juristic person (นิติบุคคล) for a condominium or office building contacts you, the complaint often arrives from a staff member relaying a concern from residents or department heads. Before responding fully, establish who the decision-maker is and whether the complaint has been logged internally.

B2B resolution almost always requires written follow-up alongside the verbal conversation: a short summary of what happened, what was found, and what has changed. Three paragraphs is sufficient. Sending it by LINE or email protects you if the complaint later reaches a committee member who was not part of the original conversation.

FAQ

How quickly should a complaint receive a first response?

The first acknowledgment should arrive within two to four hours of the complaint reaching you. A customer who messages at 9 AM and hears nothing by 3 PM has already started evaluating other options. The initial response does not need to include a resolution — it needs to confirm that someone received the message and is actively looking into it.

Can you decline a warranty callback if the customer caused the damage?

Yes, but how you decline matters. If the service history clearly shows the fault falls outside the original work — a customer-installed fitting that blocked the drainage line, for example — walk the customer through the evidence: the check-out photos from the original job, the service report, the noted condition at handover. A factual explanation is far less damaging to the relationship than a flat refusal. Follow with an offer of a paid return visit at a fair callout rate and document the decision in writing.

What if the complaint surfaces publicly in a LINE group or Facebook review?

Respond in the same channel, briefly and professionally. Acknowledge that the customer had a poor experience and that it was addressed directly. Invite further contact offline. Do not argue point-by-point in the thread. Other readers of the group are watching how you handle the situation — a calm, measured response signals more to prospective customers than any counter-argument.

Every field service business manages complaints. The ones that grow are the ones that have a consistent process: acknowledge fast, investigate with evidence, resolve specifically, and close the loop with a documented process change. A complaint handled well is a retention tool. A complaint handled poorly is an advertisement for your competitors.

If you want service records that give you the job history to resolve disputes clearly and fairly, take a look at what OnSiteQ is building for Thai field service businesses.

How to Handle Customer Complaints in Field Service