How to Train the Office on What Never to Promise

Why this matters

The office is the first place a shop makes a promise and the last place anyone checks for one. A CSR who wants to calm a worried caller says "the warranty should cover that," "your insurance will pay for it," or "he'll be there at ten," and every one of those sentences is something the shop may now owe, or something a regulator (the FTC under Section 5 of the FTC Act, or your state under its deceptive practices act) may read as misleading, while nobody in the field knows it was said. These are not bad CSRs. They are good ones without a list. A short list of forbidden promises, each with the reason and the replacement words, practiced out loud and checked monthly, removes most of the problem in a quarter.

Step 1: Build the list from your own complaints, not a generic one

Pull the last year of disputes, chargebacks, bad reviews and complaint letters, and for each one ask: did it start with something the office said? Write each promise in the words the CSR actually used. Then add any of the common ones below that your shop has not hit yet.

Why: a list drawn from your own record is one the office believes, because they recognize the calls. A generic list reads as theory.

What breaks if you skip it: you train on promises nobody in your office makes and miss the one your best CSR says ten times a week.

Step 2: Write the reason next to each promise, in one line

The office will follow a rule it understands and quietly drop one it does not. The reason also tells them which promises are legal problems and which are commercial ones, so they know where the line is firm. A typical list looks like this:

Forbidden promise Why it is forbidden Say instead
"He'll be there at ten." An exact time is a commitment the schedule cannot keep; a missed one is the most common first complaint "Your window is ten to two. He'll text when he's on the way, about 30 minutes out."
"It's probably just a [part], around [amount]." A price before diagnosis becomes the price in the customer's head, and quoting a repair price as a bait for a visit is the bait-and-switch pattern regulators look for "I can't price the repair until he's found the cause. The visit is [amount], and here's what it covers."
"The warranty will cover it." The office cannot know: coverage turns on the failed part, the registration, the install date and the cause "If the unit is under warranty, he'll check coverage on site and tell you before any work."
"Your insurance will pay for that." Coverage is the insurer's decision. Several states, Texas and Florida among them, restrict contractors from interpreting a policy or negotiating a claim for the homeowner "Your insurer decides coverage. We'll give you a written report and photos you can send them."
"You're approved" or "everyone qualifies" for financing. Credit decisions belong to the lender, and the financing conversation has its own fair lending rules "We offer financing through a lender. They decide approval; it takes a few minutes to apply."
"We'll waive the fee." or "He can probably knock it off." A CSR cannot bind the tech's pricing, and a waiver promised on the phone is owed at the door "The service call is [amount]. If something changes, the tech will tell you before he starts."
"It'll be fixed today." Parts, access and diagnosis all decide that; the customer plans their day around the promise "Most of these are fixed on the first visit. If he needs a part, he'll tell you how long it takes."
"You don't need a permit for that." Permit rules are local, and a wrong answer is both a misrepresentation and a code problem "The tech or the office will confirm the permit requirement for your town before work starts."
"We're the cheapest in town." An objective comparative claim the shop has to be able to prove "We give a firm written price before any work, so you can compare."

The words that make a sales pitch into a promise (guaranteed, lifetime, free, certified) are covered in the sibling card on words that create legal promises; the office list should borrow its two or three most relevant rows rather than re-arguing them.

Why: a forbidden promise without a replacement leaves the CSR with silence where they used to have reassurance, and silence gets filled with improvisation.

What breaks if you skip it: the CSR learns not to say "the warranty will cover it" and starts saying "I'm sure it's covered," which is the same promise in new clothes.

Step 3: Teach it as a phone skill, not a policy memo

Hold a 30-minute session, not a reading assignment. Go down the list one row at a time: the owner reads the forbidden line, a CSR says the replacement out loud, and the group talks about the last time a caller pushed back on it. Hand out the table as a single printed page for the desk, and put it in the shared knowledge base.

Why: the replacement wording only works if it comes out naturally under pressure. People say what they have practiced saying, not what they read once.

What breaks if you skip it: the page goes in a drawer, and the first stressed caller gets the old sentence.

Step 4: Role-play the caller who pushes

The real test is not the calm caller. It is the one who says "Just tell me it's covered or I'm calling someone else," or "My neighbor paid less than half that." Run each CSR through three of these with the owner or office manager playing the caller. Score only one thing: did the CSR hold the replacement wording without sliding back into a promise, while still being friendly?

Why: promises get made under pressure. A CSR who has rehearsed the pushback has the sentence ready; one who has not reaches for whatever ends the pressure fastest, which is usually the promise.

What breaks if you skip it: the training covers every call except the ones that cause the complaints.

Step 5: Review a fixed sample every month

Each month, pull 20 booked calls at random across all CSRs, using recordings if your shop records (with the consent announcement your state requires) or the call notes if it does not. Score each against the list: any forbidden promise made, and whether the replacement wording was used where it applied. Track the count by CSR and by row.

Why: a rule that nobody checks decays. A monthly review at a fixed sample size makes drift visible as a number, and it tells you which row of the list is weakest so you can retrain on that row.

What breaks if you skip it: the training works for six weeks and nobody notices it stopped working.

Step 6: Treat a slip as a coaching moment and a customer task

When the review finds a forbidden promise on a call that has not happened yet, the office calls the customer back with the correct information before the tech arrives. When it finds one on a finished job, the owner decides whether the shop honors it. Coaching for the CSR is private, short and about the specific sentence.

Why: the review is there to catch promises before they cost money, not to rank people. A review that feels like discipline teaches CSRs to stop writing honest notes, which ends the review.

What breaks if you skip it: the review finds the promise, nobody tells the customer, and the tech meets it at the door.

A worked quarter

A pest control and lawn care shop with three CSRs builds its list from the past year: 22 complaints, of which 9 started with something said on the phone. Those 9 break down as 4 "it's covered under your plan," 3 exact arrival times, and 2 "the re-treat is free" on services where it is not. The shop adds four rows from the table above that have not caused trouble yet, for a list of seven rows.

Month one. Training session and role-play in the first week. The month-end review of 20 calls finds 6 forbidden promises: 3 arrival times, 2 "it's covered," and 1 "free re-treat." By CSR: 4 of the 6 from the newest CSR, 1 from each of the other two.

Month two. The owner retrains the newest CSR on the two weakest rows and adds a line to the plan description screen showing exactly which services include a free re-treat. Review of 20 calls: 3 forbidden promises, 2 arrival times and 1 "it's covered."

Month three. The arrival-time row is still the most common, and listening to the calls shows why: customers ask "can you be more specific?" and the CSR has no answer beyond the window. The shop adds an on-the-way text with an estimate about 30 minutes ahead, and the script gains a line saying so. Review of 20 calls: 1 forbidden promise, an arrival time.

Reading the result. Forbidden promises fell from 6 to 3 to 1 per 20 calls over the quarter. The arrival-time row was the one that held on, and it took a process fix, not more training, because the CSRs were answering a real customer need with the only thing they had. Of the 10 forbidden promises found across three months, 6 were arrival times, which is why that row got the fix. Phone-originated complaints the next quarter: 2, against a prior run rate of 9 a year, which is about 2 a quarter. That comparison does not show improvement yet. A quarter is too short to read complaints, which are rare enough that 2 against an average of about 2 is noise; the per-call promise count is the measure that moved, and complaints are the lagging check to read at year end.

What would change it. In a shop that does not record calls, the review relies on notes, and notes undercount, because a CSR who made a promise rarely writes it down. That shop should have a supervisor sit in on 5 calls a week instead. In a state with strict rules on contractors and insurance claims, the insurance row is not a commercial preference but a legal line, and it should be the first row taught, with the reason stated in those terms; a roofing or water damage shop in Florida or Texas should have its attorney confirm the replacement wording.

References

  • FTC Act Section 5 and your state's unfair and deceptive practices act (statements to consumers must not mislead)
  • See related: Words That Create Legal Promises in a Sales Pitch
  • See related: How to Write a Price Disclosure Script for the Phone
  • See related: Equal Credit and the Financing Conversation
  • See related: Advertised Prices and the Bait-and-Switch Line