A customer calls because the repair has failed again. The engineer remembers a different conversation from the one the customer describes. The invoice has already gone out. Before anyone can put the problem right, the office has to establish what happened.

That is where complaint handling becomes an operational issue. You need a calm response, a fair investigation and a remedy that addresses the failure. You also need records that let someone who was not on site understand the job.

This guide explains how to handle customer complaints in field service, using illustrative situations across repairs, installations and commercial maintenance. It covers practical responses, UK and Irish consumer obligations, escalation and prevention. The scenarios are examples, not customer case studies. The legal guidance is general information, not legal advice.

Key takeaways: Handling field service complaints

• Listen to the customer's account, assess immediate risk and assign a named owner before committing to an investigation or remedy.

• Check the agreed scope, job records, photographs and approvals before deciding what failed and who should pay for corrective work.

• Distinguish consumer remedies from commercial contract obligations, and separate mandatory corrective action from any discretionary gesture of goodwill.

• Set realistic update commitments, follow through on the remedy and check whether the customer considers the original issue resolved.

• Fieldmotion connects forms, photographs and job information, giving your team a documented starting point when investigating a customer's complaint.

Why complaint handling matters for customer retention

Complaint handling gives your business an opportunity to address a failure before the customer decides the relationship is no longer worth maintaining. It does not guarantee that the customer will stay.

A 2007 meta-analysis by de Matos, Henrique and Rossi examined the service recovery paradox: the idea that recovery can leave customers more satisfied than if nothing had gone wrong. The researchers found a positive overall effect on satisfaction, but no significant effect on repurchase intentions, word-of-mouth or corporate image.

This is general service research, not a field service retention benchmark. It supports a cautious conclusion: recovery may repair satisfaction, but you should not treat an avoidable failure as a route to greater loyalty.

Keep recovery separate from prevention

A successful remedy addresses the customer's immediate problem. Prevention changes the process that allowed it to happen. Both need an owner.

If a repair fails because the original diagnosis was incomplete, sending another engineer may settle that complaint. Improving diagnostic information and technical review addresses the risk of another callback. Keep those actions separate in your record of reducing callbacks.

The same distinction applies to customer retention. Record whether the issue was resolved, but do not assume a closed complaint means the customer has renewed a contract or booked again.

How to handle a field service complaint step by step

Handle a complaint by establishing the customer's account, checking risk, assigning responsibility, investigating the evidence and agreeing a remedy. Keep the customer informed while that work happens.

Listen before explaining the job

Let the customer describe what happened without interrupting to correct each point. Find out what they expected, what they experienced and what outcome they want.

A useful opening is: “I want to understand the problem properly. Can you take me through what happened and what is still not working?” Then summarise the concern back to them. A complaint about an engineer arriving late may also involve a missed shutdown window or a vulnerable occupant left without heating.

Acknowledge the impact in specific terms: “You arranged access for the morning and then had to wait without an update. I understand why you are unhappy.” Avoid a conditional apology that makes the customer's reaction the problem.

Check safety and urgency immediately

Assess the actual consequences before placing a complaint in a routine queue. A missed maintenance appointment can carry a safety or compliance risk; a polite customer can be reporting an urgent hazard.

Check for risk to people, property, essential services and contractual or regulatory deadlines. An allegation of unsafe electrical or gas work needs immediate competent triage, not a standard promise to call back tomorrow.

Use the applicable emergency procedure and qualified personnel. Where emergency services or a specialist emergency network are needed, direct the customer to the appropriate service. Do not ask them to test, dismantle or troubleshoot hazardous equipment. Record the safety action separately from the investigation into responsibility.

Assign an owner and the next update

Give each complaint one named owner and a backup. The customer should not have to repeat the account to a dispatcher, engineer and accounts team while each assumes someone else is handling it.

Confirm what happens next and when the customer will hear from you. For a routine, non-urgent issue, an illustrative commitment might be: “I will check the job record and speak to the engineer, then call you by 3pm tomorrow.”

That is an example, not a legal deadline or industry benchmark. Choose a commitment that fits the urgency and that your team can deliver. If the investigation remains incomplete, provide the update anyway and explain the outstanding evidence.

Investigate the agreement and the work delivered

Start with the original scope, quotation or contract. Compare it with the work instruction, engineer's notes, asset details, photographs, test results, approvals and invoice.

Speak to the engineer and any relevant witnesses privately. Identify where the records support an account, where they contradict it and where information is missing. Missing evidence is uncertainty, not proof that either person is wrong.

Fieldmotion supports on-site forms and photograph capture through its mobile app. These records can help the office investigate, but their usefulness depends on what was recorded. An unsigned form, unclear photograph or incomplete test result should not be presented as conclusive evidence.

Explain findings and agree the remedy

State what you established, what remains uncertain and what you propose to do. Separate correction of the original work from any additional chargeable work.

For example: “The inspection shows the connection we installed is leaking. We will arrange corrective work at no charge and confirm the available appointment with you today.” Only make that commitment once responsibility and the appropriate remedy have been established.

If the evidence does not support the complaint, explain your reasoning and give the customer a route to challenge it. A signature at completion does not rule out a defect that was hidden or appeared later.

Check the outcome before closing the complaint

Close the complaint when the remedy has been delivered and the outcome has been checked, not when the return visit has been booked.

Ask a concrete question: “Has the leak stopped since the remedial visit?” or “Have you received the outstanding reports, and are there any gaps remaining?” Record the answer and any further action.

If the customer remains dissatisfied, keep that visible. An internal status of resolved should not conceal an ongoing dispute. Explain the next review or escalation route rather than allowing the complaint to disappear from the working list.

Field service complaint scenarios and practical responses

Use these illustrative scenarios to distinguish the investigation, customer response, remedy and prevention action. The suggested wording should be adapted to the actual evidence, urgency and commitments you can meet.

A missed appointment disrupts the customer's day

Situation: A domestic customer reserved the morning for a maintenance visit. The engineer arrives after lunch without warning. The customer has missed another commitment and wants an explanation.

Check: Confirm the promised window, booking message, engineer's progress and any attempted notification. For commercial sites, also check whether access, permits or an isolation window have expired. Do not assume a late arrival can proceed as originally planned.

Say: “We agreed a morning visit, and you were left waiting without an update. I am sorry. I will check which options we can offer, including a new appointment that you can plan around.”

Resolve the missed visit without another uncertain promise

Offer realistic alternatives based on current capacity. Confirm any required access arrangements before booking. Do not promise an exact arrival time merely to end an uncomfortable conversation.

If the customer claims a financial loss, record the details and review the contractual or legal position before classifying compensation as goodwill. A discretionary gesture can address inconvenience, but it does not replace any remedy the customer is entitled to.

Prevent: Define who contacts customers when a visit is at risk, what triggers the update and which channel is used. Check whether messages reach the correct person. Notification attempts and successful delivery are different facts.

The same fault returns after a repair

Situation: A boiler displays the same fault symptoms a month after a paid repair. The customer understandably believes the original problem was never fixed.

Check: Review the diagnosis, parts replaced, test results and operating conditions. Similar symptoms can have different causes. Distinguish inadequate original work, a component failure and a separate fault before deciding who should pay.

Say: “I can see what was replaced and tested at the last visit. We need to establish why the symptoms have returned. I will arrange the appropriate assessment and explain any proposed charges before work proceeds.”

Make the return visit a proper investigation

Give the attending engineer the original record and a clear question to resolve. A repeat visit should not start from the same incomplete information as the first one.

If your original work was deficient, apply the appropriate no-charge remedy. If a genuinely separate fault requires additional work, explain the evidence and obtain agreement to the new scope and price. Discuss inspection charges in advance rather than surprising the customer afterwards.

Prevent: Record the fault, relevant readings, work completed and post-repair tests. Specify any limitations or unresolved concerns at handover. A vague note saying “working on departure” gives the next engineer little diagnostic context.

The invoice exceeds the approved quotation

Situation: The customer receives an invoice substantially above a fixed quotation. An engineer found additional corrosion during the job, but the office cannot find a clear variation approval.

Check: Compare the accepted quotation, variation, authority to approve expenditure and invoice. Establish what was said about additional cost before work continued. On commercial sites, the person granting access may not have purchasing authority.

Say: “The invoice includes additional work beyond the accepted quotation. I am checking what was agreed, who authorised it and whether the invoice reflects that agreement. I will send you the relevant records and our proposed correction or explanation.”

Resolve disputed extras on their contractual basis

Do not assume that necessary work was automatically authorised, or that a signature settles every question about scope and price. Review the actual agreement and applicable obligations. Emergency circumstances may need separate consideration.

Correct unjustified charges. Where the position is disputed or unclear, take appropriate advice rather than relabelling an invoice correction as goodwill. Coordinate with accounts so routine reminders do not contradict the agreed handling of the dispute.

Prevent: Use clear variation records stating the work, price and schedule effect, approved by the appropriate person before proceeding. The discipline starts with accurate quoting and carries through to the engineer's instructions.

A customer alleges property damage or unsafe workmanship

Situation: One customer reports cracked tiles after an installation. Another reports a burning smell from recently installed equipment. These need different response routes.

Check: Triage the potential hazard immediately. For a non-urgent damage claim, gather before-and-after photographs, work records and the customer's account. A missing pre-work photograph does not prove your team caused damage. A completion signature does not rule out a hidden defect.

Say for damage: “I will arrange an assessment and review the original photographs with the engineer. We will confirm what we find and the next steps with you.” For suspected unsafe work, activate the appropriate emergency procedure first.

Preserve evidence while making the situation safe

Safety action must not wait for an argument about liability. Use qualified personnel and the appropriate emergency services or networks where needed. Preserve relevant evidence where doing so is safe.

Notify your insurer or broker in line with policy requirements if the allegation may involve a claim. Do not agree a settlement or dispose of important evidence without checking the implications. Fieldmotion's business insurance guide explains the wider coverage considerations.

Prevent: Capture relevant site condition before work, document checks and retain test results. Photographs support an investigation; they do not replace competent testing or required certification.

A commercial client disputes missing service documentation

Situation: A facilities manager is preparing for an audit and cannot locate several inspection reports. They say your maintenance contract has not been fulfilled.

Check: Reconcile the contract schedule against visits, asset records, completed forms and report delivery. Separate completed-but-undelivered documentation from missing evidence and missed work.

Say: “I will reconcile the records against your schedule and update you by the agreed time. We will identify which reports exist, which need delivery and any work or evidence gaps that require action.” Do not promise that every gap can be resolved before the audit.

Address documentation gaps honestly

Send authentic records that exist. Where a report is prepared later from contemporaneous evidence, identify its basis and preparation date accurately. Never fabricate findings, backdate certificates or imply a catch-up visit proves historical compliance.

If work was missed, acknowledge it and agree an appropriate plan. Review contractual consequences and any safety or regulatory implications. A newly completed inspection and a missing historical inspection are separate facts.

Prevent: Assign responsibility for report completion, review and delivery. Fieldmotion's customer portal provides access to job information and reports; your business still needs to check that the required records are complete and available to the right client contact.

A customer complains about an engineer's conduct

Situation: A receptionist reports that an engineer was rude and left waste on site. The engineer says the conversation involved unreasonable demands and an access dispute.

Check: Obtain specific accounts, relevant witnesses and site records. Speak to the engineer privately, without assuming the complaint proves misconduct. Separate workmanship, housekeeping, communication and any threatening behaviour.

Say: “Thank you for raising this. I will review the visit and speak to the people involved. I will update you by the agreed time about how we are addressing your concerns.”

Protect staff and investigate fairly

Follow the applicable employment process before taking disciplinary action. Tell the customer how their service concern is being handled without sharing confidential personnel details.

If staff experienced threats or abuse, support them and follow the incident procedure. Protecting employees and investigating a complaint fairly can happen together. Consider whether future attendance needs changed access arrangements or additional support.

Prevent: Set clear standards for conduct, site housekeeping and escalation when an engineer encounters conflict. Review the lone working arrangements that allow field staff to get help.

When should you offer rework, refunds or goodwill?

Choose the remedy according to the failure, the customer's applicable rights and the contract. Determine what you owe before deciding whether to offer anything additional.

UK consumer rights for service complaints

The Consumer Rights Act 2015 services provisions require reasonable care and skill. Information about the service can also become binding where the consumer took it into account when entering the contract or making a later decision.

For qualifying failures, repeat performance means completing the necessary corrective work at the trader's cost, within a reasonable time and without significant inconvenience. If repeat performance is impossible, or the trader fails to meet those requirements, the consumer can have a right to a price reduction.

The reduction can be the full price where appropriate. Timing and other breaches can have different remedy routes, and other remedies may remain available. Avoid presenting a return visit as the customer's only possible option.

Irish consumer rights for service complaints

Ireland's Consumer Rights Act 2022 addresses both the agreed service and what a consumer can reasonably expect, including reasonable care and skill. The CCPC's business guidance on services explains the obligations and remedies.

Where the business fails to meet its obligations, it must resolve the issue at no cost to the consumer, within a reasonable time and without significant inconvenience. Depending on the circumstances, seriousness, failed attempts or inability to resolve the issue, a price reduction or termination and refund may apply.

Do not describe a required remedy as a favour. Check the specific circumstances rather than transferring a UK rule or an internal complaints policy into an Irish contract.

Commercial contracts and service-level agreements

B2B complaints require review of the contract and the applicable jurisdiction's legal obligations. Consumer service remedies should not be applied automatically to commercial agreements.

Check scope, response and resolution commitments, documentation requirements, variation authority, remedies, dispute procedures and notice requirements. Confirm the governing law and seek advice where the legal position is uncertain.

A service credit may address an SLA failure without correcting the underlying fault. Record both actions where both are required. Do not assume a liability cap or exclusion removes every obligation; its application and enforceability need appropriate review.

Keep goodwill additional to the required remedy

Goodwill is a discretionary gesture beyond the remedy you are required to provide. It might acknowledge inconvenience through a follow-up check or another proportionate offer.

Use consistent approval rules and document the reason. A future discount may be unwelcome to a customer who needs today's problem fixed; ask what practical outcome matters before offering it.

Do not make a refund or corrective work conditional on removing a negative review. Required remedies and reputation management should remain separate.

Apologise without speculating about liability

You can acknowledge distress and inconvenience while the facts are being established. Keep the wording accurate: “I am sorry you have been left without an update” addresses the experience without inventing a technical cause.

The legal and insurance implications of statements depend on the circumstances. Where a complaint involves significant loss, injury or a potential insured claim, obtain appropriate advice before making commitments or admitting disputed facts.

How to respond to a negative public review

Respond briefly and professionally in public, then investigate the detail privately. Your reply should show a useful next step rather than become a public argument.

Use a specific but restrained response

For example: “We are sorry to hear you are unhappy with the visit. We would like to review the concerns you have raised. Please contact our office through our usual contact details so we can identify the job and agree the next step.”

Do not claim the issue is fixed unless it is. Avoid revealing addresses, account history, access codes or private correspondence to defend your position. Use your ordinary contact route rather than requesting identifying information in the public thread.

The wider process for customer reviews should remain separate from the complaint remedy. Seek honest feedback without pressure, incentives tied to positive reviews or selective requests designed to suppress negative experiences.

Keep the investigation private

Move evidence gathering to an appropriate private channel. A customer making a public complaint does not give your business unrestricted permission to publish everything in their job record.

Limit internal access to those who need the information, and retain the complaint and evidence under your applicable retention and data protection arrangements. Ask for specialist advice where the handling involves sensitive information or uncertain disclosure obligations.

Build a complaints process your team can follow

A usable complaints process defines who owns the issue, how risk is assessed, when customers are updated and what causes escalation. It should work when the usual manager is absent.

Set responsibility and authority

Tell office and field staff where to record a complaint and who receives it. Include complaints made verbally, through messages and in public reviews when they identify a service issue.

Define who can arrange an inspection, approve corrective work, issue credits and contact insurers. Set escalation triggers around safety, significant loss, repeated failed remedies, legal correspondence and missed contractual commitments.

Keep the customer update commitment visible alongside the next internal action. An engineer waiting for a part does not remove the owner's responsibility to explain the delay.

Use a connected complaint record

Use the following fields as a practical template, linked to the original job and relevant correspondence:

• Identification: Complaint reference, received date and time, contact details, channel, job, site and affected asset.

• Customer account: Description of the issue, impact, expected outcome and the customer's requested remedy.

• Triage: Safety concerns, urgency, contractual deadlines and immediate protective action.

• Ownership: Named owner, backup, next action, action deadline and next customer update.

• Evidence: Agreed scope, approvals, job notes, photographs, tests, relevant messages and any missing information.

• Decision: Findings, remedy, approval, responsibility for delivery and escalation requirements.

• Outcome: Work completed, customer response, closure date, outstanding dispute and follow-up.

• Prevention: Root cause, change owner, implementation date and effectiveness check.

Separate customer closure from process improvement

A customer may accept the remedy while the internal prevention action remains unfinished. Keep both states visible.

For example, an invoice correction can be complete while a new variation approval process is still being configured. Assign the process change to someone with authority to implement it, then check actual jobs for compliance.

A spreadsheet can work at a modest scale if it links reliably to evidence and actions. The weakness is an isolated record that requires staff to reconstruct the job from separate conversations.

Prevent repeat complaints through better operational records

Use the complaint's root cause to identify the upstream process change. Check quoting, scheduling, handovers and documentation before concluding that the problem is simply an individual mistake.

Make scope and variations explicit

Specify inclusions, exclusions, pricing basis and the approval route for additional work. Carry the accepted version into the work instruction so the engineer and office are using the same agreement.

If customers repeatedly misunderstand an exclusion, review the wording and when it is explained. A technically present clause may still be difficult to interpret in the context of the job.

Make delay communication someone's responsibility

Define what triggers an update, who sends it and who checks the revised arrangements. Include cover for absence and out-of-hours work.

Use automation where the source information is reliable, and personal contact where the customer needs an explanation or a decision. Fieldmotion's guide to field service automation explores that distinction. Do not automate a promise that dispatch cannot support.

Give engineers the full agreed context

Include access constraints, customer concerns, authorised scope and prior unresolved issues in the job instruction. Ask the engineer to flag contradictions before starting work.

Fieldmotion makes recorded job information available to field teams through its mobile app. Offline capture is useful on site, but the office cannot review newly captured information until it has synchronised. Account for that in urgent handovers.

Check the quality of completed documentation

Review whether records contain useful evidence, not merely whether every required box is filled. “Test completed” is less informative than the applicable result, method and identified limitations.

Use complaint investigations to identify weak forms or handovers. The customer warning signs that undermine confidence can also help you identify where expectations are unclear before work begins.

Measure complaint resolution and recurring failures

Measure responsiveness, completed resolution and recurrence separately. Use definitions that remain consistent across periods, and show unresolved cases rather than reporting only the complaints you closed.

Complaint rate and counting rules

For an operational complaint rate, divide distinct complaints received during the period by completed jobs during that period, then multiply by 100. Label it complaints per 100 completed jobs.

Count follow-up messages about the same issue once. Include verbal complaints and all relevant channels. Specify how you handle multiple issues on one job and complaints relating to earlier periods.

This period measure is not the exact percentage of that period's jobs generating complaints. For that question, follow a defined group of completed jobs over a fixed observation window. Compare like-for-like work and show raw counts when volumes are small.

Response time and resolution time

Measure time to first substantive response from receipt to a reply addressing the specific issue. An automated acknowledgement confirms receipt but should not qualify as an investigation response.

Measure resolution time from receipt to delivered remedy and checked outcome, using consistent working-time or calendar-time rules. Report the median for closed cases alongside open-case ages so unresolved long waits remain visible.

A fast initial reply and a delayed remedy are different outcomes. Check both against the relevant customer commitment and contract rather than imposing one target on every complaint.

Reopened and aged open complaints

For a reopened rate, divide complaints reopened within a defined follow-up window by resolved complaints that have had the full window to be observed. Multiply by 100. An illustrative window is 30 days; choose one suited to the work.

Also show the count and proportion of open complaints beyond their target resolution date. Review the reason: missing parts, unavailable access, incomplete investigation or an internal handoff failure require different actions.

Do not compare immature closure groups with fully observed ones, or interpret a small percentage change from a handful of complaints as a proven trend.

Check whether prevention changes the pattern

Group complaints by failure type and investigated cause. Review recurring scope disputes, missed updates, repeat faults and documentation gaps alongside workload and job complexity.

Where complaints cluster around an engineer, inspect allocation, training, job difficulty and evidence quality before attributing the pattern to individual performance. A higher case count may reflect a different workload.

Set a review cadence your team can maintain. Track whether corrective process changes were implemented and whether comparable subsequent work shows the same failure.

Make the next complaint easier to resolve

Start with one recurring complaint category and work through a recent case from first contact to closure. Find where evidence was missing, responsibility was unclear or the customer had to chase an update.

Change that handoff, assign an owner and test the revised process on subsequent comparable jobs. A clearer variation approval, a reliable delay notification or a complete test record gives the next investigation a firmer basis.

Keep the customer's remedy and the operational improvement moving together. The complaint is only useful feedback when someone acts on what it reveals.

FAQs about field service customer complaints

What should you do first when a customer complains?

Listen to the account and assess immediate safety risk before promising a remedy. Confirm the specific issue, assign an owner and agree the next update. If the report involves a potential hazard, activate the appropriate emergency procedure rather than placing it in a routine queue.

How quickly should a field service complaint be resolved?

Resolution depends on urgency, applicable rights, contractual commitments and the work needed. Do not use a single deadline for every case. Separate a response commitment from completion of the remedy, keep the customer informed and address safety concerns immediately through the appropriate competent response.

Does a customer signature prevent a later complaint?

No. A completion signature can help establish what was acknowledged at handover, but it does not rule out hidden defects or remove applicable rights. Fieldmotion captures signatures and job information; assess those records alongside photographs, test results and the customer's account rather than treating one item as conclusive.

Must you offer a full refund for poor workmanship?

Not automatically. The appropriate remedy depends on the failure and applicable law. UK consumer service rules include repeat performance and price reduction, potentially the full price where appropriate. Irish remedies can include correction, price reduction or termination. Commercial complaints require review of the contract and governing jurisdiction.

Can Fieldmotion help investigate a complaint?

Fieldmotion supports job information, forms, photographs and signatures that can provide evidence for an investigation. Your team still needs to record the complaint, assign responsibility and assess what happened. Complete records support a fair decision; software does not determine liability or guarantee that the work met the contract.

Should you publish job details to challenge a review?

Avoid publishing private job, site or account details in a public response. Acknowledge the concern briefly and invite the customer to an appropriate private channel. Review the evidence internally, respond accurately and keep any remedy separate from requests to change or remove the review.

How can you prevent repeated documentation complaints?

Assign responsibility for completing, checking and delivering reports, and reconcile them against contracted visits. Fieldmotion's customer portal supports access to job records and reports, but you must still check completeness. Never fill historical evidence gaps with invented or backdated findings; disclose the gap and agree the appropriate action.