No. SleekAI does not connect to your student information system (PowerSchool, Infinite Campus, Skyward, etc.) and the instruction explicitly forbids any student-specific lookup. Grades, attendance, disciplinary records, and IEP details all stay inside the SIS behind family logins. The bot answers public-content questions (calendars, enrollment requirements, school directory) and refers any record-related question to the appropriate office with the right contact info.

Because the bot has no access to student records and the instruction prevents it from soliciting student-identifying information, FERPA isn't structurally implicated by the chat itself. The guideline filter catches off-topic prompts that try to extract or share student info. If a family asks about their student's specific situation, the bot routes them to the school office or parent portal where authentication is enforced. That clean separation is the simplest defensible architecture for a district chatbot.

Yes. SleekAI Multibot supports per-school scope. A district-wide bot can handle enrollment, calendars, and transportation. A school-specific bot scoped to that school's URL pattern can focus on bell schedule, PTA info, school-specific events, and the principal's office contact. Each bot has its own instruction and presets, and display conditions tie each to the right pages.

If your transportation page exposes route data (often through an embedded routing tool or a published table), SleekAI can surface route, stop, and time info from that content. For a live address-to-stop lookup, the bot deep-links to your routing tool with instructions, since that flow involves address verification that belongs in the routing system, not in the chatbot. Either way, the bot is honest about what it can and cannot look up directly.

If your district posts closures to a specific page or RSS feed, SleekAI reads that content so the bot answers "is school closed today" with the most recent posted status. The bot does not predict closures, does not interpret weather, and points families to the district's primary closure communication channel (often a text alert system or social media) as the source of truth. For acute weather events, the official channel always wins.

Yes. SleekAI uses general-purpose LLMs (OpenAI, Anthropic, Google, OpenRouter) via your own API key, so the bot answers in whatever language the family writes in. For districts with significant English-learner populations (Spanish, Mandarin, Vietnamese, Arabic, Somali, and more), this is a meaningful access improvement at no per-language infrastructure cost. Forms are still returned in whichever languages your site already publishes.

The bot can quote your meal program info (free and reduced meal application path, daily menu links, meal pricing, and online payment portal) from your published pages. It does not approve free or reduced meal eligibility, which is a federal program with specific verification requirements. The application goes to the food services office for review, and the bot routes families there with the right form.

On your WordPress install, in the database, with model name, token usage, page URL, and full transcript. For school districts, this also functions as parent feedback intelligence: aggregate the questions and you see which topics need clearer page copy (enrollment requirements often top this list), which calendar items confuse families, and which school's contact info is hardest to find. The data stays in your database, under your retention policy, with no third-party dashboard involved.