The receptionist offers only open times on the calendar it is connected to, and the Chleb CRM with its booking calendar is built on HighLevel. HighLevel documents a Google Calendar connection that pushes appointments into the Google calendar you choose and reads your busy times back, so the same hour is not offered twice. This guide explains that documented behavior and its limits. Chleb confirms the connection for your account on the integration check during setup.
Chleb's FAQ page says the CRM is a branded workspace built on Go High Level with an appointment booking calendar, and that in the Front Office Bundle, call and booking activity from the AI receptionist writes into that same calendar and pipeline. So the booking is made in that workspace first. Your Google Calendar receives it when it is connected to the workspace as what HighLevel calls the linked calendar.
Everything below describes HighLevel's documented behavior, taken from its help center on the date in the Verification section. It is not a test run on your account. Which calendar the receptionist books into on your plan, and which Google calendars are connected to it, is confirmed on the integration check during setup, before anything is promised.
HighLevel's steps: in the sub-account, open Calendars, then Calendar Settings, then the Connections tab, choose Add New, and click Connect beside Google Calendar. You sign in to the Google account and accept every requested permission, including read and write access to Calendar. HighLevel warns that Google can let you grant only some of the permissions, and that syncing may then fail until you reconnect and grant the missing ones.
HighLevel says calendar connections belong to individual user profiles, not the whole company, so each person connects their own Google account. Its help page says both personal Gmail accounts and Google Workspace accounts work.
You pick one connected calendar as the linked calendar. HighLevel says the linked calendar is also checked for conflicts by default: events created on the linked Google calendar are fetched into HighLevel, and events created in HighLevel are pushed to Google. Its troubleshooting table adds that appointments only write back when the Write Back Appointments setting is on. With it on, an appointment the receptionist books appears on the Google calendar you chose, and an event you add in Google blocks that time for booking.
How your own Google events arrive depends on a sync preference. HighLevel's default, which it calls one-way sync, brings them in as blocked time: nobody can book over them, no contact is created for your guests, and no automations run. Its two-way sync brings them in as appointments instead, creates a contact for each guest, and can start workflows like any other appointment. HighLevel's example is a doctor's appointment you add in Google with the doctor as a guest: default sync blocks the hour, while two-way sync creates an appointment and a new contact for the doctor. The default keeps personal events from turning into contacts, and the choice is made during setup.
With write-back on, HighLevel writes new bookings to the external calendar and updates it when an appointment is cancelled or rescheduled in HighLevel. Marking an appointment as showed or no-show does not change the Google event, which HighLevel says avoids sending update emails to guests.
Other calendars can be added as conflict calendars. HighLevel reads their events and blocks those times, but only for events marked Busy. An event marked Free is fetched, yet the time stays open for booking. Conflict calendars never create appointments; they only block time.
That is how a personal or family calendar can stop the receptionist from offering an hour you are already committed to, without its details becoming appointments. HighLevel recommends keeping write-back on only your main work calendar, because write-back on several calendars creates duplicate events, and it recommends matching the time zone of your Google calendar to your HighLevel profile.
These are the documented ways a Google connection stops working or behaves differently than an owner might expect. Each one is quick to check once you know about it.
After a test booking during setup, you should see the appointment on the Google calendar you chose as linked, with the same start and end time as in the CRM. Then add a busy event in Google and ask the receptionist for that hour: it should offer a different time. HighLevel's article lists real-time appointment syncing as a benefit of the connection, and how quickly changes appear on your account is one of the things to watch in that test.
If a booking does not appear, the usual causes in HighLevel's troubleshooting table are no linked calendar selected, sync turned off, write-back turned off, or a broken connection that needs to be reconnected.
Checked on September 28, 2026 against HighLevel's help center: How to Integrate Google Calendar with HighLevel (last modified May 8, 2026), Setting Up Linked Calendars and Conflict Calendars (last modified July 8, 2026), Why Google Calendar Integration Breaks (last modified April 30, 2025), Calendar Integration Disconnection Notifications (last modified April 22, 2025) and Hide Third-Party Calendar Details (last modified February 5, 2025). The statement that the Chleb CRM is built on HighLevel comes from Chleb's own FAQ page.
Not tested: this page describes the platform's documented behavior, not a test run on your account. No booking was made into a Google calendar for this guide, sync timing was not measured, and the effect of Google Workspace admin policies on the permissions was not checked. Chleb's FAQ describes the receptionist writing into the CRM calendar for the Front Office Bundle; for other plans, the calendar the receptionist books into is confirmed with you. Chleb confirms the connection on the integration check during setup.
The booking is made on the calendar in your Chleb workspace, which is built on HighLevel. When your Google calendar is connected there as the linked calendar, HighLevel documents that new appointments are pushed to it. Which calendars are connected for your account is confirmed on the integration check during setup.
With HighLevel's default sync they arrive as blocked time, not appointments, and no contacts are created for your guests. Events marked Free do not block time. Its Private Mode for synced events, which HighLevel says is on by default, hides the details from other users.
HighLevel says syncing stops until you reconnect, existing appointments stay in the CRM, and syncing resumes after reconnection. It can alert the user who connected the calendar by email, in the app and by text.