The same car, back again on Tuesday
The customer is back. The warning light you cleared last week is on again. Or the noise from the front suspension is still there. Or there is a small oil leak that was not there before the service. The advisor apologises, books it in, and the technician fixes it. No invoice goes out, because it was your problem.
Nobody writes it down. The job is not quite a new job and not quite part of the old one. A month later, another comeback, a different car, a different technician. Is there a pattern? Maybe the same brand of parts keeps failing. Maybe one type of job is being rushed on Friday afternoons. Nobody can say.
Why comebacks stay invisible
Most garage management systems are built around jobs and invoices. A comeback is a job with no invoice, so it either gets a zero-value invoice with a vague description, a note on the original job, or no record at all.
There is also an understandable reluctance. A comeback feels like a mistake, and nobody wants to record their mistakes. So the information that would help most, what went wrong and why, is the information least likely to be written down.
What comebacks really cost
| Cause | What it costs if nobody tracks it |
|---|---|
| Faulty part from a supplier | Repeated free labour, and no warranty claim to the supplier |
| Misdiagnosis | The same fault returns, with the customer's trust |
| Something disturbed in the work | Awkward conversations, sometimes a claim |
| Rushed job at end of day | Workshop time lost to rework |
| Customer expectation not met | A bad review from a car that was actually fixed |
The labour on a comeback is unpaid, it takes a ramp away from paid work, and the damage to the customer's view of the garage is harder to see and slower to repair.
How we build a comeback record that people will fill in
- When a customer returns about recent work, the advisor finds the original job and taps "comeback" to open a linked job, so the two are joined.
- The technician who fixes it picks a cause from a short list: part failure, diagnosis, workmanship, not related, customer expectation. There is space for a short note.
- If the cause is a part failure, the part, supplier and batch are recorded, and a supplier warranty claim can be started from the same screen.
- Time spent on the comeback is recorded even though it is not invoiced, so the real cost is visible.
- A monthly view shows comebacks by cause, job type, make, part brand, supplier and technician.
- Patterns above a level you choose are flagged, such as several comebacks on the same part number from the same supplier.
We keep the language neutral. The aim is to find the cause, not to build a list of blame, and we help you set that tone with the team.
What you learn from a few months of data
Patterns that were only suspicions become clear. One brand of brake pad keeps producing noise complaints. A particular diagnostic job on one engine type has a high return rate, which suggests a training need or better equipment. Most comebacks turn out to be unrelated faults, which is useful to know when speaking to customers.
Supplier warranty claims start to be made, because the part and batch are recorded at the time.
- Every comeback linked to the original job
- Causes recorded with a short, neutral list
- Unpaid time made visible
- Supplier part failures claimed back
Are comebacks being fixed and forgotten?
- Comebacks are fixed at no charge and never recorded.
- You suspect a parts brand is causing problems but cannot prove it.
- Supplier warranty claims on failed parts are rarely made.
- The same customer complaint recurs on the same kind of job.
- You could not say how many comebacks you had last month.