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 the caller reason and whether a human is required
- Collect the minimum context before transfer
- Select the right person, queue, or fallback based on rules
- Attempt transfer and preserve a summary if nobody answers
Qualification fields
- Caller identity, reason, urgency, account or location, preferred language, and emotional state when relevant
- Transfer reason, selected destination, attempted contacts, and fallback outcome
- Summary for the human: what happened, what was promised, and what needs to happen next
Human handoff rules
- Transfer emergencies, sensitive topics, VIP callers, angry callers, and high-value opportunities
- Create callback tasks when transfer fails or the right person is unavailable
- Use alternate contacts or voicemail only when approved by the business
Do not automate
- Do not force automation after the caller asks for a person
- Do not disclose internal transfer rules unnecessarily
- Do not leave failed transfers without owner and due window
- Do not summarize sensitive details into the wrong destination
Stack handoff
- Phone transfer, Slack or Teams alerts, CRM owner routing, Zendesk or ticketing tasks, webhook events
- Transfer note with reason, urgency, destination, attempt result, and transcript link
Plan fit
- Growth when routing and CRM context are needed
- Scale for multiple queues, locations, and escalation rules
- Enterprise for custom support targets, compliance review, or complex telephony