The contract is signed. The chatbot goes on the district website with one line of code, and by Friday it’s answering questions. That part is easy. What families experience in the first month depends on the work around the launch, and most of that work has nothing to do with the chatbot itself.
A chatbot answers from your website. If the website is out of date, the chatbot will repeat the outdated answer quickly, politely, and with a link to prove it. So the first two weeks belong to the website.
Start with a list. Ask the people who answer the phones for the twenty-five questions they hear most: front office staff, the attendance clerk, the registrar, the transportation office. Then look up each answer on the website the way a parent would, on a phone. For each one, ask three things. Is the answer on a page, not only in a PDF? Is it current? Would a parent recognize the words? It’s the same test you’d run before choosing a chatbot, turned on your own site.
Fix the pages, not the chatbot. Take down last year’s calendar. Replace the scanned registration packet with a page. Add the name and phone number of the office that handles each topic. Every page you fix helps the chatbot, the website’s search box, and every family who never opens the chat at all.
Then write exact answers for the handful of questions where close isn’t good enough: start and dismissal times, how to report an absence, how to register a new student, where closings are announced. These are the answers families act on without double-checking, so a person should write them and the office that owns each one should check it.
Before launch, settle three more things. The first is accessibility. A chatbot is part of your website, so it has to work with a keyboard, a screen reader, and 200 percent zoom, and you can test that yourself in five minutes. The second is privacy. Tell families what the tool is, where its answers come from, and that they shouldn’t type personal details, because families will tell a chat box more than districts expect. The third is alerts. Decide who posts the banner on a storm morning and how quickly, so the chatbot and the text alert say the same thing.
Readiness is a district question, not only a technical one. The Gen AI readiness checklist from CoSN and the Council of the Great City Schools asks districts to work through six areas before adopting a generative AI tool, from executive leadership and data privacy to security and risk management, and to understand where generated answers come from. A website chatbot is a small tool, but the same questions apply, and a cabinet that has answered them will defend the launch when someone asks.
Launch to staff before families. Show the front office how the chatbot works, so the next caller can hear, “You can also ask the chatbot on our website, any time.” Staff who have tried it will recommend it. Staff who haven’t will work around it. Then announce it to families in the newsletter and on social media, in the languages your families read, with one example question they can try.
Then read the questions. For the first month, set aside fifteen minutes a week to read what families typed. Look for three things: questions the chatbot couldn’t answer, answers that were right but came from the wrong page, and questions nobody expected. Each one points to a page that needs work. The question log is the most honest survey your district will ever run, and the first month is when it says the most.
Track a few numbers from the start: how many questions families ask, what share the chatbot answers from your content, how many arrive after office hours, and which topics lead. At thirty days, share them with your cabinet or board, along with what you changed on the website because of them. That report is usually what turns a chatbot from an experiment into part of how the district communicates.
A chatbot doesn’t fix a website. It shows you, in families’ own words, exactly where to fix it.
AskK12’s white-glove onboarding covers the first steps with you: crawling your site, writing exact answers for your most-asked questions, and testing before families see it.