Yes. SleekAI reads tribe_rsvp_tickets and tribe_tpp_tickets the same way and surfaces both types in answers. RSVP-only events are described as free, paid tickets quote the actual stored price, and a single event can have a mix of both. The bot uses the same retrieval layer for both, so a visitor asking about availability gets one consolidated answer rather than separate flows for RSVP versus paid.

Yes. Capacity, stock and shared capacity meta are all readable, so the bot can answer 'how many seats are left?' accurately. Shared capacity, where one pool feeds multiple ticket types, is honored: if standard and early bird share the same pool, selling an early bird reduces standard availability and the bot reflects that. Sold-out tiers drop out of suggestions automatically.

If discount codes are stored as posts or meta on your site, SleekAI can read them. The bot will not invent codes that do not exist; it is instructed to refuse, and to suggest the visitor contact support if they think a code should apply. This avoids the classic bot failure of generating a plausible-looking code that fails at checkout and frustrates the customer.

SleekAI does not take payment directly. The bot links visitors to your existing Event Tickets checkout flow with the right ticket pre-selected, so the conversion path stays under Event Tickets' control and your existing analytics, fraud rules and confirmation emails all keep working. This also keeps the integration support footprint small.

Yes. The WooCommerce-backed tickets in Plus are read through their underlying WC product, including variations. A workshop with small, medium and large size variants becomes three readable answers, each with its own stock count and price. WooCommerce coupons are also exposed, since they are real post objects, so the bot can confirm a coupon's validity rather than guess.

Yes. When logged in, attendees can ask about their order, ticket transfers and check-in status using their stored attendee record. The bot reads the linked tribe_tickets_attendees data and answers 'has my ticket been scanned?' or 'when does the door open?' from real records. Transfer requests can be deep-linked into the existing transfer UI rather than handled in chat.

Event Tickets enforces stock at checkout, so true overselling is rare. If it does happen, the bot reads the negative or zero stock and reports the tier as sold out rather than offering a seat that does not exist. Capacity overrides set on the event level are honored too, so an event-wide cap that has been hit hides all of its tickets even if individual tier stock is non-zero.

Yes. SleekAI works alongside WPML, Polylang and TranslatePress for per-language tickets. The visitor's language is detected from the request, and the bot replies in that language even when the source ticket post is written in another. Prices and stock are universal, but the policy text and tier names get returned in the visitor's locale where translations exist.