The five, and the floor they share
Semble, Meddbase, Cliniko, Jane and Zanda are the systems behind the fertility and women's health clinics we build for. Four of them — Semble, Meddbase, Cliniko and Jane — will hold an initial consultation as its own appointment type and send an intake form out ahead of the visit, which is the structural requirement in this field. Zanda is the fifth in regular use.
That shared floor is why a feature grid would mislead you. None of them fail at taking a consultation booking. What separates them is how the flow reads to somebody who has been putting this appointment off for months, and how the widget behaves inside your pages.
Why there is no winner named here
A clinic with one clinician and a menopause list two afternoons a week is not choosing between the same things as a group with four consultants, a lab and a second location. Ranking five systems would tell you about our preferences, not about your diary.
So below are the questions that actually separate them for a fertility clinic. Ask them on a trial, with your own appointment types loaded.
Can the first consultation be its own thing?
Check that an initial consultation can carry its own name, its own length and its own fee, separate from a follow-up or a results review. A diary where every slot is the same size will eventually drop a first appointment into a fifteen-minute gap — the one appointment you least want rushed.
Who writes the intake form?
The form that goes out before a first visit is the most sensitive text anywhere near your website, and by default it is the vendor's template. Find out whether you can rewrite every field label and every question, whether questions can be optional, and whether it truly sends in advance rather than appearing at reception. If the wording is locked, you have handed the tone of your clinic's first contact to a software company.
Does a phone route survive beside it?
Some patients will not use a calendar widget, and that is not a failure on their part. Test whether the booking page can keep a phone number and a call-back option visible on the same screen without the embed swallowing them on a narrow display. A system that insists on being the only route in is the wrong one here.
Can somebody book a named consultant?
Where more than one consultant takes new patients, people pick a person before they pick a time. Ask whether availability can be filtered to a single clinician, whether each clinician holds their own appointment types and durations, and whether a direct link opens only that person's diary. That link is what makes a consultant profile page work.
Does it understand a sequence, not a visit?
Treatment here is rarely one appointment. Ask how the system handles a run of them: whether the next one can be booked while the patient is still in the room, whether moving one leaves the rest intact, and whether a reschedule sends a fresh confirmation or changes silently.
What does the embed do on mobile data?
Nobody asks this on a trial and everybody lives with it afterwards. Open the embed on a real handset, off the office Wi-Fi. Watch whether the page jumps as the widget arrives, whether fields are reachable with one thumb, and whether it sizes itself or demands sideways scrolling.
What does an export contain?
Ask before you need to: appointments, records, documents, history. A clinic that cannot leave its booking system starts designing its website around that system's limits.
The website half of the decision
Whichever you choose, the widget should load on the page where people book and nowhere else. A script running site-wide slows the treatment, fee and results pages, and those pages are what earn the booking in the first place. A dedicated booking page, or a widget that loads on tap, keeps both halves fast.
Where this sits
Every fertility clinic website we build embeds the system you already pay for, at a price agreed up front. For what the build itself costs, read what a fertility clinic website costs, or audit what you have with the six phone tests.