CRM for Auto Service: When Off-the-Shelf Falls Short
CRM for a car service: job orders, vehicle history, parts, service reminders. What ready systems do, when they run out, and what a custom one costs.
Short answer: an auto service is not a “deal pipeline” but a flow of job orders: intake, diagnosis, approval of the amount, parts, handover, next visit. Ready-made CRM systems for car services in Ukraine start at about ₴560 a month and cover the standard scenario of one or two work bays. A custom system is needed where specifics begin: a queue for the lifts, money owed against a job order, stock and telephony inside one card. DEXA’s guide is from $3,614 (₴150,000), timeline 6–10 weeks.
What matters in 30 seconds
Four different things live inside a job order: the list of works, the parts, standard hours, and the mechanic’s time; familiar forms often hold only the amount.
Requests arrive by phone, in Viber, in Telegram and in person; they get lost not from indifference but from the absence of a single entry point.
A ready-made system is enough for one or two bays, up to 15 job orders a day and standard documents. Beyond that come integrations, roles and margin per job order.
The money: from $3,614 (₴150,000) for a custom CRM, $361 (₴15,000) to connect the site to an existing one, support at from $72 (₴3,000)/mo.
How a day at the service differs from a “sales department”
The classic CRM was invented so nobody forgets to call back. At a car service that is not enough: here the deal has a metal part in it, two executors, and a returning client on a schedule rather than when the manager feels like it. Look at how an ordinary tool diverges from reality stage by stage.
| Stage | How it looks at the service | What an ordinary pipeline does not see |
|---|---|---|
| First contact | “Is the lift free, can I come at three?” — immediately a Viber message with a photo of the dashboard | that the person already got an answer, and on what basis they are coming |
| Approval of the amount | an approximate diagnosis, then “yes, go ahead”, then another “yes” after something extra is found | that the amount changed, and who approved it |
| Parts | ordered for this client, waiting, partial handover, returning a part that did not fit | why the job order has sat for three days, and whose fault it is |
| The work | two mechanics on one car, the bay occupied, standard hours counted differently | the real load on the bay and the actual duration |
| Handover | job order, certificate, payment in parts, “before/after” photos | the outstanding balance and the signed documents |
| Next visit | service by mileage or by year, seasonal tyres, bodywork warranties | that the client is “closed” and will never come back |
Five signs a ready-made CRM is not enough
The process is not “like everyone else’s”. Prepayment for parts, two mechanics on one order, your own job-order form and certificate that the accountant accepts without edits. Every time you “work around” a boxed limit with spare fields, someone on the team keeps doing the same thing on paper.
Stock is the source of truth. Residuals live in 1C/BAS, and re-entering them into a CRM means the two systems diverge by the first Friday.
You need the history of the car, not of the person. Owners change cars; the service remembers what was done, what is under warranty, when the next service falls due. A “client” card does not hold that.
Roles and money. The administrator sees the queue, the mechanic sees their own jobs, the buyer sees parts orders, the owner sees margin on each job order. In boxed products this is either paid for or impossible.
Reminders tied to mileage and season. “In 30 days” is not what brings a client back; what does is “oil change due in 1,500 km” and “tyre booking open until 20 October”.
What ready-made solutions for car services can do
| Solution | Price | What it covers | Where it stops |
|---|---|---|---|
| Appointer (CRM for auto services) | from about ₴560 a month on annual payment (solution page, verified 09.10.2026) | bookings, job orders, client base, notifications | your document forms, stock, specific roles |
| KeyCRM | base plan $19 a month, up to 200 orders (KeyCRM help, verified 09.10.2026) | requests from messengers, statuses, email integrations | the production process, standard hours, warranties |
| Ready-made “deal” modules in boxed systems | per-user subscription | pipeline, tasks, reporting | anything beyond the developer’s scenario |
Honestly, against our own interest: a boxed product is enough for a service with one or two bays, one administrator and no accounting system of its own. That is the right choice when the problem is discipline rather than software. The first thing to do in that situation is a single entry point for requests plus notifications to a phone: a week of work and almost no cost.
Example: what a lost job order costs
An example with hypothetical figures — put your own in. The service takes 40 enquiries a week; 8 of them get no reply within a day — the phone is busy, it is evening, it is the weekend. Conversion from those who did get an answer is 40%. That is roughly 13 lost job orders a month; at an average cheque of ₴2,500 it is about ₴32,500 of turnover gone each month.
Subtract the cost of a ready system (about ₴560 a month for Appointer) and it is under 2% of that sum. The difference between “boxed” and “our own CRM” is not in that figure but in whose process ends up fitted to whose fields.
What a custom CRM for an auto service includes, and what is counted separately
Inside $3,614 (₴150,000): the vehicle card (plate, VIN, mileage, work history), a job order with works, parts and standard hours, the queue at bays and between mechanics, access roles, document printing and export, payment status and balance, Telegram notifications, an owner dashboard showing margin on every job order, service reminders and seasonal campaigns.
Counted separately are the contours you join later: connecting the site or a form to the CRM — $361 (₴15,000), a 1C/BAS contour — $964 (₴40,000) per contour, a non-standard connector (accounting, telephony, a checkout point) — $241 (₴10,000), support after launch — from $72 (₴3,000)/mo.
What the road to a custom system looks like
A job-order audit: how the path from call to handover runs, who enters what, where paper survives. Without this, writing code is an expensive hobby.
A process map on one sheet: stages, roles, documents, control points. You approve that, not the interface.
The first contour in two to three weeks: requests, job order, statuses. You see the product working rather than “waiting for delivery”.
Then stock, telephony, reminders and dashboards, in iterations of two to three weeks.
Training and handover: the database is yours, the access is yours, code and documentation transfer under a certificate.
When a custom CRM is money thrown away
The team does not want to work in it. A half-filled system gives the appearance of order and figures nobody believes.
One bay, one administrator and no accounting system of your own: a ready-made solution will serve for years.
The process is not stable yet and changes every month. Agree the process first, automate second.
You only need one inbox for requests. That is a week of configuration, not a development project.
Client and vehicle data: what to check before launch
A client card in a CRM is personal data: surname, phone, vehicle, visit history. Under the Personal Data Protection Act (law text, verified 09.10.2026) processing must have a purpose, a retention period and a responsible person, and the individual can demand deletion of their data. Practically, inside the system that means four things: access by role (the mechanic does not see finances), an action log, a link to the processing purpose in the card, and a deletion mechanism on one request. Consent to communicate is separate: a person called with a service reminder without permission files a complaint, they do not thank you.
How we do this at DEXA
We build service CRMs from the job order rather than from the pipeline: first how your document looks and who signs what in it, then stages, roles and reporting. Public pages we build in Astro (fast and indexed without depending on JavaScript); the internal dashboard is React against your own database. Price and timeline are fixed in the contract after the process audit, and we show a demo every two to three weeks.
Why we count it this way
- Custom CRM · Standard (pipeline, roles, reports) — from $3,614 (₴150,000) · 6–10 weeks (About this service)
A custom CRM costs from $3,614 (₴150,000), over 6–10 weeks, in iterations with demos. The bill is fixed after a free process audit: if a ready-made system will be enough for you, that is what the conclusion will say.
Questions service owners ask
How much, and how long?
The base contour (requests, job orders, statuses, roles) is from $3,614 (₴150,000), over 6–10 weeks. After that telephony, stock and dashboards are added in iterations of two to three weeks, and each can be stopped: what is built stays with you.
Can we just connect the site to the CRM we already have?
Yes, and that is the most common first step. Form, chat and telephony converge into one card with a notification: $361 (₴15,000) for that kind of connection. If your system exposes no API, we check that first rather than promising an integration.
Where do requests from the site land?
In one entry point: a thread in your Telegram per client, with history, photos and files. Then into the CRM if you already have one. More on this in how to receive requests fast.
Who owns the client database?
You: the database sits in your infrastructure, access is yours, code and documentation transfer under a certificate. We want to stay on as support, not as a hostage-taker, which is why the boundaries of handover are written before the start.
What about telephony and call recording?
We connect your existing PBX or a ready telephony service: the call creates the card, and the recording stays in the visit history. If there is no telephony yet, that is a separate conversation — the operator’s licensing terms matter more there than software features.
Start with the process audit on the CRM development page, whose “for whom” block breaks the car service out separately. Next in the list: CRM or Excel, how to choose a CRM and connecting the site to 1C. A site for a car service with requests into Telegram is a separate task, solved by the “Start 500” card. For another field, the same choice — ready-made or custom — is worked through in the CRM for a beauty salon article.
automation from $2,410 (₴100,000) · a custom CRM from $3,614 (₴150,000) · CRM with AI from $6,024 (₴250,000)
Need the same solution for your business?
Three rungs: process automation on ready services, a custom CRM built around your scenario (pipelines, tasks, documents) and a CRM with an AI module. Telephony, mail and warehouse integrations.
- An audit and a process map: where deals and hours leak
- A custom CRM on React/Vue: pipelines, tasks, documents
- Integrations: telephony, mail, warehouse, your API and dashboards
Get a free website audit in 48 hours
Speed, SEO, conversion — a 12-page report with a prioritized fix plan. No obligation, no spam: we show what to improve even if you never hire us.
