Skip to main content
EzyConn

EducationIndustries and use cases

AI Chatbot for Preschools

A preschool chatbot answers admissions, fees, term dates, open days and waiting list questions at any hour. Before it does any of that, it has to be built to say nothing at all about a named child.

EzyConn EditorialThe EzyConn blog 8 min read Updated

Try EzyConn Free

Read this part first

A chat window cannot check who is on the other end. That single fact decides the whole design. Set these limits before you write a word of content:

  • It never confirms or denies that a named child attends your setting.
  • It never discusses a named child at all, in any direction, for any reason.
  • It never shares staff names, room allocations or session timetables that would show where children are at a given time.
  • A message that claims to be from a parent proves nothing and must unlock nothing, including collection changes and absence reporting.
  • Any message that sounds like a safeguarding or welfare concern goes to a named human immediately, with your designated lead's contact route in the same reply.

None of that makes the bot useless. It makes it a front door, which is what a preschool website needs anyway.

The 30-second answer

Almost every enquiry a preschool receives is one of five things: is there a place, what does it cost, when are your term dates, when can we visit, and how does the waiting list work. Those answers are public and fixed. A chatbot trained on your own website gives them instantly, evening and weekend included, and captures a complete enquiry instead of a missed call. Everything that touches a specific child goes to a person.

The enquiry that arrives at 9 p.m.

Parents research childcare after their own child is asleep. That is the hour they open six nursery websites, compare them, and message the ones that make it easy. Your office is closed. A contact form that promises a reply within two working days is a fair thing to offer and a poor thing to compete with.

A chatbot changes the shape of that evening. The parent gets your fee schedule, your session patterns and your next open day date immediately, and leaves their details in a form that already knows what they were asking about. Your manager opens the inbox in the morning to a warm enquiry with context attached. If you also run a day nursery alongside the preschool, our guide to AI chat for childcare providers covers the wider centre operation.

What it answers, and where it stops

Question
What the bot does
Hard limit
Admissions and availability
Explains age ranges, session patterns and how to apply
Cannot say whether a named child has a place
Fees and payment dates
Quotes your published fee schedule and billing cycle
Never discusses an individual account
Term dates and closures
Reads straight from your published calendar
Nothing sensitive here
Open days and visits
Gives dates, takes names and contact details, books a slot
Confirmation comes from staff
Waiting list
Explains how the list works and captures a full enquiry
Never reveals a position or another family
Anything about a named child
One polite refusal and a route to a named person
Full stop

Admissions, fees and the questions behind them

Admissions questions are rarely one question. A parent asking about availability is really asking four things at once: do you take children this age, do you have the days we need, what will it cost, and how soon could we start. A bot that answers all four in one reply removes an entire round of email.

Fees deserve care. Quote your published schedule, your session lengths and your payment dates, and stop there. Do not let the bot interpret funding entitlements, work out what a family will pay after any scheme, or comment on eligibility. Those rules vary and they change. The right behaviour is to state what you publish and offer a person for the rest.

Open days and the waiting list

Open days are the point of the whole exercise, because almost nobody chooses a preschool without visiting. The bot should give the next dates, explain how long a visit takes, take a name and contact details, and pass the booking to staff to confirm. Reminders closer to the date are worth the small effort; a family that forgets a visit rarely rebooks.

Waiting lists need a firmer hand. The bot can explain how your list works, what information you need and roughly when you allocate places for each intake. It must never tell someone their position, mention another family, or hint at who is ahead of them. Capture the enquiry, be honest about the process, hand it over.

Families who do not speak English at home

A preschool catchment is often more international than the rest of the school system it feeds. EzyConn runs GPT-4o and Claude on every plan, learns your setting by crawling your own website, and answers in many languages. A parent asks about session times in Polish or Somali and gets your published answer back in the same language. You wrote it once, in English, and it now serves families you were previously reaching through a friend with better English. Our overview of multilingual AI chatbots explains the limits worth knowing.

What it costs

Start on the free plan: $0 forever, no credit card, two seats, 500 messages a month, one chat widget, one domain, the mobile app and 30 days of history. A single-site preschool outside admissions season often stays there.

If January enquiries push past the cap, Paid plans are Starter at $25 a month and Professional at $95 a month, with 20% off on annual billing. Annual billing is 20% cheaper. The pricing page has the full table.

Four steps to launch

Write the refusals first

Before you train it on anything, write down what it will never do. Named children, staff names, session timetables, collection changes, and anything that sounds like a welfare concern. Everything else is easier once these are fixed.

Train it on public pages only

Feed it your admissions page, fee schedule, term dates, open day listings and policies you already publish. Nothing from your management system. Nothing from a newsletter that names children.

Test it like a stranger

Spend twenty minutes trying to break it. Ask if Maya is in today. Claim to be a parent. Ask which room Mrs Hall works in. If any of those get an answer, fix the instructions and try again.

Give it one clear handoff

Every dead end should land somewhere specific: a named person, a phone number, an email, and the hours they answer. A refusal without a route is just a closed door.

Show the finished flows to your designated safeguarding lead before the widget goes live, and again whenever you retrain it. Scripting the exit properly is most of the work; our notes on chatbot to human handoff are a useful checklist.

Frequently Asked Questions

Is it safe to put a chatbot on a preschool website?

It is, provided you set the limits first. The chat window cannot verify who is typing, so the bot must never confirm that a named child attends, never discuss a named child at all, and never share staff names or session timetables that would reveal where children are. Set those refusals before you switch it on, not after.

What should a preschool chatbot actually answer?

Admissions questions, fees and payment dates, term dates and closure days, open day details, and how the waiting list works. It can also explain your session patterns, your settling-in approach in your own published words, and what a family needs to bring on day one. All of this is public information that already sits on your site.

What happens if somebody raises a welfare concern in the chat?

It goes to a named human straight away. Script one calm reply that acknowledges the message, gives the direct contact route for your designated safeguarding lead, and flags the conversation to staff. The bot should not ask follow-up questions, should not offer reassurance, and should not attempt to assess anything.

Can a parent use the chat to change a collection arrangement?

No. Anything that affects who collects a child, or when, has to go through your verified process with a person. A message saying 'I'm Ava's dad, grandma is picking her up' is not proof of identity or authority. The bot should say plainly that collection changes are handled by staff and give the phone number.

What does it cost to try one?

EzyConn's free plan is $0 forever with no credit card: two seats, 500 messages a month, one chat widget, one domain, the mobile app and 30 days of history. Paid plans are Starter at $25 a month and Professional at $95 a month, with 20% off on annual billing.

A front door that is open at bedtime

EzyConn learns your preschool from your own website, answers admissions, fees and open day questions at any hour, and routes everything sensitive to a named person.

Start Free

Last updated . Plan limits described here are EzyConn's own. This is not safeguarding or regulatory advice; agree your rules with your designated lead before publishing a chat widget. View more guides.