Childcare Centre Sub-Account Kit

1. No. 01

   1 AI Receptionist

   Component 01 · AI Receptionist

   The problem

   Between eight and six every adult in a nursery is legally required to be with children, so enquiry calls hit voicemail while a parent rings the next three settings. Configuring a receptionist that must never discuss a child is careful work per account.

   Once it is loaded

   The receptionist handles enrolment enquiries only: age group, days needed, requested start date, funding questions and a tour booking. Anything about a child already attending, or any safeguarding matter, is escalated to a named human immediately.

   How it pays back

   If scripting those boundaries from scratch costs an operator six hours per setting and a group asks you to stand up eight nurseries, that is more than a working week of build, and the setting stops losing the afternoon enquiries that decide a September place.

2. No. 02

   1 AI Chatbot

   Component 03 · AI Chatbot

   The problem

   The research happens after bedtime, on a phone, comparing four settings at once. An assistant that answers fees and funded hours but refuses to discuss an individual child has to be constrained deliberately, and that constraint gets rebuilt at every setting.

   Once it is loaded

   The assistant covers fees, funded hours, session patterns, waiting times in general terms and tour availability across the website, SMS, email and social, and is scoped so it never handles daily care updates, incidents or anything about a named child.

   How it pays back

   Assume a nursery answers seventy evening enquiries a term and converts one in ten into a tour, with two of those tours enrolling at a fee that runs for two years; the account earns its keep on a single September intake.

3. No. 03

   Pipelines

   Not one of the nine — what they run on

   The problem

   The place that opens in March was promised to a family who registered last June, and if the waitlist lives inside a general enquiry board it is lost the moment somebody tidies that board. Operators learn this once, painfully, then rebuild under pressure.

   Once it is loaded

   Enquiry to tour booked to tour attended to place offered sits on the enrolment board; the waitlist stands separately with requested start date and age group visible; leavers serving notice are tracked apart, so a place is filled before it stands empty.

   How it pays back

   If separating a waitlist out of a general pipeline after the fact takes an operator five hours per setting, and you learned that on your first nursery account, every subsequent setting loads correctly on day one at no build cost.

4. No. 04

   Workflows

   Not one of the nine — what they run on

   The problem

   Term dates, the September intake, funded-hours declaration deadlines and a notice period all drive different messages, and none of them may touch the daily communication a key worker sends a parent. Keeping those two streams apart is what operators get wrong.

   Once it is loaded

   Tour follow-up, waitlist check-ins on a light cadence, offer expiry chasing, funded-hours declaration reminders and a leaver notice sequence run inside the enrolment stream only, with no path by which a marketing message reaches a parent as a care update.

   How it pays back

   If building that separation properly is ten hours per setting and a group hands you eight nurseries, the kit saves ten working days, and it also saves the conversation you would have had after a sales email landed on a safeguarding thread.

5. No. 05

   Appointment reminders, confirmations and no-show recovery

   Component 05 · Smart Appointment System

   The problem

   Families tour three settings in a week and enrol at one of them, so a tour that does not happen is usually the enrolment gone entirely. Building the reminder ladder and the same-hour recovery per nursery is unglamorous work every operator repeats.

   Once it is loaded

   A booked tour confirms with parking, entry arrangements and what to bring, then reminds at twenty-four hours, one hour and fifteen minutes; a family that does not arrive gets a call within the hour, working to the seventy per cent no-show recovery target.

   How it pays back

   If a setting books twenty tours a term and five do not arrive, recovering most of them at a place worth a thousand a month for two years makes the reminder ladder alone the reason the client renews with you.

6. No. 06

   Funnels

   Not one of the nine — what they run on

   The problem

   A nursery sells a tour, not a purchase, and the pages have to carry inspection-grade credibility, fee transparency and a funded-hours explanation without ever promising a place. Writing that carefully per setting is slow, and rushed versions read badly to parents.

   Once it is loaded

   A tour booking path, a waitlist registration path, a funded-hours eligibility explainer and a sibling-place enquiry are built, each capturing age group and requested start date, and none of them implying availability the setting cannot honour.

   How it pays back

   If a tour booking page written to that standard is four hours of an operator day and you load five settings a year, the kit returns twenty hours, and the nursery has a registration path live before the January enquiry season rather than after it.

7. No. 07

   AI Studio website

   Component 04 · Professional Website

   The problem

   The manager who holds the copy is on the floor covering ratios, so a nursery site sits at eighty per cent finished for three weeks while an operator waits on room descriptions, a fees table and confirmation of which policies may go public.

   Once it is loaded

   Room and age-group pages, a fees and funded-hours page, admissions and settling-in copy, staff qualification structure, a tour booking calendar and a registration form arrive written and organised for local search, with no field that invites child information.

   How it pays back

   If a childcare site built from nothing is fourteen hours of writing and chasing and you deliver four a year, that is seven working days recovered, and the setting launches in days, which matters because a September intake does not wait for a website.

8. No. 08

   Nurture campaign

   Component 02 · AI Outbound Caller + Component 08 · Database Reactivation

   The problem

   A family on a waitlist for eight months with no contact has enrolled somewhere else, and the place opens to silence. Building nurture that stays useful rather than pushy, and never strays into anything about a child, is genuinely delicate work.

   Once it is loaded

   Waitlist families receive a light, informative cadence on settling-in, term dates and centre news; stalled tour enquiries get a follow-up sequence; a dormant enquiry list from a previous intake is reapproached by age group and requested start month.

   How it pays back

   If a nursery has forty families on an unattended waitlist and half have already gone elsewhere, keeping even a handful engaged into the next intake, at a fee running two years, is a return the client can name in a renewal conversation.

9. No. 09

   Review automation

   Component 06 · Review Harvesting + Component 07 · Review Automation

   The problem

   Parents choose a setting on what other parents wrote, and the only safe moment to ask is after settling-in has gone well or when a child moves up a room, never anywhere near an incident. Wiring a trigger that respects that is careful per-account work.

   Once it is loaded

   The ask is timed to a settled first month or a room transition, passes a satisfaction gate, is worded so no child detail is invited into a public review, follows a multi-touch cadence and rotates platforms, aiming at five to ten reviews a month.

   How it pays back

   If a setting fills places on local reputation, a steady five to ten reviews a month reduces what it spends on paid enquiry, and a nursery that stops buying clicks while still filling places is a nursery that keeps paying you.

10. No. 10

    Seasonal automation

    Component 09 · Lifetime Nurture Campaigns

    The problem

    The intake that matters is September, and it is won in April. Term dates, funded-hours declaration deadlines and the January enquiry surge all sit on a school calendar that an operator rebuilds by hand at every setting, usually too late to matter.

    Once it is loaded

    The September intake campaign, the January enquiry push, holiday-club promotion, funded-hours declaration deadline reminders, sibling-discount prompts and a family referral message are all scheduled in the account against a set of term dates the setting supplies once.

    How it pays back

    If an operator spends eight hours a year building seasonal campaigns per nursery and a group runs eight of them, that is eight working days, and the settings have a September campaign live in April, when parents actually start looking.

11. No. 11

    Custom values

    Not one of the nine — what they run on

    The problem

    A setting that changes its fees in April changes them everywhere, and an operator who typed session times, hourly rates and the sibling discount into templates spends the fee review inside message editors rather than on the next rollout.

    Once it is loaded

    Room age ranges, session patterns, fee rates, funded-hours wording, sibling discount, notice period, term dates and the registration fee sit at account level, so a fee review is one screen and every tour confirmation quotes the current number.

    How it pays back

    If a fee review chased through templates is two hours per setting and a group of eight reviews fees annually, that is sixteen hours a year, and it removes the year-old fee arriving in a parent inbox as a written quotation.

12. No. 12

    Custom fields

    Not one of the nine — what they run on

    The problem

    What a nursery actually needs on a record is the parent contact, an age group, days and sessions required, a requested start date, funding status and waitlist position. What it must never hold is anything approaching a child or safeguarding record.

    Once it is loaded

    The record carries parent details, age group rather than identity, sessions wanted, requested start month, funded-hours status, sibling links and waitlist position, and there is deliberately no field structure inviting care notes or incident detail.

    How it pays back

    If getting that boundary right takes an operator a day of thinking per setting, the kit does the thinking once for every childcare account you run, and the value is not only the hours but not being the agency that put a child note in a CRM.

13. No. 13

    Forms and surveys

    Not one of the nine — what they run on

    The problem

    Consent is the whole difficulty. A form built quickly at the end of a rollout is exactly where a setting ends up collecting something it should not, and a group then has to review every form you shipped, nursery by nursery, before anyone can use them.

    Once it is loaded

    Enquiry and tour registration forms, a waitlist form capturing start month and sessions, a communication preference form carrying consent wording and a post-settling parent survey arrive built, each worded so a parent knows what is stored and what is not.

    How it pays back

    If drafting consent-safe forms is three hours per setting and you deliver five childcare accounts a year, that is fifteen hours, and a group can approve one form set once instead of reviewing yours setting by setting.

On purchase you receive two things: one snapshot link, and one PDF with full installation instructions. Installation is not in the kit price — load it yourself from the PDF, or add installation by us for $200 a sub-account. Every payback figure above is an illustrative scenario with its assumptions in the sentence, not a measured customer result.