Reducing callbacks

A callback is a return visit to put right work already carried out. The labor, parts and travel are spent again and invoiced to nobody, so the cost comes straight out of job margin.

Diagnosis

The most common cause is treating a symptom rather than finding the fault. The visit succeeds, the complaint returns, and the second visit finds what the first did not.

This shows up as repeat visits to the same address for the same issue, which is what multi-visit rate surfaces when read by job type.

Parts

A job completed with what was on the van rather than what the work required. It closes the visit and creates the next one.

The fix is stock levels on the common failures for the trade, set from history rather than from judgment.

Expectations

A return visit where nothing was wrong with the work is a communication failure rather than a technical one: the customer expected something that was never within scope.

These are prevented at the estimate, by stating what is included and what is not — see estimate versus quote.

Measuring it honestly

Callbacks are under-recorded, because they are frequently handled informally by the technician who did the original work and never appear as a job.

A rate that looks excellent is more often a recording problem than a quality one. Counting them requires them to be booked like any other visit, flagged as a return.

What it costs

Worth calculating once. Callback visits multiplied by the average cost of a visit gives an annual figure that is usually larger than expected, and it is the number that justifies spending on the causes.

Checking work against a standard before the customer sees it is the preventive side of the same problem — see quality control.

What the vehicle carries, and how that decides whether a job finishes on the first visit, is van stock.

Last reviewed 2026-07-30

Reducing callbacks — Omnyra Wiki | Omnyra