8 min Read

What an AI Receptionist Actually Does for a Law Firm

How law firms use AI voice and chat intake to qualify callers, capture matters after hours, and stop losing cases to voicemail.

Nikhil Sharma
What an AI Receptionist Actually Does for a Law Firm - Digital Solutions Ninja blog

Key takeaways

  • The value is not answering the phone, it is qualifying the caller before a paralegal spends an hour on someone who was never a case
  • Most firms lose more matters to the calls that arrive at 7pm than to the ones they handle badly at 11am
  • An AI receptionist is only worth having if it writes into the case management system the firm already uses, otherwise it has produced another inbox
  • Conflict checks, limitation periods and privilege are the three places this goes wrong, and all three are configuration rather than model problems

Almost every law firm that calls me about this describes the problem as a phone problem. Calls come in, nobody picks up, work walks. The fix sounds obvious: put something on the phone that always picks up.

That framing produces a system nobody uses after month two. The phone was never the constraint. Qualification was.

The actual arithmetic

A firm with six offices takes a lot of calls. Some fraction are prospective clients with a real matter. A larger fraction are existing clients chasing an update, opposing counsel, process servers, vendors, and people who found the number on a directory and have a question the firm cannot help with.

The expensive failure is not the missed call. It is the paralegal who spends forty minutes with a caller who was never going to be a file, while a genuine matter sits in voicemail. Answering every call faster makes that worse, not better. You have simply increased the volume of unqualified contact reaching people who bill.

So the thing worth building is not a receptionist. It is a filter that runs before one.

What good intake actually collects

For most practices the qualifying set is short and boring, which is exactly why it automates well:

  • Practice area. Is this something the firm does. A surprising share of inbound is not.
  • Jurisdiction. Where did it happen, and are you licensed there.
  • Timing. When did it happen. This is the limitation period question and it is the one that decides urgency.
  • Conflict inputs. Names of the parties involved, collected so a real conflict check can run.
  • Contact and consent. How to reach them, and permission to do so.

That is a five minute conversation a trained intake person has hundreds of times a year. It is repetitive, it follows a decision tree, and it is exactly the shape of work a language model handles well. It is also the work that most often gets skipped at 6pm on a Friday.

The three places it goes wrong

Clearing conflicts it should only be collecting for

A system that tells a caller "we can take your case" before a conflict check has run has created a problem for the firm, not solved one. The correct behaviour is to gather party names and say the firm will confirm. This is a configuration decision, and it is the first thing I check in any deployment I inherit.

Missing the clock

Limitation periods are the one piece of intake where being approximately right is worthless. If a caller describes something that happened close to a deadline, that call needs to reach a human today, not sit in a queue until Monday. Any system worth running has an explicit urgency path keyed to dates, and it is tested before launch.

Handling distress badly

Personal injury and family practices get calls from people in genuine crisis. A system that responds to that with a scripted question about practice area is worse than voicemail, because voicemail does not pretend to be listening. Escalation on distress signals is not a nice-to-have, it is the difference between a deployment that reflects well on a firm and one that ends up screenshotted.

The integration is the project

Here is what nobody selling a platform will tell you clearly. The voice technology is largely a solved problem. Several vendors will give you a competent conversational agent with a Canadian number this month.

What they will not give you is a qualified matter appearing in your case management system with the right fields populated, the right lawyer notified, the intake recording attached, and the whole thing logged where your file audit can see it. That work is specific to your firm, your software and your intake process, and it is where both the cost and the value sit.

If a proposal is mostly about the model and lightly about the integration, it is a proposal to give you a second inbox.

What to measure

Not call volume. Not average handling time. Two things:

  • Matters captured outside office hours that converted to a file. This is the number the system exists to move.
  • Unqualified contact reaching billable staff. If this has not fallen, the filter is not filtering.

A firm I work with runs intake this way across six offices in three provinces. The number that changed was not calls answered. It was how many people who bill by the hour spent that hour on someone who was never a case.

Is it worth doing

If your intake is one person who handles it well during business hours, and your practice area does not generate urgent after-hours contact, probably not yet. Fix the hours before you buy software.

If enquiries arrive at night, on weekends, and while everyone is in court, and if the cost of a missed matter is measured in five figures, then the arithmetic is straightforward and the only real question is how well it gets wired into what you already run.

If you want that scoped properly rather than quoted from a description, that is what an MVP Roadmap is for.

FAQ

Quick answers to the most common questions about this topic.

Some will and it matters less than firms expect, provided the system is honest about what it is and hands off cleanly. What people react badly to is a system that pretends to be a person and then fails to understand them. Stating plainly that it is an intake assistant, and routing to a human the moment it is out of depth, tests better than a convincing impression.

It can collect the names required for one and flag an obvious hit against your existing records. It should not clear a conflict on its own, and no responsible configuration lets it. Treat it as the step that gathers the information a real conflict check needs, not as the check itself.

This is the case that decides whether a deployment is competent. A personal injury or family practice will get calls from people who have just had the worst day of their life. The system needs an explicit escalation path on distress signals, and it needs to be tested against them before it goes live rather than after.

That integration is the project. The voice part is close to solved and available from several vendors. Getting a qualified matter to land in the right place in your case management system, with the right fields populated and the right person notified, is where the work and the cost actually are.

Platform subscriptions are modest and any vendor will quote you one. The build around it is what varies, because it is priced on what it has to integrate with and how your intake actually works rather than on a per minute rate. I scope that in a paid MVP Roadmap engagement and give you a real number, credited against the build if you proceed.

How the MVP Roadmap works
Nikhil Sharma

Written by

Nikhil Sharma

Founder, DigiBenders

Twelve years shipping software, five of them leading a studio in New Brunswick. I build the software and run the marketing around it, which is an unusual combination and the reason most of my work arrives by referral. One person accountable, and everything ends up in your name.

You read the thinking

Now tell me what you are actually building.

If this was useful, the call usually is too. You describe the problem, I tell you what it takes and whether I am the right person for it.

Thirty minutes, no pitch

Honest read, including when the answer is no

Replies within one business day

Book a strategy call30 min

Keep reading

More from the same desk.

What you walk away with

One instrument. You own it.

Nothing held hostage, nothing locked to a platform you cannot leave.

The codebase

Yours, in your repository

The infrastructure

Your accounts, your billing

The accounts

Registrar, analytics, ads

The documentation

Written for the next person