Legal intake
LiveA front door for legal requests — captured, triaged by AI, routed to a person, and promoted into a matter.
- ✓AI triage on arrival — type, urgency, and whether it is legal work
- ✓Triage recommends, a human applies
- ✓Rejection recorded with a rationale rather than a deletion
- ✓Routing to a named person
What it is.
Requests come in from the business through a single intake rather than by email and corridor conversation. Each one is triaged on arrival: what kind of work it is, how urgent, whether it is legal work at all. The triage recommends; a person applies. A request triaged as not-legal is recorded as rejected with a visible rationale rather than silently dropped, so the requester can see what happened and a human can reverse it.
The step that makes this more than a ticket queue is promotion: a request becomes a matter, and the matter is where the contracts, research, redlines and obligations for that piece of work then live. Intake is the top of the lifecycle, not a queue beside it.
Three steps.
End to end.
Recorded with its channel — where it came in from — and triaged on arrival.
Assign to a person. Re-run triage if the request changes.
Promote it into a matter, or close it with a reason. Either way there is a record.
What you get.
- ✓AI triage on arrival — type, urgency, and whether it is legal work
- ✓Triage recommends, a human applies
- ✓Rejection recorded with a rationale rather than a deletion
- ✓Routing to a named person
- ✓Promotion into a matter, which becomes the container for the work
- ✓A queue you can filter
Quick answers.
No. It records a recommendation and a rationale; a person applies it, and can reverse it. That separation is deliberate.
Yes, through an intake form published on a public link. Every submission becomes an intake request marked external; requests from colleagues are marked internal. See Intake forms.
Triage lists what is missing and asks for it one question at a time; each answer re-runs the triage.
More in Team & Enterprise.
Not built. The organisation is the isolation boundary; matters are how work is grouped inside it.
Four seeded roles with per-capability view / add / edit / delete permissions, plus custom roles you define.
Shared editing sessions on a document, and a propose-review-merge flow for changes to it.
Group contracts, court research, compliance items, meetings and tasks by matter — with a timeline of everything that happened on it.