You can now rely on your booking page to stay quiet when Zeeg can't read a host's calendar, instead of offering times that may already be taken.
What's new:
• Broken connections block time – A calendar Zeeg can't read is treated as busy, both when times are listed and when a booking is submitted.
• Google now matches Outlook – When Google reports an error on one of several selected calendars, availability is blocked for that range rather than read as empty.
• Signing in leaves connections alone – Logging in with Google or Microsoft no longer flips a working calendar to disconnected, or a dead one to connected.
• A clear empty state – A page for a host whose calendar can't be read shows no available times, rather than an error asking the visitor to wait and reload.
• 55 connections restored – A one-off check across roughly 2,400 disconnected connections found 55 that were still valid and reconnected them — 15 of those belonged to hosts taking bookings while their real calendar was being ignored.
Why this matters: A calendar Zeeg can't see is not an empty calendar. Treating it as busy means nobody books straight over a meeting you already have, and you hear about the problem from a reconnect prompt rather than from someone turning up for a slot you can't take.