Yes. Thrive Architect saves a mix of HTML and Thrive-specific wrappers inside post_content, and the Wizard parser recognises the common Thrive section and block patterns. The chatbot's system message receives clean section text plus structured arrays for feature lists and pricing tables, instead of raw markup.

Yes. The parser breaks the page into sections in document order, so the prompt can reference any section the visitor asks about. For very long pages, the Wizard can chunk sections and send only the ones most relevant to a query, similar to how vector retrieval works at a smaller scale.

Yes for Thrive's built-in pricing-table blocks. Each row, including label, price, and features, comes through as a structured array the model can quote. Custom pricing tables built from generic columns and lists can also be mapped through the parser config so they appear as structured data.

It can read the Thrive Architect content that hosts the quiz, but quiz logic and answers live in Thrive Quiz Builder's own tables. Map those tables through the Wizard if you want the bot to reference quiz outcomes, otherwise stick to the static page content.

The parser runs only on chat send, not on every page view, so there is no impact on the page's load or conversion performance. The chatbot itself loads as a lightweight widget, and SleekAI's data source layer queries the database only when a visitor opens the chat or sends a message.

Yes. Display conditions on URL pattern, post type, and user role let you run a separate bot per step: a lead-magnet bot on the opt-in page, a sales bot on the offer page, and a thank-you bot post-purchase, each with its own system prompt and data sources.

Thrive includes some dynamic elements like countdowns. SleekAI can be told that a countdown is in effect via a custom variable in the system message, so the bot acknowledges urgency without inventing a specific deadline. The actual countdown still runs in the page itself.

Yes, as long as the page content sits in post_content. Thrive Theme Builder templates can also be parsed if the relevant template content is exposed. For dynamic theme parts, expose them through the Wizard as separate data sources so the bot has access to consistent fields.