Step-by-step agenda

What a good voice intake and triage system does

Somebody calls a legal help line and an AI system answers. Here is what a good one does, in the order a call happens, with a question for you at each step.

Answer the questions on the parts you know from your own practice. The Commons team reads every answer, fixes what the list gets wrong, and takes the harder questions to the cohort working on this area.

The full functional agenda is here, with every capability numbered, levelled, and written for a builder.

Part 1

Answering the call

Somebody dials the number on a flyer, or the hotline forwards the call after hours. Before any of the legal work, the call has to be answered, stay up, and survive the things that go wrong on a phone line.

What a good system does

What happens today when a call to your hotline drops?

Answer this

Part 2

Telling the caller what this is

The caller has to know they are talking to a machine, that it is not their lawyer, and what happens to what they say. This part comes before a single question about their problem.

What a good system does

What does your organization have to say at the start of a call?

Answer this

Part 3

Taking the caller’s details

The details that make the rest of the call useful are the ones most likely to go wrong over the phone, including a name nobody spells the same way twice.

What a good system does

What it must never do

What goes wrong when your staff take these details by phone?

Answer this

Part 4

Finding the legal problem

A caller often does not open with the legal issue. They open with what happened, and the system has to find the issue inside the story without cutting the story off.

What a good system does

How do callers describe this problem in their own words?

Answer this

Part 5

Screening for eligibility

Screening decides whether the caller gets help here or a referral somewhere else, so it has to be right, and it has to be something staff can change when the income limits change.

What a good system does

Who sets the eligibility rules in your organization?

Answer this

Part 6

Safety, crisis, and sensitive disclosures

A caller describes being hurt, or goes quiet, or starts crying. This is the part of the call where a system that handles it badly does real harm, and missing a disclosure is the worst failure in the whole workflow.

What a good system does

What it must never do

What does your hotline do today when a caller discloses abuse or is in crisis?

Answer this

Part 7

Checking for conflicts

The organization may already represent the person on the other side. The check has to happen before a record exists, and the caller must learn nothing from it.

What a good system does

What it must never do

How does your conflict check work today?

Answer this

Part 8

Routing and referral

The end of the call is a decision about where this person goes, and a referral that goes nowhere is worse than none.

What a good system does

Which of your referrals have gone stale?

Answer this

Part 9

The intake record staff receive

The call is only useful if the person who picks the case up next does not have to ring the caller back for the basics.

What a good system does

What does your staff need in an intake record before they will trust it?

Answer this

Part 10

Staying out of legal advice

A caller will ask what they should do. The system has to be useful without answering that question, and it has to hold the line when the caller pushes.

What a good system does

What it must never do

What phrasing have you found that stays on the right side of the line in your state?

Answer this

Part 11

Serving callers in other languages

Language is where intake systems quietly fail, because the call completes and the record looks fine while the caller understood half of it.

What a good system does

How does your line handle the languages your callers need?

Answer this

What happens to what you write

Every note comes to the Commons team. We read it against the detailed agenda, correct what is wrong, and publish a new version saying what changed. The questions that need practitioners to argue them out go to the cohort for that area.

A note about one line is as useful as a note that adds a whole step. If what you know is how your hotline handles a caller in crisis, write about that.

The two agendas for this workflow

You are reading this one

Step-by-step agenda

This is the first round, and it collects what the people who do this work say a tool has to do, in the order the work happens and in plain words. Read it to argue with it, to correct it, and to say what your jurisdiction needs.

The detailed version

Functional agenda

This one is the technical specification. It numbers every capability, states the standard each one has to meet, and sorts them by level and by the scope of the system being built. A builder builds against it, an evaluator tests against it, and it gets rewritten as prototypes exist and the details are settled.

Read the functional agenda →