Yes, and it is hidden by default. The widget renders with your logo, your copy, and your colours in admin, and there is no 'Powered by' badge to remove on a paid tier. If you want to credit SleekAI you can add a footer string in the chat settings, but that is opt-in rather than the other way round.

Yes. The Multibot feature lets you run different widget instances on different templates or audiences, each with its own system prompt, model, and knowledge sources. A typical setup runs a sales bot on landing pages, a support bot inside docs, and a quieter post-sale bot on the account area, all powered by the same plugin.

Yes. The widget exposes open, close, sendMessage, and an event bus you can subscribe to for chat-start, message-sent, and conversion-style custom events. That makes it straightforward to trigger the widget from a hero CTA, fire GA4 events when a chat begins, or open the bot pre-loaded with a question from a docs sidebar.

The widget itself is JS-driven because the chat experience needs streaming responses and event handling. For visitors with JS disabled, the recommendation is to fall back to a regular contact form on the same page so you do not lose the lead. SleekAI does not block the rest of the page from rendering when JS is off.

The widget uses IndexedDB by default with a sessionStorage fallback for browsers that block IDB. That means a user can reload, navigate, or come back later in the same session and pick up the thread without losing context. Conversation logs are also written to the WordPress database server-side so your team can review them from admin.

No. The 28+ display conditions let you hide SleekAI on pages where another widget already runs, or vice versa. A common pattern during migration is to run SleekAI on documentation while leaving the legacy human-staffed chat on pricing, then phase the old one out as confidence grows.

Yes. The JS API exposes a window-level method you can wire to any button or link click, optionally pre-filling the first user message. That turns a hero CTA like 'Ask a question' into a real chat-open instead of a scroll-to-form, and it lets you deep-link from email or docs into a chat that already knows what the user asked.

Yes. The widget reads the user's reduced-motion preference and disables the bubble bounce, slide-in, and message-shimmer animations when it is set. Focus management is preserved in both modes, and the widget never auto-opens unless you have explicitly configured a delay or scroll trigger in the admin.