The day you finish setting up online booking is the last day your booking system is completely accurate. Nothing dramatic happens after that. Bookings keep arriving, the calendar keeps filling, so it never occurs to anyone to check. Meanwhile the durations stop matching reality, a service you no longer offer is still bookable, a calendar connection quietly stops syncing, and the confirmation message describes a parking arrangement that ended last spring.
Here is the takeaway up front: booking systems drift rather than break, and drift is silent because the bookings keep coming — they are just the wrong bookings. Four things age on their own: your real availability, your service menu, your connections to other systems, and the messages you send. Most of what people call booking maintenance addresses none of them.
If your setup is still being built, start with how to set up online booking — this assumes something is already running.
Why booking setups drift instead of failing
A failure is loud. If the booking page returns an error you hear about it within a day, because someone phones instead. Drift produces no complaints, because every symptom looks like something else.
You run late all afternoon and blame a chatty client. Someone books a service you retired and you quietly do it anyway. Two people arrive for the same slot and it gets written off as a fluke. Bookings dip and you assume it is a slow month.
The other reason is that the setup was configured for the business you had at the time. Prices change, staff change, hours change, you add a service and drop another. The calendar does not know any of that. It keeps enforcing rules written for a business that no longer exists.
Drift 1: durations and buffers stop matching reality
The most common one, and the most expensive, because it costs you the whole day rather than one appointment.
When you set up, you estimated how long each service takes. Over time the real number moves — you added a step, clients bring more questions, the room takes longer to reset. The calendar still books the old number, so every appointment starts a few minutes late and the error compounds until the last client of the day gets a rushed version of what they paid for. Buffers drift the same way: the gap you left for cleaning, notes, or travel was right for the volume you had then.
The check: for one ordinary week, note when each appointment actually started and ended. Compare that to what the system reserves, and adjust the two or three services with the biggest gap. Do this after any change to how a service is delivered — and remember that a service which now needs a different room or a different person is a scheduling change too, with the mechanics covered in how to prevent double-bookings.
Drift 2: the service menu grows and never shrinks
Adding a service takes a minute. Removing one requires a decision, so nobody makes it.
A year in, the page offers the seasonal thing you only do in summer, two near-identical options whose difference only you understand, an introductory offer that ended, and a service you would rather not do at all but which is still one tap away. Each one is a decision you are asking a customer to make, and decisions are the main thing that stops a booking being completed — why customers abandon a booking page covers the rest of that.
The check: once a season, read your own service list as a stranger would. For each item ask: do I still offer this, would I be glad to receive this booking tomorrow, and can someone outside my trade tell it apart from the one below it? Hide anything that fails. Hiding is not deleting — most systems keep it ready for when you want it back.
Drift 3: connections lapse quietly
This is the one that produces double-bookings and vanished enquiries, and it stays invisible until someone is standing in your doorway at the wrong time.
- Calendar sync. Authorisation to read and write your calendar expires, gets revoked by a password change, or breaks when an account is renamed. The system then offers slots that are not free.
- Notifications. Booking alerts route to an inbox nobody opens, or start landing in spam after an email change.
- Payments. A card on file expires or an account needs re-verification, and deposits silently stop being taken.
- Staff accounts. Someone leaves and their calendar stays connected, still blocking or offering time. Someone joins and is never added, so their hours are invisible.
- Links out in the world. The "Book now" button on an old profile, a directory listing, a printed card, an email signature — all pointing at a URL you changed when you reorganised the page.
The check: once a quarter, make a real test booking end to end. Not a preview — a booking, from a device that is not yours, signed out of every account, taken through to the confirmation message and then cancelled. Then click your own booking links wherever they live: profiles, listings, signature, the last newsletter you sent.
Drift 4: the messages age
Your confirmation and reminder messages were written once and have not been read since. They are also the only writing your customer is guaranteed to see.
What goes stale: the address after you moved, entry or parking instructions, the cancellation window after you changed the policy, the name of someone who left, a number you no longer answer, a link to a form you replaced. Reminder timing ages too — a schedule that suited a quiet diary is not always right once the same clients rebook regularly.
The check: twice a year, read every automated message in the order a customer receives it — confirmation, reminder, reschedule, cancellation, follow-up — on a phone, where they are actually read. Fix anything untrue, delete anything redundant. The reasoning behind reminder timing is in the friction-math approach to no-shows.
What maintenance is theatre
Not everything that feels like looking after the system is looking after the system:
- Watching the dashboard daily. Booking numbers move for reasons outside the system. Daily checking produces anxiety, not information.
- Adding a third or fourth reminder. Past a point, extra messages are ignored or resented — and they mask a wrong duration or a broken sync.
- Redesigning the booking page. Colour and layout are the last thing limiting completion, and no redesign fixes availability that is wrong.
- Tightening the cancellation policy in isolation. A stricter policy nobody reads changes nothing except how you feel when someone misses.
- Turning on every feature the software offers. Each one is another thing to keep true.
The pattern: theatre changes how the system looks, or how you feel. Real maintenance changes whether the system is telling the truth.
A routine short enough to actually keep
| How often | Time | What you check |
|---|---|---|
| Weekly | 5 minutes | The next two weeks look right; nothing bookable while you are away; no unexplained gaps or overlaps |
| Monthly | 15 minutes | Did anything run consistently late? Are notifications still arriving? Any payments that did not go through? |
| Quarterly | 30 minutes | Full test booking from an outside device; every booking link clicked; staff and calendar connections reviewed |
| Twice a year | 30 minutes | Read every automated message; audit durations and buffers against real times |
| Yearly | 45 minutes | Prune the service menu; set the coming year's closures; confirm who has access and who should not |
Put the quarterly one in the calendar as an appointment. It catches the most, because a real test booking exercises availability, services, connections, and messages in a single pass.
Check after every change, not only on schedule
- A price or service changes — update it everywhere it appears, including the confirmation message.
- Someone joins or leaves — add or remove their calendar, and check nothing is still routed to them.
- Hours change, or a holiday is coming — block it before it can be booked, not after.
- You move, or a room changes use — the address in the messages, and any service tied to that room.
- You change a password or an email address — re-check every connection that used it. This is the most common cause of a sync going quiet.
FAQ
How often should I test my own booking page? Once a quarter as routine, and immediately after any change to services, staff, hours, or accounts. Test the way a customer would: another device, signed out, through to the confirmation.
My calendar sync stopped and I did not notice. How do I catch it next time? Build it into the quarterly test booking — if the test slot does not appear on your calendar within a minute, the connection is down. Until then, treat any unexplained double-booking as a sync failure rather than a fluke.
Should I delete old services or hide them? Hide them. Deleting can strip the history attached to past bookings, and a hidden seasonal service is one click from returning. Delete only what you are certain you will never offer again.
Are reminders worth keeping if my no-shows are already low? Yes, but check they still say true things. A reminder with the wrong address or an obsolete cancellation window does more harm than none, because people act on it.
Bookings dropped and nothing looks broken. Where do I look? Work backwards from the page: are the links pointing at it still correct, is there real availability in the next couple of weeks, and does the service list still show what people actually come to you for. Empty availability and a stale menu look identical to a customer who simply leaves.
The system does not need constant attention. It needs a short, honest check often enough that drift never gets more than a few weeks old. Book yourself once a quarter, read your own messages twice a year, and fix the durations when the day starts running late. If you want booking that stays accurate without the babysitting, take a look at BookForme Store.
