Registrations for The Events Calendar runs on top of The Events Calendar. Events are the standard tribe_events custom post type with start, end, and venue meta. RTEC stores registrations in WordPress with custom fields per attendee, including first name, last name, email, and any custom fields you defined on the form. Capacity per event is tracked through the plugin's settings and registration counts.

SleekAI's data sources map all of that into named variables. The bot sees the current event title, dates, venue, capacity, remaining spots, the form's required fields, and any policy text on the event page. A question like "how many seats are left for the meetup tomorrow" returns the actual number, not a guess.

Display conditions scope each bot by post type, taxonomy term, user role, logged-in state, and URL pattern. An event-page bot can answer about that specific meetup, an admin-only bot can summarize this week's registrations, and a logged-in attendee can ask about their own existing signup. Every chat is logged inside WordPress with the model name, token usage, and origin page.

Community events live on momentum. A visitor who has to read three event pages and a long FAQ to figure out whether there is room for them on Thursday will usually leave instead of signing up. The reasons are the same on every event site: is there capacity, what does the form ask for, can I bring a friend, what happens if I cannot make it.

A generic chatbot does not know any of that. It invents capacity, hallucinates venues, and contradicts the form fields three lines down. The result is more no-shows and more abandoned signups.

Registrations for The Events Calendar already has the structured data the bot needs. Events are tribe_events posts with venue and date meta. Registrations are entries with the form fields you defined, plus a running count for capacity.

SleekAI maps that data into the chatbot prompt with point and click data sources, so the chat agrees with the registration form on every detail. Per-bot display conditions then let you run an event-page bot, a calendar bot, and an organizer-only reporting bot from the same install, each scoped exactly where it is useful and running on a key the organizer controls.