While an auto repair shop is small, bookings live in a notebook and the service advisor’s phone, and vehicle history lives in someone’s head. As you grow, that starts costing money: double-booked bays, forgotten parts, customers who never come back for their next service. This guide covers what an auto repair shop CRM should do, what goes into the first version, what can wait, and how to start without a big budget.
What a day at a repair shop looks like
Take a hypothetical example. Say you run a shop with four bays: two for routine service and small repairs, one for suspension work, one for diagnostics and electrical. You have a service advisor, a few mechanics and a small stock of consumables.
A typical day goes like this:
- A customer calls or texts: “Can you change the oil tomorrow and check what’s knocking up front?”
- The advisor checks the notebook, guesses which bay is free, and writes it down.
- The car is checked in and inspected, and a work order is drawn up: jobs, parts, price.
- During the repair something else turns up. The advisor calls the customer to approve the extra cost.
- A part is missing. It gets ordered, and the car sits.
- The customer calls several times to ask if it’s ready.
- The car is handed back, the customer pays, and the shop forgets about them until the next breakdown.
At almost every step information gets lost or duplicated. The point of a CRM is not reports. It is to stop these steps from depending on one person’s memory.
What an auto repair shop CRM should do
Booking by bay and time
The key difference from ordinary booking: a job takes up a bay, not just a mechanic, and jobs vary in length. An oil change takes under an hour, suspension work can take half a day. The system should know typical job durations and show free slots based on the bay the job needs.
Keep online booking simple for the customer: service, make and model, date and time, phone number. A complex repair is something the customer cannot describe anyway, so “book a diagnostic” is enough.
Customer and vehicle history
One customer may bring two or three cars, and a car may change owners. So it helps to store customers and vehicles separately: plate number, VIN, mileage at each visit, every past work order. A mechanic sees in a minute what was replaced six months ago and does not suggest it again.
Work orders
The work order is the core document of a repair shop: what is being done, which parts, how much, who did it. In the system it moves through statuses: checked in, in progress, waiting for parts, awaiting approval, ready, handed over. Extra work is added with a note that the customer approved it. That removes arguments at pickup.
Parts stock
What is in stock, what is reserved for a specific work order, what needs reordering. Even basic tracking of consumables (oil, filters, brake pads) saves time: the mechanic does not walk to the shelf, and the advisor can tell the customer right away whether the part will arrive today. If you already track stock in 1C, connect the CRM to it instead of running two inventories.
Status notifications
When the advisor changes the work order status, the customer automatically gets a message: car checked in, we need your approval for extra work, your car is ready. Fewer “any news?” calls, and the customer feels looked after.
Next service reminders
This is the feature that brings in money directly. The system knows the date and mileage of the last service and, after the right interval, sends a reminder with a booking button. Do not overdo it: one timely reminder is useful, weekly promotions are annoying.
What to build first and what can wait
Do not try to cover everything in the first version. A sensible order:
- First version: bay schedule, customer and vehicle records, work orders with statuses, simple customer notifications. That is enough to retire the notebook and the “is it ready” calls.
- Second stage: parts stock and reservations, service reminders, online booking on a website or a Telegram bot.
- Later, if needed: mechanic pay based on completed jobs, reports by bay and job type, 1C integration, a customer portal or app with repair history.
For more on choosing what goes into a first version and why starting with a prototype is cheaper, see prototype first.
Start with what hurts every day: the schedule and work orders. If the advisor and mechanics do not use the system daily, no reports or reminders will save it.
Off-the-shelf or custom CRM
There are subscription systems built for repair shops, and honestly, for many small shops that is a fine start. You will quickly learn which features you actually need and which only looked important on paper.
A custom system makes sense when:
- you have several locations with their own booking rules and a shared customer base;
- you need parts tracked your own way or linked to 1C;
- you want a customer portal or app under your own brand;
- the ready-made system cannot send the notifications or reminders you need, and per-user subscriptions get expensive.
The general signs that it is time for a CRM, and a comparison of ready-made and custom, are in CRM for small business. As a reference, at NOVO a CRM prototype starts at $300, a first version at $1,200 and a turnkey system at $3,000. The exact price comes after a brief.
Website, bot or app for customers
The customer-facing side can take different forms:
- A website with online booking. Works for everyone: people find it through search and maps, and it shows your services and address.
- A Telegram bot. Handy for booking and notifications: nothing to install, and messages land where the customer already chats.
- An app. Worth it if you have many regular customers or several locations: repair history, reminders, loyalty points. For a single shop it is usually overkill at the start.
How to choose between them is covered in website, app or Telegram bot.
Common mistakes
- Reports before process. The owner wants revenue per mechanic, but if work orders are filled in only half the time, the reports will be wrong.
- Booking that is too complex. Ten fields and a mechanic picker scare people off. Service, car and time are enough.
- No single schedule. Bot, website and phone bookings live separately, and double bookings stay.
- Not asking the mechanics. If entering data is awkward, people stop doing it. Show the prototype to the people who will use the system every day.
- Messaging customers too often. Status updates help; promotions every three days get you blocked.
In short
- An auto repair shop CRM is mainly about the bay schedule, work orders and vehicle history, not reports.
- Status notifications cut down on calls, and next service reminders bring customers back.
- Put daily-use features in the first version; add parts stock and reminders in the second stage.
- If your process is standard, start with a ready-made system. Custom pays off with several locations, your own stock rules, a 1C link or a customer app.
- Show the prototype to the advisor and mechanics before development starts.