Yes. UpdraftPlus stores backup run history, schedule entries, and remote storage settings in WordPress options and transients, which SleekAI can be configured to read as data sources. The bot's system message exposes those values as named variables, so the model has structured data to answer with rather than guessing at backup advice. The wizard handles the mapping in a few minutes per site.

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 UpdraftPlus rows.

The bot can read whatever UpdraftPlus writes to your database, so anything visible to you in the Existing Backups table and Settings tab is fair game. Some advanced add-on data, like the Migrator's job history, only exists on Premium. The core flow of last run, schedule, and remote destination works regardless of tier.

By default, SleekAI is read-only against UpdraftPlus data. It surfaces state and points at the right Restore button. If you want write actions, you can wire a custom PHP callback into a SleekAI tool and have the bot call it under a tight capability check, but most teams keep destructive actions inside the UpdraftPlus UI where confirmations are explicit.

Yes. Conversation logging is on by default per chatbot, with user messages, assistant replies, model name, token usage, and the page URL stored in WordPress. For a backup bot, that audit trail matters: when a restore goes wrong, the team can trace which snapshot the bot referenced and why.

Per-site, yes, because each SleekAI install runs against its own database. Agencies that want a fleet view typically run the chatbot inside their own dashboard site and feed in a daily JSON export of backup status from each managed install, which SleekAI then queries as a single data source.

A fast model is fine for routine reads like last-run timestamps and schedule lookups. For longer prompts that explain why a backup failed and which retry strategy to try, a stronger model from OpenAI, Anthropic, Google, or OpenRouter gives more useful synthesis. SleekAI lets you pick the model per chatbot, so cost stays in line with the workload.

Each SleekAI install runs its own chatbots with its own data sources, so the configuration is per site. You can export and import the chatbot config across sites and re-point the data sources, which is useful when an agency runs the same backup-help bot across several client sites with the same UpdraftPlus setup.