Yes. Gravity Forms stores entries in gf_entry with values in gf_entry_meta, and SleekAI can be configured to read them as data sources. The system message exposes form metadata, recent entries, and counts as named variables, so the model answers from structured data rather than guessing.

Yes. The bot can see fields across every page of a Gravity form because Gravity Forms stores them under the same entry record, regardless of which page the value was captured on. That makes the bot just as accurate on a 12-page application as it is on a single-step contact form.

Yes. SleekAI's multibot feature lets you run separate chatbots on the same site, each with its own system message, data sources, and display conditions. A common setup is one admin bot reading entries inside WP Admin and one public bot answering pre-sales questions on marketing pages, with no shared data.

For high-volume forms, push older entries into an OpenAI Files vector store of up to one gigabyte per file. Recent entries stay live in the data source so questions about today still feel real-time, while history goes into retrieval and the prompt stays compact.

Not if you scope the bot with display conditions. Lock the entry-reading bot to administrators or a specific role and the widget is invisible to anyone else. Any public bot on the same site is a separate chatbot under multibot, with no access to gf_entry.

Yes. SleekAI ships with a JS API and a PHP embed, so you can launch the bot from a button, a hook, an admin notice, or a custom screen. That lets you wire entry summaries into a recruiter dashboard or a site-health page rather than only running it as a floating widget.

Yes. Uploaded files are stored as a value in gf_entry_meta, so the bot can list filenames per entry, surface a download URL when you have one, and reference how many uploads the latest applicant attached. The model never receives the file contents themselves unless you wire that up explicitly.

Yes. Gravity Forms keeps partial entries in a separate state, and SleekAI's data source exposes that as its own field. The bot can answer how many partial vs completed entries a given form had this month, useful for spotting drop-off in long applications or registration flows.