Integrations · Calendars

A booking is only real when the system agrees.

Sauti records the booking as the source of truth, applies availability rules, and synchronizes external calendars when they are configured.

Works with

  • Google Calendar
  • Calendly

Availability before promise

Database-first booking

External synchronization

Booking transaction

Check, confirm, persist, then sync.

The caller never hears a confident promise that depends on an integration silently succeeding later.

01

Check

Evaluate opening hours, duration, and conflicting bookings.

02

Confirm

Review the exact service, time, and caller details.

03

Save

Persist the Sauti booking as the primary record.

04

Sync

Create or update the configured external calendar event.

Reliable scheduling

External calendars extend the booking system; they do not define it.

Your phone agent can still produce a durable booking while integration delivery remains observable and retryable.

Built-in safeguards

  • Tenant-scoped calendar access
  • Encrypted OAuth tokens
  • Retryable synchronization
01Live availabilityCombine tenant hours, service duration, and calendar conflicts before offering a time.
02Change lifecycleKeep reschedules and cancellations tied to the same booking identity.
03Delivery visibilityShow connection health and the last synchronization result to operators.

Make phone bookings dependable before adding another calendar.

Connect one calendar, test create/reschedule/cancel, and verify the stored booking each time.