Calendar sync you cannot quite trust

You drag the 14:00 into the 15:00 slot in Google Calendar because the client asked. Your booking system still believes 14:00, and tomorrow it will remind them about it.

Sync is usually one and a half directions#

Nearly every booking tool does two things: it reads your calendar to work out when you are busy, and it writes an entry when a booking is made. Very few do the third thing, which is to look again at an entry it already created.

So if you move or delete one of its appointments in Google Calendar or Outlook — the most natural thing in the world to do — the booking system carries on believing the original.

What that costs#

• A reminder with the wrong time. The worst of it, because it reaches your customer and reads as incompetence.
• The old slot stays blocked for a meeting that is no longer there, so you quietly lose availability.
• Your records diverge. The booking page, the calendar attachment and your dashboard all still say 14:00.

Most tools handle this by telling you not to do it — rescheduling must happen inside the tool. That is a workable rule and an easy one to forget at 08:50 with a client on the phone.

How to test the one you have#

Make a test booking. Drag it an hour later in your own calendar. Wait. Then check whether the booking, the reminder and the freed slot have caught up. Then delete it and see what happens.

What Business Box does#

It compares its bookings against your calendar and treats a move and a deletion differently, on purpose.

You move it

The move is followed. The booking is updated, unsent reminders are re-timed to the new time, and the old slot is released. Your customer is not emailed again, because your calendar provider has already moved their copy of the invitation — and moving it yourself does not use up one of the customer's own reschedules.

You delete it

Nothing is cancelled. Deleting is ambiguous — the meeting may be off, or you may be tidying, or it may be a slip — and the cost of guessing wrong is a customer arriving to an empty room. The booking is flagged, the time stays held, and you get one email asking what you meant.

You move it onto another booking

Not followed. Our copy stays where it was and you are emailed with the clash named, because that is almost certainly a mistake.

Changes you make in your own calendar

And it is checked often enough to matter#

Every few minutes for anything starting within twelve hours, immediately before any reminder is sent so none can carry a stale time, nightly for everything else, and whenever you press refresh.

The honest limit#

Detection is by comparison rather than by a push notification from the provider, so a change to something three weeks out is noticed within a day rather than within seconds. The cases where lateness actually costs anything — imminent bookings and reminders — are covered closely; distant ones are not instant.

And if the calendar cannot be read at all#

Bookings pause rather than guess. Your page offers no times, you are emailed, and reconnecting is one button. It is deliberately the safe failure rather than the convenient one.

Last reviewed 28 September 2026.