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 appointment type, duration, location, preferred staff member, and timing constraints
- Check approved availability or collect preferred windows when direct booking is not enabled
- Confirm the next step and repeat caller details
- Write the booking, request, or reschedule note into the calendar or CRM
Qualification fields
- Caller name, contact details, service type, preferred date and time, location, and language
- New or existing customer status, required preparation, duration rule, and cancellation/reschedule reason
- Calendar owner, booking source, confirmation channel, and fallback status
Human handoff rules
- Transfer urgent, sensitive, VIP, or exception-heavy scheduling requests
- Create callback tasks when no slot fits or the calendar is unavailable
- Escalate double-booking risk, payment disputes, and policy exceptions to staff
Do not automate
- Do not double book outside source-of-truth availability
- Do not override staff buffers, service durations, or location rules
- Do not promise appointment confirmation when only a request was captured
- Do not collect sensitive data not required for booking
Stack handoff
- Google Calendar, Outlook, Calendly-style schedulers, HubSpot, Salesforce, practice or field-service calendars
- Calendar event or request note with transcript link and required fields
Plan fit
- Growth for booking plus CRM/calendar handoff
- Scale for multi-location, multiple staff calendars, and reporting
- Enterprise when custom scheduler or security review is needed