Customer communication for independent garages: the approval bottleneck
Customer communication for independent garages: fix the approval bottleneck first, then add reminders and collection messages.
Osman RamadanUpdated 11 min read
On this page
- What we'll cover
- Key takeaways
- The approval bottleneck
- Making approvals fast
- MOT and service reminders
- Booking, drop-off and collection
- Parts and the delays you cannot control
- The questions worth answering automatically
- What to leave to a person
- What this looks like on a Tuesday
- Frequently asked questions
- Related reading
The best customer communication tool for an independent garage is one that automates three messages: the repair approval request, the MOT and service reminder, and the ready-for-collection notice. Start with the approval request. The work stops until a customer answers the phone, and that delay costs more than any other communication gap in a workshop.
A car is on the ramp, the technician has found something that needs doing, and nothing further can happen until somebody reaches the owner and gets a yes. That customer is at work or in a meeting. Meanwhile the ramp is occupied and the afternoon's schedule is slipping.
What we'll cover
Key takeaways
- The approval request is the first message to automate, because a stalled approval occupies a ramp and delays every job after it.
- Send approvals in writing with a photograph, an itemised cost and a one-tap approve or decline.
- Escalate an unanswered approval to a phone call from a person after a set time.
- Time MOT reminders at a month, a fortnight and a few days before expiry, include the registration, and stop them when the customer books.
- Leave safety questions, complaints and large unexpected costs to a person.
The approval bottleneck
The approval bottleneck costs more than it appears. A delayed approval does not cost you the twenty minutes spent ringing. It costs the ramp time, the technician's time, the job that could have been on that ramp, and the customer's confidence, because a call saying "we found something, it will be another two hundred pounds" lands badly when it is a voice on the phone with no detail attached.
The cascade is the real damage. One job overrunning pushes the next, which pushes the one after. A garage running four ramps with two stalled approvals has lost most of an afternoon's capacity, and nothing about that appears in any report.
Why phone calls fail here specifically: the customer is at work during exactly the hours you are trying to reach them, the decision involves money so they want to think, and there is nothing to look at while they decide.
Making approvals fast
Automated approvals are the highest-value automation available to a workshop, and a good approval message has five parts.
Send it in writing, with pictures. A photograph of the worn part, a line on what it means, the cost, and what happens if it is left. A customer looking at a photograph of their own brake discs approves far faster than one hearing a description down the phone, and they feel better about it afterwards.
Make approving one tap. Not a call back, not an email reply. Approve, decline, or ask a question, from the message.
Itemise so they can approve part of it. Customers often want the urgent item and not the advisory one. Offering that choice avoids an all-or-nothing figure, and it removes the conversation where somebody feels pressured.
Escalate to a call after a set time. An automated message that goes unanswered for forty minutes should become a phone call from a person, not a second message. This is the pattern that works: messaging for speed, a person for the ones that need one.
Record the approval. The message trail is your record that the customer agreed to the work and the price, which is worth having when somebody queries an invoice three weeks later.
The whole flow (photograph, itemised cost, approve or decline, escalate on silence, record the outcome) is simple to describe and tedious to assemble from parts. On CodeWords you describe it in plain language, including what should happen when nobody replies, and Cody, the automation builder, builds it, connects it to your workshop system and messaging, and deploys it. Automations connect to 3,000+ integrations (CodeWords, 2026). The Free plan ($0) covers light use, with Pro at $39 per month and Business at $100 per month as usage grows (CodeWords pricing page, 2026); details are on the pricing page.
MOT and service reminders
MOT and service reminders are the better-known process, and the details decide how well they work.
Time it properly. A month before expiry, then a fortnight, then a few days. Too early and they forget; too late and they have booked elsewhere. The first message is the one that matters most, because whoever reaches a customer first usually gets the booking.
Include the registration. A generic reminder is ignored; one naming their vehicle is read. It also prevents the confusion in households with two cars.
Make booking possible from the message. The same principle as approvals. A reminder telling somebody to ring during working hours is a reminder competing with their job.
Combine service and MOT where the dates are close. Customers appreciate one visit rather than two, and it fills a longer slot.
Stop when they book. The most common complaint about garage reminders is a message arriving after the booking was made.
Keep the list current. Vehicles sold, customers moved on, cars written off. A reminder about a vehicle somebody no longer owns is a small embarrassment and easily avoided by acting on the replies.
Booking, drop-off and collection
Booking, drop-off and collection messages cover the everyday communication around the visit itself.
Confirm the booking with everything they need. Date, time, what to bring, where to park, whether a courtesy car is arranged, how long you expect to have the vehicle.
Remind the day before. Garages have no-shows like anybody else, and a slot lost on the day is difficult to refill.
Tell them when it is ready. This is the one customers most notice being handled badly. A car finished at two and a customer told at five is three hours of somebody wondering, and it is the most common cause of a poor review in this trade.
Send the invoice ahead of collection. They arrive knowing the figure and frequently having already paid, which removes the queue at the desk and the awkward conversation.
Ask for the review after collection, not before. And suppress it entirely for any job that went wrong, which is one condition and prevents the worst possible timing.
Parts and the delays you cannot control
Parts delays generate the most customer frustration and the least communication.
A part is on back order, the supplier says Thursday, Thursday comes and goes. In most workshops the customer finds out by ringing to ask.
Tell them when the delay happens, not when they ask. A message saying the part is delayed, with a new expected date and what you are doing, converts a complaint into an inconvenience.
Update when it changes again. Delays extend. A customer told once and then left is a customer who assumes you have forgotten.
Flag the vehicle internally. A car waiting on parts occupies space and can be forgotten. A check that lists vehicles on site for more than a set number of days catches the one that has slipped.
Offer the choice. If the delay is long, some customers would rather take the car and rebook. Asking is better received than deciding for them.
The questions worth answering automatically
A garage fields the same questions continuously, and each one interrupts somebody.
Is my car ready? The most common, and entirely answerable from the workshop system.
How much will an MOT cost? Fixed information.
Do you do diagnostics on my make? A yes or no you can encode.
Can I drop off early or collect after hours? Policy questions with fixed answers.
What is included in a service? Fixed, and frequently asked because customers are comparing.
Answering these automatically removes a share of the interruptions to whoever is on the desk. Keep two boundaries firm: anything involving a diagnosis or a safety judgement goes to a person, and anything where the answer depends on looking at the vehicle should say so rather than guessing.
What to leave to a person
Anything about safety. A customer asking whether a car is safe to drive needs a technician, immediately.
Bad news about cost. A large unexpected bill is a conversation. The written approval flow works well for a couple of hundred pounds and badly for a figure that changes somebody's month.
Complaints. Route straight to a person, with no automated acknowledgement that could read as dismissive.
Anything after a job that went wrong. Suppress the automated check-ins and reviews for those, and have somebody call.
The first conversation with a nervous customer. Some people are uneasy about garages for good historical reasons. Those relationships are built by a person explaining things, and automation should support that rather than replace it.
What this looks like on a Tuesday
This example day shows the cost of the approval bottleneck.
Eight fifteen. Four cars in, four ramps occupied. Two are routine services, one is an MOT, one is a diagnostic job.
Nine forty. The technician on ramp two finds worn discs and pads. Under the old arrangement, the desk rings the customer, gets voicemail, leaves a message, and moves on. The car stays on the ramp because nobody wants to move it twice.
Automated instead: a photograph of the discs, a line explaining what it means, the itemised cost with the advisory item separated, and approve or decline. The customer sees it between meetings at ten past ten and approves the discs while declining the advisory wiper blades.
Ten fifteen. Work resumes. Ramp two is free by midday rather than by three.
The afternoon that follows is the actual saving. The 2pm booking starts at 2pm. The technician does not spend forty minutes waiting. The customer who would have been told at five that their car was ready is told at one.
The sequence needs only a photograph, a price, a button and a rule about what happens after forty minutes of silence. The value comes from the message going out at nine forty rather than whenever somebody has a moment to ring.
Frequently asked questions
What should a garage automate first?
Automate the approval flow first. A stalled approval occupies a ramp and delays the rest of the day's schedule, so it carries the largest hidden cost. A photograph with an itemised cost also gets a faster answer than a phone call.
Do customers actually respond to messages faster than calls?
Yes, customers answer messages faster than calls, because a message can be answered from a meeting and a call cannot. The pattern that works best is a message first for speed, then a phone call as the escalation after a set time.
Is WhatsApp suitable for a garage?
Yes, WhatsApp suits garages, especially for approvals, because photographs are central and customers read it. Confirm consent for the channel, and keep a record of approvals where your invoicing can reach it, not only in the conversation.
Will this replace the person on the desk?
No, automation will not replace the person on the desk. It removes the repetitive work of chasing approvals, sending reminders and answering the same five questions. It leaves the part customers value: somebody who can explain what is wrong with their car.
How do we handle customers who do not use messaging?
Record the preference and keep calling those customers. An automation can prepare the call list, with the photographs and itemised cost ready for whoever makes the call. This keeps the process consistent without forcing a channel on anyone.
What about the workshop management system we already use?
Check your workshop management system first, because some include reminders and approvals. Where it does not integrate directly, a scheduled export is enough for reminders, the easiest of these messages to run alongside an existing system.
How do we measure whether it worked?
Track the average time from finding extra work to getting approval, and the share of MOT reminders that convert to bookings. Both are measurable, and both were invisible before automation.