AI automation for car dealerships and service workshops

What a dealership hands over, and what stays with the mechanic

AI automation for a car dealership or workshop handles everything around the vehicle rather than the vehicle itself: answering an enquiry about a listed car in seconds at any hour, booking test drives, filling the service diary against real capacity, sending service reminders from the record, answering parts availability questions, keeping the customer informed while their car is in, and capturing the trade in conversation properly. No fault is diagnosed and no repair is priced without a mechanic looking at the car.

Two businesses usually sit under one roof here, and they have different problems. Sales loses money to slow replies and untracked enquiries. The workshop loses money to an empty bay, a customer who cannot be reached for approval, and a service that never got booked because nobody reminded anyone.

Most of the value is in the second one. Sales attention goes to the forecourt, while the service department quietly holds the relationship that brings a customer back to buy the next car.

• Selling: enquiries from listings and messages, qualification, test drives, follow up, trade in capture
• Servicing: booking against capacity, reminders by date and by mileage, approvals, collection
• Parts: availability questions answered or routed, orders raised, customers told when something lands
• Records: job cards, service history, warranty paperwork, all findable rather than filed somewhere
• Knowing where you stand: enquiries by source, test drives, bay utilisation, returning customers

The week you actually have

No solutions in this section. Count.

• An enquiry about a listed car arrives at ten at night and is answered the next afternoon, by which time they have seen two others
• Somebody asks whether a part is in stock and the answer needs a walk into the store
• A test drive is arranged on the phone and nobody records who took it or what they said afterwards
• A customer who bought three years ago has never been asked about changing the car
• The service diary is a paper book, so the workshop is either empty or overbooked
• A service reminder goes out only when somebody remembers to look at last year's list
• A job card is written by hand and the price is given on the phone twice, differently
• Approval for extra work waits all afternoon because the customer is at work and nobody can reach them
• A car is finished and sits on the forecourt overnight because nobody told the owner
• The trade in conversation happens three times before anyone commits to a number
• Warranty claims are prepared from paperwork that has to be found first
• Missed calls at lunchtime are never returned
• Nobody can say which listings actually produced enquiries last month
• A customer asks for their service history and it takes a search through files

The arithmetic on your own forecourt

No industry averages here. Three sums using numbers your own systems already hold.

• Sum one: your gross profit on an average vehicle, multiplied by the enquiries last month that got a reply the following day or no reply at all.
• Sum two: your average service invoice, multiplied by the number of cars you serviced two years ago that have not been back since.
• Sum three: the hours your service desk spends each week on the diary, reminder calls, approval chasing and parts questions, multiplied by what an hour costs, multiplied by fifty two.

The second sum is usually the largest and the least examined, because a customer who stops coming back does not complain. They simply go somewhere closer to home.

What gets built, and where a dealership starts

Sales sites usually start with the enquiry, because the reply time decides who gets the viewing. Workshops usually start with the service reminder, because the list of cars due already exists and nobody is working it.

• Instant replies to enquiries from listing sites, WhatsApp, the website and missed calls, carrying that specific vehicle's details
• Qualification gathered before a salesperson picks it up: part exchange, finance interest, timing and location
• Test drive booking with a confirmation, a reminder and a follow up afterwards that gets recorded
• Service booking against real workshop capacity rather than a paper diary that only one person can read
• Service and inspection reminders raised from the record, timed by date and by mileage where you have it
• Parts availability answered from the stock record where the system allows it, or routed to whoever can see it
• Job card status messages to the customer: booked, in, work identified, waiting for approval, ready
• Approval requests sent as a message describing the work with a price, with the reply recorded against the job
• Collection reminders when a car is ready, so the space clears and the invoice is settled
• Service history and warranty paperwork assembled from the record instead of found in a folder
• Trade in enquiries captured with the details a valuation needs, with the number itself given by a person
• A dashboard: enquiries by source, test drives, bay utilisation, returning customers, average invoice

What stays human in a workshop

No fault is diagnosed without a mechanic looking at the car. A customer describing a noise, a warning light or a smell gets a booking and a sensible question or two, never an opinion about what is wrong and never a price for work nobody has inspected.

That rule exists for a commercial reason as much as a safety one. A price given over a message and revised in the workshop is the single fastest way to lose a customer's trust.

• Any diagnosis, and any advice about whether a car is safe to drive
• Any price for work that has not been inspected, and any change to a price already agreed
• The trade in valuation figure itself, which a person gives after seeing the vehicle
• Finance, credit and insurance conversations, which are regulated in most markets and often require a licensed person
• Complaints, and any dispute about work already carried out
• Anything published in the dealership's name, including replies to public reviews

What changes market by market

The workshop is the same everywhere. What surrounds it is not.

• Regulation differs. Consumer rights on a used vehicle, warranty obligations, cooling off periods and what must be disclosed vary widely, and selling finance or insurance usually requires a licensed person rather than a system.
• Inspection regimes differ. Where periodic roadworthiness testing is compulsory, the reminder cycle around it is one of the most valuable automations available. Where it is not, the equivalent trigger is mileage and service interval.
• Channel differs. Listing portals dominate in some markets, WhatsApp and Instagram in others. Business messaging on WhatsApp runs on opt in, on approved templates and on a window that closes after the customer's last reply, so a service reminder has to be an approved template.
• Payment differs. Where most cars are bought on finance, the enquiry conversation is about monthly figures and approval. Where most are bought outright by transfer or cash, it is about price and condition, and the follow up is a different sequence.
• Seasonality differs. Model year and plate changes, weather driven demand, and the pre holiday rush of people servicing a car before a long drive all move the workload, and the reminder calendar should move with them.

Where the workshop diary is the constraint, not the software

Three situations where buying this is the wrong move.

A fourth, on permission. Reminders sent to a list that never agreed to be contacted are a problem in most markets and an annoyance in all of them. Check what you actually hold consent for before switching anything on.

• If your bays and technicians are already full, a booking system fills the diary faster and makes the lateness worse. Capacity is the constraint, and no message solves it.
• If your stock record is not accurate, do not answer parts questions from it. An automated wrong answer costs more than a slow right one, and the customer remembers the wrong answer.
• A single mechanic operation with a loyal local following usually needs a phone that gets answered and a diary somebody keeps, not a system. The trigger is the point where cars are being turned away while bays sit empty.

An AI receptionist for a dealership or workshop, and the fault it must not name

An AI receptionist for a dealership books the service against the real diary, tells a customer whether the part has arrived, takes the message that reaches the service manager, and puts anybody describing a problem with their car straight through to somebody who can look at it.

Diagnosis stays out of it, for the reason given above. So does any pretence of being human. Callers who ask whether they are speaking to a person and get an evasive answer do not shrug it off, and a forecourt that earns a reputation for it loses the service business to the garage down the road that answers its phone honestly.

Parts, courtesy cars and a price for a repair all belong to a person. What a machine can genuinely take off the desk, and what it costs to run, is on the AI receptionist page.

The sequence, the handovers, and who keeps the two year list

The timing on a dealership build is faster than owners expect on one side and slower on the other. The audit takes the first week, and the finding in it is usually the feed: whether your listings, your dealer management system and your service diary can be read at all decides half the scope before anything is priced. One piece is live inside a fortnight, and for a workshop that is nearly always the reminder run against the cars serviced two years ago, because the list already exists and nobody is working it. The sales enquiry layer follows across month two, since the reply has to carry that specific vehicle's details and that depends on the feed.

Where the system stops is a commercial rule before it is a safety one. A customer describing a noise, a warning light or a smell gets a booking and one or two sensible questions, then it hands it to a person, because a price given by message and revised in the bay is the quickest way to lose somebody for good. Extra work found mid job goes out as a described request with a figure attached and waits for human approval, recorded against the job card, so nobody argues in a fortnight about what was agreed on a phone call. Finance, credit and insurance conversations route to whoever is licensed for them. The trade in figure comes from a person who has seen the vehicle.

The asset here is the customer and vehicle history, so ownership is worth settling before the first build rather than at the end of it. The job cards, the service history, the message threads and the automations sit in accounts under your own logins, so you own the system and the reminder run keeps going out whether or not the arrangement continues. That also means the two year list stays yours, and it is the most valuable thing on this page. A dealership with a capable service manager can keep the reminder run going in-house once it is built, which is a legitimate way to buy only the first month of this.

Ibrahim owns build and workflows at Wobble and is usually the person a service manager deals with week to week, on the principle that the desk should be able to change the wording of a reminder without ringing anybody. Moiz Khan owns automation architecture and decides what the system may and may not say about a car. Wobble works from Karachi, bills month to month, and carries 25 engagements across six countries. The nearest of them to this trade is inbound and outbound voice agents running more than 500 calls a day for Big Texas Land Buyers, a different industry with the identical problem of a phone nobody can reach.

Common questions

Will it tell a customer what is wrong with their car?

No. A customer describing a noise or a warning light gets a booking and a couple of sensible questions, never a diagnosis and never a price for uninspected work. That boundary is written into the build rather than left to judgement, because a guess given by message becomes an expectation by the time the car arrives.

Can it book services against our real capacity?

Where your diary or workshop system allows an outside connection it does, and a booking respects technician availability and job length rather than filling a slot that does not exist. Where it does not allow that, the system collects everything needed and a person places the booking, which still removes most of the phone time.

Can it answer questions about parts availability?

Only if your stock record is accurate enough to trust. Where it is, the answer goes out in seconds with a price and a lead time. Where it is not, the honest build routes the question to whoever can look, because a wrong availability answer costs more than a slow one.

Will it quote for repairs?

It can quote from a fixed price menu for defined items such as a standard service or a set of tyres. It does not price diagnostic or repair work before a mechanic has seen the car, and it does not revise a price already agreed with a customer. Those go to a person every time.

Does it handle trade in valuations?

It handles the conversation around them. Registration, mileage, condition, service history and photographs are collected in one exchange so the valuation can be prepared quickly. The number itself comes from a person who has seen the vehicle, because a figure given in a message and then reduced on the forecourt loses the deal.

We are a small independent garage. Is this worth it?

One piece of it usually is. Service reminders from your own customer list and a reply to missed calls are cheap to build and pay back on the first few bookings. A full dashboard and stock integration can wait until the diary is consistently full and you are choosing which work to take.