Yes. SleekAI reads the capacity field on each team post and compares it to the current roster count, which most programs track in an ACF number field updated by the tryout intake. The bot answers questions like "does Team Atlas have spots?" with the live remaining seat count and offers to add the family to a tryout list when a team is locked. Programs running rolling cuts can also expose a tryout window field so the bot knows when each team's roster firms up.

Yes. Each program tier has its own post with age band, season length, build hours, kit description, and competition format. The bot quotes those fields when a family asks about the difference between FLL Challenge and VEX IQ for a middle schooler, or between VEX V5 and FRC for a high schooler. It mirrors the explanation your program already publishes, so families get consistent framing whether they read the page or ask the bot.

Yes. The season calendar custom post type holds qualifying tournaments, state and regional championships, and travel cost ranges. The bot quotes the right dates for each team and gives families an honest travel commitment estimate, including whether the team typically advances to state and what that adds to the season. Programs with a championship travel subsidy can mention that subsidy and link to the request form.

Yes. Display conditions in SleekAI let you scope a bot to a category or URL pattern. The elementary FLL Explore pages can have a beginner-friendly bot focused on first-season expectations, while the FRC team pages get a separate bot with deeper context on build season hours, mechanical and programming subteams, and college recruiting. Each has its own instructions and data scope.

Yes. Your scholarship application process, partnership schools, and the percentage of need-based aid awarded sit in a policy post or options page. The bot explains the process when a family asks, names any Title I or community partner that fully funds participation, and links directly to the application. Programs with a confidential aid path can have the bot route requests to the director without exposing the form publicly.

Your published parent agreement loads as a separate data source. The bot answers questions about volunteer hours, tournament chaperoning, fundraising expectations, and the optional mentor track for parents with engineering backgrounds. Setting expectations honestly in chat reduces the families that quit mid-season because the volunteer commitment was a surprise, which is one of the most common retention problems for youth competitive programs.

Yes. Coach and mentor bio posts with credentials, prior FRC team experience, and which teams they staff are part of the bot's context. Asked "who coaches Team Helix," the bot names the coach, mentions any youth-safety certifications, and links to their full bio. For programs that pair head coaches with industry mentors from sponsoring companies, the bot can highlight those mentors when families ask about real-world exposure.

Logs sit on your own WordPress database, readable only by users with the admin or director role you specify. Because you provide the API key, prompts and replies go directly between your site and your chosen model provider, with no intermediate vendor storing family content. You can redact logs by email or content match if a parent later requests it, which matters because robotics programs work with minors and parents care about that detail.