Yes. If your VDP inventory is published as WordPress pages, custom post types, or via a third-party plugin that writes to wp_posts and postmeta, SleekAI maps stock number, MSRP, mileage, exterior color, interior color, trim, and option packages into named variables. The bot answers availability questions with real units on the lot. If your inventory feed comes from a separate IMS, you can mirror it into a custom post type and the bot reads from there.

It quotes published payment ranges with the standard disclaimers. If your site has lease specials pages with monthly payment, term, money down, miles, and effective date, the bot reads them and quotes accordingly. It never invents an APR or a residual value, and the instruction is explicit that all quotes are subject to credit approval, plus tax and fees, and that the F&I office finalizes numbers. Compliance teams get exactly the disclaimer language you publish.

The bot describes your trade-in evaluation process and routes the customer to your trade appraisal flow (in-person walk-in, online photo submission, KBB instant cash offer integration, etc). It does not quote a specific trade value because that requires hands-on inspection, mileage verification, and condition assessment. The instruction prohibits invented trade numbers, sourced from your published trade-in policy page.

Yes. Multibot scopes a sales bot to inventory and finance scope and a service bot to maintenance scheduling, recalls, and parts. The service bot reads from your service menu and shop calendar while the sales bot reads from inventory and lease pages. Display conditions route each customer to the right scope based on URL path, post type, or page template.

Yes, if you publish them. Manufacturer rebates, college grad programs, military appreciation, recent graduate offers, and loyalty incentives all live on dedicated pages at most dealerships, and SleekAI reads them. The bot can confirm whether a customer qualifies based on their description (recent graduate, active military, current Toyota owner) and surface the offer with the standard "see dealer for details" language.

If your used inventory pages publish Carfax or AutoCheck summaries (one-owner, no accidents, service history visible), the bot reads them and surfaces the highlights. It links the customer to the full report instead of trying to summarize a 14-page Carfax in chat. For specific concerns like accident history or service records, the bot routes them to the link.

Yes. If your dealership publishes Spanish content (a translated VDP page set, Spanish finance specials, bilingual sales staff bios), SleekAI can read whichever language is active on the request. The bot can also be configured to respond in the customer's language by detecting the message language, which matters in markets where 30-40% of inquiries come in Spanish.

Every conversation is logged in WordPress with the vehicle, customer name, contact info, and any trade-in mentions. From there, the lead can be pushed to your CRM (VinSolutions, DealerSocket, Elead) via webhook, Zapier, or a direct integration plugin if one exists. The bot doesn't replace your CRM, it feeds it cleaner leads with vehicle context attached.