Yes, as long as your services pages document the split. The bot uses drivetrain as the first cut: front-wheel-drive cars can usually take a two-wheel alignment, all-wheel and four-wheel-drive vehicles get quoted at four-wheel by default. Customers asking why pay more on an AWD Subaru or Audi get a plain-language explanation that adjusting only the front leaves the rear toe off, which accelerates inner-edge tire wear.

Yes. If your menu separates standard passenger-car alignments from lifted, leveled, or aftermarket-suspension trucks, the bot quotes the right line. It can flag that a lifted truck may need camber bolts, longer tie-rods, or specialty alignment racks, and that time-on-rack is usually closer to two hours instead of an hour. Customers see the higher rate up front with the reason in plain language.

If your shop documents the policy that any control-arm, tie-rod, ball-joint, strut, or steering-rack replacement requires an alignment, the bot enforces that in conversation. A customer asking about strut replacement gets quoted the strut work plus the alignment together, instead of being surprised by the second invoice. Post-collision and post-curb-strike alignments are flagged as needing a printed before-and-after spec sheet.

Yes. If your services page lists a 6-month, 6,000-mile, or lifetime alignment warranty, the bot quotes those terms in chat. Lifetime alignment plans for repeat customers also work; the bot can recommend the upgrade for daily drivers and explain when the standard warranty is enough. The exact terms come from your WordPress page so there's no risk of overpromising coverage you don't actually offer.

If your shop services EVs and publishes the relevant info, yes. The bot knows EVs are heavier per axle and that some racks have weight limits. Tesla, Rivian, and other EV-specific notes (camber adjustments on Model S, for example) live in the prompt context if you publish them. If your rack can't safely lift a particular EV, the bot says so and routes the customer to a shop that can.

Yes. SleekAI fills the same WordPress booking fields you already use, whether that's Bookly, Gravity Forms, Amelia, or a custom calendar widget. Customers never bounce to a separate scheduler. Your front desk sees one calendar with the same booking format they already work with, just with richer intake notes from the conversation attached.

Inside WordPress, with the page URL, the vehicle info, the prior work mentioned, and the quoted alignment line attached to each conversation. The alignment tech opening the rack at 8 AM sees the full intake instead of "alignment, four-wheel." Service managers can review threads, tag follow-ups, and spot which quotes converted versus which went silent.

Yes. Multibot lets you scope a separate bot to /fleet or a specific user role with different pricing, invoicing language, and net-30 terms. The retail bot stays focused on consumer alignments while the fleet bot handles by-VIN booking and tracks alignment history across the fleet. Each bot keeps its own scope without bleeding into the other.