Scheduling & dispatchalso called re-service

Callback

A callback is a return visit because the first one did not solve the problem. The customer is not charged, the technician still drives and works, and the slot it occupies was capacity that could have served somebody else. It is the clearest example of a cost created upstream.

Callbacks are usually discussed as a quality number. They are also, quietly, a capacity number.

Why it matters

Every callback consumes a full appointment: drive in, work, drive out. At eight percent of visits, roughly one in twelve of your appointment slots is producing no revenue at all — and the business is still paying for it in full.

The second cost is trust. A customer who needed a second visit judges the service differently from one who did not, even when the second visit solves it.

How you notice it slipping

The rate is tracked for the company but not by service type, technician or season, so the pattern inside it is invisible. Callbacks are blamed on individuals when they cluster by job type. Nobody records the reason in a form that can be counted.

What to do

Break the rate down before acting on it. Callbacks concentrated in one service type point at a duration or a method problem. Callbacks concentrated in one season point at expectation setting. Callbacks spread evenly point at something systemic — usually visits that are scheduled shorter than the work actually takes.

Related terms

Where this shows up