legal intake services vs. an intake system your firm owns
a firm decides to start advertising. the budget is set, the landing pages are close, and someone asks the obvious question: who is going to answer all of this? the phone will ring at 9pm. the web form will fill up on a sunday. the inquiry that matters most will arrive while everyone is in a deposition. so the firm starts pricing legal intake services, and within an hour it has three tabs open that all use the same phrase for three different things.
that's the first thing worth knowing about legal intake services. the label covers at least three different purchases, and the right one depends less on price or features than on one question most comparisons skip: who writes the rules that decide what happens to an inquiry, and where does the record of that decision live?
three things sold as legal intake services
rented people. an answering service or an outsourced intake team picks up calls in your firm's name, works through a script, and passes the result to you. the value is coverage: a human voice at any hour. the script is yours on paper, but the people applying it work for someone else, and the record of each call usually lives in their system until it's sent to yours.
rented software. an intake platform, an ai receptionist, or an intake module inside practice-management software. the value is speed and consistency: every inquiry answered the same way, logged, sometimes scored. the rules live in the vendor's configuration screens, and the data lives in the vendor's database, under the vendor's terms.
a system you own. the same jobs, capturing every inquiry, pulling out the facts, and routing it to the right person on a clock, built on accounts the firm controls. the rules are written down in the firm's own words. the record lives where the firm's other records live. nobody can switch it off or reprice it because a contract renewed.
none of these is wrong. a solo practice that needs a person on the phone tonight should hire one. the mistake is buying any of them without asking the question that actually separates them.
the question that sorts them: who decides what an inquiry means
every intake service does two jobs, even when it only advertises one. the first is capture: getting the name, the number, and what happened. the second is interpretation: deciding what the inquiry is, how urgent it is, and who should see it.
capture is easy to outsource. interpretation is where firms get into trouble, because interpretation slides toward judgment without anyone noticing. a script that says "if the caller wasn't injured, thank them and end the call" has just decided something about a potential case. an ai receptionist that "qualifies leads" is making a call about which inquiries reach a lawyer. when that call is wrong, the firm usually never finds out, because the lead that was turned away doesn't come back to complain.
so the first thing to ask any intake vendor is not "how fast do you answer." it's "show me exactly what your system decides on its own, and where I can read the record of each decision afterward."
the line a law firm can't hand to anyone
there's a hard version of that question for law firms. deciding whether someone has a case is legal judgment, and legal judgment isn't something a firm can delegate to a script, a call-center agent, or a model. what a person is allowed to tell a prospective client, and who may decide whether to take a matter, varies by state and by bar. nothing here describes what any particular jurisdiction requires. the practical point is narrower: a well-built intake process separates the facts from the decision, so it's always clear which one a person made.
in practice that split looks like this. a language model reads the inquiry and pulls out facts: what kind of incident, when, where, whether there was treatment, who else was involved. it stops there. ordinary code, which never sees a model's opinion, applies rules the attorneys wrote to those facts and routes the inquiry: this one goes to the on-call lawyer now, this one goes to the morning queue, this one is outside the firm's practice areas. a lawyer still decides whether the firm takes the matter. the software just makes sure the lawyer sees it, with the facts laid out, before the moment has passed.
that's the architecture behind a personal injury intake build i described elsewhere. when that firm's paid ads went live, inquiries were captured, graded and in front of the firm within seconds, and the first two were picked up in under fifteen minutes. the firm reported its first signed retainer from the ads twelve days after they first served. that's one case, not a performance number, but it shows the shape working.
what to ask before you sign for any of them
whichever kind of legal intake services you're weighing, these questions separate the ones that fit a law firm from the ones that only look like they do:
- who wrote the rules that decide routing, and can i read them in plain language? if the answer is "our proprietary model," you can't audit it.
- does anything in the system judge whether a matter has merit? look for scores, ratings, "qualified" labels and automatic declines. each one is a decision someone needs to own.
- what happens to the inquiry the system isn't sure about? the right answer is "it goes to a person, flagged." the wrong answer is "it's classified as the closest match."
- where does the record live, and can i take it with me? every inquiry, what was extracted, who saw it, and when. if you leave, does that history leave with you?
- what's the response clock, and who gets alerted when it's missed? speed matters most on the first contact, so the system should notice when nobody has picked an inquiry up.
an answering service can pass most of these with a good contract. intake software can pass them with the right configuration. a system you own passes them by design, because you wrote the rules and you hold the record. that's the trade: more setup at the start, in exchange for never renting the part of intake that carries legal weight.
where to start
most firms don't need to choose today between hiring people and building software. they need to know where their inquiries actually go now, which ones are lost, and which parts of intake are safe to automate. that map is the first step of the work described on ai for law firms.
it's also what a workflow audit produces: a fixed two-week engagement, $2,500, credited toward a build if you go ahead. it ends with a written plan of what to automate, what stays with your people, and what it costs. details are at /workflow-audit.