Job updates: the customer cannot see the car, and needs it back

The customer who rings at eleven and again at two is not checking on your competence. They are trying to work out whether to arrange a lift home, whether to cancel the school run, and whether the thing they cannot see is going to cost £200 or £700. Every one of those is a real decision with a deadline, and none of it is answerable from where they are sitting.

That is what makes a garage different from most businesses that talk about status updates. The item being worked on is the customer's only transport, they have no visibility of it at all, and the longer the silence runs the more they fill it in themselves, usually badly.

What we'll cover

• What the chasing call is actually asking
• The stages worth a message
• Bad news early beats good news late
• The first message matters most
• Building it with CodeWords
• Collection is where the day goes wrong
• The customer with no alternative transport
• What an update should not contain
• When the update turns out to be wrong
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

What the chasing call is actually asking

Three questions, in a fixed order of importance, and the customer will usually only ask the third.

When can I have it back? Their day is built around the answer.

How much is this going to be? The second thing they think about and the last thing they raise.

Is it worse than we thought? The one they are actually afraid of.

Every chasing call is one of those three wearing a polite disguise. Which means a status message that says "work in progress" answers none of them and prevents nothing. The updates that stop calls are the ones carrying a time, a figure, or a plain statement that nothing has changed.

The stages worth a message

Fewer than most systems offer. A message per stage produces noise, and noise gets muted.

Arrived and logged. Confirms the car is with you and somebody knows it exists. Short and immediate.

Looked at, with a finding. The first moment you know something they do not. This is the highest-value message of the day.

Approved and under way, with a time. Only worth sending if it carries an expected completion.

Ready, with what happens now. Where, until when, how much, how to pay.

Anything that changes the time or the price. Which is not a stage, it is a rule, and it is the one that matters most.

Note what is missing. "We have started" carries nothing the customer can act on. A message that cannot change what somebody does is a notification, and each one makes the next one less likely to be read.

Bad news early beats good news late

This is the part garages get backwards, and it is worth stating plainly because it feels wrong.

A customer told at ten that the car will not be ready today can rearrange their afternoon, borrow a car, work from home. The same customer told at four has already wasted the day and now has an evening problem. The news is identical; the value of it collapses with every hour it is held.

Garages delay for a good reason, which is the hope that it will be fine and the message will not be needed. That hope costs the customer the option to do something about it.

So make delay a trigger in its own right. If the expected completion moves, the customer hears within the hour, with a new time and a plain reason. No apology theatre, no explanation of the parts supply chain. A time and a sentence.

The first message matters most

The message that does the most work is the one that goes out an hour or two after the vehicle arrives, saying what has been found so far and when you will know more.

It does three things at once. It confirms the car exists and is being dealt with, which removes the low-grade anxiety that generates most morning calls. It sets a next-contact time, which converts an open-ended wait into a defined one. And it gets the first real information in front of the customer while they can still act on it.

A workshop that sends nothing else but gets this one right removes most of its inbound calls, because the majority are asking "has anyone looked at it yet".

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: the stages that send, what each message carries, and the rule that any change to time or price sends immediately.
3. Authorize the connections to your garage management system, your diary, and your WhatsApp Business Platform account.
4. Describe the exceptions: a customer waiting on site, one who has asked to be phoned, a job on hold awaiting approval, a vehicle that cannot be released.
5. Run it on one bay for a fortnight and count the inbound calls before and after, which is the only measurement that tells you anything.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Collection is where the day goes wrong

The ready message is treated as the end of the process and it is the start of another one.

A customer who arrives after your last technician has gone, with no way to pay, to find the car blocked in, has had a bad experience regardless of how the repair went. Most of that is fixable in the message.

Say until when. "Ready for collection until 5.30 today, or any time tomorrow from 8" prevents the arrival at 5.45.

Say the figure. The amount due, including VAT, in the same message. A customer discovering the total at the desk is a customer having a conversation about it at the desk.

Say how to pay and whether they can do it before arriving.

Say what happens if they cannot come. Overnight storage, keys, security. A vehicle left because nobody said whether that was allowed is a problem for both sides.

The customer with no alternative transport

Worth designing for explicitly, because this customer behaves completely differently.

Somebody with a second car tolerates a day's slip. Somebody who needs the vehicle for work tomorrow morning does not, and they will ring every ninety minutes until they have certainty.

Ask at booking, record it against the job, and treat those jobs differently: earlier updates, a definite answer sooner, and a real conversation the moment a delay looks likely. The cost of that is a few minutes. The cost of not doing it is a customer stranded, which is the version of a bad day that gets written up publicly.

Where a courtesy car or a lift is part of the offer, say so unprompted rather than waiting to be asked, since most people will not ask.

What an update should not contain

Internal process language. Stage names from your management system mean nothing to the person reading them.

Explanations nobody requested. Why the part is late is your problem. The customer needs the new time.

Unqualified promises. "Ready by three" said hopefully becomes a lie at three.

A technical assessment nobody asked for. Findings that affect the price or the time, yes. A running commentary, no.

Anything that reads as automated. A message clearly generated by a system, with no name and no way to reply, produces the phone call it was meant to prevent.

When the update turns out to be wrong

It will, regularly, and how a workshop handles that determines whether the system earns any trust.

Correct it immediately and in the same channel. A customer told at eleven that it will be ready at three, and at two that it will not, has been dealt with properly. One who finds out at three has been let down twice.

Never let an automated message contradict something a person has just said. Any status update firing on a job where somebody had a conversation in the last hour should route to that person instead of sending. Two different answers from the same garage in the same afternoon does more damage than saying nothing.

Making it survive

Check the job state at send, since a stage that changed five minutes ago makes the message wrong.

Route replies to a person with an actual time bound, because an update inviting a response and receiving none is worse than no update.

Make delay a trigger, not an exception somebody remembers.

Suppress automated sends on any job with a live conversation.

Count the inbound calls. That number going down is the whole point, and it is the only honest measure.

Limits worth knowing about

Updates do not make the car ready sooner. They change how the wait feels and what the customer can do with it.

Some customers will ring anyway, and a few of those are worth ringing back.

A message cannot carry a difficult conversation. A vehicle that is uneconomic to repair needs a person.

Waiting on a third party is still waiting. A parts delay communicated well is still a parts delay.

More messages is not better. Past a handful per job they get muted, and then the important one is muted too.

What to build first

One message, sent an hour or two after arrival, saying what has been found so far and when you will know more. Nothing else. It removes more calls than the rest of the sequence put together, because most of those calls are asking whether anyone has looked at the car yet.

Two habits make the difference. Send bad news the moment you have it, since a customer who can still rearrange their day has been treated well and one who cannot has not. And put the figure and the collection window in the ready message, because the alternative is having that conversation at the desk at half past five.

Frequently asked questions

Why do customers keep ringing for updates?

They are asking when they can have the car back, what it will cost, and whether it is worse than expected. A status message that answers none of those prevents no calls.

Which stages are worth a message?

Arrival, the first real finding, work under way with an expected time, and ready with the figure and the collection window. Plus an immediate message any time the time or the price changes.

When should a delay be communicated?

As soon as it is likely, not when it is certain. A customer told in the morning can rearrange their day; the same news at four is worth almost nothing to them.

What is the single most useful message?

The one an hour or two after arrival saying what has been found and when you will know more. Most morning calls are asking whether anyone has looked at the car.

What should the ready message include?

The amount due including VAT, how to pay, until when it can be collected today, and what happens if they cannot make it.

How many updates is too many?

More than a handful per job. Once messages start getting muted, the important one is muted with them.

What should never be in an update?

Internal stage names, unrequested explanations, hopeful promises stated as facts, and anything that reads as generated with no way to reply.

What about customers with no other transport?

Ask at booking and flag the job. They need earlier updates and a definite answer sooner, and they are the ones who suffer most when a day slips quietly.

What happens if an automated update contradicts a phone call?

It damages trust more than silence would. Suppress automated sends on any job where somebody has spoken to the customer recently, and route the update to that person instead.

How do I know whether it is working?

Count inbound calls per job before and after. That number is the point of the exercise, and open rates on messages tell you nothing useful about it.

Related reading

• Estimates, approvals and authority
• What the garage diary actually sells
• Why customers stop coming back