Yes, through the Constant Contact API and what the WordPress integration exposes. SleekAI reads the matched contact's lists, tags, and recent campaign activity, then injects the selected fields into the prompt. You decide which fields enter context, so private notes and unrelated lists stay out while name, list, and tag history flow through.

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

Indirectly. The bot can describe the next step and fire a webhook that performs the actual list add or tag application through Constant Contact's API. Letting the bot write directly would bypass consent and list rules, which is why SleekAI guides into your existing automations rather than emulating them. Constant Contact stays the source of truth for list rules and unsubscribe enforcement.

Yes. The API exposes contacts, lists, tags, and campaign engagement consistently across paid tiers, so SleekAI treats them identically. What differs is the feature set inside Constant Contact, like advanced automation and event marketing, not the data shape the bot reads. The bot can reference whatever the plugin and your account expose.

Yes. SleekAI's multibot feature lets you run one bot for cold traffic and another for list members on the same install, each with its own system prompt and display conditions. A common setup is a public bot for general FAQ and a member bot that opens with the contact's name, last list, and last campaign opened.

Inside WordPress, with full session history, model name, token usage, and page URL per chat. Marketing leads review the logs to refine the prompt over time and to feed common questions back into newsletter copy. Logs live on your site; the LLM provider sees only the request payload at inference time, not a stored copy of the conversation.

Only if outdated event details stay in the prompt. SleekAI does not have an event-expiry concept; it answers from whatever is loaded. The pattern is to maintain an active-events block and rotate it as workshops finish or sell out. Once the event drops out of the prompt, the bot stops offering seats it no longer has.

Yes. Constant Contact's unsubscribed and opt-in status are part of the contact record SleekAI reads. Exclude unsubscribed contacts from the lookup before exposing list and tag data, or strip personalization for that group. The bot honors the deliverability rules your forms and lists already enforce, not the other way around.