Why customers call, and how to stop it

Every shop has an afternoon shaped by the same interruption: customers calling to ask where their car is. It reads like a customer-service problem. It is a communication-design problem, and it is largely self-inflicted.

The call is caused by silence

Nearly all of these calls come from people who have been told nothing since they dropped the car off.

They are not angry. They have a day to plan and a missing car, and the only way to find out anything is to call the one number they have. The call is a reasonable response to an information vacuum.

Which means the volume of status calls is roughly proportional to how long customers go without hearing anything. That is a variable you control.

Why "we'll call you when it's ready" fails

The standard promise sounds fine and fails for a specific reason: it is one message at the end of an unknown wait.

A customer who drops a car on Monday and is told they will hear when it is ready has no idea whether that means Tuesday or Friday. So they call on Tuesday to find out — not because the promise was broken, but because it did not contain the information they needed.

One message at the start with a realistic timeframe removes most of that. Not a guarantee, a horizon: this is a two to three day job, you will hear from us when it moves to paint.

Make the update a side effect of the work

The reason updates do not get sent is not that anyone objects. It is that sending them is a separate task, and separate tasks lose to actual work every time — especially on the busy days, which are exactly the days customers most want to hear something.

The fix is to stop making it a task. If work moves through stages, and a card moves when the work moves, then the card movement is a signal that already exists. Attach a message to the stages worth reporting and the update goes out because the work happened, not because somebody remembered.

Three or four stages is usually right. Arrival confirmed, work started, ready for pickup, and one in the middle that matters for that trade. A message on all twelve columns is not communication, it is noise, and customers stop reading it — which is worse than silence because now they will not read the one that matters.

Approved once, sent many times

The obvious worry about automated messages is tone. A shop's relationship with its customers is personal, and nobody wants a vendor writing to their customers in a voice that is not theirs.

That is an argument for templates written and approved once by the shop, with the job's details filled in — not for composing each message by hand, and definitely not for a system that generates text on the fly.

It should also send from the shop's own address, so a reply lands in an inbox the shop already reads and the customer is talking to the business they gave their car to.

What you get back

The measurable result is fewer inbound calls. The bigger result is what an advisor does with the recovered time, which is usually the work that actually moves cars: chasing parts, following up on unanswered approvals, and calling the customers who genuinely need a conversation rather than a status.

There is also a second-order effect worth naming. A shop that reports progress on a schedule looks like a shop that is in control of its work — and for the customer deciding whether to come back, that impression is formed almost entirely by how often they had to wonder.