Implementation playbook
The workflow details buyers need before a demo.
Resolve the practical workflow details before routing callers: what the agent says first, which fields it captures, when it stops, where the record goes, and which plan shape usually fits.
Sample call flow
- Identify service type, duration, location, staff preference, and preferred window
- Check approved calendar availability and buffer rules
- Confirm the slot or create a booking request when direct booking is not allowed
- Send calendar note and caller summary to the team
Qualification fields
- Caller name, phone, email, service type, duration rule, location, and preferred time
- New or existing customer status, reschedule or cancellation reason, and confirmation channel
- Calendar owner, event title, notes, attendee rules, and transcript link
Human handoff rules
- Create callback tasks when no slot fits or calendar access fails
- Transfer urgent, sensitive, VIP, or exception-heavy scheduling calls
- Escalate double-booking risk, unavailable staff, and policy exceptions
Do not automate
- Do not book outside source-of-truth availability
- Do not ignore buffers, service durations, location rules, or staff constraints
- Do not promise confirmation when only a request was captured
- Do not add sensitive notes to shared calendars
Stack handoff
- Google Calendar availability, event creation, notes, reminders, shared calendars, and CRM follow-up
- Fallback summary when availability lookup or event creation fails
Plan fit
- Starter for one calendar and simple booking
- Growth for CRM handoff and multiple workflows
- Scale for multi-location calendars, buffers, and reporting