A prospective client fills out the form on your website at 9:40 on a Tuesday night. Right now, that submission lands in someone's inbox, gets forwarded to a paralegal Wednesday morning, gets typed into the case management system Wednesday afternoon, and gets a callback Thursday if nobody is in court.
Intake automation is the set of rules that turns that form submission into a contact, a matter, a conflict check, and a follow-up without anyone retyping anything. It is the most common starting point in law office automation because the steps are the same every time and the delay costs real clients.
The intake pipeline as a chain of triggers
Think of intake as a sequence of events, each of which can fire an action. Form submitted. Contact created. Conflict check cleared. Consultation scheduled. Consultation completed. Engagement letter sent. Engagement letter signed. Matter opened. Each transition is a trigger, and each trigger can do work.
The tools that run this chain fall into two groups. Legal intake CRMs (Clio Grow, Lawmatics, Filevine's Lead Docket, and similar products) have the stages built in and let you attach actions to stage changes. General automation platforms (Zapier, Make) connect a form tool to a case management system when the CRM does not cover a step, or when the firm is not using a dedicated CRM at all.
The design question is which transitions matter for your practice, and what should happen at each one.
Form submitted: what should happen in the first five minutes
The form itself should collect enough to run a conflict check and route the lead: full name, email, phone, the other party's name, the practice area, and a short description.
On submission, the automation creates a contact in the intake tool (or directly in Clio Manage, Filevine, or PracticePanther if you are skipping a CRM), tags the lead with its source and practice area, and creates a task for whoever handles intake with a due time measured in hours. It also sends the prospect an immediate acknowledgment, ideally by text and email, that says a human will call and when. The Clio Grow intake guide covers how that platform handles the first step.
Routing rules go here too. A personal injury lead and an estate planning lead should reach different people, and a lead that mentions a court date within the week should jump the queue. Most intake tools can branch on a form field; Zapier and Make can do it with a filter or router step.
Conflict check as a gated step
Nothing should move past the first stage until a conflict check is recorded. The automation cannot run the check for you, but it can create the task, attach the names from the form, and block the engagement letter step until someone marks the check complete.
In practice this means the "send engagement letter" action is triggered by a stage change (lead moved to "Cleared") rather than by the form submission. If your intake tool cannot gate on a stage, use a required custom field ("Conflict check date") and have the automation check that it is filled before proceeding. A related pattern is the intake summary, where an AI tool reads the form narrative and produces a short brief for the attorney before the consultation, which we cover in AI client intake summaries.
From qualified lead to signed client
Once the consultation happens and the attorney says yes, the automation should do four things in order. Generate the engagement letter from a template, populated with the contact's name, matter description, fee terms, and responsible attorney. Send it for e-signature through DocuSign, the CRM's built-in signing, or whichever service the firm uses. Watch for the signed event. And, on signature, create the matter in the case management system, with the standard folder structure, and move the lead to "Client."
The engagement letter step has enough detail of its own that we wrote a separate page on engagement letter automation. The main point is that the letter is generated, not drafted, and that signature is the trigger for opening the matter, not a task someone remembers later.
After the matter exists, the same chain continues into onboarding: a welcome email with what to expect, a request for documents the client needs to provide, and a scheduled check-in. That hand-off from intake to ongoing contact is where client communication automation picks up.
Which tool sits at the center
If you are a Clio firm, Clio Grow is the natural intake layer because it creates matters in Clio Manage directly when a lead converts. Filevine firms usually use Lead Docket for the same reason. Lawmatics works across several case management systems and is a common choice when the firm wants more marketing automation in the same tool.
Zapier and Make are the glue when the form builder, the CRM, and the case management system are three different products, or when a firm wants an action the CRM does not offer natively.
Whatever the center, keep one system as the source of truth for the lead's stage. When two tools both think they own the pipeline, leads fall between them.
Questions we get
Can we automate intake without a CRM, just with our case management system?
Partly. A form connected through Zapier can create a contact and a task in Clio Manage or Filevine, and the firm can track the lead as a matter in a "prospective" status. What you lose is the pipeline view, the drip follow-up, and the stage-based triggers. For a firm with a modest lead volume that is often fine.
Does automated follow-up feel impersonal to prospects?
Not if the messages are written by a person and sent under a real name. The automation controls timing, not tone. A text within two minutes that says "Thanks, this is Maria at the firm, I will call you before noon tomorrow" beats a warm email three days later.
How do we handle leads that come by phone rather than the website?
Give reception the same form the website uses, either as an internal version of the intake form or as a "create lead" button in the CRM. The point is that every lead enters the same pipeline at the same first stage, so the same automations run regardless of how the person reached you.
If you want to map out what your intake chain should look like, tell us what you are working with.