Keep the role narrow
The intake goal is to collect facts for an attorney to check. It is not legal advice, a conflict clearance, an engagement decision, or a promise that the firm will take the matter.
Open with direct scope language:
I can collect a few details for the firm. I cannot give legal advice or confirm representation.
Start with the routing fields
- caller name and safe callback details;
- practice area or matter type;
- state, county, court, or agency involved;
- incident date and any known filing, hearing, custody, or response deadline;
- opposing-party names for the firm’s conflict-check process;
- current or prior representation;
- requested consultation or callback window.
Then use a firm-approved branch for the matter:
- personal injury may need incident, treatment, report, insurance, and representation fields;
- family law may need the matter type and hearing date;
- criminal defense may need custody status, charge, jurisdiction, and court date;
- immigration may need the case type and agency or court deadline.
Collect only what the firm has approved. Do not ask for a full confidential narrative in a tool that is not suitable for it.
Leave the decision with the firm
The call record should support one next step for firm staff:
- attorney or intake-team follow-up;
- request for missing information;
- consultation request;
- polite callback or decline handled under firm policy.
The AI should not say the matter qualifies, that a conflict is cleared, or that an attorney-client relationship exists.
Call notes template
Caller: ___ | Safe contact: ___
Matter / jurisdiction: ___
Dates or deadlines reported: ___
Conflict-check names: ___
Current representation: ___
Requested next step: ___
Staff decision required: Yes
Compare the legal intake and lead-qualification playbook with the separate consultation-request workflow.