Yes. Add-ons store their data in postmeta on the same ajde_events post type, so the bot reads them automatically with no separate adapter. Whether you've added age restrictions, custom price tiers, RSVP fields or repeat-event modifications, all of it is exposed to the prompt as part of the event's meta. New add-ons work the same way as existing ones, since SleekAI reads any post type and any meta.

Yes. Scope each chatbot to one or more EventON categories so users on a music page get music-only answers. Display conditions also let you run different bots on different parts of the site, so the music page, the comedy page and the homepage each get their own bot tuned to their own category. Cross-category questions are still possible if the bot is scoped to multiple.

Each repeat instance is exposed individually so 'when is the next trivia night?' returns the next concrete date rather than a series description. EventON's repeat-event modifications and exclusions are honored, so a trivia night that's been moved or cancelled for one specific week reflects that change in the bot's answer. Past instances drop out of context automatically.

Yes. External ticket URLs and prices stored in event meta are quoted in answers and turned into clickable links. EventON often uses external ticketing partners, and the bot links to whichever one is configured per event. If the URL is missing, the bot says so rather than inventing a checkout link, which avoids sending visitors to a 404.

Yes. SleekAI works alongside WPML, Polylang and TranslatePress, and the bot responds in the visitor's language regardless of how the event content is stored. Times and addresses are universal, but venue names and event descriptions get returned in the visitor's locale where translations exist. International festivals end up with a single bot rather than one per language.

Yes. Run separate bots per category, taxonomy or page so each calendar has its own assistant. A city guide running a music calendar and a food calendar can have two bots, each scoped to its own category and surfaced through display conditions on the matching landing page. The bots share infrastructure but draw from different corpora.

Age restrictions stored as custom fields on the event are read into context and quoted in answers. So 'is the Brewhouse 21+?' returns 'yes, after 8pm' from the actual stored field rather than generating a plausible-sounding rule. If your venue uses a custom field name for age policy, the bot reads it as long as it's exposed in the prompt configuration.

Events that lack a linked event_location or event_organizer are still indexed, but the bot will say 'venue not specified' rather than invent one. This is more honest than guessing, and it gives the visitor a signal to ask the organizer directly. Events that are missing key meta also get flagged in the logs, so you can spot data hygiene issues and fill in the gaps.