Embedding Famly on a Nursery Site Without Slowing It Down

#What Famly gives you

Famly is nursery management software: children, rooms, registers, learning journals, invoicing with funded hours, messaging, a parent app. The piece that touches the website is the enquiry side. A prospective family fills in a form, they appear in Famly as an enquiry with their child's details and the sessions they want, and the manager works the pipeline (viewing booked, place offered, enrolled) from inside Famly. The form can be hosted by Famly or placed on your own site.

The performance question is where that form goes. The answer: on the pages where a parent is ready to fill it in, and never on every page.

#The rule

Nothing from Famly loads until the parent reaches Join the waitlist or Book a viewing. Our rooms, A day with us, Fees and funding and Our team are for reading; they are the pages parents share and the pages that need to be fast on a phone with poor signal in a pushchair-friendly cafe. They link to the two action pages; they do not carry the embed.

#Page 1: Join the waitlist

Famly's enquiry form on a single page. Above it, three sentences on how the waitlist works: how places are offered, whether there is a registration fee, how long a parent has to accept. Below it, the phone number. Nothing else.

Keep it fast: reserve the form's height in CSS so the page does not jump when the embed loads; preconnect to Famly's domain in the head; no gallery, no reviews widget, no map on this page.

<link rel="preconnect" href="https://app.famly.co">
<div class="famly-enquiry" style="min-height: 720px">
  <!-- Famly enquiry form embed here -->
</div>

If the embed's styling fights your site, or it is heavy on phones, a form built on the site with the same fields (parent, contact, child's name and date of birth, sessions wanted, start date, sibling, how they heard) can post into Famly through its enquiry integration or an automation tool. The family lands in Famly either way. The Famly-hosted form is the simpler route; the site-built form is the faster and more consistent one.

#Page 2: Book a viewing

Famly takes the enquiry; the viewing slot is usually a booking tool's job. Acuity or Bookeo on this page, with two or three viewing times a week you can honour, a confirmation and a reminder. One line of reassurance and the phone number. The booking tool's embed obeys the same rule: this page only, height reserved, preconnected.

#Buttons from every page

Every room section on Our rooms ends in Book a viewing and Join the waitlist. Fees and funding ends in both. The home page carries both in the first screen and at the foot. Where Famly's form accepts parameters, pre-select the sessions from the fees page the parent was reading; where it does not, pass the page name through a hidden field on a site-built form so you know which room brought them.

#Configure Famly first

• The enquiry form's fields set to what you need to place a child, and no more.
• Sessions in Famly matching the sessions on your fees page, so a parent's tick maps to a real session type.
• Notifications to the manager for new enquiries.
• Templated replies in your voice for the confirmation and the viewing offer.
• The pipeline stages you actually use, so the list stays honest.

Submit a test enquiry from a phone before wiring the site.

#Testing on phones

Safari and Chrome on iOS and Android, and inside Instagram's and Facebook's in-app browsers, because a lot of nursery traffic arrives from local parent groups. Complete an enquiry and a viewing booking in each. If the embed misbehaves in an in-app browser, link those entry points to Famly's hosted form instead. Check the enquiry appears in Famly with the sessions ticked and the manager's notification arrives.

#Tracking

• enquiry_submit for the waitlist form, viewing_booked for the viewing, each with the page that sent the parent as a parameter.
• A thank-you page after each so completions register in analytics.
• Famly's own enquiry list for the pipeline.
• Monthly: enquiries and viewings by page, so you know whether the baby room or the fees page is producing them.

#Monthly check

From the home page, a room page and the fees page, on a phone: tap Join the waitlist and submit one; tap Book a viewing and book one; confirm both arrive. Famly and the booking tool update their embeds; find out before a parent does. This is on the care plan for every Famly site we look after.

#Blossom and the others

The same setup applies to Blossom, Kinderly with a form tool, or Nursery In A Box, and to ClassForKids or Sawyer for clubs and classes: the form on one page, the calendar on another, nothing on the reading pages.

#Common mistakes

• The enquiry form in the footer of every page, slowing the site for the majority who are reading.
• Sessions on the form that do not match the fees page.
• Famly's hosted form as the Instagram link with no way back to the rooms and fees.
• No viewing calendar, so the manager still phones to agree a time.
• Nobody watching the enquiry notifications during the day.

#Where this sits

Famly is the system we wire into nursery websites most often, and this setup, two action pages, buttons from every reading page, and tracking on both, is the version that keeps the childcare website fast and the enquiries landing in Famly. Famly runs the pipeline; the site gets the parent into it in one tap.