Is AI intake safe for a law firm?
The question is not whether the model is smart. It is where the boundary sits.
Answered in short
5 things that decide this
- 01AI intake is safe for a law firm when it stays routing work: confirm the enquiry, collect facts, screen conflicts, qualify the matter and book the consultation.
- 02It becomes unsafe the moment it evaluates a claim, predicts an outcome or suggests a strategy, because that is legal advice from software the firm answers for.
- 03Confidentiality is a design question. Contracts and settings stop the model provider training on intake data, with encryption and logged access. It is solvable, and it must be solved before launch.
- 04A disclosure that the assistant is not a lawyer, plus a human review step before engagement letters or deadlines, closes the remaining gap.
- 05Adoption is low enough to be an advantage: Clio's research puts broad AI adoption at 8% of solo firms and 4% of small firms, so a firm that does this correctly is early, not late.
Three ways intake automation actually goes wrong
The first failure is the accidental opinion. A prospect asks whether they have a case, and a helpful model answers. Now the firm has arguably given advice to a non-client, formed expectations, and possibly started a clock. The fix is a hard boundary in the system's design, not a polite instruction in a prompt.
The second is data leaving the building. Intake conversations contain exactly the facts privilege exists to protect. Whether sending them to a model waives anything is its own question. The safe posture is contractual: zero data retention, no training on inputs, and a vendor chain the firm has actually read.
The third is the missed conflict. An automated intake that books a consultation before names are screened can put a lawyer in a room with the other side of an existing matter. Conflict screening belongs before scheduling in the flow, every time.
- AcknowledgeInstant, disclosed as automated.
- Collect factsStructured, no evaluation.
- Screen conflictsNames checked before booking.
- Qualify and routeMatter type, urgency, jurisdiction.
- BookA consultation, not a conclusion.
- LawyerAdvice starts here, only here.
Everything left of the lawyer is logistics. Logistics is what software is for.
Related questions
01Do we have to tell prospects they are talking to AI?+
Yes, disclose it plainly. Some jurisdictions are moving that way by rule, and the disclosure protects the firm anyway. A prospect who knows the assistant is automated does not mistake its questions for a lawyer's judgement. Clear labelling costs nothing and removes a whole argument.
02Can AI intake handle privileged information?+
Treat intake facts with the same care as privileged material, even before an engagement exists. The design answers it: providers under zero-retention terms, encryption in transit and at rest, and access limited to the matter team. The confidentiality question has an engineering answer, and it should be written down.
03What happens when the system meets an emergency?+
Certain phrases must escalate to a human immediately: arrest, imminent hearing, protective order, deadlines expiring. The escalation list is jurisdiction and practice specific, and it is part of the design review, not an afterthought. A routing system is judged by what it refuses to handle alone.
