No. The free ACF plugin works. ACF Pro features like repeaters, flexible content, and options pages are supported when present, and the chatbot adapts to whatever fields exist on the current post. If you upgrade to Pro later, the additional field types appear in context automatically without reconfiguration.

Yes. Site-wide options pages can be configured as global context that every chatbot can use. This is useful for company info, default policies, or shared data that should be available regardless of which post the visitor is reading. ACF Pro options pages and any sub-pages you have configured work the same way.

Yes. The field selector lets you whitelist or blacklist fields per chatbot, and any field marked private in ACF is excluded by default. For sensitive data like internal notes, contractor rates, or unpublished outcomes, that exclusion is automatic. You can also override on a per-chatbot basis if a specific bot needs broader access for internal users.

Both work. The bot follows the relationship to the linked post and includes its key fields as nested context. So a project page with a 'project_lead' post object pointing to a team member entry exposes the team member's name, role, and bio as nested data the bot can reference. Multi-post relationships work the same way, returning arrays of linked entries.

Nested repeaters serialize as nested arrays. The system prompt can reference rows like {project.tasks.0.title} to pull individual values, or iterate over the full array. Two or three levels of nesting work fine; deeper nesting is technically possible but adds prompt complexity, so flatter structures usually give better answers.

Field reads are cached per request and the AI call is async, so visitor-facing performance is unaffected. ACF's own caching applies at the database layer; SleekAI just reads the resolved values. For pages with very large field groups, pre-loading via the field selector reduces serialization time, though most sites do not need the optimization.

Not directly through the public chatbot. SleekAI's focus is conversational answers from existing data. If you want write access, the JS API can fire custom JS events that you wire to ACF actions or REST endpoints, but that is a custom implementation rather than a built-in feature. Most use cases are read-only Q&A from existing structured content.

Yes. ACF blocks render server-side, so their output is part of the page context just like any other block. The bot reads the rendered block content along with the underlying field values, so questions about block-driven content get accurate answers. Block-level field groups follow the same per-bot access rules as page-level field groups.