Yes. Any custom field you add through GD's field manager is available to the chatbot as a named context variable. Standard fields like hours, phone, and website are included by default, and the field selector in SleekAI lets you choose which fields each chatbot can see using a checkbox UI.

Yes. GeoDirectory's CPTs (gd_place, gd_event, etc.) are all supported, and you can scope the bot to specific CPTs with display conditions. Run one bot for restaurants and a separate bot for events, or use a single chatbot that knows both and routes based on the visitor's question.

Yes. Average ratings and review counts flow into the context so the bot can rank or surface top-rated listings. Individual review text is also indexable as context, so the bot can mention recurring themes in reviews when relevant, like consistent praise for a specific dish or complaints about wait times.

If you sell paid listings, the package level is a meta field. The bot can include or exclude listings based on package, although typically all active listings are included. The system prompt can be tuned to weight featured or premium listings higher when the visitor's request is otherwise ambiguous, similar to how the directory itself sorts.

For large datasets, SleekAI uses OpenAI Files vector search so only the most relevant listings are pulled per question. That keeps token costs predictable even on directories with tens of thousands of entries, and answers stay fast. Listings are re-indexed when they change, so the vector store stays current without manual rebuilds.

Yes. All conversations are stored in WordPress admin with the page URL, query, and matched listings, perfect for spotting demand gaps. Export to CSV to find queries that returned no useful matches; those are direct feedback on what your directory should add. Common unanswered queries are also a sales signal for outreach to potential listing customers.

Yes. The hours field is part of context and the bot can compare against the current time when answering. Mention 'open now', 'open this Sunday', or 'open after 9pm' and the bot filters accordingly. Time zones are taken from the WordPress site setting unless your listings store their own time zone meta.

Yes. SleekAI is compatible with WPML and Polylang, so a directory with translated listings can serve answers in the visitor's language. The bot reads whichever locale matches the visitor's URL and replies accordingly. AI-side translation also handles cases where listing content exists in only one language.