Warranty Callbacks Are Free Labor You Didn't Sign Up For

When I took over this shop in January 2020, I inherited three trucks and an informal warranty program I didn't know existed.

Mike — my dad — had spent 36 years telling customers "we stand behind our work." He meant it. He's not a guy who says things he doesn't mean. But he never wrote it down. Never put a time limit on it. Never said what "our work" included. It was a handshake with the whole neighborhood. When his hip went and I took over the phones, customers started calling in on jobs from 2014, from 2011, from jobs I couldn't even find in the paper files.

We showed up. Because what else do you do? Nobody knew what the promise covered, so we treated it like it covered everything.

You're probably doing the same thing right now. You just don't have it on paper — which means the only version that exists is the one the customer imagines. Their version is always more generous than yours.

You Trained Them to Call. You Just Don't Know It Yet.

Dom had been running calls on his own for maybe eight months when this happened.

Lady on one of the streets off Broadview, called in on a slow kitchen drain. Dom goes out, snakes it, sixty feet, clears a grease blockage. She's happy, pays the invoice, done. Following July she calls back. Drain's slow again.

Dom goes out. Snakes it again. Sixty feet, grease. He charges her nothing because it's a "warranty call" and nobody told him different.

That drain wasn't a workmanship defect. Dom cleaned it right the first time. The customer had been pouring bacon fat down it since Thanksgiving, which is a Cleveland tradition and also a pipe killer. But Dom showed up, apologized with his body language the way young guys do, and snaked it for free. Because that's what we do.

The customer did nothing wrong. She called, we came, we fixed it, we didn't charge. From her perspective, that's just how Whittaker works. She told her neighbor on Nextdoor — I know because the neighbor called three months later with a slow drain and mentioned she'd heard we take care of our customers.

So now you respond generously to something that isn't your fault, the customer has a good experience, they tell people, and the whole street thinks your warranty is anything, anytime, no questions asked. Customers aren't running a con. They learned the rules from you.

And look — the customer is always somebody's mom. You treat the call like your mom called. That's still true. But your mom doesn't expect you to re-excavate her side yard for free because roots grew back.

How you treat people is not the same question as what you're on the hook to fix for free.

The customer didn't invent this. You did. Every time you showed up for free without asking a question, you were writing the policy — just not on paper where it could protect you both.

What Your Warranty Actually Covers (And What It Definitely Shouldn't)

Most shops think a tight warranty policy will make customers feel nickel-and-dimed. I thought this too, for years.

What I've found in my shop: vague warranties don't prevent disputes. They guarantee them. When there's no document, you're negotiating coverage in real time, in the customer's kitchen, while they're upset. That's a bad moment to be figuring out what you owe somebody.

The thing you need straight in your own head is the difference between a workmanship defect and a conditions problem.

A flex line I didn't torque right that drips in three days — that's on me. I go back, I fix it, I don't charge, I own it.

Collapsed clay sixty feet under a Parma side yard that shows up on a scope six weeks after I snaked the drain — that's not on me. That's Cleveland geology doing what Cleveland geology does. The drain was slow because of the clay, not because of anything Dom did. That's a new job with a new ticket.

Most shops treat both of those the same way. Guy calls, we go, we fix, we don't charge because the job was recent and it feels related. But those two situations are not the same and your invoice shouldn't treat them like they are.

A warranty clause doesn't need to be long. Mine covers: what work is included, how long the coverage runs, what voids it, and who makes the call on which category a complaint falls into. On that last one — it's you. You're the licensed contractor. You go look, you assess, you decide. That's not adversarial. That's the job.

The Callback That Cost Me a Tuesday

Dom installed a water heater for a woman on the Broadview Heights side, last fall. Fifty-gallon gas, Bradford White, standard replacement. Good install — right clearances, expansion tank, solid work. Dom walked her through it before he left.

She calls back two weeks later. Noise. Dom goes out, spends two hours, finds nothing wrong. He leaves. She calls again the week after. I go myself.

The noise was the expansion tank. Slight ticking as pressure shifts during heating cycles. Normal behavior, especially in the first thirty days on a new tank. I know this. Dom knew this. We'd told her — verbally, at the install.

Except there was nothing in writing. No install summary, no "what to expect in the first 30 days," nothing she could look at at 9 PM when the tank made a sound and she got nervous. So she called. Twice. I ate a half-day of Dom's labor and most of my own Tuesday morning to explain something that had already been explained, with nothing to back it up.

That afternoon I called Becca. She spent forty minutes in Jobber building a one-page install summary — what was done, what's covered, what's not, what normal behavior looks like in the first 30 days for the specific type of equipment. Expansion tanks tick. Water heaters make sounds when they heat up. New supply lines can weep at a fitting once and then seal on their own. Plain English, one page, goes out attached to every invoice.

Dom hands it to every customer now. Doesn't prevent every callback. But it gave us something to point to — and it gave customers something to check before they called. The callbacks that do come in are easier to sort because the customer already has a baseline in writing.

Forty minutes of Becca's time. That's what it cost.

How to Write a Warranty Policy Without a Lawyer or a Week You Don't Have

You need a paragraph and a footer. That's it.

My current Jobber invoice has a warranty clause right above the signature line. I'll paraphrase it because I'm not handing out legal templates: workmanship defects are covered for 90 days from the date of service. Pre-existing conditions aren't covered — that's what I think of as the Cleveland clay clause. Customer-caused damage isn't covered. Parts go through the manufacturer warranty, not through us.

Four sentences. Fits in a footer.

The 90-day number isn't magic. It's what made sense for the kind of jobs we do. Drain work might be 30 days — roots and grease are environmental and outside my control past that point. A sewer repair where we pulled permit and the inspector signed off, I'll do a year on workmanship because I have a dated record that the work met code. Water heater install — 90 days on workmanship, manufacturer handles the unit, which is typically six years on the tank.

And that permit card matters more than people realize. If the work passed inspection, you have a record that it met code on that day. Anything that goes wrong after that date raises a pretty simple question: what changed? That's not an accusation. It's the right question. The inspector's signature lets you ask it.

Get the policy on paper. You can fix the language in six months. You can't defend yourself with a policy that only exists in your head.

What to Do Next Week Before Any of This Gets Complicated

One. Pull your last five callbacks. Sort them: did we do something wrong, was it already broken before we got there, or did the customer do something after we left? If you can't figure out which is which, that's the whole problem right there. You don't have enough documentation to categorize your own work.

Two. Write one paragraph tonight. Phone, truck, after Hank goes down — whenever. What you cover, how long, what voids it. Text it to whoever handles your invoices and ask them to put it in the footer of the next one that goes out. Don't wait until it's perfect. Make it exist.

Three. Next callback call that comes in, before you dispatch, ask one question: "Has anything changed in that area since we finished the job?" Not an accusation. Just what a professional asks before driving thirty minutes. What they say — and what they hesitate on — will tell you a lot about which pile you're in.

I've had that question save me a truck roll on calls that turned out to be customer-caused before my guy ever left the shop. Not every time. But enough.

---

FAQ

If I start charging for callbacks, won't customers just leave a bad Google review?

Some will. Not as many as you think, and not as often as the free-callback habit costs you. What I've seen in my shop: customers who get a clear explanation of why something isn't covered — in writing, calmly, before it turns into a fight — mostly accept it. The ones who go nuclear were probably going to find a reason to write a bad review regardless. And the Nextdoor rep you build by being straight with people is worth more in a neighborhood like mine than any single one-star. Document everything, be kind about it, and let the permit card do the talking if it gets ugly.

What's a reasonable warranty period for drain work versus a water heater install versus a full sewer repair?

In my shop: 30 days on drain cleaning. 90 days on a water heater install for workmanship, manufacturer warranty on the unit. One year on workmanship for a sewer repair with a permit, because we dug it up, we replaced it, and I have an inspection record. Those numbers came from thinking hard about what I can actually stand behind and prove if someone pushes back. Your jobs might be different. The point isn't the specific number — it's that you pick one and write it down.

What do I do about callbacks on jobs my dad's shop did before I took over?

This one's real for me. Short answer: you make a business decision, not a warranty decision, because there is no warranty. Those jobs were closed under verbal promises that weren't documented, for customers who've been with the shop for years. I generally help them — once. I'm upfront that I'm doing it as a goodwill call, not a warranty call, and I make sure that's on the invoice. It buys loyalty. It doesn't set a precedent because I document what I did and why. Not the right answer for every shop. It's the right answer for Whittaker, where half our customer base knew Mike personally.

My guy made an honest mistake on the install — that's clearly on us. How do I handle that without torching the customer relationship?

Go yourself. Don't send the same guy if the customer's frustrated, or at least go with him. Say you reviewed the job and you're taking responsibility — say it fast, don't make them fight for it. Fix it. Eat the labor. Document what was wrong and what you did to correct it. Don't over-apologize and don't discount the original invoice, because that signals the whole job was bad when mostly it wasn't. You made one mistake and you fixed it. That's a follow-through situation, not a refund situation. Most customers will respect it if you own it cleanly and don't grovel.

How do I bring this up with a customer who's already expecting a free return visit?

Call first, tell them you're coming out to look. Before you go, ask what changed since you finished the job. If you get there and it's clearly not your problem, be straight: here's what I'm seeing, here's why this isn't on us, here's what it'll cost to fix. Have your invoice ready with the warranty language on it. You're not picking a fight. You're being the professional. Most people respond to calm and specific a lot better than they respond to apologetic and vague.

Can I backdate a policy change, or do I have to honor the old "we stand behind our work" promise on jobs already closed?

You can't backdate it. If a job closed without written warranty terms, whatever was said is what you're on the hook for. I lived this when I took over from Mike. Going forward, every new invoice gets the clause. For old jobs, you make judgment calls — is this customer loyal, is this actually our fault, how much goodwill is on the table. The written policy protects you on work you haven't done yet. It doesn't rewrite history on work you already closed. And honestly, you wouldn't want it to. Neither does the customer.