Get started

An AI phone agent for the calls your childcare center cannot get to

A childcare center's phone problem is a ratio problem. The director is covering a classroom, the front desk is managing drop-off, and every adult in the building is supervising children — the one job that cannot be interrupted. Meanwhile the phone carries the center's future: a parent calling about an opening, a family asking about the waitlist, a guardian running late for pickup. Many of those calls arrive in the evening, when nobody is at the desk at all, and a new-family inquiry that lands in voicemail is often an enrollment lost to whichever center answers first.

ThunderPhone gives a childcare center, daycare, or preschool an AI phone agent that works in both directions: inbound coverage for the calls you receive, and outbound campaigns for the calls your team never has time to place. It follows your instructions and searches your approved knowledge base without inventing policy.

Two boundaries are fixed from the start. First, every caller the agent serves is a parent or guardian, and every outbound call is parent-directed — the agent never communicates with children. Second, the agent is an administrative assistant, not a caregiver: it never discusses an individual child's day, behavior, or development — those conversations route to your teachers and director. And because childcare calls routinely involve information about children, how recording and consent are configured is the operator's responsibility to set deliberately before going live — more on that below.

What a childcare phone agent can handle

Enrollment inquiries and tour scheduling

The first call from a prospective family follows a predictable shape: the child's age, the desired start date, the schedule the family needs, and how they found the center. The agent can walk through that intake conversationally, answer approved questions about programs and availability, and book the concrete next step — a center tour — through a connected calendar or scheduling API. The structured record lands in your system, so the director walks into the tour already knowing the family.

Waitlist intake and position questions

Infant rooms fill first and stay full, so the waitlist is where much of a center's enrollment actually lives. The agent can take a waitlist request with the fields your team needs — child's date of birth, desired start month, schedule — and explain your written waitlist policy from approved content: how the list works, whether there is a fee, what happens when a spot opens. What it does not do is quote a family's current position or predict when a spot will open; those answers depend on your director's judgment, so the agent captures the question and routes it to staff instead of guessing.

Absence and late-pickup reporting

"Mia won't be in today" and "I'm stuck in traffic, I'll be fifteen minutes late" are calls that need accurate capture more than conversation. The agent records the absence — child, classroom, reason if offered, expected return — and delivers it to your systems immediately, so the morning check matches reality before ratios are set. Late-pickup calls capture who is coming and when; anything about changing who may pick a child up routes straight to staff, because release authorization is never an agent decision. Every report arrives as a structured record instead of a scribbled note.

Tuition and schedule questions from approved content

"What are your hours?", "what does the toddler room cost?", and "are you open the Friday after Thanksgiving?" interrupt a front desk all day, and they have stable answers. Load your rate sheet, program schedules, holiday calendar, and policy handbook into the knowledge base, and the agent answers from that material — and only that material. Questions about a specific family's account, balance, or subsidy paperwork route differently: the agent collects who is calling and what they need, then transfers to your billing contact or files a structured callback task rather than improvising a number.

Enrollment-paperwork reminder calls

Where state licensing rules require immunization records and health forms on file before a child's first day, paperwork-chasing becomes a deadline workflow. An outbound campaign can call families with a confirmed start date and outstanding items, remind them what is still needed and where to send it, answer approved questions about the requirements, and log each response. The agent works from your checklist of what is missing — it names the form, never the contents.

Seasonal-program registration

Summer camps and school-break programs compress a year of enrollment questions into a few weeks. An outbound campaign can work your list of current and past families with a script your team approves — announce the program, answer approved questions about dates, ages, and pricing, and capture registrations or book enrollment calls directly. Inbound, the same agent absorbs the registration-season call spike without adding seasonal staff. All outreach is parent-directed and runs under the consent and calling rules you configure; deciding who may be called, when, and under what consent is the operator's responsibility.

Closure notification calls

When a room closes for a staffing gap or the center closes for weather, every affected family needs to hear it, fast, by a channel they will actually notice — and a ringing phone gets attention that an email does not. An outbound campaign can call your family list with the approved message: what is closed, why, and the expected reopening. Voicemail detection can leave your configured message or retry on the schedule you set, and every outcome — reached, voicemail, unreachable — comes back by webhook, so the director can see at a glance who still needs a personal call.

New-parent orientation scheduling

Between "you're enrolled" and the first drop-off sits a sequence most centers run by hand: the orientation session, the classroom visit, sometimes a gradual-start schedule. The agent can call newly enrolled families to book orientation into the director's available slots, confirm the details as the date approaches, and answer approved logistics questions — what to bring, where to park, how drop-off works. Families arrive on day one already oriented, and the director's calendar fills without a week of phone tag.

Multilingual parent communication

For many centers, the families hardest to serve by phone are the ones who need care most — parents who are not comfortable in English often cannot call and expect to reach someone who speaks their language, and the language gap follows them from the first inquiry through every absence report. ThunderPhone supports 47 voice languages. Set a primary language and the additional languages your community speaks, and the agent can switch mid-call when a caller changes to one of them — no separate line, no waiting for the one bilingual staff member. The same rules apply in every configured language, and every call produces a transcript your team can review.

After-hours inquiry capture

Parents search for childcare at night, after the children are asleep. After close, the agent keeps answering: it captures new-family inquiries in full, books tours into open slots, takes next-morning absence reports, and answers schedule and policy questions from the knowledge base. Anything it cannot resolve becomes a structured, categorized message in your queue instead of a voicemail — and the family that called three centers at 9 p.m. remembers the one that answered.

Sample childcare call flow

Agent: Thank you for calling Willow Grove Children's Center. Are you calling about enrollment, reporting an absence, or something else?

Caller: We just moved here and I'm looking for a spot for my daughter. She's 18 months.

Agent: Welcome to the area. May I ask when you would like her to start, and what schedule you are looking for?

Caller: Full time, starting in October if possible. Also — how is she going to do with the transition? She's never been in daycare.

Agent: That is a great question for our director, and the tour is the best place for it — she talks through the transition plan with every new family. I can offer a tour Wednesday at 9:30 a.m. or Friday at 4:00 p.m. Which works better?

Caller: Wednesday. Do you have anyone who speaks Portuguese? My husband may call sometimes.

Agent: Yes. This line supports Portuguese — he can simply speak it when he calls and I will follow. You are booked for Wednesday at 9:30 a.m. Would you like me to repeat the details?

Whenever a caller asks about a specific child's experience — how they are adjusting, what happened at lunch, how they are developing — the agent schedules the right conversation or routes to staff rather than answering it.

Guardrails a childcare center should configure

The agent does what your configuration says, and these are the guardrails that matter when the callers are parents and the subject is children:

  • Parent-directed communication only. The agent serves parents and guardians. Outbound campaigns call the parent and guardian contacts on your list, never children, and the greeting confirms it has reached a parent or guardian.
  • Recording and consent are the operator's responsibility. Childcare calls routinely involve information about children. How recording is configured, what consent your jurisdiction and enrollment agreements require, what the agent may collect, and where call data may be sent are your settings to configure deliberately — with your own counsel's guidance where needed — before the agent takes a single live call.
  • No individual-child conversations. The agent never discusses a specific child's day, behavior, or development, and never characterizes how a child is doing. Those questions route to teachers or the director every time.
  • Emergencies follow your script. If a caller reports an emergency or raises a child-safety concern, the agent follows the center's written script exactly and escalates immediately — a warm transfer to the director or on-call number, or your configured urgent path. It never handles these calls itself.
  • Scope the knowledge base. Attach rate sheets, policies, calendars, and logistics — not child records. Give the agent only what any parent may hear.
  • Pickup authorization stays human. The agent can record that someone is running late; it never adds, confirms, or changes who is authorized to pick a child up.

Features that matter in a childcare center

Scheduling and center-system connections

Agents can use connected apps, HTTP APIs, or MCP tools during a call — checking tour availability, booking an orientation, or filing an absence when the receiving system exposes the action. Webhook deliveries are HMAC-signed and retried automatically, so a briefly unavailable endpoint does not lose an inquiry.

Knowledge grounded in your documents

Attach parent handbooks, rate sheets, program descriptions, and holiday calendars — as text or PDF/DOCX uploads (up to 5 MB per text file and 50 MB per PDF or DOCX), or imported directly from your website. Each agent uses only the documents you scope to it.

Your numbers, your telephony

Bring your center's existing numbers through a supported VoIP connection or SIP configuration; verified numbers handle inbound and outbound calling. A web voice widget can put the same agent on your website, so a parent browsing at 9 p.m. can ask by voice without dialing.

Human handoff

Cold transfers are available for immediate routing. Warm transfers work on eligible production VoIP or SIP numbers that can place an outbound leg: the parent waits while the agent privately briefs the director, then connects only if the director accepts.

Compliance posture

ThunderPhone is GDPR and HIPAA compliant. The center still controls the workflow: what the agent collects, how recording and consent are configured for calls involving children's information, and where call data flows are the operator's decisions.

Testing before parents hear it

Use a browser mic test for quick iteration, then run AI-caller simulations of the scenarios that worry you — a parent asking how their child behaved today, a late-pickup call at closing time, a mid-sentence language switch, a caller reporting something urgent. Simulations create transcripts and grading, and graded scenarios can be kept as a regression suite so a prompt change never quietly breaks the no-individual-child rule or the emergency script. When two scripts seem equally good, an A/B experiment on live traffic settles it. Production calls produce transcripts, recordings where enabled, and grading the center can review.

What would this cost each month?

Suppose a center handles 600 AI-assisted calls per month, averaging 3 minutes each:

600 calls × 3 minutes = 1,800 minutes per month

  • Spark: 1,800 × $0.02 = $36/month
  • Bolt: 1,800 × $0.05 = $90/month
  • Storm: 1,800 × $0.09 = $162/month

That is base engine usage, not a quote. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.

Frequently asked questions

Can a ThunderPhone agent book center tours?

Yes, when it is connected to a calendar or scheduling API that permits the action. The agent gathers the required fields, checks available times, books or reschedules, and confirms the result. The connection can be an HTTP API, an MCP server, or a webhook into the center's own systems.

Will the agent tell a parent how their child is doing?

No. The agent never discusses an individual child's day, behavior, or development. When a parent asks, it captures the question and routes the conversation to the child's teacher or the director — a boundary you write into the prompt and test with simulations before launch.

What happens if a caller reports an emergency?

The agent follows the center's written script and escalates immediately — a warm transfer to the director or on-call number, or whatever urgent path you configure. Emergency and child-safety calls are never handled by the agent itself; your script defines the exact action and the agent executes it.

Can it take absence and late-pickup calls?

Yes. It records the report — child, classroom, timing, reason if offered — and delivers it to your systems immediately by webhook, so staff know before ratios are set or closing time arrives. Anything touching pickup authorization routes to a person; the agent never changes who may collect a child.

What about recording calls that involve information about children?

The center controls that, and it should be decided before launch. Recording settings, consent language, what the agent may collect, and where call data is sent are all operator configuration — set them deliberately, with your own counsel's guidance where needed, before the agent takes live calls.

Can it run closure-notification or paperwork-reminder campaigns?

Yes. Outbound campaigns can call your family list with an approved message — a weather or staffing closure, outstanding enrollment paperwork, or seasonal-program registration — and report each outcome by webhook. Campaigns are parent-directed and run under the consent and calling rules you configure; deciding who may be called and under what consent is the operator's responsibility.

Can one agent serve parents in multiple languages?

Yes. Configure a primary language and additional languages, and the agent can switch mid-call when the caller changes to one of them, provided the selected voice supports both. The same applies across ThunderPhone's 47 supported languages.

How do we make sure it sounds right before families hear it?

Test in the browser first, then run AI-caller simulations of your hardest scenarios — a parent pressing for details about their child's day, a frantic late-pickup call, an urgent report that must trigger the escalation script. Simulated calls are graded against your criteria and can be re-run as a regression suite whenever the prompt or knowledge base changes.