No. SleekAI works with whatever JetEngine version you have. All meta types and relations are read automatically when present. If you upgrade or add modules later, the additional features appear in the chatbot context without reconfiguration. The free and Pro versions of JetEngine both expose data through the same WordPress meta APIs SleekAI uses.

Yes. Dynamic listings render server-side, so their output is part of the page context just like static content. Listing Grids, Sliders, and Inner Sections all work transparently. The bot reads whatever the visitor sees on the page, including content that was generated at request time from JetEngine queries.

Yes. One-to-many and many-to-many relations are followed and the related posts' key fields are included as nested context. This is what makes JetEngine sites genuinely conversational: a question about a project can include details about the linked client, team, and outcomes in one answer, rather than fragmenting the response across multiple lookups.

Filters do not matter for the bot since SleekAI works from the rendered page. Whatever the visitor sees becomes the context. JetSmartFilters reload listings via AJAX; SleekAI reads the current state, so a visitor who has filtered to remote courses gets answers about remote courses. The bot does not need to interpret filter UI, only the rendered result.

The JS API can fire custom JS events that you wire to JetEngine actions, but the bot itself focuses on conversational answers. For sites that want write access, like form submissions or status changes triggered from chat, that integration is a custom implementation. Most JetEngine chatbot use cases are read-only Q&A, where the visitor gets information and clicks a real button to act.

Yes. Every chat is stored in WordPress admin with the page URL, fields used, and full transcript. For JetEngine sites where data lives across many CPTs, the logs show which relations and fields visitors actually ask about, which is useful feedback for content modeling. Frequent unanswered queries often reveal missing relations or fields.

Per-bot field control is the main lever. For CPTs with dozens of meta fields, restrict each chatbot to the subset relevant to its purpose. SleekAI also uses vector search via OpenAI Files for sites with thousands of entries, so token costs stay predictable. The combination of field selection and vector search handles even the largest JetEngine deployments.

JetEngine Forms render as standard HTML on the page, so their structure is part of the bot context. The bot can describe what a form asks for and link to it, but submitting the form is the visitor's action through the standard JetEngine flow. For chat-driven submission you would need a custom integration via webhooks or the JS API.