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.

Availability before promise Database-first booking External synchronization
Works with
Google CalendarCalendly
Connections are workspace-owned. Agents receive only the tools you enable.
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
01

Live availability

Combine tenant hours, service duration, and calendar conflicts before offering a time.

02

Change lifecycle

Keep reschedules and cancellations tied to the same booking identity.

03

Delivery visibility

Show connection health and the last synchronization result to operators.

Explore the stack

Every integration has one clear job.

Voice infrastructure

Route live calls through one managed Telnyx conversation layer.

Explore
Speech & voice

Let callers speak naturally across languages, accents, and interruptions.

Explore
AI models

Use model intelligence without giving it unchecked control of business actions.

Explore
Start with one connection

Make phone bookings dependable before adding another calendar.

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

Plan your pilot