Yes. If your class schedule is a WordPress page or custom post type with style, age range, and time slot fields, the bot reads all three and filters accordingly. It also handles the multi-style question (a parent who wants ballet plus jazz for the same kid) and quotes the multi-class discount. Most academies see a noticeable lift in multi-class enrolments once the bot surfaces the discount in conversation.

Yes. If your competition-team pages document audition dates, commitment levels, team-fee structure, costume deposits, and choreography fees, the bot routes serious prospects to that flow and quotes the real cost stack. It will not let a parent accidentally enrol a child in the competition team via the recreational form; the audition step is preserved. Most studios run a dedicated competition-team bot via Multibot on those pages.

Yes. If recital dates, performance times by class, costume fees, ticket sale dates, and seating policies live on a WordPress page, the bot reads them. Spring recital season generates more chatbot conversations than any other period for most academies, and most of those conversations are repetitive. The bot handles them consistently, which frees the front desk for the harder questions.

Yes. Uniform requirements (leotard colour, tights, shoes) per class and recital costume policies (fee due dates, fitting schedule, sibling discount) are read from your published policies. The bot quotes them accurately and routes anything novel (a costume-allergy concern, a recital absence) to the front desk. Update the page once and the bot updates immediately.

Yes. Jackrabbit Dance, DanceStudio-Pro, Studio Director, Calendly, Acuity, and custom WordPress booking plugins all work via deep link or webhook. The bot collects the preferred slot, style, age, and level in conversation, then either passes the family to your booking link or fires a webhook that creates the trial server-side. Most academies use Jackrabbit or DanceStudio-Pro deep links.

Yes. Multibot supports a recreational bot on the recreational class pages and a competition bot on the competition-team pages, each with its own tone, source pages, and audition logic. Conversation logs stay separate per bot, which makes it easier to review competition enquiries (often higher-touch, with cost-stack questions) without filtering. Most multi-track studios run two bots.

Consistently. The bot reads your recital page once and answers every variation of the same five questions (when, where, costume, picture day, tickets) the same way for every family. Most academies see a 60 to 80 percent drop in recital-related phone calls during the April to June window once the bot is live, with no degradation in family satisfaction. The questions still get answered, just faster and without involving the front desk.

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, including names, ages, parent contact details, and recital photo-release questions. The plugin does not add a new vendor to your data path. Apply your existing WordPress access controls and retention rules, and redact after enrolment.