Software for auto repair shops in San Diego

An auto repair shop runs on a constraint that almost no other small business shares. Capacity is bays, and a bay produces nothing while it waits. Meanwhile the demand is largely unannounced — a noise that started this morning, a warning light on the way to work, a tyre that will not hold pressure. The business is a queue with no advance notice and a fixed number of servers.

That is the frame for every software decision in this trade.

Fill the quiet days with the work you already know about

You cannot schedule a walk-in. You can schedule everything else, and most shops have a great deal of everything else sitting unused.

The deferred work list is the clearest example. A technician recommends a repair, the customer declines it for now, and the recommendation is recorded on a ticket that nobody ever looks at again. That list is a set of known jobs on known vehicles belonging to customers who already trust the shop. A short message in the right month converts a real share of it, and it arrives on a day you chose rather than a day the road chose.

Service intervals work the same way. So do seasonal items. Together they are enough to smooth out a week, which is the whole ambition — the automation page covers how it is set up without becoming nagging.

Specialisation is worth more online than in the bay

A shop that repairs everything is difficult to find, because the search that matters is not general. An owner of a particular European make searches for that make, often with the model and the symptom, and the shop whose website says so plainly wins a far more valuable visitor than a general repair page ever will.

I built a site for an import specialist, and this was the whole strategy: say the specialty clearly, say what else is covered afterwards. Breadth still exists, it simply stops being the headline. The general contractors page page covers how that structure is built.

Two locations need two pages, properly

A multi-location shop gets this wrong more often than not, usually by presenting both addresses on one page. Each location needs its own page with its own address, hours, phone number and the neighbourhoods it serves, because that is what both a searching customer and a search engine are looking for.

The phone matters here too. A caller trying to reach one shop should not have to work out which one they have got, which is a configuration detail that answering coverage (the plumbers page covers the mechanics) has to be told about rather than something it can infer.

The phone is the counter

In a shop, the phone is not a lead channel. It is the counter, and it rings while the service writer is already talking to someone standing in front of them. The caller with a noise hears it ring out and drives to whoever answers.

This is the most common gap in independent shops and the least complicated to close. Cover the phone, take the vehicle and the symptom, get a callback number, and hand it to a human.

Reviews accumulate honestly here

Auto repair is chosen under uncertainty by people who cannot assess the work, which makes other customers’ experiences the proxy. The habit that works is one link, sent after every finished job, every time. A year of steady accumulation reads as a real shop; a sudden cluster reads as something arranged, and readers do notice.

A sensible order

Cover the phone. Start working the deferred list. Make the specialty explicit on the site. Then consider a customer record (the framing shops page covers the mechanics) properly.

What the ticket history has to support

Everything useful in a shop depends on being able to search what has already happened.

Which vehicles are due. What was recommended and declined, and when. Which customers have not been seen in two years. Which vehicle belongs to which phone number, still. A shop whose history exists only as paper tickets in a cabinet cannot answer any of those, and no amount of software added on top will change that until the history is reachable.

Getting there is unglamorous and it is the prerequisite for the rest. The HVAC hub describes the identical problem with installed equipment, and the general contracting hub covers where records sit in the order of things.

The demos show the pieces and starting a project takes one sentence.

The five pieces

Every one of these is built separately and sold separately. Most shops need two of them, not five, and the order matters more than the count — a CRM with nothing feeding it is a very tidy empty room.

• Website — The site itself — pages, photos, forms, speed, and the search work that makes it findable. Page in progress.
• CRM — Where a lead lands, who owns it, and what happens on day two, day seven and day thirty. Page in progress.
• AI receptionist — Answers the calls nobody can pick up, asks the qualifying questions, books or hands off. Page in progress.
• Automation — The follow-ups, reminders, review asks and status updates that stop depending on memory.
• Estimator — A structured way to turn a job into a number, the same way twice, without a spreadsheet. Page in progress.

If you would rather see the software than read about it, the demos are real and seeded with sample data, and the process page covers how a build actually runs. When you are ready, start a project.