AI Receptionist for Law Firms: What It Can Do, What It Must Never Do
An AI receptionist can answer every call to a law firm, take a caller's details, work out how urgent the matter is and book a consultation. What it must not do is give legal advice, run a conflict check, calculate a limitation date, or imply that the call is privileged. This page sets out the line between those two lists, the UK rules that actually apply, and what the thing costs.
Written for firms in England and Wales. Last checked 4 September 2026. We are an automation agency, not a law firm, and this is commercial information about a market we work in, not legal advice.
The short answer, in five lines
It answers the phone, every time, including at 7pm on a Friday. Roughly the work a good front-of-house does before a fee earner gets involved: who is calling, what about, how urgent, when can they speak to someone.
It must not advise. Not "you probably have a claim", not "you have three years", not "that sounds like constructive dismissal". Those are the sentences that turn a call-handling tool into a regulatory problem.
The regulator most people name is the wrong one. For marketing calls made by an automated system it is the ICO under PECR, not Ofcom. Ofcom's powers bite on a different thing: silent and abandoned calls.
UK pricing sits roughly between GBP 25 and GBP 250 a month for self-serve tools, per-minute plans typically around GBP 0.30 to GBP 0.80. Done-for-you builds cost more and are a different product.
The hardest part is not the technology. It is deciding what happens on the calls the AI should not finish, and making sure a human actually picks those up.
What a law firm actually gets from answering every call
The case for this in a law firm is narrower and more specific than the case in most businesses, and it is worth being precise about it rather than repeating a generic missed-calls argument.
A prospective client with a live legal problem is rarely shopping calmly. Someone who has just been dismissed, served, arrested, or handed a contract with a deadline on it tends to call several firms in one sitting and instruct whoever engages first. The cost of a missed call in that context is not a lost enquiry, it is a lost matter, and the value of the matter is known: it is your average fee for that work type.
That is the number worth doing the arithmetic on before buying anything. If your average matter is worth GBP 1,800 and you miss six genuine new-client calls a month, the gap is not a GBP 99 subscription question.
The second thing it does, which gets discussed less, is protect fee earners' time. A solicitor interrupted mid-drafting to be told a caller wants to know whether you do probate has lost more than the two minutes the call took.
The four things an AI receptionist must never do in a law firm
This is the part most vendor pages skip, and it is the part that decides whether the deployment is safe.
1. It must not give legal advice, or anything a caller could reasonably hear as legal advice. The risk is not only regulatory. A caller who is told "you have three years to bring that" and acts on it has been given advice by your firm, through a system your firm configured. Scripts must decline the question and route it, not answer it approximately.
2. It must not perform or imply a conflict check. An AI can capture the names of the other parties. It cannot clear a matter. Nothing in the call flow should tell a caller you can act for them, because at the point of the call nobody has checked whether you can.
3. It must not imply privilege or an established retainer. "Anything you tell me is confidential" is a sentence that should not exist in the script. Confidentiality obligations and legal professional privilege are not the same thing, and neither attaches simply because a caller spoke to an automated system.
4. It must not calculate or confirm a deadline. Limitation periods, filing dates and time limits are exactly the class of question where an approximately-right answer is worse than no answer. Capture the date the thing happened; do not compute what follows from it.
The practical way to hold all four is to write the refusals into the system prompt as hard rules with an explicit fallback line, and then test them adversarially: call your own system and try to get it to advise you. Most builds fail that test the first time.
The regulation, in the order it actually applies
There is a lot of confidently wrong content on this subject. Here is what we believe applies, in the order it bites, with a plain note where we think a firm should take its own advice rather than ours.
Inbound calls are the easy case
A caller ringing your published number and being answered by an automated system is not a marketing call. The bulk of the PECR direct-marketing regime, which is what most of the scary content online is about, is aimed at calls a business makes outbound. If all you are doing is answering your own phone, most of that regime is simply not engaged.
If you make outbound automated calls, it is the ICO, not Ofcom
Automated calling systems used for direct marketing are governed by the Privacy and Electronic Communications Regulations, and PECR is enforced by the Information Commissioner's Office. Regulation 19 is the provision dealing with automated calling systems, and the consent standard there is stricter than for live calls.
Ofcom is not irrelevant, and content that says "Ofcom, not ICO" or "ICO, not Ofcom" is oversimplifying in both directions. Ofcom's powers concern persistent misuse of a network, which in practice is the silent and abandoned calls regime. Two regulators, two different problems. Most competitor pages we read while researching this named only one, and usually the wrong one for the thing they were describing.
Call recording brings in UK GDPR
If the system records or transcribes, you are processing personal data and often special category data, because the substance of a legal enquiry frequently reveals health, criminal allegations or similar. That needs a lawful basis, a retention period you can actually justify, and notification to the caller. A firm should decide deliberately whether it needs recordings at all; a structured summary is often enough and carries far less risk than a stored audio file of someone describing their divorce.
SRA obligations do not move because a machine answered
Confidentiality, client care and the duty not to mislead apply to the firm regardless of what picked up the phone. In practice the two questions an SRA-minded reader will ask are: does the caller know they are speaking to an automated system, and can the firm evidence what was said. Both are answerable, and both should be answered before go-live rather than after.
Where we stop. We are confident about which regulator enforces PECR and about the UK GDPR position on recording. We are not the right source for how your specific firm should document any of this, and a compliance officer will reasonably want to see the actual call scripts before signing anything off. Take the framework here as a starting point for that conversation, not a substitute for it.
What it costs in the UK
Published UK pricing at the time of writing clusters into three shapes. These are the ranges we saw across UK vendor pricing pages in September 2026, not a quote.
| Model | Typical UK range | What it suits |
|---|---|---|
| Flat monthly, capped calls or minutes | GBP 25 to GBP 250 a month | Predictable low volume. Watch the overage rate, which is where these bite. |
| Per minute | Roughly GBP 0.30 to GBP 0.80 a minute | Spiky volume. A long intake call is not cheap on this model. |
| Per call | Around GBP 0.40 to GBP 0.80 a call | Short, high-frequency calls. Poor fit for legal intake, which runs long. |
| Done-for-you build | Quoted per firm | Custom intake logic, case management integration, human handoff rules. A different product from the list above. |
Two things to check on any quote, because they are where the real cost hides. First, what happens past the cap: a plan with a low headline price and an aggressive overage rate can cost more than a higher flat plan. Second, whether the price includes the integration you actually need. An AI receptionist that cannot write into your case management system is a notepad.
AI receptionist, answering service, or virtual receptionist?
These three get used interchangeably and they are not the same thing.
| What it is | Best for | Weakness | |
|---|---|---|---|
| AI receptionist | Software answers, follows your intake script, books into your calendar | Consistency, out of hours, unlimited simultaneous calls | Handles the unexpected badly. Needs a human escalation path that actually works. |
| Human answering service | An outsourced person answers as your firm | Judgement, distressed callers, anything unusual | Cost per call, queueing at peaks, variable knowledge of your firm |
| Virtual receptionist | Usually a person, often dedicated, sometimes part-time | Continuity, knows your matters | Not 24/7 without paying for 24/7 |
The honest answer for most firms is a hybrid: AI takes first pick-up and handles the routine majority, and anything it cannot finish rings through to a person. Firms that deploy AI with no escalation path are the ones that end up with a bad story.
The grey zone: what is safe, what has a consequence, and what firms actually do
Not everything in this space is clearly permitted or clearly forbidden. Here is the honest map.
Safe and effective
- Answering, identifying the caller, capturing the matter type and booking a consultation.
- Telling callers plainly that they are speaking to an automated assistant.
- Taking the other side's name for a later conflict check, without clearing anything.
- Out of hours cover that takes details and promises a callback at a time you can keep.
Moves with a consequence attached
- Letting the AI answer "do I have a case" even hedged. This is the single most common failure and it is advice.
- Recording every call by default with no retention policy. A UK GDPR problem waiting for a subject access request.
- Using the same system for outbound marketing calls without checking the PECR position first. Different regime, stricter consent.
- Any script line that says or implies confidentiality or privilege.
Borderline, and firms do it anyway
- Not announcing the AI. Some firms judge that a natural-sounding assistant that never claims to be human is acceptable. Our view is that announcing costs you almost nothing and removes the argument entirely, but firms differ and it is a judgement about your own risk appetite.
- Letting the AI quote fixed fees for standardised work such as a will or a straightforward conveyance. Defensible where the fee genuinely is fixed and published. Dangerous the moment the work is not standard.
- Triaging urgency automatically. Useful and generally fine, but the definition of urgent has to come from the firm, in writing, and someone has to own what happens when the system flags one at 11pm.
What we hear from the other side of these calls
One finding from our own sales conversations is worth passing on, because it contradicts the usual assumption. The most technically literate person in the room is usually the most hostile to this. Not because they think it will not work, but because they know exactly how it fails and they have decided the failure mode is unacceptable.
In a law firm that person is often the practice manager or the fee earner who covers the phones when reception is out. Winning them over is not a demo problem. It is answering one question honestly: what happens on the call this thing cannot handle, and who picks it up. A build with a good answer there gets adopted. A build without one gets quietly bypassed.
Frequently asked questions
Can AI replace a receptionist at a law firm?
Not the whole role. It replaces first pick-up and routine capture, which is a real share of the
work. It does not replace judgement, walk-ins, distressed callers, or the person who knows that Mrs
Patel always rings about the same file.
Is an AI receptionist worth it for a small firm?
The arithmetic is usually about missed new-client calls rather than salary. If you miss enough
genuine enquiries a month that the lost matters exceed the subscription, it pays. For most firms
that threshold is low, and it is worth counting your actual missed calls for a fortnight before
deciding.
Can an AI receptionist handle calls out of hours?
Yes, and that is usually where the value concentrates. Legal problems do not keep office hours, and
evening and weekend calls are where a competitor picking up first costs you the matter.
Is an AI receptionist better than a virtual assistant?
Different job. A virtual assistant does varied work for you. An AI receptionist does one job on
every call, identically, at any hour. Firms that need consistency at volume tend to prefer the AI;
firms that need someone to think tend to prefer the person.
What skills does an AI receptionist need for legal work?
Accurate name and contact capture including spelling out unusual names, matter-type
classification against your actual work types, urgency triage on your firm's definition, calendar
booking, and a clean handoff. Everything else is optional.
What are the potential downsides of using AI in law firms?
Three real ones. It answers the question it was asked rather than the question that mattered. It
can sound confident while being wrong, which is worse than sounding uncertain. And it creates a
data trail you are responsible for. All three are manageable, none disappears on its own.
Do I have to tell callers they are speaking to AI?
There is no single UK rule that says a law firm must announce it on an inbound call. Our view is
that you should, because the cost of announcing is close to zero and it removes any later argument
that the caller was misled. Firms take different views; this is one to settle with your compliance
officer rather than with a vendor.
Can it book directly into our case management system?
Depends entirely on the system and whether it has an API. This is the question that most often
turns a straightforward deployment into a project, so ask it before you buy anything, not after.
How we checked this, and what we could not settle
Checked: that PECR is enforced by the ICO and that regulation 19 covers automated calling systems; that Ofcom's relevant powers concern persistent misuse rather than PECR marketing consent; that UK GDPR applies to call recordings and transcripts; UK vendor pricing ranges, read directly from published UK pricing pages in September 2026.
Not settled, deliberately: whether any specific firm must announce automation on inbound calls, which we think is a matter of professional judgement rather than a bright-line rule. Whether a given AI intake script crosses into reserved legal activity, which depends on the actual words and is a question for the firm's own compliance function. And the precise SRA documentation a supervisor would want, which varies by firm.
Where we were not confident, we have said so on the page rather than rounding it up into certainty. If you spot something here you believe is wrong, tell us and we will correct it.
Sources
- PECR 2003, regulation 19, automated calling systems
- The Privacy and Electronic Communications (EC Directive) Regulations 2003, full text
- ICO, Guide to PECR, the regulator that enforces it
- Communications Act 2003, section 128, Ofcom persistent misuse powers, the silent and abandoned calls regime
- ICO, special category data, health data in call recordings
- Data Protection Act 2018, full text
- SRA Code of Conduct for Solicitors, RELs and RFLs, confidentiality and client care
- Legal Services Act 2007, reserved legal activities
Written by Edmund Gay, Learnmind.ai. This page is commercial information about a market we work in, not legal, clinical or regulatory advice. Regulation and vendor pricing on this page carry the date we checked them, and both change.
If you want this built properly
We build intake and call handling for firms that want the routine calls handled and the difficult ones escalated cleanly, with the four hard limits above written into the system rather than hoped for.