AI Chatbot for a School Website: Parent FAQs From Your Handbook

To add an AI chatbot to a school website, turn the handbook into a cleaned question-and-answer document, load only that into a chatbot builder, instruct the bot to answer from it and nothing else, add a hand-over to the office, test thirty parent questions, then embed it on the site. A small school can finish in a day.

The handbook does most of the work, so most of the effort goes into preparing it. Free allowances exist, but they are small, so check your likely volume first. The steps suit the office manager or head of a small school who edits the website; the figures and examples use an imagined 190-pupil primary school.

Follow me on Instagram@sagnikteaches

Step 1: decide what the bot is for, and who it is for

Write one sentence: "This assistant answers parents' and carers' practical questions from the school handbook, and sends everything else to the office." It will keep every later decision honest.

Connect on LinkedInSagnik Bhattacharya

Look at where the office's calls and emails come from. In an illustrative week of 60 contacts, a typical small primary might see the pattern below. The counts are an example, so replace them with a tally from your own office for one week.

Subscribe on YouTube@sagnikteaches

On those numbers, 44 of 60 contacts are answerable from the handbook. That is the prize. The other 16 are why the hand-over matters more than the clever part.

Step 2: clean the handbook until it speaks with one voice

A chatbot does not know which of two conflicting statements is right. It will pick one, and sound sure. So before any tool is opened, work through the handbook with a pen.

1. Date everything. Put "Last reviewed: [month year]" at the top. If a policy has no date, find out when it was last checked.
2. Find conflicts. Look for a lateness rule in the handbook that differs from the one on the website, a gate time that changed after building work, or two different lunch prices. Settle each and fix the source.
3. Remove what must not be public. Staff mobile numbers, individual pupils' names, photographs with captions, any named family. If it should not sit on a public web page, it should not be in a chatbot.
4. Cut the legal boilerplate. Long policy text answers a parent's question poorly. Keep the one-paragraph summary parents need and link the full policy.
5. Split into questions. Rewrite the practical content as question-and-answer pairs. Forty to sixty is plenty for a small school.

Here is what two cleaned entries might look like, with a before and after.

Before (handbook text): "Pupils arriving after the registers have closed at 9:05 should be signed in at the main office by an accompanying adult, whereupon the lateness will be recorded in accordance with the attendance policy (see Appendix C)."

After (FAQ entry):

Q: My child will be late. What do I do?
A: Registers close at 9:05. If you arrive after that, please bring your child to the main office and sign them in. Phone the office on [number] or use the absence form [link] if you know in advance. Full policy: [link to attendance policy].

The "after" is shorter, answers in the parent's own words, and gives the next action. It also keeps the register time in one place, so when it changes you edit one line. If you have never written FAQ entries for a bot, the method in how to build the FAQ your AI chatbot needs is a good companion.

A realistic mistake. A school loaded a handbook PDF whose term-dates page was a year old; the new dates were on a separate letter. For the first week the bot gave parents last year's half-term. It was caught only because a parent called to ask why the website said one thing and the bot another. The fix was a rule: the FAQ document, not the old PDF, is the single source, and its first line holds a review date.

Step 3: choose a free tier, knowing how fast it runs out

Free plans are good for a pilot and rarely enough for a school's busiest week. The facts below are list prices as I found them in November 2026; check each page before you commit.

A quick sum for the imagined school. Suppose 190 pupils means about 150 families, and 20 per cent of them use the bot in a given month, each in one conversation. That is 30 conversations, comfortably inside Botpress's free 100 or Tidio's free 50 for a first month. But after a newsletter announcing the chatbot, or at the start of term, usage can double or triple. A pilot with 50 free conversations might be gone in two weeks. For that reason, decide in advance what happens: either upgrade, or switch the widget off and show the office number.

Three practical points. Branding: free and low plans usually show the vendor's name in the widget, and removing it can cost extra (Tidio lists a no-branding add-on at $16.67 a month), so decide whether that matters to you. Hand-over: Chatbase's helpdesk inbox for passing chats to a person starts at Basic, not Hobby, so on a Hobby plan hand-over is a link or a phone number. If the free options tempt you, ask a vendor the questions in what to ask an AI chatbot vendor before you sign up, especially about where chat text is stored and for how long. Discounts: Botpress runs a Botpress for Good programme that it says makes its plans more affordable for nonprofits and educational institutions; a school applies through a form linked from the pricing page, and no discount figure is published, so budget at list price until you hear back.

Step 4: load the handbook and set the rules

Create the bot and load only the cleaned FAQ document. Resist the temptation to add the whole website, past newsletters or the staff handbook. Each extra source is another place for a contradiction. Then paste instructions. This block works as a starting point:

You are the parent information assistant for [school name]. You are an AI, not a member of staff. Answer only from the FAQ document. If the answer is not there, say "I don't have that information" and give the office number [number] and opening hours.
Never discuss any individual child, behaviour, health, welfare or admissions decisions. For these say: "I can't help with questions about individual children. Please contact the office on [number]."
If anyone mentions a child being at risk, harmed or in danger, reply: "Please contact [safeguarding lead role] at the school straight away on [number]. If a child is in immediate danger, call [emergency number]."
Do not ask for or repeat names, phone numbers or addresses. Keep answers under 70 words, in plain English, and end with how to reach the office.

Have the school's safeguarding lead approve the safeguarding line itself. It is the one sentence that matters if something goes wrong, so the wording and the number belong to a person with that responsibility, not to the chatbot builder.

Set the first message so that it is clear who the assistant is for and what it is:

Hello, I'm the school's AI assistant for parents and carers. I can help with term dates, uniform, lunches, clubs and how to contact us. I can't answer questions about individual children. Please don't type names or personal details.

Step 5: design the hand-over to the office

The hand-over is what turns a chatbot from a risk into a service. Decide it before you test.

• Route. The simplest safe route is a message that gives the office number and the hours, plus a link to a contact form that goes to the shared office inbox. It does not need live chat.
• Form fields. Parent's first name, a phone number or email, a message. Add a line: "Please do not include sensitive information about your child here; the office will call you." A form built in Google Forms writes to a sheet, and a simple automation can email the office; the pattern is the same as in the tutorial on five school office jobs to automate with AI.
• Response time. Promise "the office replies within one school day" only if it is true on the busiest Monday.
• Out of hours. A different reply that gives the next opening time and the emergency instruction.

An illustrative hand-over reply:

I can't help with that here. The office is open 8:15 to 16:00 on school days and will reply within one school day. Call [number] or use this form: [link].

A filled-in slice of the FAQ document

An example makes the target format concrete. Here are six entries from an imagined school's document, all illustrative. Note that each answer is self-contained, because the bot may quote one entry without the others.

Review date: [month year]. Source: parent handbook, reviewed by the head.

Q: What time do the gates open and close?
A: Gates open at 8:35 for the 8:45 start and close at 9:05. Breakfast club children enter by the side gate from 7:45. Pick-up is from 15:10.

Q: What is the uniform?
A: Grey or black trousers or skirt, a school sweatshirt in the school colour, and sensible shoes. PE kit is a plain white T-shirt and dark shorts, worn to school on PE days. Full list and supplier: [link].

Q: How do I pay for lunches?
A: Through the school's online payment system [link]. Lunches are paid in advance. Packed lunches are welcome. If your child is on a free-lunch entitlement, contact the office on [number].

Q: Which clubs are running this term?
A: [List, with day, time, age group, and cost.] Places are allocated by the club leader. To ask about a space, contact the office.

Q: My child is ill. What should I do?
A: Please report the absence before 9:00 by phone or the absence form [link]. Give the reason and say when you expect your child back. We can't give health advice here.

Q: How do I contact the headteacher?
A: Through the office on [number] or [form link]. The office will pass your message on and reply within one school day.

Three things to copy from this. The "Which clubs" entry holds the current list rather than pointing at a PDF, so the bot answers rather than deflects. The "My child is ill" entry gives the process and declines advice in a single paragraph. And every entry ends on a next action, which is what parents were phoning for in the first place.

Reading the bot's mistakes: symptom, cause, fix

When an answer is wrong, resist editing the instructions first. Most errors come from the source, so work down this table.

Keep a simple change log: the date, the symptom, the fix and who made it. After a term it shows you which parts of the handbook are unstable, and those are usually the parts where the school itself has not decided something.

Accessibility and the phone

Most parents will meet the bot on a phone, often one-handed, in a corridor. Check the widget at phone width: does the opening message fit, does the keyboard cover the reply, can the close button be reached? The same test on a screen reader or with the text size set larger is worth ten minutes, since some parents will rely on it. Place the office phone number and hours beside the widget on the page as well, so a family that cannot or does not wish to use a chat is not left searching. A bot should be an addition to the office's front door, never the only one.

The office's first morning with it live

Hand the person who answers the phone a one-page sheet: the three things the bot will not do, what a form hand-over looks like when it arrives, and where to log a wrong answer. Ask them to keep a tally of calls that start with "the chatbot told me" for the first fortnight. If the tally is above two or three a week, read those conversations together that Friday. It is the fastest way to find the entry that is misleading parents, and it signals to staff that the bot is theirs to correct rather than something imposed on them.

Step 6: test with thirty real questions

Write the test list before launch, using actual questions from your office diary. Include these groups and record the exact reply to each.

Run the whole list on a phone and a laptop. Fix failures in the FAQ or the instructions, never by adding more sources, then run all thirty again. Ask two staff members who did not write the FAQ to try to break it for ten minutes; they will ask questions in ways you did not think of.

Step 7: put it on the website and launch quietly

Every builder produces a short snippet to paste into the website, and most school sites accept it through a "custom code" or "embed" setting in the content system. Add it to one page first, the "Contact us" or "Parents" page. Watch it for a fortnight and read every conversation, then widen to the whole site. Tell parents in the newsletter only after the first fortnight, so that a rush of curiosity does not exhaust a free allowance before you have looked at the answers.

Write a one-line description for the school's privacy information: that an AI assistant answers parents' questions on the website, that chats are stored by the supplier for a set period, and who to contact. Ask the school's data-protection lead to approve it, and to look at where the vendor keeps transcripts. If the vendor cannot tell you, it is not ready for a school.

Telling parents it exists

When the first fortnight is clean, announce it in the newsletter in plain terms. Illustrative wording:

New on our website: an AI assistant that can answer everyday questions about term dates, uniform, lunches and clubs, any time of day. It is a computer program, not a member of staff, and it only uses information from our parent handbook. It can't answer questions about individual children, so please keep calling the office for those: [number].

The paragraph does three jobs. It sets expectations about what the bot is, it protects the office from a flood of sensitive messages sent to the wrong place, and it tells parents who prefer a person that nothing has been taken away.

Step 8: keep it right after launch

• Weekly for four weeks: read the conversations, tag the answers, and write down every "I don't have that information" question.
• Each time something changes: update the FAQ first, change its review date, reload it into the bot, and re-run five test questions from the group it touches.
• Each term: repeat the thirty-question test and recheck the conversation count against the plan.

An illustrative first-month log for 70 conversations: 52 answered correctly, 11 handed over, 4 gave out-of-date answers (all from one superseded club timetable) and 3 were test messages. Two of the three "missing" questions that appeared more than once (the school's policy on birthday cakes and the arrangements for wet playtimes) went into the FAQ with a date. That loop of reading, finding gaps, writing the answer and dating it is the real work, and it takes about thirty minutes a week.

The cost of the whole project for the imagined school is a day of the office manager's time, possibly the vendor's cheapest paid plan once volumes grow, and half an hour a week. For schools that want the wider office jobs mapped before building, the five-job cost breakdown shows where a chatbot sits among them, and if you want someone to review the handbook and the instructions with you, that is covered by my AI implementation consultation.

Questions heads and office managers ask about a school chatbot

Can pupils use the chatbot?

Design it for parents and carers, and say so in the first message. Pupils may still find it, so the bot should not ask for names, should not discuss individual children and should point anything worrying to the office. If you want a pupil-facing tool, that is a separate project with separate safeguarding checks.

What happens when the free allowance runs out?

It depends on the tool, and the vendor's page is the only reliable answer. Some stop replying, some prompt an upgrade, and some bill extra packs automatically. Check before launch and set the widget to show the office phone number if the bot goes quiet.

How often should the handbook be reloaded?

Every time a policy, term date or contact changes, and at least once a term. A chatbot is only as current as its source, and the commonest failure is an answer from last year's handbook.

Should the bot answer admissions questions?

Only with the information already public on the admissions page, and never anything about a particular child or whether a place is available. Admissions decisions sit with the head or admissions lead, so route those questions to them.

Further reads

• AI Answering Service for a School Office: Absence Calls and Cost — The phone version of absence reporting, with costs.
• AI Consultant for Schools: Role, Cost and How to Brief One — If you want outside help briefed and priced.
• Free AI Tools for Schools: Who Qualifies and What Data They Keep — What free school AI tools do with the data they hold.
• AI Implementation in Schools: A One-Term Plan for a Small School — Fits the chatbot into a one-term plan.
• When Should an AI Chatbot Hand Over to a Human? — More hand-over patterns for the office.
• Dance Studio Handbook: Parent Policies Drafted With AI — Turning a handbook into parent-facing policies.
• AI Training for School Staff: Session Plan, Tasks and Handout — A ready-to-run one-hour AI session for school staff, with timings, a live demo, data red lines, practice prompts and a handout.
• Is Gemini Free for Schools? What Is Included and What Costs Extra — Which Gemini features a school gets free, which cost extra by edition and add-on, the admin switches to flip, and pupil age limits.
• Can AI Draft a Headteacher Report to Governors From Your Data? — Turn anonymised attendance, progress and finance tables into a governors' report draft, with a figure-by-figure accuracy check before it goes out.
• Can AI Write School Attendance Letters? A Three-Stage Sequence — A three-stage attendance letter ladder written by AI with placeholders only, merged from the register by your office, and signed off by the head.
• Preschool Parent Handbook: Draft It With AI and Check State Rules — Use AI to outline the handbook and rewrite policies in plain English, then check every section against your licensing authority's own published rules.
• School Parent Survey: Can AI Summarise Hundreds of Comments? — Design the survey, strip names, let a chat assistant sort 400 comments into themes, spot-check against the raw text and report to governors.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Tidio, Botpress and Chatbase pricing pages (November 2026); Zapier and Google Forms help pages for the hand-over form.