Yes. SleekAI reads the mec-events post type regardless of edition, and any extra fields Pro adds are read through postmeta. Recurrence rules from Pro, additional fields like seat numbers, and any custom meta the studio has added all get exposed to the prompt automatically. There is no separate Pro adapter to install, because everything Pro adds lives on the same post type.

Each occurrence is treated as a discrete event instance, so 'when is the next pottery class?' returns the next concrete date rather than 'every Saturday'. MEC's recurrence rules are flattened at index time into individual entries, with exclusions and modifications honored. So a class that's been moved or cancelled for one specific week reflects that change in the bot's answer.

If MEC bookings are enabled, the bot reads remaining tickets per event and quotes them. It will not claim availability when seats are full. Sold-out classes drop out of suggestions automatically, and the bot suggests the next available occurrence instead. This is essential for studios where a popular class fills up days in advance.

Yes. MEC categories and labels are part of the context, so visitors can ask 'show me all music events this weekend' and the bot filters accordingly. Display conditions also let you scope a chatbot to specific categories so different audiences get focused answers, for example a Yoga-only bot on the yoga page and a general bot on the homepage.

Yes. The bot returns the canonical permalink with any pre-selected ticket so visitors land directly on MEC's checkout. Payment stays on the existing MEC booking flow, which keeps your analytics, payment processor and confirmation emails all working without needing to rebuild them in chat. The visitor sees the chat answer, clicks through, and lands on a pre-filled checkout.

Yes. You can scope each chatbot to a category or location so different calendars run their own assistant. A wellness studio with a yoga calendar and a pilates calendar can have two bots, each only surfacing classes from its own category. Display conditions let the bots load on different pages, so the right corpus surfaces in the right context.

MEC stores timezone meta per event, and the bot quotes times in the event's stored timezone by default. If a visitor specifies their own timezone in the conversation, the bot can convert. For studios with both in-person and virtual classes, the in-person classes use the studio's local timezone while virtual classes use the timezone the organizer has configured per event.

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