Law Firm AI Intake System: Triage, Follow-Up, and Human Handoffs

The operating problem is rarely a lack of software. A prospective client may call after hours, use a general contact form, reply to a referral email, or request a consultation from a practice-area page. Each path can create a different fragment of the same story. If those fragments do not become one reviewable record, the firm depends on voicemail checks, inbox memory, and repeated explanations.

A useful system narrows that gap without pretending that intake is legal work. It gives the prospective client a clear acknowledgement, gives the firm enough context to choose the next administrative step, and makes the person responsible for review visible. The final decisions remain with the firm.

Start with the prospective-client boundary

The intake path begins before the firm decides whether it can or should act. That makes the boundary more important, not less important. The ABA Model Rule 1.18 page on prospective clients explains that duties can arise from information learned during a consultation about a possible attorney-client relationship, even when no relationship follows.

The rule is a model rule, not a universal instruction for every jurisdiction. A firm should use its state and local rules, engagement procedures, conflict process, privacy requirements, and professional guidance to decide what may be collected, where it may be stored, who may review it, and what the system may say.

The intake system may organize a request. It should not make the firm’s professional decision.

Separate the reasons people contact the firm

A single “contact us” route hides the decision the firm must make. The first improvement is to separate customer moments in language a prospective client can recognize. The categories will vary by practice, but the operating distinction should be clear.

1. New-matter inquiry. The person wants to know whether the firm handles the issue and what information is needed for an initial review.
2. Existing-client request. The person needs the approved client-service route, not a new-business qualification sequence.
3. Time-sensitive situation. The person believes a hearing, notice, custody issue, deadline, safety concern, or other event may require prompt human attention.
4. Referral. Another lawyer, professional, former client, or community contact introduced the person and the source should remain attached to the record.
5. General information. The person may need a useful public answer or the correct service page before a private intake path is appropriate.

These routes can share the same customer record while following different questions and expectations. An existing client should not be asked to retell a matter through a sales form. A referral should not lose the referring context. A time-sensitive signal should not wait in the same queue as a general information request.

Collect the minimum useful intake record

The purpose of the first interaction is not to collect the entire file. It is to help the next qualified person decide what should happen next. The firm should approve the minimum facts that change the route, the priority, the reviewer, or the type of conversation.

Useful starting fields may include

• Name, preferred contact method, and permission to respond through that channel.
• Whether the person is a prospective client, an existing client, or contacting the firm on someone else’s behalf.
• The practice area or general situation in the person’s own words.
• The jurisdiction or location needed for the firm’s initial routing process.
• The date or event the person believes may be time-sensitive, clearly labeled for human review.
• How the person found the firm, including the referring professional or client when relevant.

The first path should avoid requesting documents, identification numbers, account credentials, detailed medical information, or a full confidential narrative unless the firm has approved the channel and purpose. A shorter record is often safer and easier to review than an unbounded conversation.

Use AI for approved questions, not open-ended legal judgment

An AI intake agent can ask approved administrative questions, restate the next step, create a structured record, and route a conversation according to firm-defined rules. It should not interpret the law, predict an outcome, confirm representation, decide a conflict, calculate a deadline, or improvise beyond the approved boundary.

The ABA Formal Opinion 512 on generative AI tools discusses professional duties including competence, confidentiality, communication, supervision, candor, and reasonable fees. A law firm evaluating any AI-assisted intake path should review the opinion with the rules and guidance that apply to its jurisdiction and use case.

The practical design question is not whether the agent sounds human. It is whether the system stays inside the approved task, handles uncertainty honestly, protects the information it receives, and reaches a human escalation when the rules stop.

Design triage around signals and escalation

Triage should identify signals for review without claiming that software has determined the legal significance of those signals. The firm defines the categories, the questions, the escalation path, the response window, and the exceptions.

A bounded triage rule contains six parts

• Trigger: the word, answer, event, matter type, or missing information that changes the route.
• Customer language: what the system tells the person without making a legal conclusion or promise.
• Reviewer: the lawyer or approved team role responsible for the next decision.
• Response expectation: the timeframe the firm is prepared to honor, not an invented sense of immediacy.
• Fallback: what happens when the reviewer is unavailable, the information is incomplete, or the situation does not match a rule.
• Record: what the firm keeps so it can verify the handoff and improve the process.

A time-sensitive answer can create an alert and a human callback task. It should not tell the prospective client that a legal deadline exists, that the firm can protect it, or that the matter has been accepted.

Make conflicts and acceptance explicit human gates

A polished intake experience can accidentally imply that the firm has accepted the matter. The confirmation language should state what has happened and what has not happened. The inquiry was received. The firm will review it. A lawyer has not yet agreed to represent the person. The system has not cleared conflicts or confirmed any deadline.

Conflict review is not merely another automation step. The firm decides what information is required, who may search it, when the review occurs, and how the result is communicated. The intake system can prepare an administrative record and hold the request at the correct gate. A qualified lawyer or approved firm process controls the decision.

Follow up without turning silence into pressure

Follow-up should reduce uncertainty, not chase every contact through an aggressive sequence. The next message depends on what the firm is waiting for: permission to call, a scheduling choice, a missing non-sensitive fact, confirmation that the person found help, or a decision after a completed consultation.

The firm should approve the message, channel, frequency, stop conditions, and retention rules. If the person declines, hires another firm, asks not to be contacted, or reaches a professional-review boundary, the sequence should stop or move to a human. The communication record should remain understandable to the team.

The ABA Model Rule 7.1 page on communications concerning a lawyer’s services states that communications about a lawyer or legal services should not be false or misleading. Follow-up and website language should be reviewed with the advertising and solicitation rules that apply to the firm.

Connect the website, phone, booking, and review queue

A connected front door does not require every channel to look identical. It requires the channels to agree about services, fit, boundaries, next steps, and responsibility. The website can help a person choose a practice-area path. A phone agent can ask the same approved questions conversationally. A booking path can use the route and context already captured. The record can show the team what the prospective client was told.

The legal, financial, and advisory systems page shows how public trust, intake, response, and follow-up can work together for a professional firm. Firms comparing conversational workflows can explore AI intake systems without treating voice automation as the entire system.

The public layer matters too. Clear practice-area explanations, accurate attorney information, useful answers, consistent firm details, and genuine proof help prospective clients evaluate the firm. They also make the business easier for search and AI systems to understand. The Search and AI Readiness guide explains that relationship without promising rankings, citations, or recommendations.

Govern the system as an operating process

AI risk is not resolved at launch. Prompts change, services change, people leave, phone numbers are rerouted, and unusual inquiries expose gaps that a demonstration never reached. The firm needs a review process for the live system.

The NIST AI Risk Management Framework organizes voluntary AI risk management around govern, map, measure, and manage. A law firm can use those ideas as an operational lens while relying on its own legal, ethical, security, and professional requirements for the final controls.

A practical review cadence should examine

• What the system is allowed to do and the exact situations that require human escalation.
• Which inquiry types produced confusion, overcollection, or an incorrect route.
• Whether customer promises matched the response the firm actually delivered.
• Whether recordings, transcripts, summaries, and contact records are retained and accessed according to firm policy.
• Whether the approved language still matches current services, staffing, jurisdictions, and professional rules.
• Whether a failed integration, unavailable reviewer, or unusual request reached the fallback path.

Audit real inquiries before choosing a configuration

The first scope should come from evidence inside the firm. Review a representative set of recent phone calls, contact forms, referral emails, consultation requests, missed calls, and unresolved follow-ups. Protect personal information during the review and use the firm’s approved procedures.

1. Record why the person reached out and which channel they chose.
2. Identify the first response and whether it created a useful next step.
3. Note which information was missing, repeated, or collected too early.
4. Record when a professional decision or conflict review became necessary.
5. Identify the person or queue that accepted the handoff.
6. Compare the message given to the prospective client with the action the firm delivered.
7. Classify the outcome without assuming that every inquiry should become a client.

This review may reveal that the first useful improvement is a clearer practice-area page, a shorter form, one after-hours acknowledgement, a better referral route, a visible conflict-review queue, or an approved escalation path. A firm that wants to map the complete journey can book a Systems Review before choosing a configuration.