Service reminders for auto repair shops

The constraint that shapes an auto repair shop is that capacity is bays, demand is unannounced, and a bay produces nothing while it waits. The whole opportunity in automation here is to put predictable work into the gaps that unpredictable work leaves.

Most shops are sitting on more of that predictable work than they realise.

The deferred list is the asset

A technician inspects a vehicle and recommends three things. The customer approves one and declines two, usually for reasons of timing rather than disagreement. The declined items are written on a ticket, the ticket is filed, and nobody ever looks at it again.

Those declined recommendations are a list of known jobs, on known vehicles, belonging to customers who have already been to the shop and already trust the diagnosis. There is no comparable list available through any amount of advertising, and in most shops it is entirely dormant.

Working it requires two things: that the recommendations were recorded in a form that can be searched, and that somebody sends a note at a sensible interval. The first is a records problem covered on the auto shop hub; the second is what automation is for.

Timing on the repair’s own logic

The temptation is to pick an interval and send everything on it. That produces messages that arrive for the shop’s reasons rather than the vehicle’s, and customers can tell.

A brake recommendation and a suspension component have different horizons. A fluid service has a mileage logic. A tyre recommendation depends on how much tread was left when it was measured. Sending each on its own reasoning is what makes the message read as a shop that was paying attention, rather than as a mailing.

This is the same principle as the HVAC reminder page: specificity is the mechanism, and generic timing removes it.

Aim at the quiet days

A shop generally knows which days are thin. Early in the week, certain weeks of the month, the stretch after a holiday.

Because these messages concern work that is not urgent, they can be aimed. Inviting deferred work into a slow Tuesday is straightforwardly better than having it arrive on a Friday when there is no bay for it, and it costs nothing to choose the day.

That is the whole scheduling benefit, and it is more valuable than it sounds in a business where an idle bay is the only real waste.

Stop signals matter more here than elsewhere

Vehicles change hands. A customer who sold the car and keeps receiving notes about its brakes learns immediately that nobody is reading these messages before they go out, and that impression contaminates the ones that were accurate.

The same applies to a repair that was subsequently done elsewhere, and to a customer who has said they are not interested. Two reminders about a declined recommendation is attentive. Five is a shop that is not listening.

Building in the stop conditions is unglamorous and it is what separates a programme that compounds from one that burns the list down over a year.

Reviews, on the same rails

The other automation worth running in a shop is the review request, and it works for the same reason: it arrives after a real event, for a real reason, addressed to one person.

One link, sent after every finished job, to everybody, without pressure. A steady accumulation across a year reads as a real shop. A cluster of five in one week reads as arranged, and customers reading reviews notice the pattern more than most businesses assume.

What has to be true first

The ticket history needs to be searchable. A shop whose recommendations exist only on paper tickets in a filing cabinet cannot run any of this, and the honest first step is getting that history into a form a query can reach.

What a good reminder looks like from the customer’s side

It names the vehicle. It names the repair that was recommended, and roughly when. It says why it is being raised now. It offers a way to book that does not require a phone call during working hours, because the customer is at work during working hours too.

And it stops after two. A recommendation raised twice is attentive; raised five times it is a shop that is not listening, and the customer generalises from that to how the shop handles everything else.

Multi-location shops

A shop with two locations has a configuration question that single-site shops do not: which location does a reminder invite the customer to.

The answer is wherever they went last, unless they have asked otherwise. Inviting a customer to the shop across town because it had more capacity that week is a small discourtesy that does real damage, and it is entirely avoidable by keeping the location on the vehicle’s record.

The auto shop hub covers the related point about giving each location its own page and its own number.

What to measure

One figure: bays filled from reminders rather than from walk-ins.

That is the whole purpose. It tells you whether the programme is smoothing the week or merely sending messages, and it is measurable within a month of starting. Open rates and click rates tell you nothing about a bay, which is the only capacity the shop actually has. The HVAC version of this page applies the same standard to service visits.

Once it is, this is usually the highest-return thing an independent shop can do with software. The demos include the automation running against sample vehicles, the auto shop hub covers where it sits in the order, and starting a project begins with what your tickets look like today.