Yes. SleekAI reads the rendered template output, so single CPT, archive, and section templates all become part of the bot's page context. Whether you've used Bricks' single-CPT template targeting a specific post type or its global page templates, the rendered HTML is what the bot consumes — no special integration per template type.

Yes. Tags are resolved on the server before the page is read, so the bot sees real ACF and meta values rather than placeholders like {acf_completion_date}. This means the bot can answer questions about specific field values — "when was this completed" returns March 2024 because that's the resolved value of the field on this post.

The widget script is asynchronous and small. The OpenAI call only happens when a visitor opens the chat, so PageSpeed scores aren't affected for non-interacting visitors. For Bricks sites optimized down to the millisecond, this matters — the chatbot doesn't undo render-blocking optimizations or inflate the JS bundle for visitors who never interact.

Yes. Multibot plus 28+ display conditions makes it easy to assign distinct chatbots to specific CPTs, archives, or roles. So projects can use a project-detail bot, products can use a product-spec bot, and the homepage can use a general site assistant — each with its own system prompt tuned to that template's content.

No. SleekAI reads the page live, so any change you publish in Bricks is reflected on the next message. If you update an ACF field on a project — say, change the architect credit — the next chatbot conversation about that project gets the updated value. There's no embedding step, no document upload, no scheduled sync.

Yes. The JS API exposes open, close, and send-message methods you can wire to any button element in Bricks. So a custom CTA button on a project page can launch the bot pre-loaded with a question like "tell me about this project," and the conversation starts in context. Bricks code blocks make this straightforward to wire up.

Yes. Whatever the query loop renders is part of the page output, so an archive template using a query loop to display project cards exposes those cards' content to the bot. The bot can then answer aggregate questions like "how many residential projects do you have" from the rendered list, scoped to the current archive's query.

Yes. WordPress user roles, Bricks-specific roles like "Bricks editor," and any user meta — including ACF user fields — are available as context. So a logged-in member viewing a member-only section can get answers personalized to their account, while an anonymous visitor on the same template gets the public version.