No. SleekAI is configured to decline eligibility decisions on specific documents and consistently route those questions to the in-office examiner. The bot will state the published rules (identity-document tier, 90-day residency window, 12-month expiration tolerance) but will not say "yes you qualify" or "no you don't" based on what the visitor describes. The reason is that eligibility depends on the actual document, which the bot has not seen; the examiner has.

If your wait-time data is in WordPress (as ACF fields, custom post type, or an internal API the data-source wizard can read), yes. SleekAI reads it at request time and quotes per-office wait estimates. If your wait times come from a state-level vendor system not on the site, the bot can deep-link to that system rather than estimate. The bot does not invent wait times when the data is not available.

By default the bot deep-links to your existing appointment portal rather than booking in chat, because most DMV appointment systems run on state-level vendor stacks that should remain the source of truth. SleekAI can answer when slots release, which services require appointments, and how to reschedule, then hand the visitor to the portal with the right service preselected if the portal supports query parameters.

Yes. Real ID is the most common DMV question by volume and the bot reads your Real ID checklist page at request time, including the federally required document tiers and your state-specific acceptable documents. It states the rules clearly and declines to make a specific-document eligibility call. For visitors who do not need Real ID (passport-only travelers, non-drivers), the bot can also explain the standard license option.

Multibot scopes a separate bot to the CDL pages, with the medical certificate requirements, endorsement categories (hazmat, tanker, double/triples), and CDL-specific document checklist. The bot does not make medical-certification eligibility calls; that is the medical examiner's review. It points CDL applicants to the registered medical examiner directory and the office's CDL-specific appointment slots.

It reads the registration and title pages at request time so the bot quotes current fees, the document list (title, bill of sale, lien release, emissions if required), and the office windows that handle each service. For out-of-state titles or salvage titles, the bot points to the specialized intake counter rather than treating those as a routine flow, because those cases need additional examiner review the bot cannot substitute for.

Conversations log to your WordPress database with model name, token usage, page URL, and history. Retention is configurable to match your state public-records policy. There is no Sleek-hosted log. For agencies subject to FOIA or equivalent state laws, treat the conversation log the same way as web-form intake records and document the retention in records management.

Yes. Multibot lets each office have its own scoped bot embedded on its location page, with that office's hours, wait times, services offered, and any office-specific quirks (cash-only window, no walk-ins after 3pm, CDL Tuesdays). The bot embedded on the locations index can compare offices, while the bot on each location page focuses on that specific office's current state.