Callback Cost: Eat vs Charge vs Split by Cause Attribution Decision Matrix

Why this matters

A callback is a return trip to a job you already completed and were already paid for. Every callback carries a real cost: a tech off the schedule, fuel, parts, and the lost revenue of the job that tech could have run instead. How you handle the cost question shapes both your margin and the customer relationship. Eat a cost you should have charged and you train customers to expect free returns. Charge for a cost that was your own workmanship failure and you lose the customer and earn a bad review. The deciding variable is almost always cause attribution: who or what actually caused the second visit.

Getting this right protects three things at once: your margin (you are not absorbing avoidable cost), your reputation (you are fair on the cases that are genuinely yours), and your technicians (a clear policy removes the awkward judgment call from the truck).

The situation

A customer calls back after a completed job. The same system is failing, a new but related problem appeared, or something the tech touched is no longer working. A dispatcher or owner has to decide before the truck rolls: is this a free return, a billable new visit, or something in between? The decision has to be defensible later if the customer disputes it.

What is at stake

The downside of guessing is asymmetric. Charging for a true workmanship defect produces a complaint, a chargeback risk, and a public review far more expensive than the visit. Eating a cost that was clearly customer-caused or unrelated erodes margin invisibly across hundreds of jobs a year. The goal is a repeatable rule, not a case-by-case mood call.

Decision factors

• Cause attribution. Did your work cause it, did the customer or a third party cause it, or did an unrelated component fail on its own? This is the primary axis.
• Time elapsed since the original job. A failure within days points toward workmanship; a failure months later points toward independent wear, unless a part carries a longer warranty.
• Warranty coverage in force. A labor or parts warranty you issued may already obligate a free return regardless of fault opinion.
• Was the original scope complete? If you flagged a related deferred item and the customer declined it, a later failure of that item is not a callback.
• Diagnostic certainty at first visit. A correct diagnosis that the customer declined to fully repair is different from a missed diagnosis.

The decision: options and when each wins

Eat the full cost (free return) wins when the failure traces to your own workmanship or a part you installed, inside your stated warranty window, and the original scope covered the failed item. A loose connection you made, a fitting you did not seat, a setting you misconfigured. This is not generosity; it is honoring the work. Roll the truck, fix it, document it as a warranty callback, and review why it happened.

Charge as a new visit wins when the new problem is unrelated to your prior work, or the customer (or a third party) caused the failure after you left, or the customer declined the repair you recommended and the declined item is what failed. A different component, customer misuse, or a deferred-and-declined item. Quote it like any new job. Show the customer the prior documentation that recorded the recommendation or the limited scope.

Split the cost wins when attribution is genuinely mixed or unprovable. Partial workmanship contribution, a pre-existing condition you should have caught but did not fully cause, or a gray-zone failure where insisting on either pole damages the relationship more than the dollars justify. A common split is to waive the trip/labor and bill only parts, or vice versa. Reserve splits for true ambiguity; overusing them turns into eating costs by another name.

What to document

• The original job number, scope, and completion notes, pulled before the truck rolls.
• The cause determination in plain language, with photos of the failed item.
• Which decision was applied and why, tied to the matrix above.
• If charged: the prior recommendation or scope limit that supports billing.
• If split: which portion was waived and the stated reason.
• A callback tag on the record so the rate is trackable as a quality metric over time.
• The customer communication: what they were told about the decision and any acknowledgment, so a later dispute has a clear record of what was agreed before the truck rolled.

Track your callback rate by technician and by cause. A rising "your workmanship" share is a training signal, not just a margin leak. The attribution discipline that decides one visit also tells you where the real defects are coming from.

References

• Magnuson-Moss Warranty Act, 15 U.S.C. ss 2301-2312 (governs consumer product warranties and what a written warranty obligates).
• FTC, "Businessperson's Guide to Federal Warranty Law" (warranty disclosure and honor obligations).
• Uniform Commercial Code Article 2, ss 2-313 to 2-315 (express and implied warranties of merchantability and fitness; basis for workmanship-standard expectations).
• ASA (American Subcontractors Association) and trade-association standard-form contract language on warranty/callback periods, as a model for written workmanship-warranty terms.