No. Tidio keeps doing what it does: live chat, multi-channel messaging, agent inbox, and the Lyro AI features inside its console. SleekAI sits one step earlier and handles routine WordPress and WooCommerce questions in-page so fewer of them reach the Tidio queue or burn Lyro AI messages.

Two patterns. The simpler approach collapses the SleekAI widget and opens the Tidio widget on the same page with a first message pre-filled summarising the chat. The more integrated path is a webhook that calls Tidio's API to create a conversation with the transcript attached, so the agent sees full context inside Tidio.

Lyro is a solid AI layer inside Tidio, but it lives in the Tidio console and bills per AI-resolved message. SleekAI lives in WordPress, reads your post types and WooCommerce data directly, and runs on a model API key you own. For sites where most pre-sales answers depend on live WP data, that grounding plus BYO-key pricing is usually the cheaper and more accurate setup.

Yes. SleekAI reads variation data through the WooCommerce data layer, so a question about a specific size or color returns real stock numbers. For orders it reads either legacy post-based storage or HPOS via wc_orders, so logged-in customers can ask about their own order without breaking when a store flips on HPOS.

SleekAI is bring-your-own-key. Plug in OpenAI, Anthropic, Google, or OpenRouter and pick the model that fits the tone and budget. A cheaper model handles routine product Q&A; a stronger model handles refund-policy nuance and ambiguous returns triage before either reaches Tidio.

Inside WordPress, with model name, token usage, page URL, and (optionally) the matched WordPress user attached per session. You can push transcripts into Tidio as a note when a handoff happens, so durable logs live on your site and Tidio gets just the slice it needs for the agent.

Yes. SleekAI's display conditions match post type, taxonomy term, user role, login state, and URL pattern. A common setup is a WooCommerce product-page bot, a docs-and-policy bot on info pages, and Tidio picking up handoffs from either. Multibot keeps the system prompts separate and the prompts tight.

SleekAI's surface is the WordPress site. Tidio handles email, Messenger, and Instagram channels through its own infrastructure. When a chat handoff happens, the conversation enters Tidio and your agents respond through whichever channel Tidio is configured for, including those non-web surfaces. SleekAI does not touch those channels directly.