Quform stores forms in quform_forms with the form structure as serialized data, entries in quform_entries with status and metadata, and per-field entry values in quform_entry_data. The structure covers field type, label, conditional logic, validation rules, and notification settings. Each entry references a form ID and has one row per submitted field value in the data table.

SleekAI's data sources map both definition and entry data into named variables. The visitor-facing bot knows the current form's fields with types, labels, and validation, so it can answer field-specific questions in plain language. The admin-only bot can summarise entries across forms, surface conversion patterns, and answer questions like "how many newsletter signups came from the homepage this week" without anyone exporting CSV.

Display conditions scope each bot by post type, taxonomy term, user role, logged-in state, and URL pattern. A landing page form gets its own bot tuned to that offer. An admin in the dashboard gets a different bot with broader data access. Every chat is logged inside WordPress with the model name, token usage, and origin page.

Forms decide whether a visitor becomes a lead. A confusing field, an unclear validation message, or a sudden new branch in conditional logic is enough to push a visitor away. The standard questions are predictable.

Why is this required, what does the validation actually want, what happens after I submit, why did this field just appear when I picked the previous option. A generic chatbot does not help. It invents validation rules, contradicts the post-submit flow, and suggests save-and-resume behavior that does not exist on this site.

The result is more abandoned forms and lost leads. Quform already stores the truth in structured tables. quform_forms holds the field definition and conditional logic.

quform_entries and quform_entry_data hold the submissions. SleekAI maps that into the chatbot prompt with point and click data sources, so the chat agrees with the form on every detail. Per-bot display conditions then let you run a visitor-facing form helper and an admin-only entries analyst from the same install, each scoped exactly where it earns its keep and each running on a key the site owner controls.