Yes. If your tracks are documented as WordPress pages with age brackets (Junior 7-10, Intermediate 10-13, Advanced 12+), the bot reads those brackets and asks two or three short questions about the child's age, prior exposure, and interest. It then recommends a track with a quick explanation of why, which is the exchange that most often converts a curious parent into a trial booking.

Yes. Camp sessions, weekend workshops, and birthday parties all live on their own WordPress pages with start dates and pricing. The bot routes the parent to the right format based on the question (week-long summer camp versus 10-week after-school cohort) and quotes accurate pricing. Most schools see camp enquiries spike in March and April, which the conversation log surfaces clearly.

If your prerequisites are on the track pages, yes. The bot enforces them in conversation: a parent asking about Python for a 7-year-old gets a recommendation to start in Scratch with a clear reason, not a hard refusal. For Unity, the bot can require prior Python or block-based experience, again based on what your page says. The goal is to set the right expectation before the trial, not after.

Yes. Multibot lets you run one bot on the after-school cohort pages and another on the camps page, each with its own tone, source pages, and presets. Camps tend to attract a different audience (travel families, gift-buying grandparents) and a separate bot lets you tune the system prompt for that flow without diluting the main cohort experience. Conversation logs stay separate per bot.

Yes. Calendly, Acuity, TutorBird, and custom WordPress booking plugins all work via deep link or webhook. The bot collects the preferred slot, child age, and track in conversation, then either passes the parent to your booking link with the slot pre-selected or fires a webhook that creates the enrolment server-side. Most schools use deep links because they integrate with the existing front-desk workflow without code changes.

If your cohort pages mark a session as full or waitlisted, the bot reads that and routes the parent to the next available cohort or a waitlist form. Update the page once and the bot updates immediately, which matters in late summer when fall cohorts fill quickly. The bot will not over-quote availability, which is exactly what you want for trust.

If your sibling policy is documented, the bot reads and quotes it. Many schools offer 10% off the second sibling or a shared-slot option for same-age siblings; some run a separate family workshop on Saturdays. The bot quotes what you publish and routes anything novel to the front desk, so the policy stays consistent across every channel.

Logs stay in your WordPress database. Bring-your-own-key sends prompts directly to OpenAI, Anthropic, Google, or OpenRouter with no third-party processor in between. That matters when minors are part of the conversation: you control retention and redaction with your existing WordPress security. Many schools redact the log after enrolment is complete or set short retention windows for fields like child name and DOB.