Jump to section
A prospective client fills out a form on your website at nine in the evening. In most firms, that message sits in an inbox until someone copies the details into a lead, chases the missing pieces, and, days later, opens a matter by hand. Every step is a chance to lose the file or the person. The work that follows is about closing that gap: turning a web form into a lead the moment it arrives, and turning that lead into a ready-to-work matter with one action, without taking the decisions away from a lawyer.
This is a practical walk through how the intake pipeline now fits together, where the automation earns its place, and where a human still signs off.
Every Form Submission Becomes a Lead
The first change is quiet but important: a submission is never just a stored response anymore. When someone completes one of your public forms, the system reads the answers, pulls out the name, email, and phone number, keeps the full submission on the record, copies across anything they uploaded, and creates a lead. Nothing a prospective client sends you falls into a folder no one checks.
That matters because the worst intake failures are not dramatic. They are the quiet ones: a form that submitted successfully, a confirmation the client trusted, and a message that never reached a person because it needed manual copying to become a real record. Making the lead automatic removes that failure mode entirely.
Note. Submissions were always saved. What changed is that they now surface as leads in your pipeline automatically, instead of waiting to be transcribed. The contact details are detected from the answers, and the whole submission stays attached so nothing is lost in translation.
From Lead to Matter in One Step
Once an inquiry is a lead, opening a file used to mean re-keying the same facts a third time. Now a lead carries a Start matter action. The action needs your own AI key: it reads the lead's details and any attachments, opens a new matter under the client, and shows the extracted facts on a review screen.
The word that carries the weight there is review. The tool proposes; it does not commit. Parties, court, dates, and the rest are shown as suggestions you confirm, correct, or discard before a single value is written to the file. The client record is created quietly, without firing off a portal welcome email, because starting a matter internally is not the same as inviting someone to a portal, and the system should not conflate the two.
The intake pipeline, end to end
- Submits your web formAt any hour, in their own words, with any documents attached.
- Becomes a leadName, email, and phone detected; the full submission and files kept on the lead.
- Start matter with AIThe lead is read, a matter opens under the client, and the facts are extracted.
- Review and confirmYou approve every field before anything is saved to the file.
If you have thought about the boundaries of AI at intake, the piece on using AI to triage intake without losing the human covers the same principle from the other side: the model does the clerical pre-reading, and a person owns the decision.
Court Forms That Fill Themselves, No AI Key Required
The third piece is about the forms you file, not the ones clients fill. A court form is only useful to generate automatically if the system knows which matter detail belongs in which box on the page. That mapping is the unglamorous work behind one-click form filling.
You can now draft those maps two ways. With an AI key, a model reads each form and proposes the mapping. Without one, a built-in matcher does the obvious work for free: it compares each field's label to your data and confidently maps party names, addresses, dates of birth, the court file number, and the registry, while leaving anything ambiguous alone. Either way, you approve each draft before it is used, so a wrong guess never reaches a filed document.
Watch out. Automatic mapping is a head start, not a final answer. The no-key matcher is deliberately cautious: it would rather leave a field unmapped than map it wrong. Review each draft, fill the gaps it skipped, and treat the approval step as the real control.
Why the Pipeline Keeps a Human at Every Gate
It would be easy to build this so a form submission silently spawned a matter, filled the forms, and queued them to file. It would also be reckless. Intake carries professional judgment: whether the firm can help, whether there is a conflict, whether an urgent deadline is hiding in a paragraph of plain text. Those are lawyer decisions, and the design leaves them exactly there.
So the automation is aimed squarely at the clerical layer: capturing the inquiry, carrying the details forward without re-typing, and proposing a structured file for a person to confirm. The lawyer still opens the review screen, still approves the mapped fields, still decides the matter is worth taking. The efficiency comes from removing the copying, not the thinking.
Getting Started
The pieces work independently, so you can adopt them in any order. Publish a public form and watch the leads arrive. Add your AI key when you want to use the Start matter action; until a key is added, the action is unavailable and you open matters from Matter Intake instead. Draft your court-form maps now with the no-key matcher, and revisit them with AI later. Each step stands on its own, and each keeps you in the chair for the decisions that matter.
For the wider picture of running a modern practice, the legal tech and AI cluster covers safe automation across the firm. And if you want intake, matters, and court forms in one system built for small Canadian firms, A1 CMS is worth a look.
