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
- Classify repair, maintenance, inspection, tow-in, estimate, warranty, or billing intent before staff spend time on the call.
- Collect vehicle, symptoms, urgency, and preferred time
- Book a diagnostic or capture callback
- Escalate tow and safety issues
- Confirm the next step, repeat any commitment made to the caller, and write a reviewable summary for the team.
Qualification fields
- Caller, vehicle year/make/model, mileage, symptom, warning lights, drivability, location, and preferred drop-off time
- Existing customer status, warranty note, fleet or commercial flag, and urgency
- Outcome label, next action, transcript link where allowed, owner, due window, and failed-write status
Human handoff rules
- Transfer safety-critical issues, stranded drivers, warranty disputes, angry callers, and high-value fleet accounts
- Create service-advisor callback tasks for diagnostics and estimates
- Transfer or create a callback when the caller asks for a person or the agent is uncertain.
Do not automate
- Do not diagnose vehicle failures from symptoms alone
- Do not quote final repair cost or completion time without technician review
- Do not give unsafe driving guidance
- Do not continue automation when approved knowledge, consent, destination access, or fallback ownership is missing.
Stack handoff
- Shop calendar, CRM, service ticket note, Slack or Teams advisor alert, Google Sheets intake log
- Structured call summary with intent, urgency, caller details, next action, and review status
Plan fit
- Growth for service intake and advisor callbacks
- Scale for multi-bay shops, fleet routing, and high-volume call spikes
- Enterprise for custom shop-management integrations