Hashlogics
Blog

Legal AI should route, not advise

Sorting a case to the right practice area and lawyer is logistics. Telling a client what the case is worth is legal advice, and only you, licensed, can give it. Those two things look similar in a demo. They're nothing alike in front of your bar association.

In short

5 things that decide this

  1. 01Matching a case to a practice area and an available lawyer is a classification problem. It does not require a law license to perform.
  2. 02Estimating a case's value, likely outcome, or settlement range is legal advice. An AI system that does this is practicing law without a license.
  3. 03The safe design keeps AI on the sorting side of that line and routes anything closer to it to a licensed human, every time.
  4. 04Guided intake forms produce cleaner routing data than a chat interface, because the questions are fixed instead of improvised.
  5. 05An admin who can see every case's status and every routing decision is what makes the line defensible after the fact, not just in the design document.
The two questions

Sorting and advising look alike from outside

A prospective client fills out your intake form describing a car accident. Your system reads it and does two things that feel like the same task. First, it sorts the case as personal injury and forwards it to a lawyer with an open slot. Then, if you let it go one step further, it might say something like: cases like this typically settle for a certain range.

That first task is classification. Giving the second without a license is unauthorized practice of law in every US state. Your engineer can build both in the same sprint, which is exactly why teams cross the line without deciding to.

Why the line matters

The rule exists to protect people who cannot judge the advice

Unauthorized practice of law rules aren't a formality. Someone asking about their accident case can't spot a wrong answer on their own, which is exactly why the advice has to come from someone licensed and accountable. A chatbot with no bar number and no malpractice insurance carries none of that accountability, however confident its output sounds.

Routing carries a different kind of risk. Send a case to the wrong practice area and a lawyer just redirects it. Give a wrong value estimate, though, and your client may reject a real offer, or accept a bad one, based on a number nobody stood behind.

Where the line sits in an intake systemLive
  1. Guided intake formFixed questions about the facts of the case, not open-ended chat.
  2. Practice area classificationPersonal injury, family law, immigration. A category, not a judgment.
  3. Lawyer matchingRoutes to an available, verified lawyer in that practice area.
  4. Value or outcome estimateLegal advice. Reserved for a licensed lawyer, never the system.

Everything left of the line is classification. Everything right of it needs a license.

The design pattern

Structured intake keeps the system on the right side

Lexpair, a legal lead-matching platform we built, runs on guided forms rather than open chat. A client answers a fixed set of questions about the facts of their case, and AI-assisted logic reads those answers and sorts the case into a practice area, then matches it to a verified lawyer with capacity. Admins see every lead and every match from one dashboard.

That form structure does real work for you. An open chat window can be led into a value estimate if a user keeps asking; a fixed set of questions can't. Your system has no field for a settlement range, because you never asked it to have one.

The admin layer

Visibility is what makes the line hold up later

A design decision only counts if someone can check that it held. Every lead on Lexpair carries a visible status and a match history, so an admin can see exactly what the system decided, and why, case by case.

That record is what a compliance review wants to see: proof the system routed and didn't opine. Build that visibility in from your first sprint. Bolting it on after a complaint arrives is much harder.

Questions, answered

Questions this raises

01Can AI be used for law firm intake?+

Yes, for classification and routing. Your AI can sort a case into a practice area and match it to an available lawyer without practicing law. You cross the line only when the system starts estimating outcomes or value.

02Is AI-generated legal information considered legal advice?+

It counts as legal advice when it predicts an outcome, not when it classifies one. A description of what a type of case generally involves is information for your prospect. A statement about what this specific case is likely worth is advice, and only you, licensed, can give it.

03How do law firms qualify leads with AI without practicing law?+

Keep your AI's job to classification and matching: which practice area, which available lawyer, verified against fixed intake questions rather than open-ended chat. Anything that predicts an outcome or a value gets routed to a lawyer, never answered by the system.

By Abdul Basit, CEO, HashlogicsUpdated
Start

Let’s deploy working AI into your business.

We build AI agents and automation, ship them into the tools you already run, then stay on under an agreed service level. A senior engineer reads every brief, and your call gets scheduled within 24 hours.

What happens next

  1. 01

    You send a brief or book a call

    Two minutes, whichever you prefer.

  2. 02

    A senior engineer replies within 24 hours

    Not a sales rep.

  3. 03

    Honest scoping, in writing

    And if we’re not the right fit, we say so.

Abdul Basit, CEO of Hashlogics

“I started Hashlogics because too many teams ship a demo, get paid, and disappear. We build to a standard we’d run ourselves — and we stay to keep it running.”

Abdul Basit · CEO · a direct line

Not ready to talk? Take the checklist.

12 questions to ask any AI agency before you sign. They separate a demo shop from a team that ships to production.

Get the checklist

Free · no newsletter