Help people who call a legal help hotline get screened, triaged, and routed to the right help through a voice-based AI assistant that works alongside human staff.
Why it matters for peopleFaster screening and routing gets callers to the right help sooner, before a deadline passes.
This page is the shared target for this situation. Any court, legal aid office, or builder working on it in their own region can take the vision, the blueprints, and the standards here instead of starting over, and set the parts that are local to them. The point is that the same work is not designed from scratch in every county.
Does this match how it goes where you are? Leave a note on this workflow.
Not everyone interacts with legal help through a screen. Older adults, people with limited English proficiency, people in crisis, and people without reliable internet often reach legal help by telephone rather than through a website. Legal help hotlines take more calls than the staff answering them can pick up, so callers reach voicemail or wait on hold.
Voice AI intake is a system that answers a legal help hotline call, gathers enough information to understand the caller's situation, classifies the legal issue, checks basic eligibility, and routes the caller to the right service. The AI handles the initial screening. Human staff handle the advice, representation, and complex judgment.
This is not a replacement for human intake workers. It extends their reach. A voice AI system can answer every call on the first ring, collect the essential facts while the caller is engaged, and hand off a structured summary to the human team.
Who this serves: Legal help hotline callers, court self-help phone lines, pro bono intake programs, and any organization that receives more calls than its staff can answer.
The stages below are the reading order for a team working this through from the start. If you are further along, go straight to the assets that match your role.
The shared assets are arranged by when a team needs them, from deciding whether to do this at all through running a system in the field. Each stage says what it is for and how much of it exists today.
Stage 1
Before a team scopes anything, it needs to know what the workflow is, who it serves, what callers get today without it, and whether these systems help. Reviewers told us they could not judge a conformance number because there was nothing to compare it against.
Stage 2
A team has to settle what the service will actually do before it reads a specification or signs anything. These are the decisions that determine which capabilities in stage 3 apply.
Case studies from teams that have built or are building voice AI intake systems. What they chose, why they chose it, what surprised them, and what they would do differently. Designed so the next team building this does not start from scratch.
Join the cohort to contribute →Stage 3
Read these once the team knows what service it is running. The step-by-step agenda says what the system must do in the order a call happens, the functional agenda says the same thing with every capability numbered for a builder, and the reference architecture shows one proven way to build it.
The first round of what a voice intake system has to do, written as the shape of a call from the greeting through the handoff, with the question the Commons team wants answered about each part. Start here if you run a hotline and want to say what it needs.
Read the step-by-step agenda →A checklist of every capability a good voice AI intake system has, organized by what happens during a call: greeting, consent, information gathering, classification, routing, safety escalation, and handoff. The checklist format is what lets a lawyer and a vendor talk about the same thing. Use it to scope a build, write an RFP, or evaluate a vendor proposal, and set your scope level to see which capabilities apply to you.
Read the agenda →A technical blueprint showing how the pieces of a voice intake system fit together: how a phone call becomes structured data a human can act on. Describes each component (speech-to-text, conversation orchestrator, language model, text-to-speech, case management integration) and the design decisions that matter most.
Join the cohort to contribute →Stage 4
How a team checks whether the system it has is good enough to put in front of callers, and how it keeps checking once the system is running.
A bank of realistic caller scenarios that you run through your system to see how it performs. Each scenario includes the caller's situation, the correct classification, what good intake looks like, and what bad intake does wrong. Includes straightforward cases, ambiguous situations, crisis callers, and edge cases. Use it during development or for independent evaluation.
View the test suite (Google Sheet) →The gates a system has to pass before it should be trusted with real callers: whether it performs accurately, whether callers can actually use it, whether it handles safety situations correctly, whether staff can work alongside it, and whether the organization can maintain it. Each gate has pass and fail criteria, and each one says what a failure means for a caller. Reading a score still needs the status quo baseline in stage one, which does not exist yet.
Read the standards →A hands-on course that walks a team through the decisions involved in building, deploying, and maintaining a voice AI intake system. Each module is built around a real decision the team has to make, and ends with that decision written down. We are looking for teams willing to go through a draft version and give us feedback.
The Voice AI Intake cohort is developing the shared assets on this page. The cohort steers what gets built. Members shape the agenda, review standards, and contribute implementation experience.