How to Teach Chatbots to Teens

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 teens.

Reading level: Full independent reading, including documentation. Maths assumed: Algebra, graphs, and statistics — enough for the real concepts. Realistic focus in one sitting: about 50 minutes. Pushing past that produces activity, not learning — the child keeps clicking but stops forming a model of what is happening.

Supervision: Light. Agree on tools and accounts, then get out of the way and ask to see the result. Session length stops being the constraint. What matters is whether the time produces something testable rather than passive watching.

The line a teenager needs to cross is from tutorials to a project with a claim attached. A browser demo that classifies two objects is a starting point, not a result. A project becomes defensible when it has a question, a measurement, and an honest account of where it failed — which is also exactly what a science fair judge, a teacher, or eventually an admissions reader is looking for.

This is also the age where the ethical dimension stops being abstract. A teenager who has measured their own model performing worse on under-represented examples has an argument grounded in their own evidence, which is a fundamentally different thing from repeating that AI can be biased. Push for the measurement; the argument follows from it.

Build a Scratch chatbot (about 45 minutes, ages 7–13). You need: A laptop and Scratch. 1. Pick a narrow subject the child knows well — a pet, a game, a hobby. 2. Use ask-and-wait plus if-then blocks for five questions. 3. Add a fallback reply for anything unmatched. 4. Let someone else use it and write down every question that fell through. 5. Add rules for the three most common misses. You will know it worked when the child can name what their bot cannot do and explain why.

Rules versus generative, side by side (about 40 minutes, ages 11–18). You need: The Scratch bot from above and an approved generative chatbot. 1. Ask both the same ten questions, including three deliberately odd ones. 2. Record where each succeeded and failed. 3. Note which failures were obvious and which were confident and wrong. 4. Write which you would trust for a factual question, and why. You will know it worked when the learner can articulate that a visible failure is safer than a plausible false answer.

The shortlist is deliberately short. A child who uses one tool properly and finds its limits learns more than one who samples six. Start at the top of this list and only move on when the current tool stops being able to answer the next question.

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 13–18 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. Light. Agree on tools and accounts, then get out of the way and ask to see the result. 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. Nothing in this collection was excluded on age grounds for this band.

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. 1 of the 4 can be used with no account at all: Scratch. That matters more than it sounds at this age, because an account is a data-collection decision a parent has to make on a child's behalf.

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 13–18 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.