Yes. FluentCRM stores contacts in fc_subscribers with custom fields in fc_subscriber_meta, lists in fc_lists, and tags in fc_tags. SleekAI reads them directly through the FluentCRM API and includes the matched contact's data in the bot's context. You choose which fields enter the prompt, so sensitive notes stay out while names, lists, and recent activity flow through.

Two signals. First, when a WordPress user is logged in and their email matches a FluentCRM contact, the contact loads automatically. Second, FluentCRM's tracked links set a cookie that identifies the contact, so a visitor arriving from a campaign click is recognized even if they never registered. If neither signal is present, the bot defaults to a stranger persona with no CRM context exposed.

It can describe what tags will be added and trigger a webhook or REST call you wire to a FluentCRM automation. The actual write happens through your existing automation so segment rules, double opt-in, and consent flags stay enforced by FluentCRM. Letting the bot write directly would bypass those rules, which is why SleekAI guides and your automations execute.

Yes. Pro features like advanced reporting and additional integrations live in the same database tables, so any field FluentCRM stores can flow into the bot context. The base SleekAI integration treats Pro and free identically; the difference is what data exists to expose, not what SleekAI can read.

Yes. Use SleekAI's multibot feature with display conditions on user login state, FluentCRM list membership, or tag presence. A common setup is one cold-traffic bot focused on plan comparisons and one warm-contact bot that opens with the contact's name, last list, and the campaign offer they were sent.

Inside WordPress, with full message history per session. Conversation logging lets sales managers review tone and accuracy, and is essential for tightening the prompt over time. Logs stay on your site; LLM providers see only the request payload at inference time, not a copy of the full history outside that turn.

Only if you keep expired campaign details in the prompt deliberately. Best practice is to load a small block of currently active codes and offers and rotate it on a schedule. When a code expires, take it out of the prompt and the bot stops quoting it. That keeps the bot from offering a Q1 deal in May because nobody removed it from the system message.

Yes. SleekAI only reads what FluentCRM has stored, and FluentCRM's consent and double opt-in flags are part of that record. If you exclude unconsented contacts from the lookup or filter for double-opt-in status before exposing list and tag data, the bot will only personalize for contacts who actually agreed. Treat this exactly as you would any other CRM read in your stack.