Handling warranty comebacks at a car service without losing trust

Find the original visit before discussing responsibility

Find the original visit first so you can discuss what your shop actually diagnosed, repaired and charged for. When a customer says, “The same noise is back,” ask which car, when the visit happened and what they notice now. Avoid starting with either a promise of free repairs or a refusal. Assign one person to handle the conversation, retrieve the record and arrange the next assessment. This gives the customer a clear contact instead of making them repeat their story across reception and the workshop.

Every visit, its lines, mechanic and invoice stay on the car's page in Junto. Use that record to compare the customer's memory with the original complaint, the agreed scope and the individual labour and part lines. For example, a customer may remember a visit as “fixing the suspension” when the authorised job covered one identified component. Read the available notes before contacting the original mechanic. Ask what was confirmed at the time and what remained uncertain, rather than asking them to defend their work.

Record the return as a fresh assessment

Record the return separately while keeping the original visit available for comparison. Check-in records mileage, complaint and condition, which helps compare the two visits. Write the customer's current description in plain language, including when the symptom happens and whether anything has changed since collection. Use check-in photos and a signature to record the car's condition, not to imply that the customer accepts your diagnosis. Where a complaint involves braking, steering or another possible safety concern, ask the mechanic to assess whether the car should be moved or driven.

Try to reproduce the complaint under appropriate conditions rather than assuming the previous test still applies. A noise heard on mountain roads may not appear in a workshop yard; an intermittent running problem may behave differently in Tbilisi traffic. For an imported used car, ask about available history without treating missing records as proof of neglect. If the car has an LPG/CNG conversion, record which fuel mode is involved. These details guide diagnosis; they do not establish who is responsible for the fault.

Separate a repair failure from a different fault

Separate the returning problem into evidence of an original repair failure, a different fault or an unresolved diagnosis. Start with what the original work was meant to correct, then compare the current findings. A renewed coolant complaint after a hose replacement could involve the replaced connection or another leak elsewhere. The symptom alone cannot decide the outcome. Ask the mechanic to document the checks performed, what they found and why those findings connect, or do not connect, to the earlier repair.

Use a second technical review when the connection remains uncertain, especially if the original mechanic feels personally challenged. Keep observations separate from conclusions: “moisture at the repaired connection” is more useful than “customer caused it” or “bad part.” Do not replace additional parts simply to make the comeback disappear. If a measurement, fluid requirement or tightening specification matters, check the owner's manual or ask the shop's responsible technician to verify it against appropriate service information. Explain uncertainty honestly and propose the next diagnostic step.

Explain the decision and agree on the next step

Explain your findings before proceeding, then agree on the work and any charges with the customer. Warranty terms are each shop's own policy; do not state legal warranty obligations. Keep that distinction clear when training reception staff and writing customer messages. Base your explanation on the documented scope, the evidence from the return and your shop's policy. If the earlier repair needs correction, say what you will correct. If you found a separate problem, show why it is separate without dismissing the customer's frustration.

Give the customer a short account of what happened, what you found and what you propose now. For example: “We checked the connection repaired on your last visit. It is dry, and the current leak is elsewhere. We would like your approval before proceeding with that repair.” In Junto, you can send suggested extra work through an SMS approval link so the customer sees each line and its price before work starts. Record their decision, including any declined work, and keep goodwill assistance distinct from your technical conclusion.

Use a short comeback checklist before closing the job

Use the same short checklist for every comeback so the result does not depend on who is at reception. A shared sequence is particularly useful when a different mechanic handles the return or another branch receives the car. The checklist should confirm that you found the original record, investigated the current complaint and agreed on the next action. It should not become a substitute for diagnosis or a form that staff complete after the customer has already left.

Before handover, compare the repair outcome with the complaint that brought the customer back. Tell them what was checked and any limits to the assessment, particularly if an intermittent symptom could not be reproduced. Do not promise that every possible noise or warning has been eliminated. Arrange a clear route back to the named contact if the complaint returns. When you close the visit, keep the findings, work lines and invoice understandable enough for another staff member to reconstruct the decision later.

• Retrieve the original complaint, work lines, mechanic and invoice.
• Record the return complaint, mileage and condition.
• Document checks linking or separating the two faults.
• Explain the proposed action and obtain approval.
• Check the outcome and confirm the customer's next contact.

Follow up and learn without blaming the team

Follow up after the comeback and review the cause without turning the discussion into a search for someone to blame. Ask whether the original complaint is resolved and whether the explanation made sense. Low ratings are flagged so the owner can call the customer. Use that opportunity to listen and clarify the next step, not to argue about the rating. A calm call can reveal that the repair is satisfactory but the customer still feels ignored because nobody explained a delay.

Look for preventable process mistakes across your comeback records: vague complaint notes, broad promises, missing approval or an incomplete final check. Review specific examples with the team and agree on one practical change. A mechanic may need better diagnostic notes, while reception may need a clearer way to describe limited repair scope. Do not assume every return represents poor workmanship, and do not hide genuine errors behind policy wording. Your aim is a fair decision that another person can understand from the record.

Questions and answers