The Chleb CRM and its booking calendar are built on HighLevel, and HighLevel documents a connection that sends appointments to an Outlook or Microsoft 365 calendar and reads your busy times back. Whether that works for you depends mostly on where your mailbox is hosted. This guide covers which accounts HighLevel supports, the admin approval some companies require, and what syncs in which direction. Chleb confirms the connection 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 the AI receptionist's call and booking activity writes into that same calendar. Your Outlook calendar receives the appointment when it is connected to that workspace.
Everything below is HighLevel's documented behavior as of the date in the Verification section, not a test run on your account. Which calendar the receptionist books into on your plan, and the Outlook connection itself, are confirmed on the integration check during setup.
HighLevel lists Office 365, Outlook.com, live.com and Hotmail calendars as supported, and names Microsoft 365 and Exchange Online accounts as supported. It does not support stand-alone or on-premises Microsoft Exchange servers.
HighLevel also notes a case that catches offices running the Outlook desktop program: if your events live only in Outlook on one computer and are not synced to the cloud, HighLevel cannot see them. Its Outlook sync article gives a quick check: sign in to Outlook on the web, and if your events appear there, they can sync after you connect.
HighLevel's steps: open the sub-account Settings, choose Calendars under Business Services, open the Connections tab, choose Add New, click Connect beside Outlook Calendar, sign in to the Microsoft account and accept the permissions. HighLevel lists writer access as required for sending events to Outlook.
Some companies see a Need admin approval screen at that point. HighLevel explains that this means your organization requires a Microsoft administrator to approve the connection first, in the Microsoft Entra admin center, and it links Microsoft's own instructions for reviewing the request. If you use a company Microsoft 365 account, find out who your administrator is before setup day.
HighLevel's linked calendar article covers Google, Office 365 and Outlook.com the same way. The calendar you choose as linked receives new appointments from the CRM, and events created on it come back into the CRM. By default those outside events arrive as blocked time, with no contacts created and no automations started. HighLevel's two-way sync option turns them into appointments, creates contacts for their guests and can start workflows, so a personal calendar on two-way sync would turn family events into CRM contacts.
Other Outlook or Google calendars can be added as conflict calendars. Their events marked Busy block booking; events marked Free do not. With write-back on, bookings, cancellations and reschedules made in HighLevel update the external calendar, while marking an appointment as showed or no-show does not.
Google and Outlook can be connected at the same time. HighLevel's guidance is to use one calendar as the linked calendar for bookings and the rest as conflict calendars, and to keep write-back on only one calendar, since write-back on several creates duplicate events.
These are the documented limits that matter most for an owner deciding whether to connect Outlook.
Know whether your calendar is Microsoft 365 in the cloud or an Exchange server your company runs itself, since only the first is supported. Know who can approve the connection if your company requires admin consent. Decide which one calendar should receive bookings and which others should only block busy time. Then, during setup, book a test appointment and confirm it appears in Outlook at the right time, and add a busy event in Outlook to confirm the receptionist stops offering that hour.
Checked on September 28, 2026 against HighLevel's help center: Integrating Outlook with HighLevel Calendars (last modified August 27, 2026), How to sync HighLevel Calendars With Outlook (last modified August 11, 2026), Setting Up Linked Calendars and Conflict Calendars (last modified July 8, 2026), 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 appointment was synced to an Outlook calendar for this guide, sync timing was not measured, and Microsoft tenant settings other than the admin approval screen HighLevel describes were not checked. Chleb confirms the connection on the integration check during setup.
HighLevel says stand-alone or on-premises Microsoft Exchange servers are not supported. Microsoft 365, Exchange Online, Office 365, Outlook.com, live.com and Hotmail calendars are.
HighLevel explains that the Need admin approval screen means your organization requires a Microsoft administrator to approve the connection in the Microsoft Entra admin center before it can finish.
Only if they are synced to the cloud. HighLevel says events in the Outlook desktop program that are not synced to the cloud are not visible to it. If you can see them in Outlook on the web, they can sync.