Google Calendar sync for booking systems, what matters
· Updated · 5 min read
Two calendars that do not talk to each other are worse than one. Here is what makes sync reliable, and where it usually breaks.
Why two calendars are worse than one
Two calendars are worse than one because each holds appointments the other does not know about. A personal appointment agreed by phone goes into the phone calendar, the booking system never hears of it, and a customer is given exactly that slot. With several staff members each keeping their own calendar, there are that many more places for a clash to start.
As long as there are two sources of truth, a collision is a question of when. So the first question to ask about any system is which direction it syncs in.
One-way versus two-way
One-way sync writes appointments from the system into Google Calendar but never reads from it. That is enough to see your day on your phone, and not enough to prevent a clash, because an event you added by hand does not block the slot in the system.
Two-way sync also reads what is already in the calendar and treats it as busy. That is what lets you keep running your life in Google Calendar, the accountant, a school meeting, travel, and know no customer will be booked over it.
- One-way: you can see appointments on your phone. Does not prevent clashes.
- Two-way: every calendar event blocks a slot. This is what you actually need.
Where sync breaks in practice
Four failure points come up again and again:
- Lag. A sync that runs every 15 minutes leaves a window in which two people can take the same hour. The more bookings per hour, the more that window costs.
- Time zones. An event stored without an explicit time zone shifts by an hour across a daylight-saving change. It looks like a random bug and is very hard to trace.
- Multiple calendars. If you keep a work calendar and a personal one, the system has to read from both and write to only one.
- Deletions. An appointment deleted in the calendar must free up in the system too. Systems that do not read deletions leave "ghost appointments" blocking free time.
Why this matters more with an AI agent
When a system only shows a booking page, slow sync causes inconvenience. When an agent answers a customer within seconds and promises an hour, slow sync causes a wrong promise, and that costs trust rather than convenience.
So in igentor the appointment is written to Google Calendar as a real event at that moment, and availability is read from your calendar when a customer asks, before any offer is made, so what the agent offers follows what the calendar shows at that moment.
What about Outlook or Apple Calendar?
Not every business runs on Google Calendar. Plenty of clinics and offices live in Outlook or Apple Calendar, and the question becomes whether the system supports those directly or only through a bridge.
The common answer is indirect sync: connect the other calendar to Google Calendar, and from there to the system. It works, but every extra link adds lag and a failure point, and it is often one-way. If your primary calendar is not Google, check that explicitly before committing rather than assuming it will sort itself out.
What happens when an appointment moves or is deleted?
When a customer asks on WhatsApp to move an appointment, the agent checks a free time in the calendar, moves the event in Google Calendar itself, and the reminder moves to the new time. There is no second record to fix by hand.
When someone on the team drags or deletes an appointment in Google Calendar, the booking in igentor follows on the next calendar check: it moves or is cancelled, so it no longer counts on a day it does not happen.
An appointment written straight into Google Calendar, with the customer's phone number in the event, is recorded as a booking too, on a paid plan or during the trial. If you turned on reminders for such appointments, it gets the same reminder as any other.
What to test during the trial
Three five-minute checks catch the failures above:
- Add an event by hand in Google Calendar and confirm the system stops offering that time.
- Book an appointment in the system and confirm it appears in the calendar, at the right time, not an hour out.
- Delete an appointment in the calendar and confirm the slot becomes bookable again.
Google Calendar sync in igentor: common questions
Is the sync two-way? Yes. An appointment the agent or the booking page sets is written as an event in the Google calendar you connected, and before every offer the agent reads that same calendar: an event you added yourself blocks its time. An event you marked as "Free" in the calendar does not.
What happens when a client cancels? When a client cancels over WhatsApp, the agent deletes the event from Google Calendar and the time is free again. If you set cancellations to wait for your approval, the request reaches you first. If the waitlist is on, the freed time is offered to whoever is waiting for it.
How many calendars does a team need? One: the business's Google calendar. Every team member's appointments are written to it, each one with the team member it belongs to, and availability is checked for each person separately. An event in the calendar that is not assigned to a team member blocks everyone. Other personal calendars are not read, so private time that should block goes into the business calendar.
Frequently asked questions
Why does an appointment show up an hour off in my calendar?
The usual cause is time zones: an event stored without an explicit time zone shifts by an hour across a daylight-saving change. To check, book an appointment in the system and confirm it appears in Google Calendar at exactly the right time.
Can a booking system sync with Outlook or Apple Calendar?
It depends on the system. The common answer is indirect sync, connecting the other calendar to Google Calendar and from there to the system, but every extra link adds lag and a failure point, and it is often one-way. If your primary calendar is not Google, check that explicitly before committing.
What are ghost appointments in a calendar?
They are appointments deleted in Google Calendar that stay in the booking system, because the system does not read deletions. They keep blocking time that is actually free, so during the trial check that deleting an appointment in the calendar makes the slot bookable again.
How often should calendar sync run?
As close to real time as possible. A sync that runs every 15 minutes leaves a window in which two people can take the same hour, and the more bookings per hour, the more that window costs. In igentor availability is read from the calendar in real time before every offer, and the appointment is written to the calendar at that moment.
In short
Insist on real-time two-way sync, and run the three checks above before you commit. One reliable calendar is worth more than any feature list.
How igentor does this in practice
Especially relevant for
More guides
igentor vs Tor4You, an app or a conversation?
Tor4You is built around a calendar and an app the client opens. igentor is built around the message the client already sends. Two approaches to the same calendar.
WhatsApp Business API vs QR connection: differences, cost and risk
There are two ways to connect a business number to a system: Meta's official channel, or an unofficial linked-device connection by QR scan. Here is how they differ in setup, cost, verification and risk.
A WhatsApp CRM for a business that gets dozens of enquiries a day
Many leads in an appointment business are not lost to a competitor but in the chat list: nobody wrote down who was waiting for what. Here is a minimal system that fixes it.
How much does a booking system cost?
The monthly plan is only part of the bill. Here is what you actually pay, when software is too cheap to matter, and when you should pay nothing.