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
- Disclose AI and identify practice-area fit before collecting sensitive detail
- Capture matter type, jurisdiction, timeline, opposing party, and contact information
- Check conflict-screening fields and routing rules where approved
- Schedule intake, create callback, or transfer urgent matters to staff
Qualification fields
- Caller name, phone, email, location, matter type, urgency, and preferred callback time
- Opposing party names for conflict review where approved
- Deadline, court date, incident date, language preference, and referral source
Human handoff rules
- Transfer active deadlines, court dates, detained clients, threats, urgent safety issues, and upset callers
- Route wrong-fit matters using approved decline language
- Create attorney or intake-team tasks with transcript and conflict-screening notes
Do not automate
- Do not give legal advice
- Do not assess case value or likely outcome
- Do not create attorney-client relationship language
- Do not collect unnecessary sensitive facts before fit and conflict rules
Stack handoff
- Clio, Lawmatics, HubSpot, Google Calendar, Outlook, secure email, Slack or Teams intake alerts
- Matter-intake record with practice area, urgency, jurisdiction, opposing-party field, and next step
Plan fit
- Growth for one intake line and calendar handoff
- Scale for multiple practice areas, offices, and advanced routing
- Enterprise for security questionnaire, retention, and custom legal operations requirements