Yes, for the questions parents ask first and for booking a show-round. A chatbot can answer fees, hours, rooms, meals and settling-in, check the basics of fit (child's age, days, start date) and offer visit slots from a booking page. It should hand anything about a particular child, such as allergies, additional needs or a place offer, to the manager.
The catch is trust. Parents are choosing who looks after their child, and they judge the setting by its first reply. A chatbot that answers instantly but gets the fees wrong, or implies there's a place when there's a waiting list, does more harm than a reply the next morning. So the design principle is narrow and accurate: answer only from your own documents, never promise a place, and make the hand-off to a person feel like good service rather than a dead end.
The enquiry journey, stage by stage
| Stage | What parents want | Chatbot's role |
|---|---|---|
| First question | Fees, hours, age range, "do you have space?" | Answer from the knowledge pack; explain how availability works |
| Fit check | Will my child's age and days work? | Collect child's age in months, days wanted, start date |
| Availability | A straight answer | Never confirm a place; offer a visit or waiting list; manager confirms |
| Show-round booking | A time that suits them | Offer slots from the booking page; send confirmation |
| Before the visit | Where to park, what to bring | Automatic reminder the day before |
| After the visit | Next steps, forms | Send the registration pack; manager handles questions |
| Anything about their child's needs | Reassurance from a person | Collect a contact number and hand off the same day |
The knowledge pack the chatbot answers from
Write one document the chatbot is allowed to use, and nothing else. Keep it factual and dated. An illustrative excerpt for a nursery with three rooms:
KNOWLEDGE PACK (updated 01/09/2026, next review 01/12/2026)
Opening: Mon-Fri 7:30-18:00, closed public holidays and 1 week at New Year
Rooms: Babies 3-24 months | Toddlers 2-3 years | Pre-school 3-5 years
Sessions: full day 7:30-18:00; morning 7:30-13:00; afternoon 13:00-18:00
Fees: full day $X; half day $Y; minimum 2 days a week
Fees include meals, snacks, nappies and wipes. Formula milk not included.
Funding: we accept [name the childcare funding schemes you accept].
For eligibility, parents should check with the scheme directly.
Meals: cooked on site; menus on the website; we cater for dietary needs
after a conversation with the manager.
Allergies: we are a NUT-AWARE setting, not nut-free. [exact policy wording]
Settling in: two free sessions of 1 hour, then 1 half day.
Availability: we do not confirm places by chat. The manager confirms
availability within 1 working day after the enquiry.
Show-rounds: Tue-Thu at 10:00 or 14:00, 30 minutes, with the manager.
Parking: two visitor spaces at the front; buggies can come inside.Two lines in there matter more than the rest. The availability line stops the chatbot guessing, and the allergy line gives exact wording, because "nut-aware" and "nut-free" mean very different things to a parent of a child with an allergy. Detail on structuring this kind of document is in training an AI chatbot on your FAQs, policies and prices.
Funding questions need one more line, because chatbots like to do sums. A parent asks, "If I get funded hours, how much would three days cost me?" An illustrative reply from a bot without the rule: "With funding, three days would cost about half the usual fee." That figure depends on the child's age, the parent's eligibility, which sessions the funding covers and how your setting applies it, none of which the bot knows. Add to the pack: "Never calculate a price after funding. Give the full fee, say the nursery accepts [schemes], and offer the manager's help to work out the parent's own figure." The fixed reply quotes the full fee and hands the funded figure to a person, which is also the conversation the manager wants to have.
How show-round booking works in practice
Keep booking separate from the chatbot's "brain": the chatbot collects the basics and then sends the parent to a booking page, or shows the next available slots if your tool integrates with one. That way the calendar, not the AI, is the source of truth for times.
- Calendly: the free plan allows one event type, which is enough for "Show-round, 30 minutes". Standard adds unlimited event types and automations from about $10 a seat a month.
- Google Calendar appointment schedules: a personal Google account or Workspace Business Starter gives you a single booking page; higher Workspace plans add extras such as email reminders and checking several calendars.
- Your nursery software's enquiry module: if it has one, it may already hold the waiting list, which avoids re-keying. Worth checking first; choosing nursery software with AI lists what to compare.
Offer visit slots at quiet times, such as mid-morning and mid-afternoon, not during lunch or nap time, and cap them at two or three a day so the manager isn't pulled off the floor.
The booking page only knows what the calendar knows. In one realistic slip, a staff training day was on the nursery's wall planner but not in the booking calendar, so two families booked show-rounds for a morning when the building was closed. It showed up when a parent arrived to a locked door. Block every closure day, training day and holiday week in the booking calendar at the start of each term, and make it part of the same review that updates the knowledge pack's dates.
A 60-place nursery's first month with a chatbot
Here's how it could look for an illustrative 60-place nursery getting about 25 enquiries a month, roughly half of them in the evening or at weekends. Before the chatbot, the manager replied the next working day, and a few parents a month had already booked visits elsewhere by then.
The nursery added a website chat widget with an AI agent, loaded the knowledge pack, and linked a Calendly show-round page. A typical evening conversation (illustrative):
Parent: Hi, how much is it for 3 days a week for a 10 month old from January? And do you have space?
Chatbot: Hi, I'm the nursery's automated assistant; the manager picks up anything I can't answer. A full day in our baby room is $X, so three full days a week would be 3 × $X a week, including meals, nappies and wipes. We don't confirm places by chat, because availability changes week to week, but the manager will let you know about January within one working day. Would you like to book a 30-minute show-round? The next slots are Tuesday at 10:00 or Wednesday at 14:00.
Reviewing transcripts in week one turned up two problems worth copying lessons from:
- A place was implied. An older "welcome pack" PDF, uploaded as background, said "we currently have spaces in all rooms". The chatbot quoted it to two parents. The fix: remove every document except the knowledge pack, and add a hard rule never to comment on current availability.
- "Nut-free" appeared. A parent asked whether the nursery was nut-free and the chatbot said yes, because "we cater for dietary needs" sounded close enough. The exact allergy line in the knowledge pack above was added after this, plus a rule to hand any allergy or medical question to the manager after quoting the policy.
By the end of the month, most first replies were instant, evening enquiries were being booked into show-round slots, and the manager's evening inbox was mostly hand-offs that genuinely needed her. Whether that pays back depends on your fees and how many enquiries you currently lose; website chatbot cost and payback has a way to work it out.
A rough version of that sum for this nursery: Tidio Starter plus Lyro's entry tier from the table below comes to about $57 a month, or roughly $680 a year. If a two-day-a-week place brings in, say, $600 a month and a child typically stays two years, one registration is worth about $14,400 in fees. So the chatbot pays for itself if it keeps just one family a year from registering elsewhere while waiting for a reply. Put your own place fee and length of stay into the sum; the useful comparison is always one extra child against the annual cost.
After the visit: the follow-up that turns visits into registrations
The chatbot's job ends at the booking, but AI can help with the step many nurseries rush: the follow-up after a show-round. Parents often visit three or four settings in a fortnight, and a specific, personal follow-up the same day is memorable. The manager jots two or three lines after each visit, and AI turns them into an email she checks and sends.
The manager's note (illustrative):
Visit Tues 10:00. Mum + 10-month-old, 3 days from Jan.
Worried about settling: never been left with anyone but grandparents.
Loved the garden. Asked about the key person system.The draft after a two-minute edit:
Thank you for visiting this morning; it was lovely to meet you both. You mentioned your little one has only ever been left with grandparents. That's very common, and it's why settling in starts with two free one-hour sessions, and you're welcome to stay in the room for the first one so your baby can get to know their key person with you nearby. You also asked about key persons: each baby has one named practitioner who does most of their care and is your main contact. I've attached the registration pack. I'll confirm January availability by Thursday, and I'm happy to answer anything else by phone.
The manager checked one thing before sending: that parents really can stay in the room for the first settling-in session, which was true for her setting. The two free sessions came from the knowledge pack; the "stay in the room" promise came from the AI, which had no way of knowing it. Anything the email promises about how the nursery works has to come from the manager, so read every reassurance line as if you'll be held to it, because you will. Keep the parent's first name and your notes in your enquiry system rather than in a chat history, and use a business AI plan for these drafts.
What always goes to the manager
These topics get a short, warm hand-off, never an AI answer beyond quoting your written policy:
- Allergies, medical conditions and medication
- Additional needs, development worries or anything about a diagnosis
- Safeguarding, staff checks or anything that sounds like a concern
- Place offers, start dates, contracts, deposits and discounts
- Complaints, or a parent who sounds upset
- Questions about a named member of staff
The hand-off message matters. "I'll pass this to our manager, who'll call you by tomorrow lunchtime. What's the best number and time to reach you?" feels like care. "I can't help with that" feels like a door closing.
Additional needs are where an over-eager bot does most harm, because the kind answer and the right answer differ. An illustrative exchange before the rules were tightened:
Parent: My son is 2 and has a speech delay, he sees a speech therapist. Would you be able to support him?
Chatbot: Absolutely! Our practitioners are experienced in supporting children with speech delay and will work closely with his therapist to help him thrive.
Every claim in that reply is a promise the bot can't check: staff experience, liaison with therapists, the level of support. The fixed reply: "Thank you for telling me about your son. Our manager talks every family through how we'd support their child, so I'll pass this to her and she'll call you by tomorrow lunchtime. What's the best number to reach you? You'd be very welcome to mention it at a show-round too." It's warmer, not colder, because it treats the question as important enough for a person.
Instructions for the chatbot
You answer enquiries for a day nursery.
Open every chat: "Hi, I'm the nursery's automated assistant; the
manager picks up anything I can't answer."
ALWAYS
- Answer only from the knowledge pack. Quote fees exactly.
- Collect: parent first name, contact number or email, child's age
in months, days wanted, preferred start date.
- Offer a show-round using the booking link.
NEVER
- Confirm or hint at availability or a place.
- Answer allergy, medical, additional-needs or safeguarding questions
beyond quoting the exact policy line; then hand off.
- Ask for the child's full name, date of birth or health details.
- Discuss discounts or negotiate fees.
HAND OFF with: "I'll pass this to our manager, who'll get back to
you by [time]. What's the best number to reach you?"
Tone: warm, calm, plain. Under 90 words per reply.Choosing a tool for a nursery's volume
Nursery enquiry volumes are low compared with a shop's, so pick pricing that suits 20-60 conversations a month rather than thousands.
| Tool type | List price (USD) | Fits a nursery when |
|---|---|---|
| Website chat with an AI add-on (e.g. Tidio with Lyro) | Tidio Starter $24.17/month billed annually; Lyro from $32.50/month for 50 conversations | Most enquiries come through the website |
| Help desk with per-resolution AI (e.g. Intercom Fin) | $0.99 per outcome plus seats (Essential $29/seat/month, annual) | Usually more than a single nursery needs |
| WhatsApp Business app with Meta Business Agent | App free; agent charged per token, roughly 4-5 cents a message | Most of your parents message on WhatsApp |
| Nursery software enquiry forms | Often included in your subscription | You want enquiries straight onto the waiting list |
For WhatsApp, a quick sum keeps the per-message charge in proportion. At 25 enquiries a month and around eight agent messages per conversation, that's about 200 messages; at Meta's rough figure of 4-5 cents each, roughly $8 to $10 a month, with no free allowance since charging began in August 2026. Meta's terms allow a bot tied to one business task such as enquiries and bookings, but not a general-purpose assistant, which is another reason to keep the bot's instructions narrow.
Nursery software vendors are adding assistants of their own, so check the one you use before adding anything. Procare bought Playground, with its Camber AI assistant, in September 2026, and Blossom Educational is now called Ovivio, with an assistant named Bloom. Whether these answer website enquiries or mainly help staff inside the software is the question to put to your vendor.
Before signing up, run the vendor through the questions to ask an AI chatbot vendor, especially where conversation data is stored and for how long.
Being open with parents and careful with their data
Say it's automated in the first line. That's good practice anywhere, and if your nursery serves families in the EU, the EU AI Act's transparency rules have required it for chatbots since 2 August 2026; what to tell customers at the start of a chat has wording options. Collect only what you need to reply and book a visit: a first name, contact details, the child's age in months, days and start date. Don't ask for dates of birth, surnames or health information in chat, and add the chatbot to your privacy notice with how long transcripts are kept.
Measures that show the enquiry bot is winning show-rounds
- Enquiry to show-round: the share of chats that end in a booked visit. Compare with the previous three months of email and phone enquiries.
- Show-round no-shows: if they rise, add a reminder the day before and a one-tap "can't make it" link.
- Hand-off speed: are hand-offs answered by the time the chatbot promised?
- Transcript review: read ten a week for the first month. Look for anything that sounds like a promise.
- Ask at the show-round: "How did you find getting in touch with us?" Parents will tell you.
An illustrative first-month scorecard for the 60-place nursery, against the three months before:
| Measure | Before (monthly average) | Month one |
|---|---|---|
| Enquiries | 25 | 27 |
| Show-rounds booked | 9 | 14 |
| No-shows | 1 | 3 |
| Hand-offs answered by the promised time | Not tracked | 11 of 13 |
| Transcripts with a problem | Not applicable | 2 of 40 read |
Read it row by row. More visits booked is the headline, but the rise in no-shows says evening bookings are easier to make and easier to forget, so the day-before reminder goes in. The two late hand-offs both fell on the manager's day off, which is a rota fix, not a chatbot fix: the promised reply time should say "within one working day" or name a deputy.
Once children start, AI can help behind the scenes too; using AI for observations and learning journals covers the rules for that very different job.
Further reads
- Is It Safe to Use AI With Children's Data in a Nursery? — What children's data a chatbot should never collect or store.
- 9 AI Chatbot Mistakes That Lose Small Businesses Customers — The chatbot errors that quietly lose enquiries.
- How Wedding Venues Use AI for Viewings, Enquiries and Follow-Ups — Another viewing-led business: useful ideas for post-visit follow-ups.
- AI Booking Systems for Appointment Businesses: What to Check — What to check in a booking tool before parents use it.
- How to Measure Customer Reaction After Introducing AI — How to find out what parents really think of the chatbot.
- Should You Build or Buy an AI Chatbot for Customer Service? — Off-the-shelf widget or something custom: the trade-offs.
- AI Ethics for Small Businesses: A Practical Checklist — Twenty-five questions in six groups, each with why it matters and how to check, plus red lines and a nursery example run end to end.
- How Nurseries Use AI to Write Daily Reports for Parents — The drafting step from practitioner notes to parent's phone, built-in writing assistants, a house style card, and the wrong-child mistake to design out.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Tidio, Intercom and Calendly pricing pages; Google Calendar help on appointment schedules (all checked September 2026); Meta's Business Agent pricing and WhatsApp Business terms; EU AI Act Article 50; Procare and Ovivio announcements. Nursery figures and conversations are illustrative.