Google Calendar sync for bookings: How to test a busy slot
Test Google Calendar sync for bookings with one busy event and a second slot for comparison. Copy a test worksheet and diagnose a slot that stays open.

To test whether Google Calendar sync for bookings blocks a time, mark one test event Busy and look for the slot on your client booking page. Check a nearby slot that should stay available, too. Keep the first check small enough that you can repeat it when someone changes their Google account, reconnects a calendar, or takes over reception.
Start with a slot you can see before the test. If 11:00 was already missing because the studio was closed or the service needs more notice, choose another start for the test.
Write down which calendar does what
On a piece of paper, give each person one row. Record the booking profile clients select, the Google account connected to it, the calendar the booking tool reads for conflicts, and the calendar where it writes appointments. Those can be different calendars. Calendly's connection guide describes separate settings for checking conflicts and choosing where to add bookings. Google's own booking-page help explains what happens when you select calendars to check for availability.
Read the calendar name on the event itself. Two calendars can display together in the same Google view, and both might be called Work. Use the account and calendar name together in your notes. If the tool reads only the connected account's primary calendar, an event saved to a secondary calendar you see in the same week view may be outside the connection's scope.
Write down which actions you expect in each direction. An exported consultation shows that the tool can write a Google event. To check whether Google affects online availability, create an event directly in the calendar that the tool reads. Give each check its own result.
Test one busy event against a visible slot
Use a test location, a private test service with a client preview, or a period the team has explicitly reserved for testing. Use an account and booking route you control. Give the event a plain name such as Calendar test, with no client details or guests. You can check the public slot list without submitting a real appointment.
Here is a fictional test for Mira, who offers 30-minute consultations starting on the hour or half hour. The test date is within the booking window and her 11:00, 11:30 and 12:00 starts all appear. She selects her own name on the booking page. If the page has an option for any available professional, she checks that separately: another person may still be able to take the same time.
| Change one thing at a time | What Mira checks on the booking page |
|---|---|
| No test event | 11:00, 11:30 and 12:00 are visible |
| Google event at 11:00–11:30, marked Busy | 11:00 drops out; 12:00 remains as a control |
| Same event, now marked Free | 11:00 returns after the change has reached the page |
| Set the event to Busy again at 11:00–11:30 | 11:00 drops out again |
| Move the Busy event to 11:30–12:00 | 11:00 is visible; 11:30 drops out; 12:00 remains |
| Remove the test event | All three starts return to their starting state |
This example assumes the service has no extra buffer and that a booking can start when another event ends. If your tool adds preparation time or rounds starts to a different grid, choose a control far enough away and write down which neighboring starts you expect to lose. If you cannot explain the affected times, check the service duration guide before changing a sync setting.
Record when you saved the event, the business time zone and when you reloaded the client page. Use the refresh interval your provider documents, where it gives one. Avoid making three more edits while you are waiting for the first one to show up. If the expected result still fails, write down what you saw and keep the actual unavailable time blocked in the booking tool while you investigate.
Read the pattern when the check fails
The event appears in Google, but clients can still pick the time
Check the account, exact calendar, Busy setting and sync direction first. Open the booking link that clients use, choose the same location, service and person, and confirm the displayed time zone. Then try the dummy event on the calendar your provider says it actually reads. If it works there, you have isolated a calendar selection problem. Reconnecting the same account without checking the source calendar may leave the problem in place.
The first slot stays missing after you move or remove the event
Compare the old start and the new start in one check. If both are blocked, look for another Google event, an internal hold, or a booking that covers the old time. An old event may also be visible in a second calendar on the Google screen. Turn off that calendar's display temporarily to see which calendar owns the event. Then restore its display. Review the event or hold itself before releasing the slot.
A normal week works, but a recurring or all-day block behaves differently
Test one occurrence of a repeating block by moving only that date. Check both that week and the unchanged following week. For an all-day closure, test one date and the morning after it, using the business's local time. Give the all-day event an explicit availability status. If a closure fails this check, put the closure in the booking tool itself until you know which dates the external calendar blocks.
Keep a short record at reception
Check what happens to a test booking you move
If your setup also writes appointments to Google, run a separate check from the booking tool. Use a test service and your own test contact. Put the appointment at 14:00 and find its Google event. Move the booking to 15:00 in the booking tool, then look at both times in Google. Record whether the old entry cleared and the new time shows once. Cancel the test booking at its source and check again. If a copy remains, record which calendar contains it before removing the dummy entry. A private event and a booking can look similar on the calendar while needing different people and actions to update them.
Give the next shift enough information to repeat the check
Save a line that another colleague can repeat: date and time zone, staff profile, source calendar, test event time and status, expected starts, observed starts, person responsible and next check. Use the same service and a normal open period when retesting after a new hire or a change to calendar sharing. Remove the dummy event and confirm the comparison slot still appears before handing the page back to the team.
Skedful's calendar privacy notes describe the connected owner's primary calendar and how two-way sync uses event times to block unavailable slots. If you're setting up a studio with multiple Google calendars, ask Skedful which calendar your account can use. Send the intended calendar roles and a dummy example with the expected slot behavior; leave out client names and calendar screenshots with private events.
About this article
Skedful is the publisher and corrections contact. Our editorial checklist covers product availability, source dates, worked examples and the limits of each claim.
About this articleWorked examples and sample calculations describe hypothetical scenarios. When an article cites research or customer results, follow the source for its context and limits.
Found an error? Send us the article link and the passage that needs a correction.
Report an error to SkedfulReminders come with every Skedful plan, on a schedule you set once. PricingSkedful vs Fresha vs Booksy