Service slot, part price, and whether the courtesy car is free.
A chatbot for car dealership sales and service, on both counters at once.
OpusDone answers service, parts and sales questions at the same time, using only what you have approved, and books the visit into your workshop calendar. Three questions, three different people, all arriving while the service desk has a queue and the phone is ringing. It will not invent a part price, a lead time or a courtesy car policy, and anything it does not hold goes to a person by name. Both counters get an answer instead of a queue.
- Answers sales and service enquiries
- Never quotes a part it cannot verify
- Books the workshop visit itself
Reviewed
Why do aftersales questions arrive while sales is busy?
The service desk is a bottleneck by design
One person, a queue of keys, and a phone. Every online enquiry joins the back of a queue it cannot see, and most of them only wanted to know whether Thursday was free.
Part prices are the wrong thing to guess
A number given casually online becomes an argument at the counter. Anything the customer was told has to be something somebody actually approved, or it costs you the goodwill and the job.
Buyers browse at eleven at night
The used stock gets looked at after dinner, in bed, on a phone. The enquiry that lands at 23:20 is answered at 09:40, and by then they have booked a test drive somewhere else.
What it takes on across both counters.
The questions it takes off your desk
Five it will answer today, from knowledge you approved: “What does an interim service cost?” · “Is a courtesy car included while mine is in?” · “Can you do a pre-ITV check next week?” · “Do you take part exchange?” · “Do you offer a warranty on used cars, and how long?”.
Workshop visits and test drives written into the diary
Slots are 30 minutes at 15-minute granularity by default, minimum notice 120 minutes, horizon 60 days, buffers zero — all editable. Your closed days are verified in three independent places, including immediately before the write, and event ids are deterministic, so a retry after a network timeout cannot book the same car in twice.
Google Calendar or Cal.com. One calendar for the business, not per technician.
A monthly report of what the evenings brought in
A weekly digest and a monthly email show after-hours bookings, hours saved, the share the assistant handled alone and the month-on-month change. It is the honest way to see whether the 23:20 enquiries were worth anything.
How does OpusDone turn your workshop diary into a booked service?
Everything below is done on a screen, in an afternoon, without touching how the workshop runs.
- 01
It reads your site for services and hours
The crawl picks out your servicing, repair, pricing, FAQ, contact and hours pages by English and Spanish keywords, then reads the meta description, Open Graph tags and JSON-LD for the workshop address, phone and opening hours. One model pass turns that into structured services, FAQs, policies and four to ten draft knowledge entries. It fills empty fields only, so text a human wrote is never replaced. - 02
You mark live only what you will stand behind
Nothing reaches the assistant until you approve it; drafts, imports awaiting approval, archived and rejected entries stay invisible. Each turn carries at most 12,000 characters of knowledge and no single entry may take more than 40% of it, so your courtesy car policy cannot be buried behind one enormous page about the brands you service. A quality gate drops navigation soup, cookie text and near-duplicates at 85% overlap. - 03
You set bay hours, closures and how far ahead it books
Working hours, and closed days set by clicking a day or dragging a range on the month calendar — the August fortnight in two drags. Slot length is 30 minutes by default with 15-minute granularity, minimum notice 120 minutes, buffers zero and a 60-day horizon, all editable. Closures are mirrored into Google as an all-day event carrying your business name, and deleting that event does not reopen the day. - 04
You connect one calendar for the workshop
Google Calendar over OAuth with no API key, or Cal.com with one. It reads every calendar you mark as busy and merges them, so a technician’s holiday or a bay already committed removes the slot. It books the workshop rather than a named technician, and its access is narrow: read and create events, never delete a calendar. - 05
You test it on the calls you take twenty times a week
The sandbox runs your real instructions and your real tools and stops before writing anything — no booking, no lead, no alert. Ask for a service slot next Thursday, a price on a part, and whether there is a courtesy car, and see exactly where it hands over. It is free and never gated, so you can tighten the wording as often as you need. - 06
One script tag, and the service desk stops ringing after six
The widget is one line on the site you already have, and Telegram is the second live channel; both run through the same function, so the answer is the same wherever the customer started. Hours and closed days are checked before a slot is offered and again before it is written, availability is re-read at the moment of writing so two customers cannot take the same bay, and it offers at most six options with no more than two from any one day. It replies in the language the customer wrote in, and adds the Article 50 AI disclosure once per conversation.
Can it tell a customer whether the part is in stock?
No. It cannot check stock, track an order, send a document or apply a discount — those are not tools it has, so it cannot half-promise them either. It says a person will confirm, takes the registration and a phone number, and puts the enquiry in front of the parts desk with the transcript attached.
Slot, part price, courtesy car
The same three questions, from before you open to after you close.
- 07:48
Before the shutter
Someone asks about a service slot twelve minutes before you have unlocked the door.
- 08:30
The part price
It quotes only the figure you approved and refuses to guess at anything you did not write.
- 11:15
The courtesy car
It repeats your policy word for word, including the part customers would rather not hear.
- 16:20
A slot goes mid-chat
Someone else takes it first, so the customer is offered alternatives rather than an error.
- 19:50
After the shutter
Evening messages still get answered, and anything it cannot handle lands in your inbox with a summary.
What it does instead
What will OpusDone never do on the forecourt?
Everything it says is something you typed and marked live. Nothing else gets through.
It will not invent a price or a lead time
No estimate for a clutch, no guess at when the part lands, no “usually about a week”. If it is not in your live knowledge, it fetches a person.
It will not book a named technician
One calendar for the business, no per-bay or round-robin allocation. It secures the slot; you decide who has the car.
It will not talk about finance
No monthly figures, no affordability, no comparisons. Finance conversations are escalated to a person with the details already gathered.
It will not look at the photo of the damage
There is no image or document understanding. An attachment it cannot read skips the model entirely: it says so and hands over, rather than guessing at a repair.
Car dealership chatbot questions, answered
Can one assistant cover both sales and the workshop?
What if two people take the last Thursday slot at once?
Can we try it against awkward customers before it goes live?
My technicians don’t all do the same work. Can it send the right job to the right one?
A customer asks about a used car that sold this morning.
Someone wants to cancel a service booking.
Part prices move every month. How do I keep what it says current?
More for dealerships and workshops
Booked the service before you raised the shutter
Website widget and Telegram, on Google Calendar or Cal.com. One calendar for the workshop, thirty-minute slots by default, and every setting — notice, horizon, buffers — editable from the dashboard.
Request access