No. The bot deep-links to your existing registration platform (RecTrac, RecDesk, ActiveNet, or a WordPress booking plugin) with the program preselected. The actual enrollment, payment, and waiver flow stays in that system, which is where the household account, payment method, and emergency contacts live. The bot's job is to find the right class and get the family to the right registration page faster.

No. The bot can point to your financial assistance page, quote the application requirements, and explain the review timeline from your published policy, but it does not rule on eligibility. Eligibility involves household income, family size, and program-specific factors that require staff review. The bot's role here is to make the path to applying clear, not to gatekeep or pre-approve any application.

If your registration platform exposes capacity data (via REST or by being embedded in WordPress with a JSON feed), SleekAI can surface "this class is full, waitlist available" alongside the program. Without a live capacity feed, the bot quotes published capacity numbers and routes the visitor to the registration portal, which is the system of record for waitlist position. Either way, the bot is honest about uncertainty rather than guessing.

Yes. SleekAI Multibot supports per-page scope: a youth-programs bot scoped to the youth URL pattern can be tuned for parent questions (age fit, level, after-school timing), while an adult-fitness bot can focus on schedule, instructor style, and class-pass packages. Each bot has its own instruction and presets, which keeps the conversation focused without splitting your site.

Yes. If your programs are tagged by season (spring, summer, fall, winter) and have registration open and close dates published, the bot scopes its answers to the active or upcoming session. A resident asking about fall soccer in July gets the fall season dates with the registration open date called out, and the bot does not surface programs whose registration is already closed unless the resident specifically asks about a past session.

Facility pages with hours, open swim times, gym schedules, and ice rink slots get indexed the same way as programs. The bot answers "when is open swim on Saturday" with the published schedule for that pool, with any seasonal variation respected. It does not predict crowd levels or guarantee a specific lane will be open; it just quotes the schedule.

The bot quotes your published refund policy (typical structure: full refund before session starts, prorated after, no refund within X days of the last class) and points to the cancellation request form or contact email. It does not approve refunds itself, since those involve account verification and discretion. The clean handoff keeps the policy enforceable by staff while still answering the most common pre-registration question.

On your WordPress install, with model name, token usage, and page URL stored with each transcript. For recreation departments, this becomes useful programming data: aggregate the questions and you see which programs people are looking for, which age groups have unmet demand, and which season's catalog has confusing copy. That feedback loop often improves catalog page design and program scheduling more quickly than internal feedback alone.