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 no-heat, no-cool, maintenance, install, quote, or billing reason
- Capture system type, symptoms, address, and whether vulnerable occupants are affected
- Check approved booking windows for routine work
- Transfer safety, gas, no-heat, and extreme-weather calls by rule
Qualification fields
- Caller, site address, system type, equipment age, symptoms, and error codes
- Urgency, indoor temperature, vulnerable occupant flag, service agreement status
- Preferred arrival window, access notes, and current customer status
Human handoff rules
- Transfer gas smell, electrical risk, no-heat in cold weather, no-cool in heat risk, and upset customers
- Queue tune-ups and routine maintenance with calendar rules
- Escalate install opportunities and commercial accounts to sales or dispatch
Do not automate
- Do not give safety advice beyond approved emergency language
- Do not diagnose equipment failure from caller description alone
- Do not promise technician arrival outside dispatch rules
- Do not quote replacement pricing without approved guidance
Stack handoff
- ServiceTitan, Housecall Pro, Jobber, Google Calendar, HubSpot, Salesforce, Slack or Teams dispatch alerts
- Call summary with urgency score, equipment details, and transfer result
Plan fit
- Growth for seasonal overflow plus CRM/calendar handoff
- Scale for multiple locations, high-volume spikes, and dispatch reporting
- Enterprise when custom telephony, procurement, or support targets are required