Demonstration site
This is where the
booking portal starts
On a live build, the buttons on the previous page hand over to the practice’s own booking software — Dentally, Software of Excellence or similar — on a subdomain such as book.ashcroftclinic.co.uk. That system owns the diary, the clinician rotas and the patient login, so it is not something the website recreates.
What the handover involves
Three things get wired up at this point on a real project, none of which are visible to the patient:
A deep link per clinic. Each location button carries the practice identifier, so somebody who chose Wetherby lands on the Wetherby diary rather than a location picker they have already answered.
Treatment context. Where the visitor arrived from a treatment page, the appointment type is pre-selected — an implant assessment is a sixty-minute slot with one named clinician, and letting somebody book it into a twenty-minute check-up is how a diary falls apart.
Consent and analytics boundaries. The portal is a third party, so it is the point at which a cookie notice becomes necessary and at which patient data leaves this site’s control. Everything before it here is static and sets no cookies at all, which is why this demonstration has no cookie banner.
Back to the site
The Ashcroft Clinic is a fictional practice built by Omnify Labs to demonstrate design and build quality. Nothing here books a real appointment.