Yes. Registrations, Sell Tickets and Calendar all extend the same event_listing post type, so the bot reads their data automatically. Whatever fields the add-ons store, including registration limits, ticket types and external calendar URLs, are exposed to the prompt as postmeta. New add-ons work the same way as existing ones, since SleekAI reads any post type and any meta without needing a custom adapter.

Yes. Events with _event_start_date before today are excluded from suggestions by default. The filter runs at retrieval time, so freshly past events drop out without waiting for a re-index. Same-day events are kept until the start time has passed, in case visitors are asking on the day. For multi-day events, the event stays in suggestions until _event_end_date has passed.

Online events are flagged via _event_online and the bot quotes the join URL for registered users only. Public visitors see 'register to receive the link' rather than a leaked Zoom URL. This matters for paid webinars where the join URL is gated content. The bot's behaviour can be tightened or relaxed per chatbot via the system prompt.

Yes. _event_pricing meta is read into context so the bot quotes the actual cost or marks events as free. The bot does not invent prices, and the system prompt instructs it to refuse to do so. If a price is missing from meta, the bot says 'pricing not specified, please check the registration page' rather than guessing a number that might be wrong.

Yes. event_listing_category and event_listing_type are part of context, enabling 'show me all marketing webinars' style questions. Display conditions also let you run a category-scoped bot, so a webinar-only bot only sees webinars and a conference-only bot only sees conferences. Multi-category filters work too, for example 'free webinars in machine learning'.

Yes. Events with both _event_start_date and _event_end_date are correctly described as spanning the full range. So a three-day conference returns 'May 14 to May 16' rather than just 'May 14'. Sub-events within a multi-day event, where add-ons split sessions into their own listings, are surfaced individually so the bot can answer 'what's happening on day two?' with the day-two sessions.

Replays are typically stored as separate listings or as custom fields on the original event. If they are listings, the bot reads them like any other event. If they are custom fields, the bot reads the meta and quotes 'recording available within 48 hours of the live session'. The replay URL is gated to registered users in the same way as live join URLs.

Registration deadlines stored as custom fields are read into context and quoted in answers. The bot can say 'registration closes at noon on April 26' from the actual stored deadline. If the deadline has passed, the bot says so and suggests checking back for the recording or the next event in the same series, rather than offering a registration link that no longer works.