Thursday morning, a customer's car drives into the service — the same car that was already here ten days ago. The service advisor barely has time to look up when the customer delivers the line no one wants to hear: "You did the same thing last time, and here we are again." The manager standing nearby knows immediately that the next hour will not be about technical work. It will be about trust and money.
When a car comes back with the same problem, it is rarely just "another job." Behind it sits a chain of decisions — from how the initial complaint was written down, to how the mechanic approached it, to how the car was handed back to the owner. In most cases it is not one person's mistake. It is the sum of several small, uncontrolled details that only become visible when it is already too late.
What a repeat visit actually costs
A returning car does more damage than a single invoice shows.
First, it is unpaid work: the mechanic takes the same assembly apart again, but no one pays for those hours. Second, a workstation is lost — that same lift could have been earning money with another customer. Third, there is the emotional bill: a customer who leaves disappointed usually doesn't just walk away — they share the story with friends, colleagues and in Google reviews.
Why cars come back with the same issue
The reasons tend to repeat, even though every manager thinks "our case was unique."
A vague write-up of the initial complaint. When the service advisor notes "strange noise while driving," every mechanic interprets it differently and starts checking in their own direction. Part of the day goes the wrong way.
A shallow initial inspection and defect assessment. This is probably the most important stage, and the easiest one to cut short when three more cars are waiting. When 15 minutes are spent on a defect assessment and diagnostic that needed an hour, the mechanic only sees what's obvious at first glance. The real cause — for example, an adjacent worn component that keeps reproducing the symptom — is never captured. Only the part closest to the symptom is replaced, and a week later the customer is back with the same story. A proper defect assessment means not just identifying the main issue, but also looking at related systems and logging everything, including what the customer has "left for next time."
An incomplete handover of work history. The next-shift mechanic does not see what has already been checked or replaced and starts making intuitive choices — often doing the same work twice.
Rushed decisions before releasing the car. When another customer is already waiting at the counter, the final test drive becomes superficial. That is exactly where the thing the customer will notice that same evening slips through.
Missing customer history. A long-standing client arrives to a new service advisor who does not see what was done six months ago and has no context to make the right call.
Choosing parts by price, not by fit. Saving €20 today sometimes means paying for it two weeks later with a free repair and a lost customer.
The first five minutes when a customer comes back to complain
When the customer stands at the counter and talks about a repeat visit, everything depends on how fast the service advisor can show what has already been done.
If the answer is "I'll have to find out who worked on it," and the advisor starts juggling paper folders and phone calls to colleagues, the customer has already drawn the conclusion that the service does not track its own work. If, within five seconds, the advisor opens the car's file — which mechanic worked on it, which parts were replaced, when it was tested, what the original estimate was — the conversation moves onto a different plane.
This is not just about software tools. It is about whether your service has a memory, or whether that memory depends on who happens to be working that day.
Signs that your process is already slipping
Before a repeat visit, there are almost always signals that are easy to ignore — until that customer comes in with "the same story again":
A mechanic asks, "what did we do on this one last week?" and no one can answer within a minute.
The service advisor asks the customer to wait while he phones a colleague.
The parts keeper orders a component that another employee already ordered three days earlier.
The manager asks how many customers came back with the same issue this month, and the answer is "feels like a lot."
All of these signs point to the same thing: information is scattered across several places and people's heads, but not on a single screen.
What you can do this week
First — capture the customer's initial complaint as precisely as possible. Not "strange noise," but "noise appears above 60 km/h, in left turns, only on wet road." The more precise the intake, the less the mechanic has to guess.
Second — before handing the car back, record at least a short quality-check note: what was checked, what was test-driven, under which conditions. This isn't paperwork for its own sake — it's protection against the conversation a week later.
Third — set aside 20 minutes every week to review how many customers came back with the same complaint and what the causes were. Not to find a guilty mechanic, but to see the pattern in your processes that you otherwise won't notice.
This is exactly where we most often look for solutions together with our clients — with ARTWIN we try to make sure the service advisor doesn't have to call a colleague or flip through a notebook when a customer returns and asks about the last visit. The full history of the car — from the first estimate to the completed work and the replaced parts — is visible on one screen, not across three apps and two chat threads. It isn't magic. It's just fewer small annoyances every day, and more time for the conversation with the customer that determines whether they'll come back.
A repeat visit isn't bad in itself
If the service can explain to the customer what happened and show a clear plan, most of the time the customer stays. The problem starts when the service itself has no clear answer about its own work. And in that regard, a clean process will always be stronger than good intentions.
