A voice agent that is actually built for law: what jurisdiction-aware has to mean

A woman rings a legal-aid clinic’s intake line at 23:40 on a Thursday. She speaks Portuguese. She has a letter from her landlord, a date on it, and no idea whether the date matters. The clinic is closed. The agent that answers has to do three things before anyone at the clinic sees the brief in the morning: understand her, work out which rules apply to her, and not tell her anything that is wrong.

The first of those is a speech problem. The other two are law. Over the fourteen months since AI Interview became generally available, we have come to think that “jurisdiction-aware” is the phrase people use for the part they have not built yet. Here is what we think it has to mean.

Jurisdiction is not a language setting

A caller’s language tells you almost nothing about which law governs her problem. Portuguese is spoken in Lisbon, São Paulo, Luanda and a flat in Luton. The letter in her hand might be a section 21 notice, a Brazilian notificação, or something a landlord typed from memory. The agent cannot infer the forum from the accent.

So the first structural decision in Interview was to separate the language model of the conversation from the legal model of the matter. The conversation runs in whichever of 38 languages the caller chooses. The matter is pinned to a jurisdiction, and the jurisdiction is established by asking, early and plainly: where is the property, where was the contract signed, where do you live now. Until those answers are in, the agent asks questions. It does not compute anything.

That sounds obvious. In practice it means the agent sometimes spends the first ninety seconds on what feels like administrative detail while the caller wants to talk about the letter. We have tuned the ordering a good deal. We have not removed the step, because every shortcut we tried produced a brief that looked complete and was quietly wrong about which notice period applied.

The clock starts during the call

The reason jurisdiction has to be resolved early is that the most consequential number in an intake brief is usually a date. Limitation periods, notice periods, appeal windows: all of them are computed from a trigger event and a set of rules that differ by forum and by cause of action, sometimes within the same country.

Interview computes these during the call, not afterwards. When the caller says the letter is dated the 14th, the agent already knows the forum, so it can ask the follow-up that matters: was it posted or handed to you, and when did you receive it. The structured brief that reaches the clinic shows the computed deadline, the rule it used, the assumptions it made and the inputs it is unsure of. If the forum could not be established, the brief says so in the first line rather than printing a date with a caveat buried underneath.

We treat an unresolved jurisdiction as a hard stop for date arithmetic. A deadline the caller cannot rely on is worse than no deadline.

What the agent must refuse to do

A voice agent built for consumer support is optimised to resolve the call. A voice agent built for law has to be comfortable leaving it unresolved. Three refusals are built into Interview and cannot be switched off by a tenant:

• It does not give legal advice. It gathers facts, computes dates where the rules are deterministic, and tells the caller when a human will review the brief. It will say “a lawyer at the clinic will look at this tomorrow”, not “you should respond by Friday”.
• It does not guess at the jurisdiction. If the caller does not know where the contract was signed, the brief records that as unknown and flags it.
• It does not continue past a conflict. Since the conflict-check integration, the agent cross-references the names it hears against the firm’s matter database before the call ends; if a potential conflict appears, the call is handed off and the brief is sealed from the intake team until a conflicts officer clears it.

Each of these costs something in the moment. Callers sometimes want an answer and get a date for a callback instead. We think that is the right trade, and the clinics using Open Bar have told us, with some force, that it is the trade they would make themselves.

Where “aware” still falls short

We would rather be precise about the limits than vague about the promise. Interview’s jurisdiction model is strongest where the rules are codified and the trigger events are clear: statutory notice periods, limitation periods for contract and tort claims, filing windows for administrative appeals. It is weaker where the law turns on discretion, where a court might extend time on equitable grounds, or where a federal and a regional rule interact in ways that depend on facts the caller cannot supply.

We also know that sub-national variation remains uneven in our coverage. A tenancy question in one Swiss canton and the same question across the border in another are handled with different confidence, and the brief says which. We are testing a confidence indicator at the field level, so that an intake lawyer can see at a glance which dates were computed on firm ground and which were not.

The phrase “jurisdiction-aware” is cheap. The behaviour it describes is a long list of things the agent declines to do until it knows enough. That list is the product.

If you are evaluating an intake agent, ask it one question first: what does it do when the caller does not know where they signed.