Submissions live in two tables created by the plugin: wp_jet_fb_records holds one row per submission with form ID, status, user ID, and timestamps, and wp_jet_fb_records_meta holds one row per field value linked back to the record. SleekAI reads both, so the bot can quote a specific submission and the individual values stored against it without scraping any UI.

Yes. Map the current user ID into a variable in the Wizard and the system prompt can resolve the user's most recent submissions, the status of an in-progress application, and any specific field they filled. The Wizard handles the join from wp_users to the records table, so no SQL is required to expose user-scoped data to the prompt.

Yes. JetFormBuilder uses macros like %CURRENT_USER_META% and %POST_META% to inject dynamic values into form fields and notifications. SleekAI resolves the same macros so the bot can reference values like the user's prior order total or a preset field, useful when you want the bot to confirm what the form already prefilled before submission.

Yes. Multi-step forms still write to the same records and meta tables, with step completion tracked in field meta. The bot reads the in-progress record and can quote which steps are done and which fields remain, useful for applicants who pause and come back later to finish a long submission with the bot guiding them.

Yes. Multibot mode runs several chatbots on one site, scoped by URL pattern, post ID, or page template. A common setup is one bot per high-stakes form, with its own system message that knows the form's field names, conditional logic, and validation rules in detail rather than a single generic bot trying to cover every form on the site.

Yours. SleekAI is bring-your-own-key, so message costs are billed directly by your provider with no SleekWP markup. Use OpenAI, Anthropic, Google, or OpenRouter, and pick a fast model for routine form help and a stronger one for complex eligibility or status reasoning under the same chatbot without changing the integration.

Only what you map. The Wizard exposes specific fields and specific record columns rather than dumping the whole record. You decide whether the bot sees document file paths, internal admin notes, payment IDs, or any sensitive field, and the rate limit plus guideline filter prevent prompt-engineered attempts to coax out unmapped data through chat.

Yes. If your JetFormBuilder forms write into JetEngine custom content types or relate to other JetEngine entities, the Wizard can also map those CPTs and their relations. The bot can follow an application record into the linked candidate profile, the linked vacancy, and the linked hiring manager when the schema models things that way through the broader Crocoblock stack.