Yes. SleekAI reads any post type, including the recurring events and additional fields Pro adds. No special configuration is required. Recurrence rules are flattened into discrete event instances at index time, so 'next pottery class' returns a concrete date rather than a series description. Pro's additional venues per event and additional organizers are exposed alongside the primary ones.

Each recurrence is treated as a separate event instance, so the bot can answer 'when is the next yoga class?' with the next concrete occurrence rather than a vague 'every Saturday'. Past instances are filtered out via _EventStartDate. If Pro adds exclusions or modifications to specific instances, the bot honors them and returns the modified date or skips the excluded one.

Yes. SleekAI uses the _EventStartDate meta to scope context to upcoming events only, so visitors never hear about events that already happened. The filter runs at retrieval time, which means freshly past events drop out of answers without waiting for a re-index. Same-day events are kept until the start date passes, in case visitors are asking on the day.

Yes. tribe_venue and tribe_organizer are linked to events via post meta and pulled into the prompt alongside event details. The bot can quote venue address and organizer contact info, including any custom fields you have added to those post types. Multiple organizers, where Pro is installed, are all surfaced in the same reply.

If you store cost in event meta or use Event Tickets, SleekAI reads those fields and quotes the live price in conversations. Past prices are not retained, so a price change shows up in the bot's answer as soon as the meta updates. If Event Tickets sells multiple ticket types per event, the bot can list each tier with its current price and stock.

Yes. Restrict by category, tag, status or any meta query so private or draft events stay hidden from public visitors. Display conditions also let you run different bots on different parts of the site, for example a music-only bot on the music page and a general bot on the homepage. Each scoped bot only sees events that match its filter.

Event Calendar timezone meta is preserved through indexing, and the bot quotes the time in the event's stored timezone by default. If a visitor specifies their own timezone in the conversation, the bot can convert. For multi-day events that span timezones, like a virtual conference scheduled for both London and Los Angeles, the bot quotes both local start times so the visitor does not have to do the math.

Date changes and post status changes trigger a re-index on the affected event within minutes, so the bot picks up the new data. A cancelled event whose status moves to draft or trash drops out of public answers immediately. If you mark an event with a custom 'cancelled' field rather than changing status, you can include that in the prompt so the bot says 'this event was cancelled' rather than quoting the old date.