No. The system prompt explicitly forbids collecting child names, exact birthdays, medical information, allergy details, or anything else sensitive. Parent contact (name and email) is only requested for a tour booking, and only after the parent volunteers it. Anything that would require child specifics, such as 'is my daughter ready for 1st grade?', gets routed to the admissions director rather than answered. Most schools treat that boundary as a marketing feature, not a constraint, because the first message a chatbot sends is the first signal the family gets about how the school handles information.

If your tuition page lists per-grade rates, the bot reads each one as a structured field. SleekAI's data-source wizard maps the tuition page or a custom post type into named variables so the bot answers 'tuition for 3rd grade' with the right line, not an average. For schools with sibling discounts, aid award percentages, or multi-year tuition agreements, those policy paragraphs are quoted verbatim and the bot routes specific award questions to the admissions team.

Yes. The bot recognises both formats and confirms the right one. Parent-only tours typically run weekdays (60 min, classroom walkthrough plus Q&A); family open houses run Saturdays (90 min, kids welcome, low-stakes browse). The bot also handles shadow-day requests for grades 3-5 by collecting parent contact and routing to admissions, rather than promising a date the school hasn't confirmed.

Yes. Because the bot reads your published page rather than a snapshot, every edit to the admissions timeline in WordPress is reflected in the next conversation. No re-training, no model fine-tune. Schools that adjust the timeline mid-cycle (extra application week, rolling waitlist) just update the page and the bot follows. For large content sets, OpenAI Files acts as a vector store so even multi-page curriculum guides search accurately.

Yes. If a parent writes in Spanish, Mandarin, French, or any language the underlying model supports, the bot replies in that language with information translated from your English source pages. For schools serving immigrant communities or international families considering relocation, this is one of the highest-value features. WPML and Polylang sites can also map per-locale content directly so the bot answers from the right translated source.

Calendly, Acuity, Gravity Forms, Fluent Forms, or a custom webhook. The bot collects the preferred slot in conversation, then either passes the parent to a pre-filled booking link or fires a webhook that creates the appointment server-side. Most schools use deep links because the booking confirmation comes directly from Calendly or Acuity, which keeps the parent's calendar invite clean and lets the admissions team manage availability in one tool.

FERPA applies to education records the school maintains, which the bot does not create. The bot answers from your published WordPress pages and routes anything record-related to a human. Conversation logs live in your WordPress database with the security you've configured, and many schools set short retention windows (30 to 90 days) on the chatbot log. Bring-your-own-key means prompts go directly to OpenAI, Anthropic, Google, or OpenRouter, with no third-party processor between you and the model.

Yes. Multibot lets you run a kindergarten-focused bot on the K page with a kindergarten-specific tour format and a separate grades 3-5 bot on the upper-elementary page. Each bot has its own system prompt, presets, and display conditions (post type, page URL, user role). Schools that run both a day-school and an aftercare program often use this to keep the aftercare bot focused without distracting the admissions bot from its open-house funnel.