A garage's service desk closes at five. The people who need their car looked at finish work at five.
That overlap problem is why so many workshop diaries have gaps that nobody can explain, the demand existed, it just arrived at 7pm, hit a contact form, and went to whichever garage down the road answered first on Monday.
Dealerships have the same problem with a bigger price tag attached: stock gets browsed at eleven at night and test-drive enquiries sit in an inbox until a salesperson opens it.
Service: price and availability, in that order
Almost every enquiry to a garage website is one of two questions.
How much? MOT, full service, interim service, brakes, cambelt, aircon regas, diagnostics. These are standard items with standard prices for most garages, and publishing them is a competitive advantage because so many don't.
When can you take it? The earliest slot is often the deciding factor. Someone with an MOT expiring on Friday isn't shopping on price.
Then a short tail of practical follow-ups: how long will it take, can I wait, is there a courtesy car, do you do collection and delivery, is there parking.
A bot answering all of that from your published content, at nine on a Sunday evening, captures a booking that otherwise wouldn't have existed.
Capturing a service booking properly
What the service desk needs to open the diary is:
- Registration, which tells you the vehicle, and often the MOT due date
- What's needed: MOT, service, specific job, or "something's wrong"
- Symptom description in the customer's own words, if it's a fault
- Preferred days, and whether they'll wait or leave it
- Courtesy car needed?
- Contact number
That's a booking your team can confirm in one call rather than three. And the registration alone saves a surprising amount of back-and-forth.
Ask any service manager what their first task is on a Monday and a surprising number will say: ringing back weekend enquiries to ask for a registration. Capturing it upfront deletes an entire round-trip from every booking.
Faults: capture, don't diagnose
Customers will describe noises. "There's a grinding when I brake." "It judders at about 50." "There's a light on the dash."
A bot must not diagnose these. A grinding on braking could be pads, discs, a stone, or a caliper, and a bot guessing creates an expectation about cost that the workshop then has to argue with.
What it should do is capture the description verbatim, ask a couple of clarifying questions your service team would ask anyway (how long has it been doing it, does it happen when cold or hot, is it getting worse), and book it in for a look.
One exception needs a script: anything safety-critical. Brake failure, steering problems, a red warning light, smoke, a strong fuel smell. The response should be to stop driving the vehicle and call you or recovery, not to book a slot for next Tuesday.
MOT reminders are a use case hiding in plain sight
Ask a bot-captured registration and you effectively have an MOT due date. Whether you use that for reminders is a marketing decision, but the capture makes it possible.
More immediately, a lot of enquiries are simply "when's my MOT due?". Answerable by pointing at the official checker, and a useful reason for someone to be on your site at all. A bot that helps with that and then offers to book the test converts a lookup into a job.
Sales needs a completely separate path
Test-drive and purchase enquiries are worth a great deal more than a service booking and behave nothing like one. Route them separately at the first question.
What sales needs captured:
- Which vehicle they're interested in, or what they're looking for
- Whether they have a part-exchange, and what it is
- Whether they need finance
- Rough budget or monthly figure
- When they're looking to change
- Contact details
A bot gathering that means a salesperson calls back with a proposition rather than an introduction.
It should not quote a finance figure. Regulated credit information isn't something to improvise, and a monthly payment generated in a chat window is a compliance problem. It can explain that finance is available and capture the enquiry. That's the whole of its job there.
Stock questions
If your inventory is on your website, a bot can answer from it: what's in stock, mileage, spec, previous owners, whether something similar is coming.
Be careful about how current it is. A bot confidently describing a car that sold last week produces a wasted visit and an annoyed customer. If your stock feed updates frequently, make sure the bot's content does too, and configure it to suggest confirming availability before travelling.
Where to draw the line
No firm quotes on repairs, the price depends on what's found. No finance figures. No promises about a specific slot unless your diary is connected. No diagnosis.
And no claims about warranty or comeback that aren't in your published terms.
Getting it live
Point it at your website. Service pricing, MOT information, stock pages, opening hours, courtesy car policy. Upload your service menu if it isn't already a page.
Split the routing at the first question: service, sales, or parts. Add the safety-critical script. Set service capture to registration, job, availability, and contact.
Knowing whether it's working
Service bookings captured outside opening hours, and test-drive enquiries reaching sales the same evening rather than the next morning.
In a business where the workshop diary is the asset and it perishes daily, filling gaps from enquiries that used to evaporate at 5:01pm is the fastest return available.