Koltra for law firms · Market exploration
Koltra is exploring legal intake software that carries the administrative path from first inquiry through screening, information collection, consultation scheduling, and professional handoff. The operating model is designed so the firm receives one structured, inspectable intake while conflicts decisions, legal assessment, advice, and client acceptance remain with authorized professionals.
Koltra's shared platform is in development with design partners. Legal intake is a market exploration, not an announced Koltra product or an available off-the-shelf service.
The delegable part of intake is structured service work. The firm defines what may be collected, which systems may be touched, when the workflow must stop, and which recorded state counts as a completed administrative outcome.
The nine p.m. inquiry should get a real first response rather than a form receipt, with the source, the response time, and the next owner already recorded.
The matter should arrive already checked against your practice areas, jurisdictions, and timing, with no view offered on merits and nothing implied about representation.
Party names and related entities should be collected in one consistent structure so your conflicts process can run. The software prepares the check; it does not clear it.
The attorney's first look should be review rather than reconstruction: approved fields gathered, documents requested, the client's own words preserved, and gaps left visible.
The consultation should already be booked, confirmed, and reminded, with declines and referrals going out only after the firm owns that decision.
Conflict clearance, matter evaluation, legal advice, urgency and risk decisions, client acceptance, and any step that could create a professional duty require an authorized person. The workflow stops at those points and transfers the collected state, provenance, and reason for escalation together. Administrative completion is never represented as legal acceptance or representation.
Both models answer the inquiry. They differ in what reaches the firm afterwards, which is what decides whether an attorney's first look is review or reconstruction.
| The inquiry | A message-taking service leaves | An operating layer should leave |
|---|---|---|
| Prospective client, in practice area | A name, a number, and a rough reason. | The firm's screening fields collected in a consistent structure, with the caller's own words preserved. |
| Conflicts exposure | Nothing collected. Party names surface later, if at all. | Party names and related entities captured so the firm's authorized conflicts process can run. |
| Asks whether they have a case | A message, or worse, an answer. | A stop with no opinion offered, routed to an authorized person with the record attached. |
| Inquiry at 9 p.m. | A callback the firm makes tomorrow, if the prospect is still waiting. | The same declared intake, with a consultation booked or an owned next step recorded. |
A useful intake system makes each administrative stage, professional boundary, system action, and terminal state explicit before the inquiry arrives.
An intake is not complete because a form was submitted or a consultation request entered a queue. The record should show what arrived, what was collected, which policy and permission checks ran, which system actions succeeded, who accepted any professional handoff, and what administrative outcome was reached.
Useful terminal states distinguish a booked consultation, a request for more information, an accepted professional review, a declined-and-referred inquiry, an owned follow-up, and an unresolved failure. That vocabulary prevents a routed matter from being reported as accepted representation.
Start with the operating process, the available service models, and the role boundary. These guides make the decision criteria inspectable without assuming Koltra is the answer.
Seven owned stages, exception branches, exit states, and downloadable workshop assets.
Read the guide →The coverage models compared by depth, operating handoff, and cost shape.
Read the guide →The work of screening, conflicts preparation, scheduling, and attorney handoff.
Read the guide →No. An answering service primarily covers the conversation and may take a message. Intake software structures the workflow and record: screening fields, conflicts information, documents, scheduling, ownership, and disposition. A useful operating design can connect the two, but a completed call is not automatically a completed intake.
Software can collect and normalize party names, identify missing information, and submit a check through the firm's approved process. Conflict clearance and the legal consequences of a possible match stay with authorized firm professionals. The record should distinguish preparation, search results, review, and the final decision.
The operating model is designed as administrative intake, not client acceptance. It does not provide advice, clear conflicts, accept a matter, or establish representation. Each firm remains responsible for its notices, consent language, jurisdiction-specific duties, professional review, and engagement process.
That depends on the selected workflow. Common system roles include intake or CRM, scheduling, document collection, conflicts, communications, and matter management. The firm should define the exact records, fields, retention, permissions, and allowed actions before any connection is treated as deployable.
Run the firm's real exception cases, not only a happy-path demo. Inspect response coverage, required-field completeness, provenance, duplicate control, professional-boundary behavior, accepted handoff, system-write evidence, failure visibility, and whether every inquiry ends in a declared administrative state.
A firm can bring one intake path and map its allowed information, screening criteria, professional decisions, systems of record, exception branches, notices, and terminal states. That operating map is useful whether the firm uses people, an intake service, existing software, or a future Koltra product.
Koltra's shared platform is in development with design partners. Legal intake is a market exploration, not an announced Koltra product or an available off-the-shelf service.