Yes. Fluent Forms keeps forms and submissions in dedicated tables, and SleekAI can be configured to read both as data sources. The system message exposes form names, fields, and recent entries as variables so the bot has structured data to work with rather than the rendered HTML of the entries screen.

Only if you set it up that way. Display conditions can lock the entry-reading bot to administrators, editors, or any custom role, and SleekAI also supports capability checks. Any public widget on the same site is a separate chatbot under multibot, with its own data sources and no link to submissions.

Yes. Fluent Forms stores Pro field values in the same submissions row as core fields, so SleekAI reads them with no extra configuration. Conditional logic, repeater fields, and signature widgets all surface as part of the submission record the bot can reference.

Push older or archived submissions into an OpenAI Files vector store of up to one gigabyte per file and let the assistant retrieve only the entries relevant to the question. Live entries can still be served from the data source, so today's metrics stay real-time while history goes into retrieval.

Yes. SleekAI's multibot feature supports multiple chatbots per page, each with its own system message, model, data sources, and display conditions. A typical setup is one public help bot scoped to landing pages and one admin bot inside WP Admin, with no shared access.

Bring your own key for OpenAI, Anthropic, Google, or OpenRouter. Usage and billing stay on your provider account. Each chatbot can pick a different model, so the campaign-reporting bot can use a stronger model than the lightweight public form-help one.

Yes, if your forms capture UTM or referral fields. Fluent Forms stores hidden inputs alongside visible fields, and SleekAI reads them as part of the submission record. The bot can break entries down by UTM source, medium, or campaign and compare a window against an earlier baseline.

Yes. Multi-step forms still write to a single submissions row in Fluent Forms, so the bot sees the full set of answers regardless of which step a value came from. Conditional fields that were never shown simply have no value, which the bot handles like any other empty field.