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
- Ask the caller what they need and identify the lead category
- Collect fit, urgency, budget or value signal, location, and timing
- Score the lead by approved rules instead of guessing
- Route qualified leads to the owner and send low-fit leads to a safe next step
Qualification fields
- Name, phone, email, company or property, location, and preferred contact time
- Need, timeline, budget or project size, decision-maker status, and urgency
- Source campaign, language, qualification score, owner, and next action
Human handoff rules
- Transfer high-value, urgent, VIP, and ready-to-buy leads
- Create CRM tasks for qualified leads outside staff hours
- Route wrong-fit leads with approved decline, referral, or nurture language
Do not automate
- Do not invent qualification scores without approved rules
- Do not ask sensitive or discriminatory questions
- Do not promise pricing, eligibility, or acceptance outside policy
- Do not bury hot leads in generic summaries
Stack handoff
- HubSpot, Salesforce, Pipedrive-style CRM, Google Sheets, Slack or Teams lead alerts, webhooks
- Lead record with score, reason, qualification answers, transcript link, and owner
Plan fit
- Growth for CRM enrichment and priority routing
- Scale for multiple pipelines, territories, and team routing
- Enterprise for custom scoring, data governance, or procurement requirements