Start stock, test-drive, and inspection questions on the dealer’s own pages
A dealer site is doing two jobs at once: cars for sale, and the workshop next door. Visitors want to know if a used car is still listed, whether a test drive needs a booking, how long an inspection takes, and whether you service cars you did not sell.
WebsiteChat answers from the vehicle, service, and booking pages you already published, plus text-selectable PDFs where the plan allows them. It is not wired to the lot system, a service scheduler, or a lender.
The lot, the service lane, and the website tell different stories
Sales and the workshop share a homepage and almost nothing else. People call because they cannot tell which page applies to the car in front of them.
A listed car is not a promise it is still on the lot
Inventory pages go stale. The honest reply is what the page says, plus a prompt to confirm with the dealer before anyone drives over.
Test drives, inspections, and servicing use different clocks
A Saturday sales desk and a weekday inspection bay are not the same hours. Mixing them sends people to a closed lane.
Finance and trade-in pages sound like an offer
“Loans available” and “we take trade-ins” are invitations to talk. They are not an approval or a number.
Parts and other-brand servicing get lost under new-car content
Owners of cars you did not sell still need the service page. If that page says you accept them, the chat can say so. If it does not, it should not guess.
Questions that show up before a test drive or an inspection
Keep sales questions and workshop questions in the words customers use.
- Is this used car still available?
- Do I need an appointment for a test drive?
- How many days does an inspection take?
- Can you service a car I bought somewhere else?
- Can I talk to someone about a trade-in?
- What time does the service desk close?
- Do you stock parts for this model?
- Can I book a service without buying a car from you?
Answer from the dealer pages you already published
The assistant’s job is to surface vehicle, service, and appointment information that is already on the site, then hand the next step to the desk you named.
Crawl sales and service as separate sources
Vehicle listings, inspection explanations, hours, and booking instructions can all be read if they are public. A DMS, a lender portal, and the workshop schedule are not.
Use a PDF when the inspection menu is a document
A text-selectable service menu or inspection checklist can be added on eligible plans. The assistant still should not turn that menu into a diagnosis.
Repeat the listing, not a fresh promise
If a car is on a public page, the reply can describe what that page says and point to the confirmation path. “Still here, I’ll hold it” is a person.
Send test drives and bookings to the published path
Phone, form, or a booking link you already show can be the next step. The chat does not write the appointment.
Diagnosis, finance approval, and the final price stay with staff
A dealer chat can explain published services. It cannot close the three decisions that need a person and, often, the car itself.
- Do not give a definite diagnosis of a noise, a warning light, or a failed inspection item
- Do not promise loan approval, a rate, or that a buyer qualifies
- Do not guarantee a price, a discount, or a trade-in figure that staff have not confirmed
- Do not treat a listed car as reserved or as definitely still in stock
Moments that used to start with “is it still there?”
These are pre-visit checks. The sale, the inspection result, and the repair order still happen with staff.
A used car open in another tab
The visitor asks if that listing is current. The reply quotes the listing page and points to the contact path so the desk can confirm the car is still available.
A test drive on the way home from work
Hours and whether an appointment is required come from the sales page. The chat does not put their name on a calendar.
An inspection before a deadline
If you published a typical number of days, that range can be repeated, with the note that the workshop confirms the actual date.
A trade-in conversation, not a number
The page that says trade-ins are discussed in store is the whole answer. No valuation is invented.
Load the dealer site, then test stock and service questions
Sales and the workshop should both be in the crawl, or the assistant will answer one and invent the other.
- 01
Create the dealer site
Use the name customers see on the building, not an internal brand code.
- 02
Crawl listings and service pages
Include used and new inventory pages you intend to stand behind, plus inspection, hours, and booking notes.
- 03
Add a service PDF if that is the real menu
Only when the text is selectable. Do not upload a rate sheet you do not want quoted back.
- 04
Set a greeting that names both desks
Tell visitors they can ask about listed cars, test drives, inspections, and published service rules.
- 05
Install on inventory and service URLs
Those are the pages where the question starts.
- 06
Test the refusals
Ask for a diagnosis, a loan decision, and a guaranteed out-the-door price. Each should bounce to staff.
Checking a used car without promising it is reserved
The reply stays on the listing and the test-drive note.
Is this used car still there, and do I need to book a test drive?
That car is on the current used-inventory page. Availability still has to be confirmed with the sales desk. The test-drive page says weekday drives are by appointment.
Contact sales
Where dealer sites usually need the next page
Hours, service scope, and “do you work on cars you didn’t sell?” are customer support questions with a workshop accent.
A test drive or an inspection request is lead generation: the chat explains the step, and a person takes the booking.
Inspection timing and what to bring, when you already wrote them down, belong with FAQ.
The product limits are in the website chatbot overview. Stock, finance, and diagnosis that the pages do not settle go through contact.