Helpline Callback Desk

Staff workflow prototype

Independent prototype of Legal Aid Society of Middle Tennessee's helpline intake, by The AI Pipe
Invented calls, live agent

Every request starts as speech, and the thing that matters is rarely at the start of the call. C-4108 says it at two minutes forty one.

The public Get Help page offers one route, a toll-free number, and a sentence promising a callback within 24 to 48 hours. No intake form was found on it. This desk reads a call transcript segment by segment, routes it by postal code to the county and the office published for it, assembles a structured new matter in LegalServer shape with its empty fields named, and orders today callbacks against that published promise, computed in code. On C-4108 the date the caller reads out in segment eleven of twelve falls inside the window her own call produces, and an ordering by arrival time puts her ninth of ten. It determines no eligibility, answers no legal question, runs no conflicts check and contacts nobody.

Measured here, end to end on one call: run one and watch. That covers the documentary work before an intake specialist picks the call up. It makes no eligibility determination, accepts and declines nothing, and states no deadline.

1. Observed public material

The helpline number, the callback promise, the two sentences about what a call is not, the eight problem areas, the eight offices with their counties and their published hours, and the paragraphs of the organization own public telephony solicitation, read on 2026-09-16. Each row carries its status.

2. Simulation

Ten invented calls with their transcripts, invented callers, relatives and attachments, and the invented internal policy of an invented program. Every clause of it is labelled simulation policy, not this organization's policy.

3. Public rules, verbatim

45 CFR 1611, 1620 and 1626 and the 2026 income appendix, quoted from eCFR with the source and the date. Real rules, never paraphrased, never attributed to the organization.

What this shows

The problem: A helpline takes calls all day and promises to return them within 24 to 48 hours. Somebody has to listen to each one, work out where the caller lives, what the matter is, who the other party is, and which call cannot wait. A queue ordered by arrival time cannot know that the twelfth thing somebody said was the date of a hearing.
The result: The run below is real and is recorded: the transcript read to the end, the postal routing run in code, the published promise turned into two timestamps, the checks run, the public rule quoted verbatim, a structured new matter with its empty fields named, and a callback queue whose order the model cannot touch.
Where it sits: It prepares a matter draft and a callback queue, and hands over a sheet that can be copied out. Standalone demonstration. It connects to nothing, writes into nothing, and is not a way to ask for legal help.
What is simulated, and what is not covered: The program, the ten calls, the callers and the internal policy are invented, and that policy is one invented program's own, not anybody's law. The counties, the offices, the published hours and the postal codes are real and are marked row by row. Four things were not published and are therefore not guessed at: the written statement of case priorities, the case service report problem codes, the queue configuration, and the income and asset ceilings the organization adopts. There is no audio here: a transcript stands in for what a transcribing voicemail produces. The English text beside a segment is a working machine rendering, never an interpretation. No connection to any case management system, and no eligibility determination, no acceptance or refusal of a case, no legal advice, no conflicts check, no problem code and no deadline. The tool layer refuses all of those, and refuses a figure that is not written in a section it was cited from.
What a pilot would need from your side: Your blank screening questions, the helpline policy in whatever form it exists today, whatever is written down about how fast a call is promised back, a short conversation with whoever runs the line and one person who can say whether an answer is right, and counts rather than calls: how many arrive in each language, how many are returned inside the promise. Callers and their calls stay invented until your legal and security leads have agreed, in writing, which fields a pilot may see, who holds them, where they sit, how long they are kept and how they are deleted. No call transcript and no caller record are needed to start, and removing names is not anonymisation.
Who built it: Frederic de Lavenne de Choulot, The AI Pipe. Built as a demonstration, not sold as a legal, eligibility or compliance product.

Simulated helpline activity

The library

Fictional desk. Do not paste real caller, client or case records.

Enter to send, shift and enter for a new line. Live tool use over ten invented calls, the published offices and counties, and the public rules.