It is Friday evening and a new inquiry is sitting in your firm’s inbox. Somebody captured it. Nobody has touched it since.
That gap is what law firm client intake automation is actually about, and it is the part almost nobody writes about. Search the term and page one is product pages: intake forms, pipelines, dashboards, a free trial. Most of it is real software. What none of it answers is the question a solo practitioner or a small firm is actually asking, which is who runs the thing once it is switched on.
Legal client intake automation gets sold as a form. It is really a chain of seven steps, and six of them happen after the form is submitted. Here is the whole chain, in order, with what your firm does instead at each step.
Law firm client intake automation covers everything between “we have a name and a phone number” and “we have an open matter, a signed engagement letter, and a file that will survive being looked at.”
The seven steps:
Most page-one answers stop at step one. They sell a better version of the form. The form was never the hard part. The hard part is that steps two through seven each need a person who is responsible for them on a Friday evening, and in a firm this size that person is an attorney.
Capture is solved, and a lot of vendors solve it, so this section is short on purpose. Inquiries reach a small firm through a web form, a referral source, or the phone, and if you want the phone half handled there is an AI receptionist that answers for the firm, which is a separate subject with its own post.
Everything below assumes the lead is already in the building. That is where intake breaks: capture is the step that gets bought, and the six after it get improvised.
Nothing legitimate happens to a new matter before the conflict check clears. Not the call back, not the engagement letter, not the file.
In most small firms the check is a search in the practice management system plus somebody’s memory. It works right up until it does not: an opposing party under a married name, a corporate entity a couple of shells away from a client you took on years ago.
Conflict check automation makes the check happen every time, at the same point, with the same inputs. The system assembles the parties named in the inquiry, runs them against the firm’s existing matter and party list, records what was searched and when, and puts the result in front of the attorney who has to decide.
That last clause is not softening language. The clearance decision belongs to a supervising attorney, and the workflow is built so the matter cannot move without one. Automation makes the check triggered, complete, and logged. It never makes the judgment.
Automated: pulling every party, entity, and related name out of the inquiry, running them against the existing matter list, flagging near matches, timestamping the search, routing the result to the reviewing attorney, and holding the matter shut until that attorney acts.
Not automated: deciding whether a hit is a conflict, whether it is waivable, and whether the firm takes the matter. That is legal judgment and it stays with the lawyer.
Once the attorney clears the conflict, the matter has to exist somewhere real. For most small firms that is Clio, and Clio should stay exactly where it is. It is the system of record and we wire into it.
The failure here is boring and expensive. The same client details get retyped into the intake form, then the matter, then the letter, and by the last one they disagree. A law firm intake process that has been automated properly writes the matter once, from the record already captured, with the fields your firm actually uses: matter type, responsible attorney, referral source, and the fee arrangement the firm has already set for that type of work.
This is where “operated, not configured” stops being a slogan. Small law firm intake software is the part you can buy. The mapping between your intake fields and your matter fields, the routing rules for who gets which matter type, and the training that gets the system past 90% accuracy on your firm’s own vocabulary: that is work, it recurs, and somebody has to own it. In our model that somebody is us, and escalation to a human is part of the design, not a setting you remember to switch on.
The engagement letter is generated from the matter record, sent to the client, and returned by e-signature. That part is mechanical.
The part that is not mechanical is the letter that goes out and never comes back. An unsigned engagement letter is not an event. It is a state, and states do not send notifications. Nobody gets a nudge that says the Ramirez letter is still unsigned.
So the client intake workflow a law firm runs has to treat “sent, not signed” as a state a system watches continuously and a person owns at a threshold. Reminders go out on the schedule the firm sets, and past a defined point the file surfaces to a named human, who calls.
Two hard limits inside this step. The system sends the fee arrangement the attorney already approved for that matter type. It does not price the work and it does not explain the terms. And nothing in the letter workflow may suggest what the representation will produce, because Model Rule 7.1 bars false or misleading communication about a firm’s services, and an automated system is an efficient way to make the same misleading statement several hundred times.
Every matter type has a list. A family law firm wants the financials. A personal injury firm wants the report, the records, the insurance correspondence. The client gets a client portal link and, often, nothing happens.
Automated client intake for law firms handles the mechanical layer well: a request list tied to the matter type, a portal to upload into, reminders that go out on their own, and a running record of what has arrived and what has not.
Then it hits the same wall as step four. A tool sends the reminder. It does not notice that several reminders went out, the client opened none of them, the reason is a wrong email address, and the actual fix is a paralegal picking up the phone.
That is the difference between an unstaffed tool and a workflow somebody runs. The reminder ladder is automated. The escalation at the end of it is a named human at a defined threshold, so the file stops sitting in the loop because nobody is watching it.
Files rarely fail loudly. They go quiet. The conflict check is sitting with an attorney who was in a deposition. The documents half arrived. Every individual step looks fine and the matter has not moved since the week before last.
Stalled-matter detection is what that state is for. The system looks across all six previous steps at once and asks a short list of dull questions. Has the conflict check been cleared? Has the letter been signed? Has anyone spoken to this client since the inquiry came in?
When an answer is no past the threshold the firm set, the file goes to a person, by name, with the reason attached. That is what escalation built into the workflow means in practice, and it is why we train the system on the firm’s own matter types and language until it is reliably above 90% accuracy at recognizing them. An alert that is wrong often enough to distrust gets ignored, and an ignored alert is the same as no alert.
Everything above emits a record, or it should. Who was searched in the conflict check and when. Which attorney cleared it. What the client was sent and when the letter came back signed. Which documents arrived and which are still outstanding. Who escalated the file and why.
This is the least exciting part of law firm client intake automation and the part that matters most the day somebody asks. A malpractice carrier, a bar inquiry, a prospect who says nobody ever got back to them: all of them are asking the same question, which is what happened and when.
Two things we hold to here. Intake information can be privileged from first contact, so it is treated as client information from the moment it arrives, not from the moment the engagement letter is signed. And the ABA’s Formal Opinion 512 sets the frame for using generative AI in practice: competence, supervision, confidentiality, and care around fees. A workflow that logs every step, keeps attorney sign-off in the path, and holds intake data as confidential is how a firm meets that frame with a record instead of a promise.
A trail is only as good as the systems holding it, which is a different job from this one and belongs to who keeps the systems those records live in running.
Every product on page one for law firm client intake automation will sell you steps one through seven as features. They are real features. The question a vendor cannot answer, because answering it contradicts how they sell, is who runs law firm intake software once your firm owns it. Who maps your matter types. Who watches the unsigned letters. Who calls the client who stopped responding. Who produces the trail on request.
That is a job, and it is the job we do. Round-the-clock intake starts with Growth at $699 a month. The full workflow above, conflict checks, matter creation, engagement letters, document chasing, and the audit trail over all of it, sits in Business Operations from $999 a month plus $50 per employee. Firms with heavier compliance needs or something genuinely custom step up to Technology Department from $2,500 a month. Personal injury firms usually start higher, because their intake carries the most documents and the tightest deadlines.
Setup is $0, it is month to month with no lock-in, migration is free, and you own your website and your data, which matters more in this profession than in most. For the wider picture, here are the industries we run day-to-day operations for. And if your firm needs something built rather than run, custom software development is a separate track, not part of the subscription.
How does a small law firm automate its client intake process?
By automating the seven steps between a captured inquiry and an open matter, not just the intake form. Law firm client intake automation covers capture, conflict check, matter open, engagement letter, document collection, follow-up, and the audit trail across all of them. The software handles the mechanics. Somebody still has to run it, and that is the half most firms are missing.
Can a law firm client intake automation system run a conflict check before a matter is opened?
Yes. It can assemble the parties named in the inquiry, search them against the firm’s existing matters, flag near matches, and timestamp the result before any matter is opened. The clearance decision stays with a supervising attorney. Conflict check automation makes the check consistent and logged. It does not decide whether the firm can take the work.
Does an automated client intake system give legal advice to prospective clients?
No. It handles intake and scheduling only. It routes an inquiry for fit to the firm, collects information, and books time with an attorney. It does not evaluate a claim, estimate what a matter is worth, quote a fee, or answer a legal question. Intake information can be privileged from first contact and is treated as confidential from the moment it arrives.
Does law firm client intake automation replace practice management software like Clio?
No. It runs on top of it. Clio stays the system of record, and the intake workflow writes the matter into it, keeps the fields consistent, and moves the file along around it. The point is integration with the system your firm already uses, not a second place for client information to live.
What does it cost to have a law firm’s client intake workflow run for it?
Round-the-clock intake starts with Growth at $699 a month. The full intake workflow, including conflict checks, matter creation, engagement letters, document collection, and the audit trail, sits in Business Operations from $999 a month plus $50 per employee. Firms with heavier compliance or custom needs step up to Technology Department from $2,500 a month. Setup is $0, month to month, no lock-in.
If you want to know where your firm’s intake actually stands, book a Free Technology Audit at cal.com/mirgen-motomtech/quick-intro. We walk your current process step by step and tell you which parts are genuinely handled and which parts are running on somebody remembering, and if writing is easier than talking you can send us the details of how your intake runs now instead.
