Handling customer complaints and callbacks

A complaint handled quickly and fairly often leaves the customer more loyal than if nothing had gone wrong. The steps are simple: listen fully, acknowledge the problem, get someone back out fast, fix it, and follow up. Then track every callback by cause and by technician, so the same problem doesn't keep coming back.

This guide covers the conversation, the callback visit, who pays, and the system that reduces callbacks over time.

What counts as a complaint, and what counts as a callback?

It helps to separate the two:

A complaint is any expression that the customer is unhappy: about the work, the price, the arrival time, the tech's behavior, a mess left behind, or a bill they didn't expect.
A callback (sometimes called a recall or a go-back) is a return visit to fix or recheck work you already did, usually for the same problem at the same address within a short time.

Not every callback is your fault. A new, unrelated failure on old equipment is a new job. A part you installed failing within the warranty period, or a problem the tech didn't fully fix, is a callback. Decide your definitions in advance and write them down, so the office and the techs apply them the same way.

How should you handle the first complaint call?

The first five minutes decide most outcomes. Train whoever answers the phone to follow these steps:

Let them finish. Don't interrupt, explain or defend. People calm down when they feel heard.
Acknowledge. "I'm sorry. That's frustrating, and it's not what we want for you." This isn't admitting fault. It's acknowledging their experience.
Get the facts. What's happening now, when it started, what the tech did. Look at the job record, notes and photos while you listen.
Offer a specific next step. "I can have a technician there tomorrow between 8 and 10, at no charge for the visit." Specific beats vague.
Confirm and document. Repeat the plan, note it in the customer's record, and tell the tech and dispatcher.

Things to avoid on that call:

Blaming the technician in front of the customer.
Arguing about whose fault it is before anyone has looked.
Promising refunds or free work you can't approve.
"There's nothing we can do."

Who should go back on the callback?

There are two schools of thought, and both work:

Send the original tech. They know what they did and get to fix it, which is a strong learning moment. It also shows the customer accountability.
Send a senior tech or the service manager. They bring fresh eyes, especially if the original tech missed something or the customer is very upset.

Many shops send the original tech with a senior tech on the phone, or a senior tech when the customer asks for someone different. If the complaint is about the tech's behavior, send someone else.

What happens on the callback visit?

Arrive on time. Being late to a callback makes everything worse.
Apologize for the trouble, regardless of cause.
Diagnose fresh. Don't assume it's the same issue.
Explain what you found, with photos if helpful.
Fix it, or explain clearly if it's a new or unrelated problem, and what options they have.
Confirm the customer is satisfied before leaving, and get a sign-off on what was done.
Record everything: the cause, the fix, the time spent and parts used.

Who pays for a callback?

Set a written policy so nobody improvises. A common approach:

Your workmanship or a part you installed failed within your warranty: no charge to the customer.
A new, unrelated problem: a normal service call, explained honestly, and many shops waive or reduce the trip fee as goodwill.
The customer declined a recommended repair and the problem came back: a normal service call. This is why written, signed options matter.

Inside the business, decide how callbacks affect tech pay. Many flat-rate and commission shops don't pay for the tech's time on their own callbacks, or pay a reduced rate. Whatever you choose, make it fair, written down and consistent, and make sure hourly employees are still paid for all time worked as the law requires.

When should you offer a refund or discount?

Refunds and discounts are tools, not reflexes. Consider them when:

The work genuinely didn't meet your standard and the customer's time was wasted.
There was a billing error.
The experience was poor even if the work was fine: a very late arrival, a mess, a rude interaction.

Be specific: "I'm taking the trip fee off your invoice" or "I'm refunding the diagnostic." Partial gestures given willingly often satisfy more than full refunds given grudgingly. Give whoever handles complaints a clear limit they can approve without asking.

How do you respond to a complaint that turns into a bad review?

Respond publicly, briefly and calmly. Acknowledge, don't argue details, and invite them to contact you directly.
Never share private details about the customer or the job in a public reply.
Fix the problem offline. Some customers update their review after a good resolution. Don't ask them to remove it in exchange for anything.

How do you reduce callbacks over time?

Every callback is information. Track it.

Record for each callback:

The original job, tech and date
The cause: workmanship, part failure, misdiagnosis, customer misunderstanding, new problem
The time and parts it cost

Look at the numbers monthly:

Callback rate = callbacks ÷ jobs completed, by tech and by job type
Top causes, ranked
Cost of callbacks in labor and parts

Act on patterns:

One tech with a high rate: coaching, ride-alongs, a checklist for that job type.
One job type with a high rate for everyone: a better procedure, better parts, longer test time before leaving.
"Customer misunderstanding": better explanations and written summaries at sign-off.

A simple end-of-job checklist (test the system, check for leaks, clean up, show the customer what was done) prevents a surprising number of go-backs.

How do you follow up after the problem is fixed?

A day or two after the callback, call or text:

"Hi Mark, this is Jen from Northside Heating. I wanted to check that everything has been working well since Luis was back out on Tuesday. Is there anything else we can do?"

That one follow-up is often what customers remember. It shows you cared about the outcome, not just closing the ticket.

FAQ

How long after a job is a return visit a callback? Many shops use a window like 30 days, or the length of their labor warranty. Pick a window that fits your trade and your guarantee, and write it down.

Should techs be penalized for callbacks? Callbacks should have some consequence in a flat-rate or commission plan, but focus on patterns, not single events. Use the data for coaching first.

What if the customer is abusive? Stay calm and polite, set a boundary ("I want to help, but I need us to speak respectfully"), and end the call if needed. Your team's safety and dignity matter.

Should I ask for feedback after every job? Yes. Asking every customer, not just happy ones, surfaces small problems before they become public complaints.

How ServFlo helps

ServFlo asks every customer "How did we do?" when they pay, and shows the answers in Reviews with an average for each technician, so unhappy customers surface early. The technician performance report estimates callbacks (a repeat job at the same property for the same service type within 30 days) and counts them against the original technician. Job photos, notes and the customer's signed sign-off are kept on each job, so the office has the facts when the phone rings. See Reviews and marketing and Reports and integrations. For the phone conversation itself, see customer service scripts for the office.

Handling customer complaints and callbacks without losing the customer