AI Legal Intake & Triage

How It Works

Tell it your practice areas, intake channels and conflicts process. This generates an intake workflow spec the way an experienced automation strategist would build it — a real, usable deliverable, not a generic checklist. The output follows the standard: legal intake workflow: channel → qualification/triage → conflicts/SOL → CMS capture → escalation; UPL-compliant. Replace every [[token]] with your specifics and it is ready to implement.

What to Provide

AI Legal Intake & Triage

This is the finished deliverable.

1. Intake channels and structured-question flows by practice area

Cover each of these explicitly rather than leaving them implied: [[web form]], [[phone]], [[chat]]. Define [[the specific rule or default for web form]] so nothing is left to guesswork.

Signal of expertise this section should show: Builds a conflicts check and SOL/jurisdiction screen into triage.

Mistake this guards against: Bot giving legal advice (UPL) or implying representation.

2. Conflict-of-interest check step before engagement

Write the specific rule for your situation here: [[the concrete policy, threshold, or owner for conflict-of-interest check step before engagement]]. Base it on your practice areas and adjust as real cases come in.

Signal of expertise this section should show: enforces UPL boundaries and clear 'not legal advice / no attorney-client relationship yet' disclaimers.

Mistake this guards against: No conflict check or SOL screen.

3. Jurisdiction/statute-of-limitations and case-type qualification/triage rules

Write the specific rule for your situation here: [[the concrete policy, threshold, or owner for jurisdiction/statute-of-limitations and case-type qualification/triage rules]]. Base it on your practice areas and adjust as real cases come in.

Signal of expertise this section should show: routes urgent matters to an attorney.

Mistake this guards against: Mishandling privileged/confidential info.

4. UPL safeguards

Define this concretely: [[no legal advice from the bot; clear disclaimers]] — spell out the actual rule, not just that one exists.

Signal of expertise this section should show: Builds a conflicts check and SOL/jurisdiction screen into triage.

Mistake this guards against: No human escalation.

5. Data capture to case-management system

Define this concretely: [[Clio etc.]] — spell out the actual rule, not just that one exists.

Signal of expertise this section should show: enforces UPL boundaries and clear 'not legal advice / no attorney-client relationship yet' disclaimers.

Mistake this guards against: Bot giving legal advice (UPL) or implying representation.

6. Urgency routing and attorney escalation

Write the specific rule for your situation here: [[the concrete policy, threshold, or owner for urgency routing and attorney escalation]]. Base it on your practice areas and adjust as real cases come in.

Signal of expertise this section should show: routes urgent matters to an attorney.

Mistake this guards against: No conflict check or SOL screen.

7. Confidentiality/privilege and intake-not-representation disclaimer

Write the specific rule for your situation here: [[the concrete policy, threshold, or owner for confidentiality/privilege and intake-not-representation disclaimer]]. Base it on your practice areas and adjust as real cases come in.

Signal of expertise this section should show: Builds a conflicts check and SOL/jurisdiction screen into triage.

Mistake this guards against: Mishandling privileged/confidential info.

8. Lead scoring

Write the specific rule for your situation here: [[the concrete policy, threshold, or owner for lead scoring]]. Base it on your practice areas and adjust as real cases come in.

Signal of expertise this section should show: enforces UPL boundaries and clear 'not legal advice / no attorney-client relationship yet' disclaimers.

Mistake this guards against: No human escalation.

9. Follow-up automation

Write the specific rule for your situation here: [[the concrete policy, threshold, or owner for follow-up automation]]. Base it on your practice areas and adjust as real cases come in.

Signal of expertise this section should show: routes urgent matters to an attorney.

Mistake this guards against: Bot giving legal advice (UPL) or implying representation.

Worked Examples

Example 1 — Personal injury firm

Inputs: Website form + phone + referral partners, existing conflict-check DB

Result: Automated urgency triage routed a statute-of-limitations-sensitive case to an attorney same-day instead of sitting in a queue.

Example 2 — Family law practice

Inputs: Phone + referral intake, conflict-check against existing client list

Result: Structured intake logic cut average time-to-first-attorney-contact from 4 days to 1.

Format Checklist

Common Mistakes to Avoid

• Bot giving legal advice (UPL) or implying representation.
• No conflict check or SOL screen.
• Mishandling privileged/confidential info.
• No human escalation.

Next Steps After You Generate This

Week 1: pilot with a small internal group or a single channel/segment. Week 2: review real output against the format checklist below and fix the top 2-3 gaps. Weeks 3-4: expand scope and set a recurring review cadence so the workflow stays accurate as your data and process change.

This deliverable gives you a working starting point on day one — keep the [[tokens]] current as your process, tools, and volume change.