No, and it doesn't need to. The data the bot uses lives in your WooCommerce tables and in the plugin's WordPress options. SleekAI reads those, and the bot describes Klaviyo behaviour from configuration plus the order and customer history that Klaviyo itself synced from. Your Klaviyo private API key never has to enter the prompt.

If the visitor is logged in, yes, since their email maps back to a WooCommerce customer record and the list membership is reflected in the Klaviyo for WooCommerce metadata stored in postmeta and options. For anonymous visitors the bot stays generic and explains how lists are structured rather than guessing.

Klaviyo abandoned cart flows trigger on a Started Checkout event sent from the WooCommerce session. SleekAI reads the same session, so when a returning shopper asks why they got an email about their cart, the bot can describe the items, the timing, and any coupon that the next flow step is about to send.

No. The system message only references settings useful to a customer-facing bot, like flow names and list labels. The private API key stored in the plugin options is excluded from the variable mapping, and the rate limiting plus guideline filter on SleekAI's public bots block prompt-injection attempts that try to exfiltrate it.

You need a working Klaviyo account that is already syncing your WooCommerce store. SleekAI assumes Klaviyo is doing what it normally does on your tier. The chatbot itself runs on whichever model provider key you choose, so a low-volume store can pair a cheap fast model with the Klaviyo Free tier.

Out of the box the bot is read-only. If you want to add write actions, expose a webhook from your provider's API and call it from a PHP hook the bot triggers via tool use. Many stores prefer to keep the bot informational and let Klaviyo automation handle the actual sending.

Yes. SleekAI reads from the WooCommerce data layer, so the same field mappings work whether your store uses legacy post-based orders or High-Performance Order Storage in wp_wc_orders. The bot's answers about order status do not need to know which storage mode is active.

Yes. Multibot mode lets you run several chatbots on one site, and the display conditions can target user role, URL, and custom meta. If you tag a customer's WordPress user with a segment hint, you can match against that tag to show a VIP bot to high-value Klaviyo segments and a default bot to everyone else.