Industry guides
AI intake for a law firm: where the boundaries belong
Design an initial intake process that collects approved details while preserving lawyer-owned decisions about confidentiality, conflicts and representation.
Published · Collection dates are retrospective editorial dates.
An intake assistant can collect a name and a callback request. It can also, through careless wording, appear to evaluate a case, promise representation or imply that a deadline is being handled. Those are very different acts, even when they happen in the same conversation.
Start the project by defining what the assistant may collect and what only the firm's responsible lawyers may decide. The intake boundary should be reflected in data access, tool permissions, customer wording and the process for unfinished requests.
This article is an operational guide for planning that review. It does not state the professional-conduct rules for a particular jurisdiction or determine when a lawyer-client relationship arises. The firm's lawyers must check the current governing rules and authorities for their actual practice before approving the workflow.
Collect enough for the next approved step
Ask the firm to specify the initial fields. Contact details, broad matter category and a request for a conversation may be sufficient for the first stage. The appropriate scope depends on the firm's practice, conflicts process and applicable duties.
Avoid inviting a full narrative by default. A conversational interface can make disclosure feel easy before the firm has decided what information should be received, where it should go or who may access it.
| Intake element | Operational question | Decision owner |
|---|---|---|
| Initial fields | What information is needed before review? | Responsible firm lawyers |
| Matter category | Which approved categories can intake use? | Practice leadership |
| Conflicts process | What is collected, restricted and reviewed? | Firm's designated conflicts owner |
| Representation wording | What may intake say about acceptance? | Responsible firm lawyers |
| Urgent communication | Where does a time-sensitive message go? | Approved firm process |
These are review questions, not legal conclusions or a universal intake form.
Do not let categorization become advice
Routing a request is an administrative task. Telling someone what claim they have, whether they will succeed or what action they should take is different. The assistant needs clear examples of the boundary supplied and approved by the firm.
In a hypothetical intake, a caller describes a dispute and asks whether it is worth pursuing. The system may record the approved category and route the request. It should not invent an assessment simply because a conversational answer would feel more complete.
Have the firm approve language for uncertainty and excluded questions. The wording should be useful and accurate without suggesting that a lawyer has reviewed facts when no such review occurred.
Review confidentiality before connecting tools
ABA Formal Opinion 512, issued in 2024, discusses generative AI under the ABA Model Rules, including confidentiality and supervision. It is background for the firm's analysis, not a substitute for the rules governing its lawyers.
Map the services receiving prospective-client information: telephony, transcription, model processing, CRM, logs, support and exports where present. Have the responsible reviewers evaluate access, data use, retention and contractual arrangements for the actual tool.
Do not assume that a restricted main database means the entire conversation is restricted. A transcript copied into a support ticket can create a different access path. The review should follow the information through the whole workflow.
This is an operational recommendation, not a determination of the legal effect of any particular disclaimer.
Keep conflicts review with the approved process
The firm's designated owners should decide what information is required, where it is stored and who may see it. The assistant should not declare that a conflict is cleared because a name search returned no obvious match.
If the first-stage integration only collects information, preserve that status. Do not label the record “qualified” or “accepted” unless the firm has approved exactly what that label means and the necessary decision has occurred.
A hypothetical enquiry may involve variant names or several entities. The operating task is to route it through the firm's approved review, not to generate a confident shortcut around that review.
Do not turn a message into a deadline promise
People may mention dates, hearings or other time-sensitive concerns. The firm must provide the approved process for receiving and escalating those communications. The assistant should not calculate legal deadlines or assure the caller that the firm is protecting their position.
Make the status of the request explicit. A callback request is not a completed consultation. A message delivered to an inbox is not evidence that a lawyer accepted responsibility. Define acknowledgement and fallback within the actual staffing arrangement.
Intake can organize a request without deciding its legal meaning.
This is an original editorial principle. It helps keep the system useful while preserving the decisions that require the firm's professional judgment.
Test the impressions the conversation creates
Use synthetic scenarios reviewed by the firm: a caller seeking advice, a request outside the practice area, a person who believes representation is already confirmed, a time-sensitive message and an unavailable recipient. Inspect both the transcript and resulting records.
Ask a reviewer what a reasonable reader might understand from the wording, then have the firm's responsible lawyers assess it under the applicable requirements. Technical success alone cannot establish that the interaction stayed within the approved professional boundary.
Finally, review the handoff with the staff receiving it. They need the caller's goal, approved details, current status and unanswered questions without an invented legal assessment embedded in the summary. Expand the scope only after the firm can explain and operate those boundaries in the ordinary and awkward cases alike.
Sources
Explore the workflow considerations for customer intake qualification.
Keep reading
