No. The free Pods plugin works. Advanced features like custom storage, components, and templates are also supported when present, with the chatbot adapting to whatever Pods features you have enabled. If you add components later, like the Roles & Capabilities or Pages component, those features remain transparent to SleekAI's field reads.

Yes. When you extend Post, Page, or User with Pods fields, those fields are picked up just like fields on Pods CPTs. This is one of Pods' main strengths, and SleekAI honors it. Extended User fields, for example, become part of the context for member directories or author archives without any extra setup.

Yes. Relationship fields resolve to the linked entry, and the bot can include the related post's key fields as nested context. Bi-directional relationships are supported too, so a query that starts on either side of the relationship can pull the connected data. The depth of nesting is configurable to keep prompt sizes manageable.

Templates render server-side, so their output is part of the page context. The bot reads whatever the visitor sees. Magic tags, custom template logic, and inline PHP all run as they normally would, and the resolved HTML enters the chatbot context. There is no separate template parsing step the bot needs to handle.

SleekAI uses vector search via OpenAI Files for large data sets, so only the most relevant entries are pulled into each conversation. That keeps token costs predictable even for sites with thousands of Pods entries across multiple types. The vector store updates as entries change, so freshness is maintained without manual rebuilds.

Yes. Every chat is stored in WordPress admin with the page URL, fields used, and full transcript for review. For specialty Pods sites where the data is the product, those logs are valuable feedback on what visitors actually ask. Common queries that returned weak answers often reveal missing fields or insufficient relationships in the model.

Yes. File fields return URLs and metadata, so the bot can mention attached PDFs or images in its answers. Color picker fields return hex values, which is mostly relevant for design or product sites. Other complex types like date and currency are formatted according to your Pods configuration when surfaced in conversation.

Yes, with one chatbot configuration per site. SleekAI runs at site level, so each site on a multisite network manages its own Pods, fields, and chatbot setup independently. If you want shared global context across sites, like a corporate-wide glossary, that can be loaded as additional knowledge files separately on each site.