What Famly gives the website, and what it does not
Famly is nursery management software. Most of what it does, registers, ratios, observations, billing, parent messaging, happens after a family enrols and never touches your public pages.
From the website's point of view there are two owner-facing pieces worth wiring up. An enquiry or waitlist form you can embed or link to, which drops a family into Famly's enquiry pipeline with their details attached. And a parent login, which is a link in your footer and nothing more.
That is the whole surface area. Anything else you have been told the site can do with Famly is worth confirming with Famly directly, because the embed options change between releases and a page built on an assumption breaks quietly.
The rule: nothing third-party loads until the parent taps Enquire
A nursery site is mostly read, not submitted. The rooms, the garden photographs, the inspection page, the fees table, the day in the life, the menus. Those are the pages doing the persuading, and they are usually being read on a phone on a bus.
Putting a third-party form script in the footer of every page slows all of that for the benefit of the one page where a family actually types. So: one page carries the embed, and every other page links to it with a button.
The enquiry page
Give it a real URL, keep it clean, and reserve the height before the form arrives so the page does not jump while it loads. Preconnect in the head so the handshake is done before the parent scrolls.
<link rel="preconnect" href="https://app.famly.co">
<div class="enquiry-embed" style="min-height: 720px"><!-- Famly enquiry form --></div>Above the form, three lines that stop the questions the office gets most: what happens after they submit, how soon somebody replies and who by name, and whether there is a registration fee. Below it, the phone number and the opening hours of the office rather than the nursery, because those differ and parents ring at four when the manager is in a room.
Do not repeat the fee table here. Link back to it.
If the embed misbehaves, or if it costs more than it earns on a slow connection, link to Famly's hosted form instead of embedding it. A fast page with an outbound link beats a slow page with an inline widget.
Keep tours off the same page
Famly runs your enquiry pipeline. Tour slots are a calendar problem and often sit better in a scheduling tool such as Acuity, pointed at the manager's real availability. Where Famly's own tour booking suits you, use it and keep everything in one system.
Either way, the site shows two buttons, Book a viewing and Join the waitlist, and the parent never sees which system is behind which.
Configure Famly before the site points at it
- Fields that match the site. Room names, session types and age bands worded exactly as they appear on your fees page. A confirmation email that uses different room names than the site is the first thing a family notices.
- Funded hours as a field, so the manager can plan the room from the enquiry rather than a follow-up call.
- Preferred start month rather than a start date. Most families are guessing, and a date field makes them guess badly.
- Source field with real options: passing by, Google, a friend, the school, Instagram. It is the only place you will ever learn what actually works.
- Notifications to a device somebody watches, and a named owner for the pipeline. An enquiry list nobody owns is a list of families who went elsewhere.
- Auto-reply in your voice, naming the person who will follow up and linking the rooms page and the fees page.
- Duplicate handling, because the same family will enquire twice across a term and being treated as new the second time reads badly.
Then submit a test enquiry from your own phone and follow it all the way to the reply.
Test it where the traffic comes from
A lot of nursery enquiries arrive from a link in an Instagram bio or a local parents group on Facebook, and neither in-app browser behaves like Safari. Test the whole flow in both, plus Safari and Chrome on iOS and Android.
Repeat monthly, and after any Famly release note that mentions forms. You would rather find a broken submit than hear about it from a parent who gave up and rang the nursery on the next street.
Blossom, Kinderly and the rest
The pattern is identical. One page carries the form, everything else links to it, the fields match the site, the reply is owned by a person. Whichever platform runs your enquiries, the website's job is to answer the parent's questions well enough that they want to fill it in.
Where this sits
Famly is the platform we wire in most often on a day nursery website, and the approach is the same one we use across our childcare and family websites: one enquiry page, fast pages everywhere else, fields that match the site, a human on the other end. Package details are on pricing.