How to Teach Chatbots to Preschoolers

There are two kinds, and confusing them causes most of the misunderstanding. A rule-based chatbot follows a script somebody wrote: if the message contains this, reply with that. It can only handle what was anticipated, and a child can build one in an afternoon. A generative chatbot produces each reply by predicting text, so it can respond to anything — including things nobody planned for, which is both why it feels impressive and why it can go wrong. Building the first kind is the fastest way to understand the second, because a child who has written the rules knows exactly where the intelligence came from.

The part worth getting right early is the misconception. Most people assume that a chatbot that says it is happy to help, or says it likes you, means anything by it. In fact it produced the words most likely to follow. There is nothing behind them — which matters enormously as children start using bots that are deliberately designed to feel like company. Correcting that once, early, saves a great deal of confusion later — and it is the single idea most likely to stick with preschoolers.

Reading level: Pre-reading to early letter recognition. Maths assumed: Counting, simple more-or-less comparisons. Realistic focus in one sitting: about 10 minutes. Pushing past that produces activity, not learning — the child keeps clicking but stops forming a model of what is happening.

Supervision: Constant, shared-device only. Keep any screen portion under ten minutes and always alongside an adult. Physical activities carry the learning at this age.

Preschoolers are at the point where they can articulate a rule they have just noticed, which is exactly what makes this age band different from toddlers. They can watch a drawing game guess what they are drawing, and they can tell you it got it wrong. That single exchange — machine guesses, guess is wrong, child notices — is the whole foundation.

What they cannot yet do is connect the guess to anything the machine learned. Training data is not a concept that lands at four. So resist explaining where the guess came from; the goal is only that a machine guessing is normal, and that a confident guess can still be wrong.

Be the chatbot (about 15 minutes, ages 5–9). You need: Index cards. 1. Write five questions on cards and five fixed replies. 2. The child may only answer using a card, matching as best they can. 3. Now ask something with no card and see what they do. 4. Together, write the fallback card. You will know it worked when the child can explain that the bot only knows what someone wrote on a card.

There is no screen-based tool worth recommending at this age. That is a real finding, not an omission — the concepts land better through physical activities, and the tools below become useful later.

The most common failure is starting with the mechanism instead of the behaviour. Adults reach for how the system works internally, because that is the interesting part to an adult. Someone at ages 3–5 needs to see the thing behave — make a right guess, then a wrong one — before any explanation of the internals means anything.

The second failure is treating a correct output as the end of the lesson. The learning is concentrated in the failures: the lighting that broke the classifier, the accent it could not parse, the example nobody thought to include. Budget deliberate time for breaking the thing on purpose, and treat every break as the result rather than as a problem to hide.

The third is over-supervising or under-supervising relative to age. Constant, shared-device only. Getting this wrong in either direction costs you — too little and the session drifts, too much and the learner stops making the guesses that teach them anything.

First, every age given is the age the tool becomes genuinely usable, not the vendor's marketing age. Those differ often. 4 tools are deliberately excluded here for being past this band — Scratch (about age 6), Machine Learning for Kids (about age 8), Google Dialogflow (about age 14), ChatGPT (about age 13).

Second, only tools with a genuinely free tier are listed — free meaning a real project can be finished without paying, not a trial that expires mid-activity. Every tool here needs an adult to create the account, which is itself a reason to keep the list short.

Third, "no screen tool is appropriate yet" is treated as a valid answer rather than a gap to fill. Where this page recommends physical objects over software, that is the recommendation, not an omission.

You can verify all of this yourself in about ten minutes: open each tool listed, check whether it demands an account or payment before producing anything, and see whether someone at ages 3–5 can reach a first result without an adult reading the interface aloud. If any recommendation here fails that test, it is wrong and worth telling us about.