"That was fine last year"
A customer comes back the day after a failure, angry. The corrosion that failed their car was not there last year, they say, and another garage told them it was fine. They want the result changed, or a free retest, or their money back.
The tester remembers the car, roughly. There are no photos. The manager was not there. What was the customer told about how to appeal? Nobody wrote it down. The conversation becomes one person's word against another's, and it can go on for days.
Why disputes are hard to handle
Disputes are rare enough that no routine exists for them, and emotional enough that they get handled on the spot. The evidence that would help most, photos and notes from the test, is often not captured, because at the time the test seemed routine.
There are formal routes a customer can take if they disagree with a result, and the centre should explain them clearly and consistently. When staff explain them differently, or not at all, the dispute gets harder.
Separately, the centre wants to learn from disputes. Are they clustered around one tester, one type of item, one kind of customer? Without a log, nobody can say.
What an unrecorded dispute costs
| Gap | Consequence |
|---|---|
| No photos from the test | Nothing to show the customer |
| No notes of conversations | Differing memories of what was said |
| Options explained differently | Customer feels misled |
| No manager involvement recorded | Unclear who decided what |
| No log of disputes over time | Patterns missed |
A dispute handled badly can end in a bad review, a formal complaint or a lost customer, even when the result was entirely right.
Staff feel it too. A tester who is confident in a result but has nothing to show the customer ends up defending themselves from memory, often in front of other customers. A clear record protects the tester as much as the centre, and takes the heat out of the conversation.
How we build a dispute log
- Testers can take photos of failure items during the test on a tablet, which are stored against the vehicle and date. You decide when photos are taken.
- When a customer disputes a result, the desk opens a dispute record for that test with a tap.
- Every conversation is logged with the date, who spoke to the customer, and what was said, briefly.
- The record includes a standard explanation of the customer's options, written and approved by you, so every customer is told the same thing, and a note that it was given.
- The manager's review and decision are recorded, along with any outcome, such as a retest arrangement.
- A summary of disputes shows patterns by tester, item type and outcome, for the manager's own quality reviews.
We do not advise on whether a result was correct or on the formal appeal routes. The log records what happened and what the customer was told, so your centre handles disputes the same way every time.
The same complaint, handled calmly
The customer comes back the next day. The desk opens the dispute record and shows the photos of the corrosion taken during the test. The standard explanation of the customer's options is given and noted. The manager reviews the record, speaks to the customer, and records the outcome.
The customer may still disagree, and that is their right. But the conversation is based on evidence, and if it goes further, the record is complete.
- Photos from the test to refer to
- Every conversation logged
- The same explanation of options for everyone
- Patterns in disputes visible to the manager
Over months, the dispute summary gives the manager something useful for quality reviews. If most disputes involve one kind of item, the explanation given to customers on the day of the test may need to be clearer, which is a simple change that heads off future arguments.
Would a dispute catch you unprepared?
- There are rarely photos of failure items.
- Conversations with unhappy customers are not written down.
- Staff explain the customer's options differently.
- You could not show how past disputes were handled.
- You do not know whether disputes cluster around certain items.