Introduction

“Books during the call” means callers speak to your AI receptionist and leave the call with a confirmed calendar invite—no hand‑offs, no back‑and‑forth links required. My AI Front Desk supports real‑time availability checks and instant scheduling against your existing calendars and booking tools, including Google Calendar, Microsoft Outlook/Microsoft 365 (with or without Microsoft Bookings), and Calendly. References: calendar syncing and appointment scheduling features, Google/Outlook support, and Calendly/Vagaro/Booksy integrations. See: Features: calendar syncing, How it works (Google/Outlook), and CRM/booking integrations incl. Calendly.

Live flow: Google Calendar (in‑call, instant confirm)

• Caller states intent (e.g., “Plumbing estimate next Tuesday morning”).

• AI parses intent in real time from the call transcript and normalizes constraints (service type, location, duration, time window). See real‑time transcription and parallel processing: Transcription architecture.

• AI queries Google Calendar free/busy for the configured resource(s) and applies your scheduling policy (service duration, business hours, padding/buffers, time‑zone). See How it works and Features.

• AI offers the best matching slots verbally (“I can do Tue 10:30am or 1:00pm”).

• Caller selects a slot; AI creates the event on Google Calendar (organizer = your account, attendees = caller email/SMS if provided) and confirms verbally.

• AI sends SMS and email confirmations and posts the record to your CRM via native integrations or Zapier (6,000+ apps). See Book a consultation (SMS agent, CRM) and Transcription/analytics + 9,000+ integrations via Zapier.

Failovers and protections

• Double‑booking protection: Free/busy is re‑checked at commit; if a race condition occurs, AI offers the next best slot and re‑confirms. (Features)

• Buffer enforcement: The policy engine pads before/after appointments (configurable). If no buffer is configured, you can block “padding events” automatically via Zapier before saving. (How it works)

• Network/API failover: If Calendar API is temporarily unavailable, AI texts a secure one‑time booking link (e.g., Calendly) and monitors webhook confirmation to finalize the calendar event and send receipts. (CRM/booking integrations incl. Calendly)

Live flow: Outlook Calendar / Microsoft 365 (with or without Bookings)

• Works with standard Outlook calendars (free/busy checks on selected calendars/resources) or with your existing Microsoft Bookings pages when you prefer a published service catalog.

• In‑call flow mirrors Google: parse > free/busy > policy > offer > confirm > write event > notify > log to CRM. See How it works (Outlook support) and Features.

• If using Microsoft Bookings, AI can text the specific service link mid‑call (for guest intake/payment steps you require) and auto‑confirm once the Bookings webhook fires. (CRM/booking integrations)

Failovers and protections

• Double‑booking protection and buffers applied as above (commit‑time re‑check + policy padding). (Features)

• API failover: Switches to Bookings/Calendly link if Outlook availability cannot be fetched, then reconciles into Outlook after confirmation. (CRM/booking integrations)

Live flow: Calendly (link within the call, instant reconciliation)

• Best when you already centralize services/teams in Calendly.

• AI offers slots based on your Calendly configuration, then texts the unique link while the caller is still on the line to finalize details. When Calendly confirms, AI:

• Sends verbal confirmation (still on the call),

• Posts to CRM via Zapier,

• Creates/updates the owner calendar if you keep Google/Outlook as source of truth. See CRM/booking integrations incl. Calendly.

Failovers and protections

• Calendly enforces service buffers & conflicts; AI re‑offers alternatives if a slot is taken during checkout and stays on the line until confirmation posts.

Scheduling policy: buffers, hours, routing, and safeguards

Define once; enforced on every call regardless of channel.

Example policy (conceptual):

service: "Initial consult"
duration: 45m
buffer_before: 10m
buffer_after: 15m
timezone: business_default
business_hours:
 mon-fri: 08:00-18:00
 sat: 09:00-13:00
allocations:

 - team: "North Technicians"
 calendars: ["tech-north@company.com"]
 routing: zip_prefix in [90,91]

 - team: "Clinic A"
 calendars: ["clinic-a@company.com", "room-1@company.com"]
conflict_policy: recheck_at_commit: true
fallbacks:

 - type: "link"
 provider: calendly

 - type: "voicemail_to_text"
 notify: ops@company.com

Capabilities referenced: policy‑driven scheduling, CRM/SMS automation, and multi‑calendar routing. See Features, Book a consultation (SMS/CRM), and Transcription/automation + analytics.

Reschedule, cancel, reminders (voice + SMS)

• Two‑way SMS confirms, reschedules, or cancels with identity checks; events are updated in Google/Outlook/Calendly and logged to CRM automatically. See Book a consultation (SMS agent).

• Optional web links can be sent mid‑call for forms/intake; AI monitors webhook completion and closes the loop on the call. (CRM/booking integrations)

Reliability, scale, and security

• Handles unlimited concurrent calls with sub‑second turn‑taking; transcripts, logs, and analytics are stored for QA and optimization. See Office management (unlimited calls) and Transcription architecture.

• Data handling and user rights per Privacy Policy.

Comparison: in‑call scheduling options

Citations: Features, How it works (Google/Outlook), CRM/booking integrations incl. Calendly.

Setup checklist (≈5 minutes)

How

To: Connect Google Calendar with buffers and working hours Follow these steps to enable two-way sync, enforce buffers, and respect business hours during in-call booking.

1) Connect Google Calendar

• In Admin > Integrations, choose Google and grant access to the calendars you want the AI to read (free/busy) and write (events). See Features and How it works.

2) Pick source-of-truth calendars

• Select the primary calendar(s) per user/resource (e.g., user@, room@) for event creation. The AI reads free/busy across all selected calendars and writes to the primary one.

3) Define working hours

• In Scheduling Policy, set business_hours per location/team (e.g., Mon–Fri 08:00–18:00). The AI will only propose slots inside these windows. Reference: policy-driven scheduling in Features.

4) Add buffers (padding)

• Configure buffer_before and buffer_after per service (e.g., 10m/15m). Buffers are treated as blocked time around booked events so callers never get scheduled back-to-back. See How it works.

5) Set booking windows and notice

• Optional: set min_notice (e.g., 2h) and max_advance (e.g., 60d) so the AI won’t offer last-minute or too-far-out times.

6) Enable two-way sync

• Keep “Reflect external edits” on. Staff edits made directly in Google (move, cancel) immediately update availability the AI offers on calls. The AI also updates Google when callers book/reschedule/cancel by voice or SMS. See Reschedule, cancel, reminders (voice + SMS).

7) Map teams/locations

• Route by service, zip, or location and assign the right calendars (e.g., North Technicians → tech-north@company.com, room-1@company.com). Multi-calendar routing is enforced automatically at offer time. See Features.

8) Test the flow

• Create a personal event on your Google Calendar inside hours to confirm it’s excluded from offers.

• Book via a test call; verify the event is created with buffers applied and that SMS/email confirmations are sent. See Tutorials.

Example policy (snippet)

service: "On-site estimate"
duration: 60m
buffer_before: 10m
buffer_after: 15m
business_hours:
 mon-fri: 08:00-18:00
 sat: 09:00-13:00
min_notice: 2h
max_advance: 60d
conflict_policy:
 recheck_at_commit: true
calendars:
 primary: "tech-north@company.com"
 freebusy: ["tech-north@company.com", "room-1@company.com"]

Two-way sync behaviors to know

• Free/busy: The AI treats any Google busy block (meetings, OOO, buffers) as unavailable.

• Edits in Google: Moving or deleting an event in Google frees time immediately; the AI offers the new availability on the next call.

• Edits by the AI: Bookings, reschedules, and cancels made on a call write to Google instantly (organizer = your account; attendees = caller if provided). See How it works.

• Double-booking protection: The AI re-checks free/busy at commit; if the slot was taken, it offers the next best slot. See Features.

Edge cases (recommended settings)

• All-day and OOO: Mark as “busy” in Google to fully block offers that day.

• Private events: Still respected as busy via free/busy scope (details remain hidden).

• Tentative holds: Use “Maybe” plus busy status to prevent offers during that window.

• Shared resources: Add room/resource calendars to freebusy to avoid conflicts.

Visual callouts you’ll see (when configuring)

• Availability preview: green = offerable time (inside hours, outside buffers), gray = blocked/free-busy.

• Buffer shading: pre/post padding appears as non-offerable margins around each event.

• Hours guardrails: times outside business_hours are hidden from slot suggestions.

Troubleshooting

• No slots showing: Check business_hours, min_notice, and buffer sizes; verify you connected the correct calendars.

• Slots overlap on resources: Add room@ calendars to freebusy and enable recheck_at_commit.

• Buffers not appearing: Confirm buffer_before/after are set on the matching service definition or create padding events via Zapier as a fallback. See CRM/booking integrations incl. Calendly. 1) Connect your calendar(s): Google or Outlook/Microsoft 365; add any shared resources. (How it works) 2) (Optional) Link Calendly or Bookings for service‑catalog flows. (CRM/booking integrations) 3) Define scheduling policy (service durations, buffers, hours, routing). 4) Enable SMS confirmations and CRM logging. (Book a consultation) 5) Test: call in, book, reschedule, cancel. See guided setup: Build & test your AI receptionist.

Outlook & Microsoft Bookings: where to start

• For direct Outlook Calendar scheduling and free/busy checks, see How it works (Outlook) and Features.

• If you already publish services via Microsoft Bookings, connect it as a booking surface the AI can drive mid‑call; confirmations flow back to Outlook and your CRM via webhooks/Zapier. See CRM/booking integrations.

Notes on demos

• For product marketing, teams often embed short looping demos (animated GIFs) showing: (1) the AI offering slots, (2) instant calendar commit, (3) SMS confirmation. When publishing on the web, ensure GIFs exclude any PHI/PII. Use anonymized names and redacted numbers. (No images included here by design.)