What Acuity gives a babysitting site
Acuity Scheduling, sold alongside Squarespace, is an appointment booking product rather than childcare software. From a website's point of view it offers three things worth wiring up.
A hosted scheduling page and an embeddable widget. The parent picks a service, picks a time, fills in a form and receives a confirmation.
Calendars per person. Each sitter can be a calendar with their own availability, which is how you let parents book a named person and see only the dates that person can work.
Intake forms per appointment type. The questions you ask a parent at booking, attached to the appointment rather than sitting loose in an inbox.
Feature detail changes between releases and plans, so confirm the specifics of any option here with Acuity before you design a page around it.
The rule: nothing loads until the parent taps Book
A babysitting site is mostly read rather than booked. The rates page, the vetting page and the sitter profiles do the persuading; the booking page just takes the answer. Putting a third-party scheduling script in the footer of every page slows all the pages that convert, for the benefit of the one that closes.
So: one booking page carries the embed, and every other page links to it.
The booking page
Give it a single job. The embed, one reassuring line, the phone number and the response time you promise. Reserve the height before the widget loads so the page does not jump, and preconnect to the scheduling domain in the head.
<link rel="preconnect" href="https://app.acuityscheduling.com">
<div class="booking-embed" style="min-height: 800px"><!-- Acuity embed --></div>Above the embed, three lines that stop the emails you get most: what the parent will be asked for, what the minimum booking is, and when they will hear back. Below it, the cancellation window. Do not restate the rates table here; link to it.
Modelling babysitting inside an appointment tool
This is where most builds go wrong, because Acuity thinks in fixed-length appointments and babysitting is a variable window.
The approach that holds up is fixed durations as separate appointment types: a four hour evening, a five hour evening, a six hour evening, an eight hour night. Each carries its own duration and price, which keeps the calendar honest about how long a sitter is committed for.
Late-night and short-notice work then sit either as their own appointment types or as add-ons on top, depending on what your plan supports. Extra children can be an add-on too. Where a rule cannot be expressed natively, do not fake it in prose on the page and correct it manually every week. Either change the rule or change the tool.
Configure Acuity before the site points at it
- Appointment types and prices matching the rates page on the site exactly. A confirmation that contradicts the page costs more goodwill than any missing feature.
- A calendar per sitter, with real availability, so a profile never offers a date that person cannot work.
- Minimum scheduling notice set to your standard window, so the flow only offers dates you can staff. Everything inside it goes to the last-minute route instead.
- Intake forms kept short: name, mobile, address, date, hours, number and ages of children. Routines, allergies, access and emergency contacts are collected afterwards through the confirmation, not squeezed onto a phone screen.
- Cancellation window and terms in the same words that appear on the page.
- Deposits or payment at booking if you take them, through whichever payment provider you already use.
- Confirmation and reminder templates in your voice, carrying the sitter's first name once matched, the address, the total and the terms.
- Notifications to a phone somebody actually watches in the evening, which is when babysitting bookings happen.
Keep marketing consent out of the booking form as a separate, optional tick with an unsubscribe route in every promotional send.
Deep link from the pages that persuade
Each sitter profile gets a Book with this sitter button pointing at that person's calendar. The last-minute page points at the short-notice route rather than the standard one. The rates page carries a Book button under the table.
If an option cannot be deep-linked on your plan, send the button to the booking page anyway and name the option in the line above the widget so the parent knows what to pick.
Be careful what the form collects
A babysitting intake form holds children's names, ages, medical needs and a home address. That is sensitive information about a child, held in a third-party system.
Ask only for what you need at booking, collect the detailed material through a route you have thought about rather than an open text box, keep your privacy notice accurate about where the record lives, and restrict who on your team can see it. Never publish any of it. If you are unsure how a regime in your country treats this data, take local advice rather than guessing; treat this as orientation only.
Test it the way parents use it
Book a test job end to end on a phone, on mobile data, then again inside the Instagram in-app browser where a lot of family traffic arrives. Check that the duration and price were right, the minimum applied, the form submitted, and the confirmation arrived by email and text. Then cancel and confirm the slot released.
Repeat monthly. Platforms change their booking pages, and you would rather find a broken step yourself.
Track it
Add a booking click event on every Book tap with the page recorded, and a call click on every tap-to-call. Once a month, compare taps by page against completed bookings. That tells you whether the rates page, the vetting page or a sitter profile is what actually fills the diary.
Where this sits
Acuity is one of the tools we wire into a babysitting service website, alongside Bookeo and custom booking forms, and the pattern is the same across our childcare and family websites: one booking page, deep links from the pages that persuade, the phone ahead of both. Packages are on pricing. Acuity holds the diary. The site's job is to answer the rate and the vetting question first.