An AI chatbot for schools that answers from your own information
School offices and course teams answer the same questions every day: term dates, fees, uniform, transport, start dates and how to apply. We build an AI assistant for your website or help inbox, aimed at parents and adult learners, that answers only from your approved pages and policies, works in the languages your families use and hands anything about a specific child, wellbeing, safeguarding or complaints to staff. Projects typically cost $2,500 to $7,500 and take five to eight weeks.
The problem
What an AI chatbot for school should and should not do
Office staff field a steady stream of questions that are already answered somewhere on the website or in a letter home. Families who speak another language at home, or who work shifts, often cannot reach the office when it is open.
An assistant for a school has to be narrow. It must answer only from approved information, never discuss an individual child, never handle safeguarding or wellbeing concerns itself and never collect personal information from young children.
What we build
What our AI chatbot for education includes
Approved answer library
Term dates, fees, uniform, transport, clubs, courses, policies and how to apply, approved by the school and the only source the assistant uses.
Website and inbox assistant
A chat widget for parents and adult learners, and draft replies for the help inbox.
Multilingual answers
Answers in the family's language where you approve it, generated from the same approved sources.
Sensitive topic hand-off
Questions about a specific child, wellbeing, safeguarding, SEND or complaints go to named staff with your contact routes.
Clear AI disclosure
The assistant says it is automated at the start and offers a person at any time.
Transcript review
A weekly list of questions it could not answer, so the library improves.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Question asked
A parent or learner asks on the website or by email.
-
02
Automated
Answer from approved pages
The assistant answers from the library and links the source.
-
03
Automated
Sensitive topics routed
Anything personal or sensitive gets your contact route and a staff alert.
-
04
Staff review
Office follows up
Staff reply to hand-offs and review unanswered questions.
-
05
Head of school or programme lead decides
Decisions about learners
Anything about a child's welfare, support or discipline is handled by designated staff.
How it behaves
How the school AI assistant behaves
What families see
- A clear note that they are talking to an automated assistant
- Short answers from school-approved pages, with a link
- Answers in their language where approved
- A staff contact for anything about their child
What staff see
- Hand-offs with the conversation so far
- Draft inbox replies to approve
- A weekly list of questions the assistant could not answer
What the automation does
- Answers only from the approved library
- Refuses and routes sensitive topics
- Logs every conversation for review
Edge cases and fallbacks
- A parent raises a wellbeing or safeguarding concern
- No AI answer; the school's safeguarding contact route is shown and staff are alerted at once.
- Question about a specific child
- Handed to the office; no personal information is discussed.
- A pupil appears to be using the chat
- The assistant points them to a trusted adult and the school office and collects nothing.
- AI provider outage
- The widget falls back to a contact form.
- Question not in the library
- The assistant says it does not know and offers a person.
Architecture
An AI assistant for a school at a glance.
- Input
- Logic and services
- AI step
- Data
- Output
- People
How it flows
- 1 A parent or adult learner asks a question and is told the assistant is automated.
- 2 The assistant retrieves the matching approved answers and passes them, with fixed rules, to the language model.
- 3 Routine questions get an answer with a link to the source, in the family's language if approved.
- 4 Anything personal or sensitive goes to staff, and every conversation is logged for review.
Project planner
How the project runs, phase by phase.
AI assistant for parents & learners project plan
Typical time to launch: about 6 weeks, then support
-
01
Discovery
About 1 week
Real questions from the office and inbox, languages, and what the assistant must refuse.
-
02
Answer library
About 1 week
Write and approve answers with the office and leadership, including safeguarding contact wording.
-
03
Build
About 2 weeks
Widget, inbox drafts, retrieval, hand-off alerts, logging and admin view.
-
04
Test
1 to 2 weeks
Real, tricky and sensitive prompts; the designated safeguarding lead signs off.
-
05
Launch
2 to 3 days
Soft launch on admissions and term pages, then widen.
-
06
Support
Ongoing
Weekly transcript review at first, then termly updates.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and answer library
Real questions, approved answers and hand-off wording.
$500 – $1,200
-
Build
Assistant, widget, inbox drafts, retrieval and admin view.
$1,200 – $4,000
-
Integrations
Website, inbox and staff alerts.
$300 – $1,000
-
Testing and evaluation set
Real, tricky and sensitive prompts before launch.
$300 – $900
-
Launch and training
Soft launch and office walkthrough.
$200 – $400
-
Total project estimate
$2,500 – $7,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. A website-only assistant in one language sits at the lower end. Model usage is billed to your account directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- AI model usage: Billed by the provider per use; short answers cost little per conversation.
- Hosting: n8n Cloud from about €20 a month, or your own server.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
EU: tell people they are talking to AI
Article 50 of the EU AI Act requires AI systems that interact with people to inform them they are interacting with an AI system, from 2 August 2026.
Source: artificialintelligenceact.euUS: COPPA and children under 13
COPPA applies to online services directed to children under 13 or with actual knowledge of collecting their data, and requires verifiable parental consent. The assistant is aimed at parents and adult learners and does not collect children's personal information.
Source: www.ftc.govUK: children's consent age
Under UK GDPR Article 8, a child under 13 cannot consent to online services without a parent, so the assistant is not offered to younger pupils.
Source: www.legislation.gov.ukFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
AI assistant for parents & learners questions, answered.
Term dates, fees, uniform, transport, clubs, course dates, entry requirements, policies and how to apply, all from your approved information. It does not discuss individual students.
It is built for parents and adult learners, not young pupils, answers only from approved pages and hands anything sensitive to staff. Your designated safeguarding lead signs off the hand-off wording before launch.
Yes. It can draft replies to the help inbox for staff to approve, as well as answering on the website.
Yes. For colleges and training providers it covers course details, start dates, fees and application steps, and hands individual cases to admissions.
Yes, where you approve it. Answers come from the same approved sources, and you can review translations of key pages.
Track questions answered without a hand-off, emails to the office, out-of-hours questions answered and gaps in the library from the weekly review.
Free 20-minute call
Want this for your schools & training?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for schools & training
All servicesEducation CRM & enquiry pipeline
Every family or learner enquiry from web, phone, open days and social in one education CRM, with tour bookings, polite follow-ups and a weekly view of enquiries, visits and applications by source.
From $1,000 · About 4 weeks Details
Admissions documents, offers & enrollment
Applications checked for missing documents, reminders sent to families, assessment and interview slots booked, offer and acceptance steps tracked and enrollment forms collected before the first day.
From $1,000 · About 4 to 5 weeks Details
Attendance alerts & parent communications
Same-day absence messages to parents from your MIS or SIS, replies logged for the attendance officer, trip and payment reminders, and routine notices sent in each family's preferred language and channel.
From $1,000 · About 4 weeks Details