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
- Answer only during approved after-hours windows or holiday schedules
- Disclose AI and ask the reason for the call
- Classify emergency, booking request, routine question, existing customer, or billing issue
- Transfer urgent callers, book routine requests, or create a callback task
Qualification fields
- Caller name, callback number, location, service need, and preferred response time
- Urgency, safety flag, current customer status, and language preference
- After-hours promise made to the caller and assigned callback owner
Human handoff rules
- Transfer emergency, safety, VIP, upset, or high-value calls to the on-call contact
- Create callback tasks for routine calls with a promised response window
- Pause or reroute if the on-call fallback is unavailable
Do not automate
- Do not promise a live response if no one is on call
- Do not answer regulated or sensitive questions beyond approved scripts
- Do not quote complex prices outside approved ranges
- Do not hide that the caller is speaking with AI
Stack handoff
- Conditional forwarding, Google Calendar, HubSpot or Salesforce, Slack or Teams alerts, ticketing, webhooks
- After-call summary with urgency, outcome, transfer attempt, and next action
Plan fit
- Starter for one after-hours number and simple callback handling
- Growth for booking plus CRM/calendar updates
- Scale for multi-location after-hours routing and review reporting