Yes. The bot tracks the conversation state across children, so a parent can say 'my 7 year old and my 10 year old' and the bot keeps both threads alive when answering schedule and tuition questions. It applies sibling discounts automatically if the rule is in the system prompt, and quotes per-child totals at the end so parents see the math. Multi-child handoffs to the enrollment form work the same way.

Yes. Whatever you publish on the about or policies page is what the bot quotes. For faith-based co-ops, this is one of the most useful features because it filters families honestly at the chat layer rather than at the enrollment-contract layer. The bot does not editorialise; it reads the page and answers. Families who aren't a fit usually self-select before the tour.

If volunteer expectations are documented (4 hours per child per semester, kitchen duty rotation, board involvement) the bot reads and explains them. Most co-ops surface this early because under-prepared parents are the top mid-semester withdrawal reason. The bot can also book a parent orientation if you offer one, and remind the family about the volunteer signup deadline.

Yes. The system prompt sets the framing. An academic co-op (full-curriculum, transcript-generating) needs the bot to talk about credits, transcripts, and university prep. An enrichment co-op (one or two days, supplemental) needs it to focus on schedule and electives. The data model is the same; the tone and feature emphasis differ. Most co-ops tune the prompt over the first month using their conversation logs.

It hands off to Homeschool Tracker, Practice Monkey, MyMusicStaff (yes, some co-ops use this), Jupiter Ed, or any tool with a public form URL via deep link. The bot collects cohort, classes, and sibling info in chat, then passes the parent to your enrollment form pre-filled. For co-ops with a custom WordPress form via Gravity Forms or WP Forms, the bot can submit via webhook directly.

Co-ops get hammered with last-minute enrollment questions in late August. The bot scales with traffic because it reads from WordPress and calls your model API; there's no admin bottleneck. Conversation logs let you see which classes parents are asking about most, so you can open a second section before the semester starts rather than turning families away. This is one of the strongest ROI cases for a co-op.

Yes, with care. If you publish course descriptions, credit hours, and grading policies, the bot reads them and answers parent questions about transcript building for college applications. It should not give specific college admission advice. Most high school co-ops add a refusal clause to the prompt that routes admissions strategy questions to the academic advisor instead of the bot.

Logs stay in your WordPress database. Bring-your-own-key sends prompts to OpenAI, Anthropic, or Google directly with no third-party SaaS in between. For co-ops handling minor names and family schedules, that matters: you control retention, redaction, and access in WordPress, and the plugin doesn't add a new vendor. Most co-ops apply their existing site security to the chatbot log table as well.