MailPoet stores subscribers, lists, and segments in its own database tables (wp_mailpoet_subscribers, wp_mailpoet_segments, and the link table between them). It also writes a mailpoet_woocommerce_purchases view that ties subscribers to WooCommerce orders. SleekAI's data-source wizard maps those tables and the related shop_order records into named variables, so the chatbot can reference the logged-in customer's lists, segments, and recent orders at request time.

That changes what the bot can do for an existing subscriber. Asked which newsletters they are on, it confirms the lists by name. Asked how to opt out of one without losing access to order receipts, it explains MailPoet's per-list unsubscribe flow. Asked which products they bought last month, it reads the WooCommerce order history and reads back the line items.

Display conditions scope the bot to logged-in customers or to specific MailPoet segments, multibot lets a public pre-sales bot run with a different system message, and conversation logs inside WordPress make every email-related answer auditable. SleekAI does not send email or write to MailPoet; it reads the tables that MailPoet already maintains and quotes the merchant's own data.

Email lists are full of confusion that a chatbot can clear up faster than a help-desk thread. Customers ask which lists they are on, how to leave one without losing receipts, and which products fit the preferences they already signaled by joining a particular segment. MailPoet has all of that data inside WordPress already: the subscriber row, the lists, the segments, the link to WooCommerce orders.

The data is just rarely surfaced where the customer is asking the question, which is usually the storefront, not the email footer. A SleekAI bot wired to MailPoet's local tables closes that gap. It reads the subscriber's lists by name, references their segment when making suggestions, and reads their order history without making them paste their email again.

It also stays honest about what only MailPoet should do: list changes go through the manage-subscriptions page, not the chat, which keeps consent records clean and avoids the worst-case 'remove me from everything' regret. Combined with multibot, segment-based display conditions, and conversation logging, the same install can run a VIP bot, a first-time-buyer bot, and a general support bot on the same store, all on an API key the merchant owns. The outcome is a smaller support queue and an email program that feels like part of the store rather than a parallel universe.