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 caller, account, lead, or service reason
- Look up existing record when phone, email, or account clue is available
- Create lead, task, note, or case according to field requirements
- Notify owner, queue, or territory when priority rules match
Qualification fields
- Name, phone, email, company, account clue, product interest, and region
- Lead source, urgency, value signal, territory, owner, and next step
- Salesforce object type, required fields, duplicate status, and transcript link
Human handoff rules
- Respect owner, territory, queue, and account rules before routing
- Escalate enterprise, urgent, or existing-account calls to the correct owner
- Create fallback tasks when required fields or permissions block record creation
Do not automate
- Do not bypass Salesforce validation rules
- Do not create duplicates when match confidence is low
- Do not write private caller details into broad-access fields
- Do not assign ownership without approved territory logic
Stack handoff
- Salesforce leads, contacts, accounts, opportunities, tasks, cases, queues, and owner rules
- Failed-write alert with required field, permission, or duplicate reason where available
Plan fit
- Growth for lead and task creation
- Scale for owner routing, queues, and reporting
- Enterprise for custom objects, strict permissions, or procurement review