Case Intake Software: What It Changes and What It Leaves Alone
Software routes, records and reminds. It does not pick up the phone and it does not supply judgment. Most disappointment with the category traces back to that line.
Case intake software is the system a firm uses to capture an enquiry, move it through defined stages, prompt the next action and report on the outcome. It sits before the case management system, because the person it deals with is not a client yet and might never be one.
Firms usually buy it after a specific kind of frustration: someone realises there is no reliable answer to what happened to the enquiry that came in last Tuesday. That is a good reason to buy, and the software genuinely solves it. The trouble starts when the purchase is expected to solve a second problem that it never touches.
What it genuinely changes
Four things improve reliably, and they are worth naming precisely rather than in the abstract.
Every enquiry acquires a record at the point of arrival. This sounds administrative and is the most consequential item on the list, because an enquiry that exists only in a voicemail or a sticky note is one nobody can manage, count, or notice the absence of.
Follow-up stops depending on memory. The single largest recoverable loss in most intake operations is people who showed interest, did not respond immediately, and were never contacted again. Software converts that from something a busy person is supposed to remember into something the system prompts. Our follow-up cadence guide covers what a sensible rhythm looks like.
The handoff to an attorney gets a defined place to happen, rather than being an email that may or may not be read. Handoffs are where a surprising share of qualified enquiries stall, and a defined step with an owner is most of the fix.
Finally, the operation becomes visible. You can see how many enquiries arrived, where they are sitting, and which sources produce matters worth having rather than merely volume.
What it does not change
Two problems survive the purchase completely intact, and they are the two that most often prompted it.
Somebody still has to answer
No intake system answers a ringing phone. If an enquiry arrives at seven in the evening, on a Saturday, or while both intake staff are already on other calls, the software will faithfully record that the contact was missed. It will not prevent the miss.
This is the distinction between a tooling problem and a coverage problem, and it is worth being blunt about because the two feel identical from inside a busy office. Tooling problems are about what happens to enquiries after contact. Coverage problems are about whether contact happens at all. Software is an excellent answer to the first and no answer whatsoever to the second. Speed to lead covers why the minutes here matter so much.
Judgment does not arrive in the box
Deciding whether a caller has a matter worth pursuing is not a workflow step. It requires knowing which facts change the answer, which questions to ask when the caller has not volunteered the relevant detail, and when something is time sensitive even though nobody has said so.
A well built system supports that judgment with structured questions and required fields. It cannot replace it. A form completed accurately by someone who did not know what they were listening for produces a tidy record of a misjudged enquiry, and the tidiness makes it less likely anyone revisits it.
The measurement trap nobody warns you about
Here is the pattern that causes the most avoidable conflict after an implementation.
Before the software, the firm counted the enquiries it knew about. Enquiries that were missed outright generally never entered the count, because there was nothing to enter them from. The conversion rate was calculated against a denominator that quietly excluded the worst failures.
After the software, everything is captured. The denominator grows to include the calls nobody answered and the web forms nobody actioned. The conversion rate drops, sometimes sharply, in the first month.
Nothing got worse. The firm simply stopped grading itself on a partial record. But the timing is unfortunate, because the number falls immediately after a visible expense, and the natural conclusion is that the software caused it. Anyone introducing a system should say this out loud beforehand to whoever reads the reports. A measurement that improves by getting less flattering is very hard to defend after the fact and easy to explain in advance. We looked at how to read these figures properly in intake conversion benchmarks.
Software, staffing, or a service
Once the distinction between tooling and coverage is clear, the buying decision becomes considerably easier, because you are choosing against a diagnosis rather than against a feature list.
If enquiries are lost after contact, through inconsistent follow-up, unclear ownership or no record, buy the software. It is the efficient fix and it will pay back.
If enquiries are lost at the moment of contact, the answer is somebody being available, which means extending staffed hours or using an outside intake service. Our overview of legal intake services sets out what that covers, and how a legal call center operates goes into how the coverage is actually delivered.
Plenty of firms have both problems at once, and there is nothing wrong with solving both. The failure is buying for one and expecting the other to resolve itself. For a feature by feature comparison and the build versus buy question, our PI intake software buyers guide goes considerably deeper than this piece does.
Questions worth asking a vendor
Ask how an enquiry gets into the system when it arrives by a channel the vendor did not anticipate. Firms receive contact by phone, web form, chat, text, referral email and occasionally in person, and a system that captures four of those cleanly still leaves you with a partial record and the flattering denominator problem.
Ask what is timestamped and whether response time can be reported on without exporting anything. If you cannot see time to first contact easily, you will not look at it, and it is the number most closely tied to whether enquiries convert.
Ask what the reporting shows about enquiries that went nowhere. Systems are usually good at describing successes and vague about losses, and the losses are where the recoverable value sits.
Ask what happens outside business hours, and listen for whether the answer describes capture or response. Capturing an after hours enquiry is useful. It is not the same as answering it, and vendors do not always make the distinction unprompted.
The short version
Case intake software is worth having. It removes an entire class of loss caused by enquiries falling out of sight, and it makes an operation legible to the people running it.
What it cannot do is be present when a call comes in, or know which caller has a case. Firms that buy it to fix organisation are usually pleased. Firms that buy it to fix conversion without asking why conversion is low end up with an accurate, well structured account of the same enquiries they were already losing.
Common questions
What does case intake software actually do?
It gives every enquiry a record from the moment it arrives, moves it through defined stages, prompts the next action and reports on what happened. Enquiries stop existing only in someone's memory, follow-up is scheduled rather than remembered, and a manager can see where things are sitting. Those are real changes to how the firm tracks work, which is different from changing how well the work is done.
Will it improve our conversion rate?
Where the loss was caused by disorganisation, yes. Forgotten enquiries and inconsistent follow-up are exactly what it fixes. Where the loss was caused by nobody answering outside office hours, or by whoever answered being unable to tell a strong matter from a weak one, it will document those losses accurately and prevent none of them.
Why did our numbers get worse after implementation?
You are seeing the true figure for the first time. Previously the denominator was whatever got written down, and outright misses were usually absent from the count. Once every contact is captured, losses that were always occurring become visible and the rate appears to fall. Nothing declined. The earlier number excluded the failures.
Is it the same as a case management system?
They overlap and are often sold together, but case management is built around accepted matters, with deadlines, documents and billing. Intake is built around people who are not clients yet, and is organised around response speed, qualification and follow-up. Running intake inside a system that assumes a decision has been made tends to work badly.
Do we need software, more staff, or an outside service?
It depends where enquiries are lost. Lost after contact is a tooling problem and software is the efficient answer. Lost at the moment of contact is a coverage problem, solved by someone being available, whether that is more staff or an outside intake service. Many firms need both, and buying one expecting it to fix the other is the common mistake.