Scheduling that runs itself

Most scheduling problems are not really scheduling problems. They are handover problems. The booking exists in one place, the intake form in another, the reminder in a third, and the person who needs to know somebody cancelled finds out when they are already standing in an empty room.

A booking system worth building closes those gaps. It is less about a calendar widget and more about everything that has to happen around an appointment for it to actually be worth having.

Who this is for

• Clinics and practices with appointment types that differ in length, room, equipment or the qualification of who delivers them.
• Service businesses where a booking commits a person and a van, and where a double booking costs a whole morning.
• Anyone whose booking currently lives in WhatsApp, a shared spreadsheet, or a paper diary that only one person can read.

What it actually does

Intake before the slot. The questions you need answered before someone arrives, asked at the point of booking rather than in the waiting room. For clinical work this is often the difference between a useful first appointment and a wasted one.

Availability that reflects reality. Not just who is free, but which room, which equipment, how long this particular treatment takes for this particular practitioner, and how much buffer is needed after it.

Reminders that reduce no-shows. Email, SMS or WhatsApp, at intervals you choose, with a one-tap way to confirm, move or cancel. The easier you make cancelling, the more slots you get back in time to refill them.

Rescheduling without a phone call. Most no-shows are not people who did not care. They are people for whom cancelling was harder than not turning up.

A waiting list that fills the gap. When a slot frees up, the system can offer it to the next person automatically instead of leaving it empty.

What a build looks like

• A booking flow on your own domain, in your own branding, that works properly on a phone.
• Availability rules, resources and appointment types, configured with you rather than assumed.
• Two-way sync with the calendar your staff already live in.
• Intake forms, with conditional questions where they help and none where they do not.
• Reminders and rescheduling, on the channels your customers actually read.
• A staff view: today, this week, who is where, what changed.

Where it makes sense, this pairs directly with an AI receptionist, so the people who would rather phone get the same availability as the people who book online, without anyone double-booking a slot.

Where the data goes

An appointment record says who someone is, where they will be, when, and often why. In a clinical setting that last part is health data and carries a much higher bar. We design accordingly: European hosting, least-privilege access, a full audit trail, and retention periods you set rather than inherit from a supplier's default.

What shapes the cost

There is no standard price, because there is no standard practice. What moves it:

• How complicated your availability really is. One person, one room, one appointment length is a small build. Six practitioners with different qualifications sharing three rooms and two machines is a genuinely hard scheduling problem.
• What it has to talk to, and whether that system wants to be talked to.
• Which reminder channels you want, since SMS and WhatsApp carry their own per-message costs and their own setup.
• Whether patient data is in scope, which adds design, documentation and review.
• Whether you need a waiting list and automatic refilling, which is the single most valuable feature here and also the fiddliest to get right.

Tell us how booking works today, including the parts that annoy you most, and we will come back with a written scope, a fixed price and a date. No charge either way.

Frequently asked questions

Why not just use an off-the-shelf booking tool? Often you should, and we will say so. If your needs fit Calendly, Zorg-specific software or whatever your practice system already includes, buying beats building every time. Custom becomes worth it when the rules are genuinely yours: resource-dependent slots, multi-step treatments, staff with different qualifications, or an intake that has to happen before a slot can be confirmed.

Can it work with the system we already have? Usually. Google Calendar and Outlook are straightforward, and many practice systems expose an API. Where one does not, we look at import and export routes before recommending you change anything. Replacing a working system is expensive and disruptive, and it is rarely the cheapest way to fix a scheduling problem.

How much does it reduce no-shows? We will not quote you a number, because it depends entirely on your patients or customers and what you send them. What we can say is that the mechanics that help are well understood: a reminder at the right interval, one-tap rescheduling instead of a phone call, and making the cancellation path easy so the slot comes back into circulation rather than simply going unused.

Where does AI come into it? Sometimes not at all, and that is a perfectly good outcome. Where it earns its place: reading a free-text intake and suggesting the right appointment type, spotting patterns in cancellations, drafting the reminder copy, or handling rescheduling by voice or chat. The scheduling logic itself should be deterministic. You do not want a language model deciding whether two appointments overlap.

Is patient data safe in it? It has to be. Appointment data in a healthcare setting is health data and we treat it that way: European hosting, access limited by role, a complete record of who saw what, and retention you control. We can walk your DPO or supplier through the design.