Yes, through the Brevo API and what the Brevo for WordPress integration exposes. SleekAI reads the matched contact's lists, attributes, and recent campaign engagement, then injects the selected fields into the prompt. You decide which fields enter context, so unrelated attributes and notes stay out while name, list, language, and last campaign flow through.

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

Indirectly. The bot can describe the next step and trigger a webhook that performs the list add or attribute update through Brevo's API. Letting the bot write directly would bypass automation entry rules and consent enforcement, which is why SleekAI guides into your existing workflows rather than emulating them.

Yes. The API exposes contacts, lists, attributes, and campaign engagement consistently across the Free, Starter, Business, and Enterprise tiers. SleekAI treats them identically because the data shape is identical. What differs is the automation depth available inside Brevo itself, not what the bot can read.

Yes. SleekAI's multibot feature runs separate bots with their own prompts and display conditions on the same install. A typical pattern is one bot for cold traffic focused on plan education and another for known contacts that opens with the contact's language, segment, and last campaign reference.

Inside WordPress, with full session history per chatbot, model name, token usage, and page URL. Marketing teams review the logs to refine the prompt and to feed recurring objections back into the next campaign copy. Logs stay on your server; the LLM provider sees only the request payload at inference time.

Yes. SleekAI reads Brevo's language attribute and injects it into the prompt, so the bot can match the contact's language on the first reply. The model picks the language from the system prompt and the user's first message. For predictable behavior, keep a language directive in the system prompt tied to the loaded attribute.

Yes. Brevo's opt-in status and blacklisted flags are part of the contact record SleekAI reads. Exclude blacklisted contacts from the lookup or strip personalization for that group before exposing list and attribute data. The bot honors the deliverability and consent rules your campaigns already enforce, not the other way around.