A driver gets home and something is wrong. A light on the dash, or a noise at every stop that was not there last week. It's late, your shop closed hours ago, and the question typed into your site isn't really technical. It's: do you work on my make, and can you take it this week.
The same night, somebody else with that vehicle asks their phone which shop nearby handles the make. Your name isn't in the question. Whatever comes back is built out of what can be found about the shops around you: their sites, their Google profiles, their reviews.
The general version of this sits on our parent site: AI is on both sides of the counter.
The one on your site
Answer what they asked. "Do you work on my make" has a yes or a no, and the customer needs the real one. A false yes costs them a morning and ties up a bay for nothing. Silence, or a contact form, sends them to whoever answered.
Take the year, make, and model, and the customer's own words about what the vehicle is doing. Those words should reach the counter unchanged. "Grinding at the front, worse when it's cold, started this week" is something your service advisor can work with. "Customer has a brake concern" is a note somebody has to redo in the morning.
Let the assistant name only prices you've already published, which rules out diagnostic and wear work, and that's most of it. A warning light or a brake noise can have many causes, and only an inspection narrows them down. Any number the assistant gives is a number your advisor has to walk somebody back from before the vehicle is on a lift, and the job starts with an argument. Explain how the diagnostic works. Say the cost comes off the repair only if that's your shop's policy.
It should also know when to stop. If somebody describes a vehicle that isn't safe to drive, say so plainly and offer the towing or pickup your shop actually has. Booking a walk-in for a vehicle nobody should drive isn't a lead. And the booking link should open the right store's calendar, not a shared form.
The one on the driver's phone
The assistant needs to know whether your shop is close enough and whether it can do the work. Close enough is easy. What you can actually do is where shops go missing. Makes and specialties get left off shop websites, or written too vaguely to help. The European work. The diesel. The high voltage hybrid training somebody paid real money for. A site that says full service auto repair leaves the assistant guessing, and the shop that named the specialty is the easier one to hand the question to.
Then there's the group problem. When the stores in a group share a page, a phone number, and a service list, an assistant can merge them into a single shop, or miss the others entirely. Customers asking for the nearest one get sent past your closer store. Every store needs its own page, its own hours, its own line, and its own description of what it does, wherever the stores are actually different.
Boat work runs on a different calendar, same problem. A boat comes off the water at the end of a weekend, the owner types that night, and the whole conversation is whether you work on that engine.
What the counter finds in the morning
Everything the site does overnight is sitting there at opening: conversations in the customer's own words, the ones with a number to call back kept apart from the ones that stopped partway. An advisor who can work that list before the doors open is getting something real out of the site. An advisor piecing it together from a vague summary is doing the job the site was supposed to do.
Read them for the questions themselves. Those belong on your pages, in those words, and that's the same work that lets an assistant somewhere else describe your shop.
What to check on your own setup
- Type the make you service least often into your own chat after hours. A cheerful maybe is worse than a straight no.
- Ask a public AI assistant which shop near you works on that make, the way a stranger would. See who it names, and whether anything it says about your shop is wrong.
- Put everything your technicians are certified in on the site, in the words a customer would use. A specialty that only ever gets said at the counter is one an assistant can't confirm.
- If you run more than a single store, open each store's page next to its Google Business Profile. Own hours, own number, own service list, not a copy of the busiest store's.
- Read what reached the counter from the overnight conversations. Is the customer's own description of the noise still in there, or has it been smoothed into something generic?
Frequently asked questions
Should an AI chatbot quote repair prices to customers?
A flat maintenance price you already publish, yes, word for word. Anything diagnostic or wear related, no. The rule: it can repeat a price you've already published, and it can never make one up.
Why does ChatGPT keep naming the same store in our group?
Often that store has the clearest public information, though distance, reviews, which sources it found, and the wording of the question all feed the answer. The fix isn't clever wording. It's giving every store the standard of detail your best documented store already has.
Is any of this worth it for a shop that's already booked out?
A full schedule isn't the same as a good schedule. Saying plainly what you want more of helps bring in more of it: the makes you named, the services you described, the specialties you spelled out. A quiet shop takes whatever shows up.
Next step
Walk it yourself. Type a make question into your site tonight, then ask an assistant where to take that vehicle in your area. If the answers don't match, you've found something worth checking, and a free visibility audit is the easiest place to start.
