Blocksy keeps most of its configuration inside theme_mods_blocksy: header builder rows with their items, footer rows, color palettes, content area layout, and per-CPT type settings. Blocksy Companion adds the ct_content_block custom post type with conditional rendering rules in postmeta, plus extensions like the popup builder, the mega menu, and the custom dashboard. A generic chatbot sees none of that, so a question about the off-canvas drawer or a hooked content block produces a guess at best.

SleekAI maps the relevant Blocksy options and the ct_content_block posts into named variables the system message can reference at request time. Display conditions scope each bot to specific post types, taxonomy terms, user roles, logged-in state, or URL patterns, so a help bot can live on the docs side while a marketing bot handles the homepage. Conversation logs land in WordPress with the model, token usage, and origin URL on every message.

Most Blocksy sites also run WooCommerce or a forms plugin like WS Form. SleekAI reads those tables in the same chatbot, so the bot that explains your mega menu can also confirm a product variation or a recent order. Bring your own provider key and the bot stays under your control end to end.

Blocksy attracts site owners who like decisions exposed in a clean customizer. Header builder, footer builder, content blocks, palettes, and per-CPT layout settings all live under theme_mods_blocksy or the ct_content_block post type. That makes Blocksy easy to customize and very hard for a generic chatbot to talk about.

The bot does not know which row is sticky, whether the cart icon shows on mobile, or why a popup appeared after fifty percent scroll. SleekAI closes that gap by mapping those exact options into the chat prompt with variables that resolve at request time. The result is a chatbot that can answer header, footer, popup, and layout questions from real customizer values rather than guesswork.

Add WooCommerce, a forms plugin, or a docs CPT to the same data source list and the bot covers both layout and content with one widget. The site owner brings their own provider key, owns the conversation logs inside WordPress, and can swap models when their workload changes. That is the kind of bot a Blocksy site deserves and the kind that generic widgets cannot deliver on this stack today.