Yes, if your inventory plugin or workflow writes the Carfax summary, owner count, and accident flags into postmeta on each VDP, SleekAI reads them like any other field. The bot summarizes the highlights honestly and links to the full report rather than trying to recite a 14-page Carfax in chat. If a vehicle has a branded title, the bot surfaces that flag explicitly rather than burying it.

It quotes ranges from your published finance partner pages with the standard disclaimers. If you publish typical APR bands by credit tier (excellent, good, fair, poor) and down payment requirements by lender, the bot quotes accordingly. It does not invent APR numbers or down payment thresholds, and the instruction is explicit that all quotes are subject to credit approval, verified income, and F&I review.

SleekAI reads from WordPress, so if your inventory feed flows from VinSolutions, DealerSocket, vAuto, or any IMS into a WordPress custom post type or your VDP plugin, the bot reads from there. Common workflows mirror IMS data via a sync plugin or a custom feed importer. The bot doesn't replace your IMS, it consumes the data your IMS already publishes to the site.

Yes, and explicitly so. If your inventory marks a vehicle as branded, salvage, or rebuilt title, the bot surfaces that flag in the first response, not after the customer asks. Customers who can't finance branded titles learn that in chat. Customers who specifically want a salvage rebuild for a budget build get routed to those listings. Hiding the flag at the chat stage just creates refund arguments at the F&I desk.

Yes. If your dealership publishes Spanish content (Spanish VDP descriptions, bilingual sales staff, Spanish finance partner pages), SleekAI reads whichever language is active. The bot can detect message language and respond in Spanish, which matters in markets where used car inquiries are 40-60% Spanish-speaking. Multibot can scope a Spanish-language bot to specific URL paths or pages if you want a dedicated experience.

If your VDP includes recall status (open recalls outstanding, completed recall work, or no recalls), the bot surfaces it. The bot won't quote NHTSA recall details directly, but it will tell the customer whether a unit has open recalls and link to the recall lookup if your site has one. Pre-sale recall remediation is a common dealership policy, and the bot can quote that policy from your published pages.

It describes your trade evaluation process and routes the customer to it. Used car dealers typically use KBB Instant Cash Offer, in-person appraisal, or a photo-submission flow. The bot quotes your process and what the customer should bring (title, registration, service records), but it never invents a specific trade value. The actual appraisal happens with the used car manager because mileage and condition variability is too high for a chatbot to estimate.

Yes. If your state allows as-is sales and your inventory marks specific units as as-is (no warranty), the bot surfaces that flag during the conversation. Customers expecting warranty coverage on an as-is unit learn that in chat instead of at signing, which is a common refund flashpoint at used car lots. Vehicles sold with a limited dealer warranty or a 30-day powertrain warranty have those terms surfaced from your published warranty page.