Yes, through the MailerLite API and what the WordPress integration exposes. SleekAI reads the matched subscriber's groups, custom fields, and recent campaign engagement, then injects the selected fields into the prompt. You decide which fields enter context, so unrelated fields stay out while name, group, and last clicked campaign flow through.

Two signals. Logged-in WordPress users whose email matches a MailerLite subscriber load automatically. Separately, tracked campaign links can pass a subscriber identifier that SleekAI uses to load the record. If neither signal is present, the visitor stays anonymous and no MailerLite context enters the prompt.

Indirectly. The bot can describe the next step and fire a webhook that performs the group add or field update through MailerLite's API. Letting the bot write directly would bypass double opt-in and automation entry rules, which is why SleekAI guides into your existing workflows rather than emulating them.

It works with the current MailerLite API. Accounts on Classic have a separate API; if you are still on Classic, point SleekAI at that endpoint. The data shapes differ slightly between Classic and the new platform, so map the fields accordingly. The bot reads whatever your account version exposes; SleekAI does not require one or the other.

Yes. SleekAI's multibot feature runs separate bots with their own prompts and display conditions on the same install. A typical pattern is a public bot for cold traffic focused on plan or product education and a group-member bot that opens with the subscriber's name and last campaign reference.

Inside WordPress, with full session history per chatbot, model name, token usage, and page URL. Creators review the logs to refine the system prompt and to feed recurring questions back into the next launch campaign. Logs live on your site; the LLM provider sees only the request payload at inference time.

Only if the code is still in the prompt. SleekAI does not have a campaign-expiry concept; it answers from whatever is loaded. Maintain an active-offers block in the system prompt and rotate codes when launches end. Once the code is out, the bot stops quoting it on the next request.

Yes. MailerLite's subscriber status (active, unsubscribed, bounced) is part of the record SleekAI reads. Exclude unsubscribed subscribers from the lookup or strip personalization for that group before exposing field history. The bot honors the deliverability and consent rules your forms and automations already enforce.