Callback: what it means
DefinitionA callback is a return visit to a customer to fix or finish something connected to work the business already did. It usually comes at the business's own expense, so counting callbacks reveals quality problems in training, parts or scheduling.
How it works in a service business
Callbacks are expensive twice: they consume a slot that could have earned money, and they hurt the customer's trust. Tracking them by technician, service and cause shows patterns. One tech may rush, one supplier's part may fail, or the booking notes may be too vague. The tradeoff is how to treat the customer fairly without being taken advantage of: a good-faith return for a real defect builds loyalty, while open-ended free work for unrelated issues drains profit. A common mistake is not recording callbacks as such, so they hide inside normal jobs. Mark them, link them to the original work order, and review the list monthly to find the root causes.
Example
A dryer vent cleaning leaves a loose clamp. The office books a no-charge callback, links it to the original work order, and notes the cause so the checklist now includes a clamp check.
Where Apex touches this
In progress
Part of this is built. The rest is not. Status as of 2026-10-07; the badge shows the least-built feature involved.
- SC33Split and merge jobs; visit-level vs job-level(In progress)
- SC25Job checklists / forms(In progress)
Apex Flow Scheduler is in early access. See how we label status.