JetThemeCore is Crocoblock's theme builder. It lets you design every template part separately (header, footer, 404, archive, single CPT, taxonomy) and assign each one to specific conditions: post type, taxonomy term, language, role, URL pattern. Most JetThemeCore sites end up with 10 to 30 templates, each tuned for a specific surface.

SleekAI maps naturally onto that model. The chat widget is a standard Elementor widget, so it can be embedded in any JetThemeCore template. Display conditions on the template apply automatically to the chat, so a chat scoped to a course single CPT template only shows up on course CPT singles. Different templates can run different bots: a discovery bot in the shop header, a support bot in the docs single, and a checkout bot in the cart template. Each bot has its own system prompt and field whitelist managed in the SleekAI admin.

The bot reads the same data the template renders. JetEngine CPT fields, WooCommerce postmeta, WordPress user context, and any dynamic widget output flow into the bot's context as structured variables. That means a chat embedded in a JetThemeCore CPT single template can reference the current entry's fields by name, just like the dynamic widgets in the template do. There is no separate data layer to wire up.

JetThemeCore exists because the right answer to 'how should this page look' depends on what the page is. A product single should look different from a docs single, which should look different from a taxonomy archive, which should look different from a 404. The same logic applies to chat.

The right answer to 'what should the bot do here' depends on which template is rendering. A floating bot that runs the same prompt across every surface is a blunt tool: it has too little context on product pages and too much on policy pages, it ignores the entry the visitor is looking at, and it cannot scope to a specific CPT without custom code. SleekAI's per-template model fixes that.

Each template gets its own bot, with its own system prompt, its own field whitelist, and its own context shape. The visitor on a destination CPT single talks to a travel guide that knows the destination's fields and related entries. The visitor on a checkout template talks to a checkout helper that knows their cart.

The visitor on a 404 talks to a navigation helper that knows the site's menu tree. That separation makes chat feel native rather than bolted-on, because the bot is always scoped to the same thing the template is. For Crocoblock-heavy sites that already invested in per-template design, adding chat is largely a matter of dropping the widget into each template and picking a bot.