The Front Office Test

Every district has a front office that answers the same questions every week. When is the next early dismissal? How do I report an absence? Where do I drop off a form? Is there school on Monday? The answers are on the website somewhere, and families call anyway.

That's the problem an AI chatbot on the district website is supposed to solve. And in a vendor demo, it usually looks solved. The chatbot answers "When is spring break?" instantly and correctly, because the vendor chose the question.

The real test is your questions.

Before an AI chatbot goes on your district website, give it the ten questions your front office answers most often, plus five it shouldn't be able to answer. Then judge it on seven things.

1. It answers from your content, not the internet. Every answer should come from the district's own published pages and documents, with a link to the page it came from so a parent can check. A general-purpose AI fills gaps with confident guesses, and a guess about another district's calendar is worse than no answer at all.
2. It says "I don't know" when it doesn't know. This is the most important thing to test, and the easiest to skip. Ask about something your website doesn't cover. A good assistant says it doesn't have that information and tells the family who does, with an office and a phone number. A wrong answer delivered smoothly does more damage than no answer, which is why you should judge an assistant by what it says when it doesn't know.
3. It works when the office is closed. Most of the value shows up after hours. The question a parent can't get answered at 9:40 on a Sunday night becomes Monday morning's rumor, and the phone call your secretary takes at 7:30. Test it at night, on a phone, the way families will actually use it.
4. It answers in the family's language. Districts translate the documents someone remembered to translate. Families ask the questions nobody put on the list. A good assistant understands a question asked in Spanish, Korean, or Portuguese and answers in that language, even when the source page is only in English.
5. It's careful with what families tell it. A website assistant shouldn't connect to student records. But families will still type in names, diagnoses, and custody details. Ask the vendor where conversations are stored, for how long, who can see them, and whether they're used to train AI models. The privacy question is about what families will tell it as much as what it can see.
6. It works for every family. A chatbot that a parent can't reach with a keyboard or a screen reader isn't just a design flaw. Under the Justice Department's ADA Title II web rule (opens in a new tab), a district's web content must meet WCAG 2.1 Level AA, including content provided through vendors, with compliance dates in April 2027 or April 2028 depending on size. Ask the vendor how the chat widget meets that standard, and test it yourself with the keyboard alone.
7. It shows you what families are asking. Every question typed into the chat box is feedback nobody had to request. A good assistant gives the district a log of those questions, so you can see which answers are missing from the website and fix the page instead of fielding the same call again. Read the log closely and it becomes the most honest survey your district will ever run.

What a good assistant won't do matters just as much.

It won't make decisions that belong to people. Whether a child qualifies for services, how a discipline policy applies to a specific case, whether an absence will be excused: those answers come from staff. The assistant can explain the policy and point to the right person. It shouldn't rule on the case.

It won't make promises. "Someone will call you back today" is a commitment only the office can make.

And it won't replace the front office. The best secretary in your district knows things no website will ever say. A good assistant takes the repetitive questions off her desk, so she has time for the ones that need her.

So run the front office test before you sign anything. Use your district's own questions, not the vendor's. Ask some in another language. Ask a few your website can't answer. Try it after dark, on a phone, with the keyboard alone.

If the chatbot answers the way your best front office staff would, accurately and briefly, with a link and a "call the office" when that's the right answer, it's ready for families. If it answers like a search engine guessing, it isn't.

See how AskK12 answers families' questions from your district's own content.