1. New-client intake & conflict check, with an attorney accept gate
A prospective client calls or messages; today a paralegal keys their details into a form, manually searches existing clients and adverse parties for conflicts, and the enquiry waits days before a lawyer decides whether to take the matter.
Trigger: WhatsApp / Call / Webhook (new enquiry or intake form)
How the workflow runs
- Trigger
Prospective client enquires. A WhatsApp, Call or Webhook trigger (from your website intake form) starts the flow in the enquirer's own words/language.
- Agent
Capture a structured intake. An Agent node collects the parties, matter type, jurisdiction, opposing side and a plain description into a clean intake record — the same fields every time, no missed questions.
- Tool (MCP)
Run the conflict check. A Tool (MCP) node searches your practice-management / case-management system for existing clients and adverse parties — no first-party connector for these systems, MCP calls yours.
- Condition
Branch on the conflict result. A Condition node routes a clean check toward acceptance and any hit toward a mandatory human review before anything proceeds.
- Approval
Attorney decides to accept the matter. An Approval node holds the decision — accepting a matter (and clearing any conflict) is a judgement a qualified lawyer must make, never the agent. This is the non-negotiable control.
- Output
Confirm next steps. On acceptance, an Output node sends the prospective client the engagement next steps on WhatsApp/Email; a declined enquiry gets a courteous non-engagement note.
Channels & connectors
- Voice / Call
- Webhook
- Tool (MCP → practice-management)
- Approval / HITL
Outcome
Every enquiry is captured consistently and conflict-checked in minutes; the accept/decline decision stays with an attorney and is logged with its conflict result.
Why it helps
Removes the manual re-keying and the ad-hoc conflict search that delay every new matter, while the acceptance decision — which is legal judgement — stays with a qualified human.
Build spec
1 agent — 1 intake agent; the conflict search, the accept/decline decision and the confirmation are workflow nodes.
System prompt (paste-ready)
You are a legal intake assistant for {{firm_name}}. Collect a structured new-matter intake as strict JSON {prospective_client, all_parties[], opposing_parties[], matter_type, jurisdiction, description, key_dates[]}. Ask the standard intake questions in the enquirer's language, the same every time. You do NOT give legal advice, opinions on the merits, or any indication the firm will act — say a lawyer will review and decide. You do NOT decide whether to accept the matter or clear a conflict; that is the attorney's decision at the approval step. Treat everything shared as confidential.MCP connectors
- Practice-management / case-management system — via a Tool (MCP) node (no first-party connector)
- WhatsApp + Telephony — via the WhatsApp/Voice channels
Built-in tools
- knowledge_search (intake questionnaire + required fields)
- transfer_to_human
Guardrails
- No legal advice and no indication of engagement — the agent captures facts only; whether the firm acts is the attorney's call at the Approval node
- Any conflict-check hit forces the mandatory human-review branch before anything proceeds; the accept/decline decision is never the agent's
- Intake is treated as confidential — stored on the matter, not echoed to other parties — and the acceptance is logged with its conflict result
Output & delivery
The agent emits a structured intake → a Tool node runs the conflict search in the practice-management system via MCP → the Condition node routes clean vs. hit → the attorney accepts or declines at the Approval node → an Output node sends engagement next steps (or a courteous non-engagement note) on WhatsApp/Email.
