No. Metorik is a reporting and segmentation tool with dashboards, exports, and email segments. SleekAI is a chatbot that reads WooCommerce data and answers questions about it. Many stores use both: Metorik for deep dashboards and segments, SleekAI for in-chat lookups and customer-facing answers powered by the same WooCommerce data underneath.

Yes. SleekAI reads from the WooCommerce data layer rather than direct SQL queries, so whether you run legacy post-based orders or High-Performance Order Storage, the bot can look up an order, its status, and its line items. Logged-in customers can ask about their own orders without you exposing the entire orders table to the prompt.

Yes if you map an aggregated view as a data source. SleekAI can read a computed summary (last week's orders, current month AOV, top products) from a custom database query exposed through the wizard. The bot then answers narrative questions against that summary, rather than reading every individual order on each request.

Yes. Display conditions support user role and URL pattern, so the admin bot only loads on /wp-admin pages and only for users with shop_manager or admin roles. The storefront bot runs on the public shop with no admin data access, both under multibot in the same install.

Yes if you map them. Refund records live on the order itself, and WooCommerce Subscriptions stores subscription state as its own post type. SleekAI can read both, so the bot can confirm whether an order was refunded and what next renewal a subscriber is on, with all the usual display-condition controls.

Those still live in Metorik and remain the right tool for outbound. SleekAI focuses on inbound conversation. A common setup is keeping Metorik for outbound segments and email automations, and using SleekAI on the storefront and admin for inbound Q&A grounded in the same WooCommerce data.

Inside WordPress, with user, model, token usage, and page URL on every conversation. Store leads can review the log to spot tone issues, recurring product objections, or admin queries that come up often and feed those back into the system message or the product descriptions.

Yes. Each chatbot under multibot uses its own provider and model. A fast model is fine for storefront product Q&A, while a stronger model helps with admin lookups that combine several data points. Each runs on your own provider key, so usage and billing remain on the merchant's account.