No. The free Connections plugin is enough. Pro fields are also supported when present, since SleekAI reads any custom field exposed on the entry. If you upgrade to Pro later, the additional fields appear in context automatically without reconfiguration. The chatbot adapts to whatever fields exist on each entry.

Yes, but only for fields that are publicly visible on the directory page. Private fields are excluded automatically, following the same privacy settings the directory itself applies. If your directory restricts phone numbers to logged-in users, for example, the bot does the same. There is no path for the chatbot to leak data that is hidden from the page.

Yes. Display conditions support showing the bot only on directory pages, single entry pages, or specific URL patterns. The widget stays hidden everywhere else, which keeps the rest of the site free of clutter. For multi-departmental directories, scope can be set per department archive too.

Yes. SleekAI uses vector search via OpenAI Files for large directories, so only the most relevant entries are pulled per question. That keeps token costs predictable and answers fast even for organizations with thousands of staff or members. The vector store refreshes as entries change, so personnel updates propagate within minutes.

Photos are referenced by URL in the listing context. The bot can include image links in answers, and the widget can render avatars alongside text. Image hosting is whatever Connections or your media library uses; SleekAI does not copy or store photos separately. Privacy settings on photos are respected the same way as other fields.

Yes. Each conversation is stored in WordPress admin with the search and matched entries for review. For internal directories, this is useful for spotting which colleagues or departments get asked about most. For external directories, the logs show what visitors are looking for, which often reveals gaps in how staff and program areas are described in bios.

Yes. Connections supports both individual and organization entry types. The bot reads both, so a query about an organization can cite the entry plus any staff members associated with it. If your directory uses categories or custom fields to link staff to organizations, those relationships flow into context as well.

Yes. If your directory restricts certain entries or fields to logged-in users or specific roles, SleekAI follows the same rules. A logged-in user gets the broader context their role allows; a public visitor gets only public data. The chatbot does not bypass any access controls Connections has configured.