Calendar and scheduling integrations — letting visitors book appointments or view availability directly from your site — depend on a live connection to a calendar service, and when bookings stop syncing, availability shows incorrectly, or the connection errors out, we fix that connection on your site’s side, though we don’t control the calendar service itself.
Check whether the issue is one-directional or affects both syncing directions
Test whether a booking made on your site correctly appears in the connected calendar, and separately whether a change made directly in the calendar correctly reflects as updated availability on your site. Confirming which direction (or both) is actually broken narrows down where the connection is failing.
Calendar / scheduling integration errors
Booking or availability sync broken between your site and a calendar service — fixed on your end.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| A calendar or scheduling integration isn’t syncing bookings or availability correctly | This fix covers it |
| You want a scheduling tool set up for the first time, not an existing integration fixed | Worth confirming this is a repair, not a new setup — approach and scope differ |
| The calendar service itself is reporting a service-wide outage | Outside what we can fix — that’s the service’s own issue, on their timeline |
| The issue is a general webhook connection, not specifically calendar syncing | Zapier / webhook connection repair, if a webhook rather than a direct calendar integration is involved |
What you are seeing
- Bookings made on your site not appearing in the connected calendar
- Availability shown on your site not reflecting the calendar’s actual current state
- An error during the booking process referencing the calendar connection
- The issue possibly affecting only one direction of sync (bookings in, or availability out) rather than both
Common causes
- An authentication token or connection permission expiring between your site and the calendar service
- A timezone mismatch between your site’s configuration and the calendar service’s own settings
- The calendar service’s API changing in a way the existing integration no longer matches
- A caching issue serving stale availability data rather than the calendar’s current, live state
- Two separate calendar connections both writing to the same calendar, creating conflicting availability data
What we do
- Test both directions of sync to identify exactly where the failure occurs
- Check authentication and connection permissions between your site and the calendar service
- Verify timezone configuration matches correctly on both sides
- Reconnect or reconfigure the integration to restore correct syncing
- Test with a real booking and a real calendar change to confirm both directions work
- Flag clearly if the cause is something only the calendar service provider can resolve
What is included
- The specific cause of the sync failure identified and corrected, where within our control
- Verified correct syncing in both directions with real test cases
- Confirmed matching timezone configuration
- A clear flag if the cause is on the calendar service’s own side
Not included
- Resolving an outage or bug on the calendar service’s own platform
- Setting up a scheduling tool from scratch, a separate, related fix if that’s not already done
- Broader webhook connections unrelated to calendar syncing specifically, a separate, related fix
- Ongoing monitoring for future changes on the calendar service’s side
Questions about this fix
Why would only one direction of syncing be broken and not the other?
The two directions (sending a new booking to the calendar, versus pulling current availability from it) often use separate technical mechanisms, so a failure in one doesn't necessarily affect the other — testing both separately is exactly how we isolate which is actually broken.
Could a timezone mismatch really cause a sync failure, not just wrong times?
Yes — beyond just displaying an incorrect time, a significant timezone mismatch can sometimes cause bookings to appear to conflict incorrectly or availability to seem wrong entirely, which looks like a broader sync failure rather than what it actually is.
What if the calendar service changes something again after this is fixed?
That's a real, ongoing risk inherent to depending on a third-party service's own API and infrastructure — a future change on their end could require reconfiguring the connection again, which isn't something a one-time fix can permanently prevent.
Will you need access to my calendar account?
Where the service supports it, a delegated or limited-access connection is preferable to your full account password — we'll ask for whatever access is genuinely needed to diagnose and fix the connection.
Can this affect bookings that were made while it was broken?
Potentially, yes — we'd check specifically for any bookings made during the failure window that may not have synced correctly, so nothing falls through unnoticed.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.