IntakeINT

Intake as a discrete category.

Personal-injury intake deserves a category, not a form. JustineAI treats intake as a discrete platform category — with its own sub-agents, its own streaming behavior, and its own structured output shape. Today the intake sub-agent runs a public, empathetic AI web chat that traverses the intake conversation and produces a structured case file the supervisor can act on the moment it ends. Phone / telephony intake is on the roadmap, not live today.

Code is truth

What the platform actually does.

  1. 01

    The AI client intake chat is a live, public, empathetic web conversation — one question at a time — distinct from the attorney-facing intake copilot.

  2. 02

    The intake conversation has scripted-but-adaptive structure — the agent traverses required questions in the order the conversation permits.

  3. 03

    Output is a structured case file (party identities, mechanism of injury, current medical posture, treatment trajectory, insurance posture) ready for supervisor handoff.

  4. 04

    A firm-branded public intake portal (/intake/{firm}) captures submissions to the firm’s inbox, structured and conflict-checkable.

  5. 05

    Phone / telephony intake — an inbound conversational voice line — is on the roadmap and is never presented as shipped today.