Events Manager stores events, bookings, locations, and tickets in dedicated tables like em_events, em_bookings, em_locations, em_tickets, and em_tickets_bookings, with an em_meta table for extras. Events and locations are also custom post types so the standard WordPress data layer works too. Postmeta fields like _event_start_date and _location_id are available on the event post directly.

SleekAI's data sources map all of that into named variables. The chatbot knows event dates, ticket types with prices and remaining counts, locations with addresses and capacity, booking statuses, and any custom meta the organizer adds. Recurring events expand into their next occurrences, so the bot can answer about the next Tuesday class or the second Friday session by date, not by pattern.

Display conditions scope each bot by post type, taxonomy term, user role, logged-in state, and URL pattern. An event-page bot answers about that event, a location-page bot covers everything at that venue, a logged-in attendee can ask about their existing bookings, and an admin bot can answer high-level reporting questions. Every chat is logged inside WordPress with the model name, token usage, and origin page.

Bookings turn on confidence. A visitor who is unsure about availability, the venue, or the policy will hesitate, and a hesitating visitor closes the tab. The standard questions are always the same: is it sold out, where is it, what does the VIP tier actually include, what is your refund policy, when is the next one.

A generic chatbot answers none of those honestly. It invents seat counts, hallucinates addresses, and contradicts the booking page just below it. Trust collapses, and the bot becomes a liability rather than a sales aid.

Events Manager already stores the truth in dedicated tables. em_events, em_bookings, em_tickets, and em_locations hold the schedule, the seats, the prices, and the venues, with events and locations also surfacing as custom post types. SleekAI maps that data into the chatbot prompt with point and click data sources, so availability, price, and policy answers agree with the booking form on every detail.

Per-bot display conditions then let you run an event-page bot, a location-page bot, and an organizer-only reporting bot from the same install, each scoped where it makes sense and each running on a key the organizer controls.