Two-way Google Calendar sync, and why one-way is not enough
Plenty of booking tools write appointments to your calendar. Far fewer read it back before they offer a time. That difference is the whole reason software books people into their own days off.
What does two-way actually mean?
Two things, and a system needs both to deserve the name. Writing means a job booked in Ansdale appears in your Google Calendar. Reading means anything already in that calendar is checked before a slot is offered to a caller.
A one-way tool only does the first. It has no idea what else is in your day, so it offers times confidently and wrongly. The failure is not obvious on day one — it shows up the first time you block out a school play, a dentist appointment or a half-day, and the phone cheerfully sells that slot to a customer.
What gets read, and what gets written
On the write side: the appointment time, the service, the customer and the address, so the entry in your calendar is useful on its own rather than a placeholder you have to look up elsewhere.
On the read side: existing events are treated as busy time. That includes the things people forget a booking system should know about — personal appointments, holidays, an install that has been extended, a morning blocked out for paperwork. If it is in the calendar, it is not available.
| One-way (write only) | Two-way | |
|---|---|---|
| Booking appears in Google Calendar | Yes | Yes |
| Knows about your existing events | No | Yes |
| Can double-book you | Yes | No |
| Handles a day blocked out by hand | Ignores it | Treats it as busy |
Is it on every plan?
Google Calendar sync runs on every plan, including the $49 one. We are deliberate about that because a booking system that can double-book you is not a cheaper product — it is a broken one, and gating the part that prevents it would be selling the bug back as a feature.
What happens when things change after the booking?
Calendars are edited constantly, which is exactly why the read side has to be continuous rather than a one-time import. A job cancelled in Ansdale frees the slot. An event added in Google closes it. Neither system is the sole source of truth, which is the practical reality of how small teams actually work — some things get typed into a phone calendar at the kitchen table, not into a dispatch board.
Where a conflict genuinely cannot be resolved automatically, the job is flagged rather than silently reassigned. Quiet resolution is how you end up with two techs at one address.
What about teams with more than one calendar?
Each person’s availability is their own. A shop with three techs is not one shared block of time — it is three separate days that happen to belong to the same business, and a slot is only genuinely open if the person who would do the work is free.
This matters most in trades where customers are attached to a specific person. A salon client booking with a particular stylist, or a customer asking for the tech who came last time, needs the calendar for that individual rather than the shop’s aggregate.
What if I do not use Google Calendar?
Google Calendar is the integration we support directly today, and we would rather say that plainly than list calendars we sync with badly. If you run on something else, outbound webhooks fire when a job is booked, completed or a customer is created, which is how teams push that data into other tools. The same availability the phone reads is what your online booking page shows customers, so the two can never disagree.
What should I read next?
If preventing gaps matters more than preventing clashes, the no-show page covers confirmations. If you want the pricing that this sits inside, it is flat monthly from $49.
No-show protection · online booking · pricing · how it works by trade.