For the customer, car repair status updates come down to two questions: when can I collect the car, and what will it cost? If the workshop does not answer them first, the customer calls and a mechanic stops work to check the job card. You need no portal or workshop software link: a few named stages, one person who sends updates and a clear rule for when the next message arrives.
This guide covers the time between handing over the keys and collecting the car: what to say at each stage, how to get approval for extra work and how to announce a delay. Seasonal tyre-change bookings are a separate topic, covered in the guide to tyre service bookings. All workshop examples are fictional.
Customers call because they do not know what is happening
The question "is my car ready yet?" is rarely about the repair itself. To plan their day, the customer needs two facts: the current stage and when they will hear more. Knowing both, they usually wait. Knowing neither, they call every few hours, interrupting someone in the workshop each time.
In a 2016 Ipsos and DEKRA survey of 1,000 new-car buyers in Germany, 18% could check their order status online and 44% wanted it but were not offered it. These are old figures from one market: they say nothing about how many calls a workshop receives today.
The lesson for a small workshop is simple: information should arrive before the question. You need not write every hour, but you must keep your promise about the next update, even without news. Moving non-urgent calls to other channels is covered in the guide to missed calls from customers.
Five stages a customer understands without a glossary
Your internal job card may have twenty fields, but the customer needs five. Each stage answers what is happening now and who the next step depends on. Keep the names identical in every message so nobody wonders whether "in progress" and "being diagnosed" differ.
Scroll the table sideways to see all columns.
| Stage | What you tell the customer | Who writes and when |
|---|---|---|
| Checked in | Job number, reported fault, time of the first update | Service advisor, at key handover |
| Diagnosis | What is being checked and when the result is due | Service advisor, at the promised time, even without a result |
| Awaiting approval | Fault, photo, price including labour, effect on the date | Service advisor, right after the mechanic decides |
| Awaiting parts | Which part, expected delivery, new date | Service advisor, once the supplier confirms |
| Ready for collection | Amount, collection hours, what was replaced | Service advisor, after the test drive or final check |
The same person writes in every row. The mechanic reports to the service advisor, not the customer, so nobody answers the phone from under a lift. At the fictional "Linden Motors" this is the front desk; in a one-person business, the owner during two fixed breaks.
At check-in, agree the channel and the time of the next update
Most calls can be prevented at key handover. A customer who hears "we will message you by 2 pm with the diagnosis" has a reason to wait. Also note how they want updates and who may approve extra costs, especially for company cars.
- Phone number and preferred channel: written message or callback
- Person authorised to approve extra work, with contact details
- Time of the first update, even if diagnosis takes longer
- A rule that any work outside the order needs separate approval
- Job number the customer quotes whenever they get in touch
- Collection hours, so the car is not ready after closing time
If the customer does not answer the approval question, the car waits and the date slips. Say so clearly at check-in and repeat it in the quote message. How to manage a case where the next move belongs to the customer is covered in the guide to waiting for a customer reply.
Extra work: a photo, a price and written approval
The approval stage is where a workshop most easily loses trust. The customer hears about "play in the control arm" by phone, cannot see the fault and does not know whether the car is safe without the repair. Send a short message with a photo, the price including labour and the effect on the date. The yes or no is then stored next to the photo.
Job [number]: while replacing the brake pads we found a cracked front left driveshaft joint (photo attached). The repair costs [amount] including labour and VAT, and collection moves to [day, time]. Without this repair the car will be ready today by [time]. Please reply "yes" or "no"; we will not carry out this work without your answer.
In Poland, Article 630(2) of the Civil Code (consolidated text, Journal of Laws 2026, item 795) states that, under a cost-estimate fee, the contractor cannot claim a higher fee for additional work done without the client's consent. It sets no form for that consent, and not every repair is billed against a cost estimate.
In Germany, Section 649 BGB requires the contractor to notify the customer without delay when a substantial overrun of a cost estimate is expected. It sets no threshold for "substantial" and no form for the notice.
This guide is not legal advice, and rules differ in other countries. Approval in a message is a record that is easy to find if the amount is disputed. Prepare the photo as described in the guide to customer support attachments: one clear shot of the fault and a short description, without personal belongings from inside the car.
Delays: a new date before the customer asks
Parts did not arrive, diagnosis found a second fault or a mechanic is off sick. Customers accept a delay more calmly when they hear about it before the promised time. A delay message has three parts: the cause in one sentence, the new date, and the time of the next update if that date is uncertain too.
Job [number]: collection moves to [day, time]. The supplier did not ship the water pump we ordered today. We will message you by 10 am tomorrow to confirm whether delivery is booked. If you need the car sooner, please reply and we will check whether it can safely be released without this repair.
Avoid "we will do our best to finish as soon as possible". It gives nothing to plan around and usually triggers a call the next day. If you do not know the new date, at least give the time when you will know it, and keep to it.
Written updates and callbacks in fixed windows
The phone stays, but it can stop interrupting work. A written message waits until the advisor is free, and a callback request with a chosen time turns a random call into a planned conversation. The guide to website callbacks explains how that works.
- Two update windows.At 11 am and 3 pm, for example, the advisor collects findings and messages every customer whose car changed stage.
- Questions in one place.Messages and contact requests land in one case list, not on the mechanics' personal phones.
- Callbacks in a planned break.A customer who prefers to talk picks a time, and you call with the job card in front of you.
- Check before closing.Make sure every car in an "awaiting" stage has a recorded time for the next update.
In Meetlead customer support, a case from live chat, the offline form or a callback request gets a reference number. A customer who returns to your website in the same browser sees their cases in the chat window, with status (open, resolved, closed), the latest message and any scheduled call. You can mark a case as waiting for the customer, and their reply reopens it. You can attach a photo to a reply, and the mobile app notifies your team of new messages and contact requests. You describe the repair stage in the message text: Meetlead does not send text messages and does not connect to workshop software.
Questions about updating customers during a repair
Should I send an update when nothing has changed? Yes, if you promised one for that time. A line such as "diagnosis still running, result by 4 pm" prevents a call. Do not send messages without a prior promise, though, or customers stop reading them.
What if the customer prefers to talk rather than write? Respect that, but book the call for a specific time instead of answering mid-job. Still confirm approval for extra work in a short message with the photo and the amount, so both sides share the same record at collection.
