If your services pages document OEM specifications by year and platform, or if you maintain a vehicle-spec lookup table, SleekAI uses that as ground truth. The bot asks year, make, and model on the first message and matches against the spec list. A 2021 RAV4 gets 0W-20 full synthetic at 4.6 quarts; a 2014 Civic gets 0W-20 too because Honda spec'd it from the factory; a diesel pickup gets the heavy-duty synthetic. If your data doesn't cover an obscure model, the bot says so and routes the customer to a service writer.

Yes. The bot has standard plain-language explanations: "Toyota requires full synthetic on your RAV4 to protect the variable-valve-timing system," "the warranty requires the OEM-spec oil weight," or "modern engines run hotter and need synthetic to prevent thermal breakdown." These don't read as upsell; they read as the same explanation your service writer gives on the phone. Customers feel informed instead of upsold.

Yes, as long as your menu separates them. Diesel oil changes run nearly three times the gas-engine cost because diesel-spec oil is more expensive and capacities are larger. Heavy-duty trucks with dual-filter setups, larger sumps, and higher service intervals get quoted at the right tier. The bot phrases the higher number with the reason attached so customers don't compare a one-ton diesel quote against a Civic quote.

Yes. If a customer mentions mileage or last service date, the bot can flag cabin filter (every 15-20k), engine air filter (every 20-30k), and wiper blades (every 6-12 months) as due. It does not suggest add-ons on every visit; it suggests them when the math says they're due. Customers stop feeling upsold and start trusting the recommendation.

Yes. Multibot lets you run a separate fleet-focused bot with different pricing, net-30 invoicing language, and by-VIN tracking. Fleet customers booking through the fleet bot don't see the consumer sign-board pricing, and the consumer bot doesn't accidentally promise net-30 to a walk-in. Each bot stays in its own scope.

If your booking system or a custom field exposes current bay occupancy, the bot can quote real-time wait times. Otherwise it falls back to typical wait expectations by time of day. Customers asking about a Saturday morning walk-in get an honest "40-50 minutes today" instead of "come on down," which means fewer angry waits in the lobby and more bookings into open appointment slots.

Inside WordPress with the customer's vehicle, the quoted oil tier, the filter SKU, any add-ons agreed in chat, and the page URL. The lube tech doing intake walks out to the car with the right oil already on the cart instead of asking "what does this one need?" at the bay. Service managers can review threads at end of day, tag follow-ups, and see which quotes converted to actual visits.

Yes. Multibot scopes a different bot per location, each with its own hours, oil pricing, and current wait times. A customer on the downtown shop page sees downtown pricing and hours; a customer on the suburb page sees the suburb's. Customers stop getting confused about which location has the 39.99 USD sign and your team stops correcting it at check-in.