The target
A mother with a nine-week-old, awake at half past two in the morning, finds your Tuesday sensory class. She checks the age band, sees the venue and the parking note, taps Book a trial, pays for one session, and gets a confirmation telling her what to bring. Four days later she comes, enjoys it, and enrols for the rest of the term from a link in the follow-up message.
1. Decide what a trial actually is
Before any software is configured, settle the commercial question. A trial is one of three things, and picking one makes everything else simple.
A paid single session at roughly the per-class term rate, which is the most common and the least abused. A free taster, which fills the hall and fills it with people who do not come back. Or a pro-rata join, where there is no separate trial at all and a parent simply starts mid-term paying for the sessions that remain.
Paid trial plus pro-rata joining covers most baby class businesses. Write it down in one sentence, because that sentence goes on the class page, in the booking flow and in the confirmation.
2. Model the term, not the appointment
This is where generic appointment tools fall over. A baby class is not a slot, it is a course: eight or ten weeks, the same babies each week, in a room with a hard capacity.
ClassForKids, Bookeo, TeamUp and Sawyer all handle courses or terms rather than one-off appointments, which is why they are the shortlist. In whichever you run, set up the term as a block with its start and end dates, the weekly time, the venue, the capacity and the age band. Then attach a trial session type to it that consumes one space in a named week.
3. Set capacity honestly, per venue
Capacity is a safety number as well as a commercial one. A church hall with buggies parked along one wall does not hold the same number as a leisure centre studio.
Set the cap per venue rather than one number across the business, and decide whether a trial takes a space from the cap or sits on top of it. Taking a space is the honest option. Selling ten term places and then letting four trials in produces a room where nobody can lie a baby down.
5. Keep the trial form to one screen
Required at booking: parent name, mobile, email, baby's name and date of birth, and the consent tick for your terms and photography policy. Date of birth rather than age in months, so the platform can check the age band itself and so the record stays true as the baby grows.
Requested after booking, through the confirmation: any allergies or medical notes, how they heard about you, and whether they want the term newsletter. Every extra required field on that first screen costs you completed bookings from a parent holding a baby in one arm.
6. Deep link the buttons
On the website, every class page gets its own Book a trial button pointing at that specific class in the platform, not at a general timetable. A parent who has just read about the four to seven month band should not land on a list of everything you run and have to find it again.
Hosted booking pages are usually more reliable on phones than embedded widgets. If you embed, put it on one booking page rather than in the footer of the whole site, and check the calendar is reachable on a small handset without an internal scroll trap.
7. Make the enrolment prompt automatic
The trial-to-term conversion is the single number that decides whether the business grows, and it is won in the forty-eight hours after the trial.
Set an automated message that goes out the day after a trial with one link that enrols the parent into the remaining sessions of the current term, and a second line about the next term if the current one is nearly done. Say what happens if they enrol mid-term, whether the trial fee comes off, and when the next term starts. One link, one decision.
8. Handle the missed week
Babies get ill and parents miss classes, and how you handle it is a question you will be asked constantly. Decide the policy, put it on the class pages and the prices page, and configure it in the platform: a set number of catch-up sessions per term, booked by the parent into a class with space, or no catch-ups but a stated approach to long illness.
9. Test it on a phone, including in-app browsers
Book a test baby end to end on mobile data. Then repeat it inside the Instagram in-app browser, because a large share of baby class traffic arrives from a link in bio and that browser is where payment sheets and widgets fail quietly.
Check that the class was pre-selected, the payment completed, the confirmation arrived with the venue and the what-to-bring list, and the register updated. Then cancel the test and confirm the space came back.
10. Measure the two numbers that matter
Add events for trial booking clicks and enquiry submissions, recorded by page. Then once a month compare trials booked against term enrolments. If trials are strong and enrolments are weak, the class itself or the follow-up message is the problem. If trials are weak, it is the class page and the age bands.
Where this sits
Trial booking, term enrolment and waitlists wired around ClassForKids, Bookeo, TeamUp or Sawyer are the core of every baby class website we build, and the same booking pattern runs through the wider childcare and family websites we make. The packages are on pricing. The platform holds the register. The site's job is to get a tired parent into it in one tap.