A customer calls three times about the same fault. The first time, a technician came, replaced something and left. The second time, another technician came and said the first one had fixed the wrong part. The third time, the customer is angry, tells the neighbours and starts looking for another service provider. Your system shows two "completed" jobs.
Complaints in service businesses rarely come from one big failure. They come from small ones that repeat: late arrival, a missed appointment, a repeat visit, a rude remark, a bill nobody explained, a job marked done that was not. This guide shows the most common causes and how SLAs, job cards, proof of service and feedback work together to reduce them.
Where service complaints come from
| Complaint | Root cause |
|---|---|
| "Nobody came" or "they came late" | No clear deadline, poor dispatch, no alert when a job is at risk |
| "Same problem again" | Wrong diagnosis, missing parts, no history of the earlier visit |
| "They said it was done but it is not" | Job closed without proof, no checklist, no customer sign-off |
| "I was not informed" | No status updates, no proper handover |
| "The bill is wrong" | Parts and time not recorded at the job |
| "The technician was rude" | No feedback loop, no coaching |
Notice that most causes are about process and information, not about bad people.
The four tools that reduce complaints
1. SLAs: make promises measurable
An SLA turns "as soon as possible" into a number: four hours for a breakdown, next day for a routine fix. A timer on each job and alerts before a deadline passes let you act early. See SLA management software.
- Set different targets by priority.
- Alert the assignee when a job is at risk.
- Escalate to a supervisor on breach.
- Report breaches by cause: staffing, parts, travel, customer unavailable.
2. Job cards: make every job the same
A job card is the job in one place: customer, address, fault, history, checklist, parts, notes. It helps the technician arrive prepared and work to a standard.
- Show earlier visits so repeat issues are clear.
- Include a checklist for each job type.
- Record parts used and time taken, so billing is right.
- Make key steps mandatory before the job can close.
Our guide to mobile forms explains how to design them.
3. Proof of service: settle disputes quickly
Photos before and after, customer signature or OTP, and a time-stamped, geo-tagged check-in turn "he says, she says" into a record. See proof of visit software.
- Do not allow job closure without proof for key job types.
- Share a summary with the customer when the job closes.
- Use the record to resolve disputes fairly, in both directions.
4. Feedback: find problems before they become complaints
A short rating after the visit catches unhappy customers while you can still fix things. A low score should create a task for a team lead to call within a day. See customer feedback software for field teams.
A step-by-step plan to cut complaints
- Collect your complaints for the last three months and group them by cause. Use the table above.
- Find the top two causes. Often they account for most complaints.
- Pick one fix for each. For lateness, SLAs and alerts. For repeat visits, job history and checklists. For disputes, proof.
- Pilot with one team for a month.
- Measure before and after: complaints per 100 jobs, SLA compliance, repeat-visit rate, customer rating.
- Close the loop with customers. Call back those who complained and tell them what changed.
- Make it routine. Review complaint causes monthly.
What to measure
- Complaints per 100 jobs
- SLA compliance rate
- First-time fix rate. In its 2026 benchmark, Aquant, a field service software vendor, reported an industry average of 77 percent, with top performers at 88 percent and bottom performers at 60 percent. It is vendor-published, so use it as a reference, not a target.
- Repeat-visit rate within 30 days
- Customer rating or NPS by technician and job type
- Time to resolve complaints
See 12 KPIs every sales and operations manager should track for definitions.
Common mistakes
- Setting SLAs you cannot meet. Promise less and deliver more.
- Closing complaints without finding the cause.
- Blaming technicians for system problems like missing parts or poor dispatch.
- Making proof so heavy that technicians skip it.
- Collecting feedback but not acting on it.
- Not telling customers about delays. A timely message often prevents a complaint.
Where this applies
These methods suit appliance and equipment service, HVAC, facility management, telecom and utilities, solar and EV service, and any business that visits customers to fix or install something. See field service and repair, telecom and utilities and solar and EV.
Where FieldExecutives fits
FieldExecutives is field force management software that brings these tools together. Managers create tasks and visits with checklist, priority and SLA, and get at-risk and breach alerts with escalation by priority. Technicians follow a guided 360-degree job card and capture photo, signature, OTP and checklist before a job can close. Customer ratings and NPS give a quality score for each technician. See the features and plans.
Want to cut repeat complaints? Book a demo and bring your top three complaint types. We will show how each would be handled.
