Yes. SleekAI reads your enrollment page and quotes the application open and close dates, lottery date, and decision date verbatim. For schools with sibling, locality, or staff-child preferences, the bot reads those as named fields and explains them accurately. It won't invent dates or preferences the school hasn't published, which keeps families from acting on incorrect timeline information that could cost them a seat.

Yes. If your school publishes typical year-over-year waitlist movement (number admitted off the waitlist, run-through period), the bot quotes those numbers from the published page. Specific waitlist-position questions ('what number are we on the waitlist') route to the enrollment director, since that requires looking up a record the bot doesn't access directly. Most charters consider this the right boundary.

Yes. Multibot lets each campus run its own chatbot with its own enrollment page, lottery calendar, and program model, while sharing a common knowledge base for the network-wide policies. Or run one bot with display conditions per campus URL pattern. Charter networks with 4-12 campuses often use the multibot approach so a Brooklyn campus answer doesn't bleed into a Queens campus conversation.

Yes. If your program model is published, the bot reads and speaks it. Dual-language immersion (90-10 or 50-50), classical (trivium-based, Latin from 3rd), expeditionary learning (multi-week projects), STEM-focused, arts-integrated, or social-justice-focused programs all have specific vocabulary the bot respects. Families researching a specific model are typically informed buyers; the bot's accuracy on the vocabulary is what builds trust in the first minute.

By routing to the special-education coordinator. The bot can explain at the policy level that the school accepts students with IEPs and 504 plans on the same lottery basis as all other applicants, and that the school's special-education services are described on a specific page. Anything case-specific (will this particular accommodation be supported, who provides the service) routes to the special-education coordinator by email, because those decisions require a record review.

FERPA applies to education records the school maintains. The bot answers from your published WordPress pages and does not create records. Conversation logs live in your WordPress database with the security you've configured, and many charter schools set short retention windows (30 to 60 days) on chatbot logs to keep the privacy posture clean. Bring-your-own-key sends prompts directly to OpenAI, Anthropic, Google, or OpenRouter with no third-party processor.

Yes. Any language the underlying model supports. The bot reads your English source pages and answers in the family's language, which matters enormously for charter schools serving immigrant, expat, or multilingual communities. For dual-language programs, the bot can answer Spanish-speaking families in Spanish from the start, which builds program-alignment trust even before the family visits the campus.

Yes. The bot reads your live published page each conversation. If you change the lottery date by two weeks because of a calendar conflict, the bot follows the moment the page updates. No retraining, no model fine-tune. For schools that adjust their calendar mid-cycle, this is essential because outdated information at the front office causes serious downstream confusion when families miss the actual deadline.