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
- Capture caller identity and reason for calling
- Match by phone, email, or company when available
- Create or update contact, company, deal, note, or task by approved rules
- Notify the owner when the lead is urgent or qualified
Qualification fields
- Caller name, phone, email, company, lifecycle stage, lead source, and language
- Intent, urgency, service or product interest, budget or value signal, and preferred callback time
- HubSpot owner, pipeline, deal stage, next action, and transcript link
Human handoff rules
- Route existing customers to the current owner when matched
- Create high-priority tasks for urgent or qualified leads
- Alert sales when a caller asks for pricing, demo, quote, or same-day response
Do not automate
- Do not overwrite source-of-truth fields without mapping approval
- Do not create duplicate contacts when matching rules are uncertain
- Do not write sensitive transcript detail into unrestricted CRM notes
- Do not mark a lead qualified without approved criteria
Stack handoff
- HubSpot contacts, companies, deals, notes, tasks, owners, lists, and workflows
- Fallback alert when HubSpot permissions, required fields, or dedupe rules block the write
Plan fit
- Growth for standard CRM enrichment and owner routing
- Scale for multiple pipelines, teams, and reporting
- Enterprise for custom objects, strict governance, or security review