Deciding What a Callback Should and Shouldn't Cost the Customer

Why this matters

Deciding a callback's cost one visit at a time, in the customer's driveway, under pressure, is how a shop ends up inconsistent and resentful. One tech eats everything, another charges for coincidences, and customers compare notes. The fix is a clear standing principle for what your workmanship covers and what stays the customer's cost, set before the callback happens. This card is that framework. It is not the single-visit call, it is the policy the single-visit call should follow.

What "warranty of your workmanship" actually covers

Every reputable shop stands behind its own work. The trick is knowing exactly where that promise starts and stops, because a vague "we guarantee our work" gets read by the customer as "everything is free forever."

Your workmanship warranty covers faults that trace back to what you did:

• A repair that did not hold because you did it wrong or incompletely.
• A wrong diagnosis, where you replaced a good part and missed the real cause.
• Damage you caused by disturbing something during the visit.
• A defective part you installed, within the part's own warranty terms (the labor to swap it is usually the negotiable piece, and worth spelling out so a customer does not assume all labor is always free).

The unifying test is causation: if your prior visit caused or should have caught it, it is on you.

What legitimately stays the customer's cost

Standing behind your work does not mean owning the whole machine forever. These remain the customer's cost, and saying so plainly up front prevents the fight later:

• A genuinely separate part that failed on its own, proven independent of your work.
• A pre-existing fault your repair unmasked (commonly the parts and labor are billable while the trip or diagnostic is waived, so the customer sees you sharing the connection without eating a whole new repair).
• New damage from the customer's own use, misuse, or a power or water event after you left.
• Wear items and consumables that reached end of life on their normal schedule.

The unifying test again is causation: no link to your visit, no obligation to absorb it.

Set the policy before the callback, not during it

Write down your callback policy once, in plain language, and hold every tech to it. At minimum it should state:

• A workmanship guarantee window - a defined period during which you return free for faults in your own work. Pick a length you can honor across your trades and stick to it; a promise you quietly break the first inconvenient time is worse than none.
• What the window covers and excludes, in the terms above.
• How gray zones get handled - who has authority to waive, and the default split for an unmasked fault.

A written policy is what makes two different techs give the same answer, which is what makes customers trust the answer.

Tell the customer the coverage up front

The best time to explain callback coverage is on the first visit, not the second. A customer who was told "our work is guaranteed for this window, and here is what that covers" is not surprised or suspicious when a callback conversation happens. They already know the rules.

• Put the guarantee on the invoice or the work order, in words a non-tech reads without a lawyer.
• State both halves: what you cover and what stays theirs. A one-sided "everything is guaranteed" sets a trap you will spring on yourself.

Callbacks as a shop metric, not just a cost

What you absorb on callbacks is also data. Track your callback rate, because a rising rate of eaten visits is telling you something a single invoice cannot.

• Clustered around one tech: a training or workmanship issue to fix at the source.
• Clustered around one part or procedure: a materials or method problem, not a people problem.
• Rising overall: your diagnosis or your quality control is slipping upstream.

The dollars you eat are the price of the callback. The pattern in them is the free lesson, and it is worth more than the visit.

The principle to keep

The customer should pay for new problems and never for your misses. Every callback-cost decision is just that one sentence applied honestly. Write the policy down so it is consistent, explain it up front so it is trusted, and read the pattern in what you absorb so the callbacks themselves get rarer. Do that and callback billing stops being an argument and becomes a quiet proof that you are fair.

References

• Trade-standard practice for workmanship warranties and callback policy
• U.S. Small Business Administration (SBA), service warranty and customer policy basics
• See related: Charge for the Comeback Visit or Eat It (decision tree); Facing the Same Customer on a Comeback With Credibility Intact