Callback visits: measure repair-job margin after the customer calls again

A repair can look profitable on Friday and become expensive when the technician returns on Monday. If the return visit sits in a general service bucket, the original job keeps an inflated margin and the correction becomes someone else's unexplained cost. Link the new visit to the original job while retaining its own date, work record, and expenses.

ServiceTitan's recall workflow explicitly connects corrective work to a completed job and treats its recall booking as a no-charge job. Other systems may use different names or defaults. Define your own categories clearly enough that dispatch, technicians, and accounting can identify the relationship without relying on a note buried in the customer history.

A return visit might correct an installation problem, replace a failed manufacturer part, complete work deliberately left open, or address a new problem the customer wants to buy. These situations should not all be counted as the same failure. Let a responsible service reviewer classify the reason using the work record rather than assigning blame from the existence of a second appointment.

Keep the classification changeable through an approved correction. A suspected installation issue may later prove to be a defective component. Preserve the first classification and the evidence behind the revision. This protects the usefulness of technician and product comparisons without erasing the cost that the business actually incurred.

Record technician time, employer labor costs included in your costing policy, additional parts, outside services, and any separately measured travel or dispatch cost. A customer invoice for zero dollars explains the selling decision; it does not mean the business consumed no resources. Preserve both the invoice status and the cost record.

ServiceTitan's costing documentation identifies materials, equipment, purchase orders, commissions, and labor burden as possible cost inputs. Check which inputs your report actually uses. A wage-only labor number cannot be compared fairly with another team's fully loaded labor cost unless the difference is shown.

Do not add a notional lost sale to actual job expense. A callback may occupy a slot that could have been sold, but that opportunity cost belongs in a separate capacity scenario. Counting both a full lost selling price and the callback's actual labor as if they were ordinary expenses overstates the accounting loss.

For a hypothetical repair, customer revenue is $800 and the original direct job cost is $420. The initial contribution is $380. A no-charge callback adds $90 of labor cost and a $70 replacement component, bringing linked direct cost to $580 and reducing contribution to $220 before any costs excluded from the calculation.

If a manufacturer later approves a $50 credit, show that recovery separately before presenting the resulting $270 contribution. Until the claim's treatment is supported under the company's policy, keep requested recovery distinct from approved or received recovery. A possible credit should not make the callback disappear from the operating record.

Retain the original and revised views. The first shows what was known when the job closed; the second shows the cost after corrective work. Managers need that history to understand whether estimating, execution, or later product performance caused the margin change.

A job completed yesterday has had less time to generate a return visit than one completed three months ago. Group jobs by original completion period and report the observation window. A monthly callback percentage based on this month's visits divided by this month's new jobs can mix unrelated populations.

Look at both count and cost. Several minor adjustments can have a different consequence from one return requiring a full replacement and outside labor. Compare similar service types, equipment, and job complexity before drawing conclusions about an individual technician. Document exclusions such as planned follow-up visits so the comparison remains reproducible.

Review repeated causes with the service manager: part quality, missing diagnostic information, unclear scope, incomplete work, or a scheduling problem. Assign the action to the cause the records support. A blanket instruction to reduce callbacks may discourage accurate classification without improving the customer's outcome.

At month-end, check open callback jobs for unrecorded labor, pending supplier bills, parts taken from stock, and unresolved credits. If the business has material warranty or other future-service obligations, give the controller the observed history for a separate estimate review. Historical callback cost is useful evidence, but it is not by itself a complete policy for estimating future liabilities.