No. SleekAI works with the standard Beaver Builder plugin and also takes advantage of Beaver Themer layouts when available. Pro features and Themer templates simply add more context surfaces for the bot to read, but the core page-aware behavior works on the free Beaver Builder plugin too. There's no Pro-only requirement on either side.

Yes. Any module that renders HTML on the page is part of the context, including third-party Beaver Builder add-on modules from PowerPack, Ultimate Addons, and others. SleekAI doesn't need a special integration per add-on — it reads whatever the page renders, so any module that produces visible output produces context for the bot.

Yes. Display conditions let you exclude specific Beaver Builder templates, page IDs, post types, or user roles. So if you want the bot on service and pricing pages but not on the legal templates or thank-you pages, you set the conditions accordingly. Multiple bots can be configured with different scopes for different parts of the site.

The bot reads the live page each time, so updates appear in the next conversation without any retraining or sync. If a client edits the services row in Beaver Builder this morning, the chat reflects it this afternoon — no document to update, no chatbot training step to repeat. The page is the single source of truth.

Yes. Colors, fonts, position, avatar, welcome messages, and preset prompts are all configurable, and there are CSS hooks for deeper styling. Agencies maintaining brand kits per client can configure widget styling to match the global colors set in Beaver Builder, so the chat doesn't look bolted on. The widget can also launch from a custom button rather than a permanent floating bubble.

Every chat is logged with the page URL, user details, and full transcript inside WordPress admin. Logs are searchable and exportable, which makes them useful for both agency-side audits and client-side reporting. Patterns in the logs frequently surface page-copy gaps — questions that come up repeatedly indicate content that should probably be on the page itself.

Yes. Saved Beaver Builder rows and modules render the same way on every page that uses them, and the bot reads whatever's rendered. So if a saved CTA module appears on twelve service pages, the bot has access to its content on each one. The saved-template structure in Beaver Builder doesn't change the chatbot's behavior — it reads the output, not the source.

Yes. SleekAI works on WordPress multisite installations, and each site can have its own chatbot configurations and logs. For agencies running a multisite hub for client microsites, this means each microsite has its own page-aware chatbot scoped to that site's Beaver Builder content, with no cross-bleeding of context.