Understand Operator's native calendar engine and external Calendly availability sync.
By default, Operator functions as a self-contained, enterprise appointment booking engine.
All bookings, schedules, and staff availability are tracked directly in your dedicated PostgreSQL database:
- Zero third-party calendar dependencies required.
- Full access to appointments inside the Operator dashboard (/appointments).
- Automatic synchronization between phone calls, web chat, and messaging channels.
Operator supports reading external busy periods from Calendly via CalendlyProvider in src/server/services/calendar-provider.ts.
The provider registry in src/server/services/calendar-provider.ts strictly registers two providers:
1. NativeCalendarProvider: Local database scheduling.
2. CalendlyProvider: Remote busy period query.
Google Calendar and Microsoft Outlook direct APIs are NOT currently supported in this release. </Callout>