Yes. SleekAI reads the rendered HTML, so it works regardless of which Oxygen editor version produced the page. Whether you're on the legacy editor or Oxygen 4 with the new builder, the output is what the bot consumes. Migrating from one editor version to another doesn't require any chatbot reconfiguration — the page is still the source of truth.

No. They resolve to real values on the server before the bot reads the page, so it sees readable text rather than tokens. A shortcode like [oxygen data='acf_lead_time'] becomes "5 to 6 weeks" in the rendered output, and that's what flows into context. The bot reasons about real values; it never sees the shortcode syntax.

The widget loads async and only fires when a visitor opens it. There's no impact on PageSpeed for non-interacting visitors. For Oxygen sites where the build prioritizes Lighthouse scores and minimal third-party scripts, the chatbot adds a single async script and an opt-in interaction, not a render-blocking dependency.

Yes. Multibot plus display conditions lets you assign distinct chatbots to single, archive, and reusable Oxygen templates. So a product-detail template can use a product-spec bot with a system prompt tuned for material and shipping questions, while the homepage uses a general site assistant — each with its own scope and behavior.

Yes. SleekAI ships with a documented JS API for opening the bot, sending messages programmatically, and listening for events. So a custom button in an Oxygen template can launch the chat with a specific question pre-loaded, or the chat can be triggered by an Oxygen pop-up rather than appearing as a permanent floating widget. Code blocks in Oxygen make wiring this up straightforward.

Conversations are logged inside WordPress admin with page URL, user, and transcript so you can audit and improve prompts. Logs are searchable and exportable, which surfaces patterns — questions that repeat across many visitors usually indicate copy or template gaps that can be addressed in the build itself, not just in the chatbot prompt.

Yes. Oxygen pairs commonly with WooCommerce for product catalogs, and SleekAI reads WooCommerce product page output the same way it reads any other Oxygen template. Product attributes, variations, stock status, and price are all part of context, so a shopper asking about sizing or availability gets answers from the actual product record rather than generic e-commerce knowledge.

Yes. Reusable parts render their content as part of whatever page they're embedded on, and the bot reads the rendered output. So a reusable footer with contact details appears in context on every page that includes it, and a reusable testimonials section adds those testimonials to the bot's knowledge wherever it's used. The reusable structure is invisible to the bot — it sees the final rendered page.