Customer complaint response scripts: what to say when a service customer is upset

A complaint call is a test of two things: whether the customer feels heard, and whether they leave the call knowing exactly what happens next. Most bad complaint calls fail the second test. The CSR apologises warmly, promises to "look into it", and the customer hangs up with nothing.

The scripts below all follow the same five steps. Learn the steps and the specific scripts become easy to adapt.

The five steps behind every script

1. Let them finish. Do not interrupt, even to correct a fact.
2. Say back the specific problem. "The tech was supposed to be there at 10 and arrived at 12:15", not "I understand you're frustrated".
3. Own your part plainly. Apologise for what actually went wrong. Do not blame the tech, traffic or "the system".
4. Offer one concrete fix with a time. A named next step and when it happens.
5. Close the loop. Say who will follow up and when, and then do it.

Steps 2 and 4 are the ones that turn a complaint into a kept customer. A specific restatement proves you listened. A specific fix with a time proves something will happen.

The scripts

1. The tech was late

"You were told [window] and our technician arrived at [time]. That's on us, and I'm sorry it cost you your [morning/afternoon]. You should have heard from us the moment we knew he was running behind, and you didn't. [Fix: e.g. 'I've taken the service call fee off today's visit.'] I've also noted on your account that you need a call 30 minutes ahead next time."

Why it works: the apology names the real failure, which is usually not the lateness but the silence. A late truck with a heads-up is an inconvenience. A late truck with no word is what turns into a complaint call. If late arrivals are frequent, measure your on-time arrival rate before you rewrite any script.

2. The tech never showed up

"I'm sorry. You took time off and nobody came, and nobody called. That should not have happened. I can get a technician to you [today between X and Y / first thing tomorrow at 8]. Which works? I'll call you myself when they're on the way."

Why it works: a no-show breaks trust in the schedule itself. Offer the earliest real time you can actually keep, not a vague "as soon as possible". Then personally confirm it.

3. The problem came back (repeat repair)

"So we were out on [date] for [problem], and it's doing the same thing again. I'm sorry, that's not what you paid for. I'm booking a return visit at no charge for the diagnosis, and I'm sending [lead tech / a senior tech] rather than the same visit again. The earliest I have is [time]. Does that work?"

Why it works: it treats the return as your problem, not a new job, and it changes something (the tech) so the customer does not expect the same result. Check your own warranty terms before promising more than the free diagnosis. The warranty callback glossary entry and how to reduce callbacks cover what to fix upstream.

4. The bill is higher than expected

"I hear you. The total came to [$X] and you were expecting closer to [$Y]. Let me walk through what's on it line by line. [Explain.] Was the price explained to you before the work started?"

If yes, and the work matches: "The tech quoted [$X] and you approved it at [time]. I know that's more than you hoped, and I can [offer the payment option you have, if any]."

If no: "That's our mistake. You should have had a price before any work started. I'm going to [adjust / talk to the owner and call you back by 3 p.m. today]."

Why it works: going line by line separates "I didn't understand" from "you didn't tell me". The fix depends on which one it is. If the customer is refusing to pay rather than disputing, see how to handle a customer who won't pay.

5. Damage to the home

"I'm sorry. Can you tell me exactly what was damaged and where? Could you send me photos to this number? I'm going to have [owner/manager] call you by [time today] to arrange the next step. Please keep the damaged item, and don't throw anything out until we've seen it."

Why it works: damage is the one case where the CSR should not promise a fix on the call. Gather facts and photos, hand it to the person who can decide, and give a callback time. Follow your insurer's claim process.

6. Rude or careless technician

"Thank you for telling me. Can you tell me what was said or what happened? [Listen and write it down word for word.] That's not how we expect anyone to treat a customer. I'm passing this to [owner/manager] today, and they'll call you by [time]. If you need more work done, I'll make sure it's a different technician."

Why it works: it takes the report seriously without convicting the tech on the phone. Write down the customer's words, not your summary.

7. Reply to a bad online review

"[Name], thank you for telling us about this. You're right that [specific failure, e.g. 'we didn't call when your technician was running two hours late']. That's not the standard we hold ourselves to. I'd like to make it right: please call me directly at [number] or reply here, and I'll take care of it personally. [Owner name], [Company]"

Rules for public replies: reply within a day or two, never argue facts in public, never mention the customer's address or job details beyond what they posted, and move the conversation to the phone.

How to adapt the scripts

• Write down your fix menu. Decide in advance what a CSR can offer without asking: waive the service call fee, a free return diagnosis, priority booking. Anything above that goes to the owner. CSRs freeze when they do not know what they are allowed to offer.
• Set callback deadlines and keep them. "By 3 p.m. today" means 3 p.m. today. A missed callback on a complaint is a second complaint.
• Log every complaint by type. Use the six types above (scripts 1 to 6). After a month, count them. If late arrivals lead, the fix is in the schedule, not the script.
• Fix the cause behind the most common one. Often that is lateness and silence. The guide to field service customer communication covers the texts that prevent the call. In CrewLink, for example, customers get a text when the tech is on the way with an ETA, and when a job is moved, which addresses the "nobody told me" part of a late-arrival complaint.

Common questions

How do you respond to a customer complaint in field service?

Let the customer finish, repeat back the specific problem, apologise for your part without excuses, offer one concrete fix with a time, and tell them who will follow up and when. Then make sure that follow-up happens on time.

Should you offer a discount when a customer complains?

Only when it matches the failure. Waiving a service call fee after a long late arrival is proportionate. A blanket discount for every complaint trains customers to complain and does not fix anything. Write down what CSRs may offer without approval so the answer is consistent.

How should you reply to a negative online review?

Reply within a day or two, thank the customer, name the specific failure if it is real, and invite them to call you directly. Do not argue details in public or share job information beyond what they posted. Future customers read the reply as much as the review.

Who should handle a property damage complaint?

The CSR gathers facts and photos and gives a callback time, then hands it to the owner or manager. Damage often involves your insurer, so the person who can decide should be the one making the offer.