Yes. MailPoet stores everything inside WordPress: subscribers in mailpoet_subscribers, list mappings in mailpoet_subscriber_segment, segments in mailpoet_segments, and stats in mailpoet_statistics_*. SleekAI reads those tables for the matched subscriber and injects the selected fields into the prompt. You decide which fields enter context, so unrelated metadata stays out while name, lists, and recent engagement flow through.

Two signals. Logged-in WordPress users whose email matches a MailPoet subscriber load automatically. Separately, MailPoet's tracking parameters in newsletter links can identify a subscriber even if they never log in. If neither signal is present, the visitor stays anonymous and no MailPoet data enters the prompt.

Indirectly. The bot can describe the next step and trigger a WordPress action or REST endpoint that calls MailPoet's API to perform the list add. MailPoet owns the actual write, including double opt-in handling and segment rule evaluation. Letting the bot write directly would bypass those checks, which is why SleekAI guides into your existing flows.

Yes. The data tables are the same across Free and Premium; what differs is sending volume and advanced features inside MailPoet, not the data shape SleekAI reads. The bot can reference whatever fields exist on your install. Premium-only features like advanced segments simply produce richer segment rows the bot can read.

Yes. SleekAI's multibot feature runs separate bots on the same install with their own prompts and display conditions. A typical pattern is a public bot for cold traffic focused on signup and a subscriber bot that opens with the reader's name, last issue clicked, and current list memberships.

Inside WordPress, with full session history per chatbot, model name, token usage, and page URL. Editorial teams review the logs to refine the prompt and feed common reader questions back into the next issue's copy. Logs live on your site; the LLM provider sees only the request payload at inference time.

It can if old issues stay in the prompt. The cleaner pattern is to load only the current issue's content and a small history block of relevant past issues. Anything outside the loaded slice will not appear in the reply. As you publish new issues, rotate the prompt so the bot focuses on what is current rather than improvising from stale content.

Yes. MailPoet's subscriber status (subscribed, unconfirmed, unsubscribed, bounced) is part of the record SleekAI reads. Exclude unsubscribed subscribers from the lookup or strip personalization for that group before exposing list and engagement data. The bot honors the consent and deliverability rules MailPoet enforces, not the other way around.