JetFormBuilder stores forms as the jet-form-builder custom post type with the form blocks inside post_content. Records live in wp_jet_fb_records and field values in wp_jet_fb_records_meta. Actions like email, redirect, and webhook are stored as form meta, and the optional payments add-on writes order rows into wp_jet_fb_payments with status, gateway, and amount. Generic chatbots cannot read any of that, so questions about a required field or a recent submission come back as a vague guess.

SleekAI maps JetFormBuilder posts, records, records meta, and payments into named variables for the chat system message at request time. Display conditions scope each chatbot by post type, taxonomy term, user role, logged-in state, or URL pattern, so a visitor-facing bot can answer field questions while an admin bot reports on today's submissions and recent payments inside the dashboard.

JetFormBuilder ships with Gutenberg blocks for fields and works with JetEngine and WooCommerce. SleekAI reads those tables too, so one chatbot can confirm a form field requirement, then check the visitor's last order or membership without juggling two integrations on the page.

JetFormBuilder is the form builder of choice on a lot of Crocoblock sites because it sits inside Gutenberg, integrates with JetEngine, and ships actions for email, webhook, payment, and post creation. The downside is that forms are exactly the place where a vague chatbot answer hurts conversion the most. A visitor asks if a phone number is required, what the next step is after submit, or how long the team takes to reply.

A generic bot guesses and the visitor abandons. On the admin side a builder asks for today's records or yesterday's payment totals and the bot says it cannot help. SleekAI maps the jet-form-builder post type, wp_jet_fb_records, wp_jet_fb_records_meta, and wp_jet_fb_payments into the chat system message at request time.

The public bot answers field, action, and policy questions from the real form. The admin bot reports on submissions and payments by date or by form. The merchant brings their own provider key, owns the logs, and picks the model.

That is the kind of form-aware AI a JetFormBuilder site has been missing and the kind a generic chatbot cannot deliver on top of WordPress without serious custom work today.