Yes. Each directory type's custom fields are picked up automatically, so the bot adapts to whatever schema you have configured. Whether you use one type or run several side by side, the chatbot reads each listing's specific fields without per-vertical setup. Custom directory types created through the Directorist UI work the same way as the built-in ones.

Yes. Country, region, city, and neighborhood taxonomies all flow into the bot context for accurate local matching. Visitors can ask broad ('anything in Lisbon') or narrow ('apartments in Marvila') and the bot resolves the right level of the hierarchy. Multi-level locations propagate up and down so a query at any level returns matching results.

Featured status is a meta field. You can configure the system prompt to weight featured listings higher when the visitor's request is ambiguous, mirroring how Directorist itself sorts. For specific queries, the bot still returns the best match regardless of featured status, so featured weighting acts as a tiebreaker rather than overriding relevance.

SleekAI uses vector search via OpenAI Files for large datasets, so only relevant listings are pulled into each conversation. That keeps token costs predictable even on directories with tens of thousands of listings across multiple types. The vector store updates as listings change, so freshness is maintained without manual rebuilds.

Yes. SleekAI works with WPML, Polylang, and TranslatePress, and the AI itself can answer in any language the model supports. If your directory has translated listings, the bot serves whichever locale matches the visitor's URL. AI-side language switching also handles cases where listings exist in only one language.

Locally in WordPress, with page URL, user info, and full transcript. You can export logs to spot popular searches and content gaps. Common unanswered queries are direct feedback on listing inventory; those are also a sales signal for outreach to potential paid listings if you operate a marketplace model.

Standard Directorist permissions apply. Listing owners see their own listings in the dashboard and the chatbot only exposes publicly visible field data to visitors. Private fields stay private. If you want listing owners to query their own data conversationally, a separate scoped chatbot on the dashboard side handles that without exposing it to visitors.

Expired listings drop out of context automatically, so the bot does not surface businesses whose paid package has lapsed. The cycle runs on the same schedule as Directorist's own status updates, so removals propagate within minutes. If you want to keep expired listings in the bot's context for historical queries, that can be configured per directory type.