Yes. WPvivid stores backup history, schedules, remote storage configuration, and staging metadata in WordPress options and its own tables. SleekAI's data sources read those rows so the bot's system message exposes them as named variables. The wizard handles the mapping per site, no code required.

Not unless you configure it that way. Display conditions on user role, capability, logged-in state, and URL pattern keep the backup bot scoped to administrators inside wp-admin. Any public chatbot you run on the same site is a separate bot under multibot, with its own data sources and no access to WPvivid state.

Yes. The free WPvivid plugin writes the same kind of metadata to WordPress that SleekAI can read. Pro-only features, like advanced incremental backups or some additional remote destinations, persist their state locally too, so they map into the prompt the same way. The core flow works regardless of tier.

By default SleekAI is read-only against WPvivid state. It surfaces what exists and points at the right WPvivid screen for an action. If you want write actions, you can wire a custom PHP callback into a SleekAI tool, but most teams keep destructive operations inside the plugin UI where confirmations are explicit.

Yes. Conversation logging is on by default per chatbot, with user messages, assistant replies, model name, token usage, and page URL stored inside WordPress. For a backup bot, that audit trail matters: when a restore or staging push goes wrong, the team can see what the bot referenced.

Yes, for whatever WPvivid logs locally. Recent run status, error codes, and retry attempts all live on the WordPress side. Ask the bot to roll up the last week of backup attempts and it can summarise success rate, frequent failure points, and which destination most often dropped the upload.

A fast model handles routine reads like last-run timestamps and destination lookups. For longer prompts that triage a failed sync or compare configurations across two sites, a stronger model from OpenAI, Anthropic, Google, or OpenRouter gives better synthesis. SleekAI lets you pick the model per chatbot.

Each SleekAI install runs its own chatbots with its own data sources, so configuration is per site. You can export and import the chatbot config across sites and re-point the data sources, which suits agencies that want the same WPvivid-help bot across a portfolio.