JetTricks adds visual effects like sticky sections, parallax, tooltips, and unfold blocks to Elementor pages. It does not introduce a custom post type or a custom table. The data your visitors actually see comes from standard sources: wp_posts, wp_postmeta, taxonomies, and JetEngine fields when you use them inside the same templates.

SleekAI's data sources map those fields into the chatbot prompt. The bot knows the current post's title, content, featured image, primary category, and any meta the template renders, plus any JetEngine custom fields or relations the page builder pulls in. That means a tooltip on a service page and the chatbot on the same page agree on what the service is, what it costs, and what is in stock.

Display conditions scope each bot by post type, taxonomy term, user role, logged-in state, and URL pattern, so a long landing page wrapped in JetTricks effects gets its own bot, a JetEngine listing has another, and the blog uses a third. Every conversation is logged with the model name, token usage, and origin page, so editors can spot questions that JetTricks effects are not answering visually.

JetTricks pages are usually long and visual. Sticky sections, parallax, unfold blocks, and tooltips reward the eye but punish the visitor in a hurry. Most pre-sales questions are short: what does this cost, what is in the warranty, how is this different from the cheaper one, where is the testimonial I read about.

Scrolling through three screens of beautiful design to find that information is a fast way to lose the visitor. A generic chatbot makes things worse, because it knows nothing about the page underneath the effects. It invents prices, contradicts the warranty card, and points nowhere useful.

The underlying data already lives in WordPress. Post content, postmeta, JetEngine fields, taxonomies, all of it is structured. SleekAI maps the relevant fields into the chatbot prompt with point and click data sources, so the bot answers with the exact numbers and terms the page renders.

Per-template display conditions let you run a bot per landing page, per JetEngine single, and per listing, each scoped exactly where its system message makes sense, and each running on a key the site owner controls.