Fred: A Childcare Assistant That Won’t Guarantee What Only Your Director Can

A parent asks your center’s website whether their son will be safe and whether staff can give him his EpiPen. A general-purpose chatbot says yes to both. No director checked your staff training, your openings, or your ratios. The center wanted a tool to help families and start enrollment. It got one making promises about a child’s safety and medical care that only your director can responsibly make.

The threat and standard articles in this series walk through how that becomes a liability. This one is the answer: what a compliant AI assistant for childcare looks like, and why the design, not a disclaimer, is what keeps a website from guaranteeing safety, committing to care, or promising a spot.

The Real Choice Is Governed or Ungoverned

Providers ask whether to put AI on the site at all. Parents already decided. They research at night and want quick, clear answers before they tour. The real question is whether the assistant is governed.

An ungoverned chatbot guarantees safety, commits staff to medication, and promises openings it cannot see. A governed one explains your program, captures the inquiry, and routes safety, medical, and availability questions to your director. Same convenience, completely different exposure when a parent holds you to what the website said.

How Fred Holds the Line

Fred starts from the opposite default of a general chatbot. A generic bot answers anything unless told not to. Fred answers only what it is cleared to, and the boundary lives in the system rather than a prompt that drifts when a parent rephrases.

In practice, Fred works from your own content. It explains your program and philosophy and how enrollment works. It does not guarantee a child will be safe or commit staff to administering medication, because those are representations only your director can make, and an unsubstantiated safety claim falls under the FTC’s deceptive-practices authority. It does not promise a spot it cannot see, and it does not issue a categorical refusal to a disability question, because childcare centers are generally public accommodations under Title III of the ADA. Fred runs more than 50 industry guardrail packs, and the childcare pack is built around licensing-dependent answers, the medical-care line, and the ADA posture.

The design proves itself under pressure. A parent will ask "so you’d give him his EpiPen if he reacted?" several ways, and a prompt-instructed bot eventually reassures them. Fred does not rely on catching the phrasing. It decides what may be said before the reply forms, so a safety guarantee or a medical commitment never reaches a parent. "Will not" is a suggestion. "Cannot" is an architecture.

Fred vs. a Generic AI Chatbot

That single screen is the argument. A general chatbot is reassuring until reassuring becomes a safety guarantee or a medical commitment. Fred is helpful across everything that moves a family toward enrollment and structurally incapable of promising what only your director can.

What Your Center Actually Gets

Set the rules aside and look at the front office. Fred handles the after-hours questions that usually wait for a callback, what are your hours, what’s your philosophy, how does enrollment work, can I schedule a tour, and answers them instantly. It captures inquiries with the details your director needs, and routes safety, medical, and availability questions to people.

The captured-family math is the real win. The parent who gets a warm, accurate answer at 9 p.m. is the one who books a tour, instead of the one who moved on to the next center. Fred turns the after-hours window into tours and enrollments without ever putting a safety guarantee or a medical commitment on the record.

So the question is not whether childcare providers will use AI. They will. It is whether yours sends the safety and medical questions to your director, every time, no matter how they are asked.

Frequently asked questions