JetPopup is Crocoblock's popup builder for Elementor. Popups are stored as a custom post type called jet-popup, with templates, triggers, and display conditions saved as postmeta on each popup post. A typical site has 10 to 30 popups: exit intent, scroll depth, time delay, cart abandonment, and category-specific offers. They all show the same canned form to whoever crosses the trigger, and conversion rates rarely move past 2 to 4 percent.

SleekAI sees the same popup data JetPopup itself uses. The plugin's display conditions, trigger settings on the jet-popup CPT, and per-page postmeta become structured context for the bot. When a visitor opens the chat instead of the static popup, the bot already knows which campaign is active, which product or article the visitor is on, and what fields the form would have collected. It writes the resulting lead into the same wp_postmeta entries JetPopup would have written to, so existing JetEngine listings and reports keep working.

Generic chatbots cannot see any of this. They sit in a fixed corner widget, unaware that there is an exit-intent flash sale or a category-specific lead magnet running on the page. Sites that try to layer two tools end up with overlapping triggers, confused visitors, and double-counted conversions. SleekAI consolidates the two into one surface that respects the JetPopup rules already configured.

JetPopup is one of the most-installed parts of the Crocoblock suite because static popups are the easiest way to push a single CTA on a single trigger. The trade-off is that every visitor sees the same overlay, no matter what page, taxonomy, or customer segment they belong to. Conversion rates on exit-intent popups tend to settle in the 2 to 4 percent range, even on well-targeted campaigns.

Replacing the static form with a short conversation tends to double or triple that, because the bot can reference the active campaign, the product, and the visitor's recent behavior in its opening message. That is only possible if the bot can actually read the JetPopup configuration, the page context, and the JetEngine CPT data behind it. SleekAI does all of that out of the box.

It runs as a standard WordPress plugin, uses the same wp_postmeta tables JetEngine writes to, and inherits whatever display conditions JetPopup already enforces. There is no separate dashboard to learn, no second consent surface, and no parallel reporting stack. For Crocoblock-heavy sites, that means adding chat to popups is mostly a setup task, not a rebuild.

Existing JetPopup automations keep firing, existing JetEngine listings keep counting, and the only thing that changes from the visitor's perspective is that the form they used to ignore now talks back.