Yes, through the GetResponse API and what the WordPress integration exposes. SleekAI reads the matched contact's lists, tags, custom fields, and autoresponder progress, then injects the selected fields into the prompt. You decide which fields enter context, so unrelated fields and notes stay out while name, list, tag, and current autoresponder step flow through.

Two signals. Logged-in WordPress users whose email matches a GetResponse 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 GetResponse context enters the prompt.

Indirectly. The bot can describe the next step and fire a webhook that performs the tag add or list move through GetResponse's API. Letting the bot write directly would bypass workflow entry rules and consent enforcement, which is why SleekAI guides into your existing automations rather than emulating them.

Yes. The API exposes contacts, lists, tags, fields, and autoresponder data consistently across MAX, Marketing Automation, Email Marketing, and free tiers, so SleekAI treats them identically. What differs is the feature depth inside GetResponse, like advanced workflows and AI campaign generation, not the data shape the bot reads.

Yes. SleekAI's multibot feature runs separate bots with their own prompts and display conditions on the same install. A common pattern is a public bot for cold traffic focused on webinar education and a contact bot that opens with the contact's autoresponder step and last campaign click.

Inside WordPress, with full session history per chatbot, model name, token usage, and page URL. Marketing teams review the logs to refine the system prompt and to update autoresponder copy where the bot kept needing to clarify. Logs live on your site; the LLM provider sees only the request payload at inference time.

Only if the session details stay in the prompt. SleekAI does not have a session-expiry concept; it answers from whatever is loaded. The pattern is to maintain an active-sessions block and rotate it as webinars finish. Once a session is out of the prompt, the bot stops offering it on the next request.

Yes. GetResponse's contact status, opt-in flags, and unsubscribed lists are part of the record SleekAI reads. Exclude unsubscribed contacts from the lookup or strip personalization for that group before exposing list and tag data. The bot honors the deliverability and consent rules your autoresponders already enforce.