Most answering service guides written for law firms are really guides written for tradespeople with the word "solicitor" swapped in. They compare coverage hours, per minute pricing and how quickly calls are picked up. Those things are not where a legal practice gets hurt.
A law firm's exposure sits earlier in the call than any of that. It sits in the moment a well meaning receptionist encourages a distressed caller to explain what happened, before anyone has checked whether the firm already acts for the other side. It sits in a message that records privileged detail on a shared system. It sits in an escalation rule that treats a client chasing a completion date the same way it treats someone sitting in a police station waiting for a solicitor.
If you run a solo practice or a small firm and you are considering an attorney answering service, the useful question is not how much it costs per call. It is what the handler is instructed to do in the first ninety seconds.
"Urgent" does not mean for you what it means for a plumber
For a trade, urgency is about damage, and the escalation rule writes itself: if water is coming through a ceiling, ring the on-call engineer.
Legal urgency is almost never about how upset the caller sounds. It is about whether a right is about to be lost. A client who cannot be reached until Monday morning loses nothing if the issue is a query about a bill. A client facing a hearing on Monday morning who cannot get instructions taken on Friday evening may lose a great deal.
That distinction is invisible to a generic handler, because the emotional volume of the two calls can be identical. The person chasing a routine update is frequently the more agitated of the pair. Someone who has just been arrested is often calm, brief and clear, because there is a custody sergeant standing nearby and the phone call is short.
So the rule cannot be "escalate if the caller says it is urgent". It has to be a defined list of triggers, and the handler needs to know that being shouted at is not one of them.
Before the conflict check: what can and cannot be discussed
This is the part generic checklists never touch, and it is the single most important instruction you will give.
A conflict check needs identity. It needs the caller's full name, the names of any other parties, and enough about the matter type to know which file to look for. That is a legitimate and necessary thing for a first responder to collect.
What it does not need is the story. The moment a handler says "tell me what happened", the firm risks receiving detailed information from someone it may be unable to act for, and a note of that information now exists on a system. It is awkward at best, and worse if the firm already acts for the other side.
The practical instruction is a boundary, phrased so it does not feel like a brush-off. Something along the lines of: the firm needs to run a standard check before anyone can discuss the details, so for now the handler will take names, contact details and the general area of law, and a solicitor will call back. Callers accept this readily when it is framed as protecting them, because it is.
Two further points follow from this. First, the handler should never confirm or deny that the firm acts for anyone. A caller who names the other side and hears "oh, that name sounds familiar" has just been told something they should not know. Second, if the firm has to decline, the record of the enquiry should be minimal by design, because a thin file is easier to hold cleanly than a detailed one.
The confidentiality line: capture versus wait
Once conflicts are clear, there is still a line between administrative information and privileged substance.
An answering agent can reasonably capture the caller's name and contact details, the best time to reach them, whether they are an existing client and which fee earner they usually deal with, the matter reference if they have one, the broad category of the enquiry, and whether any deadline or hearing date is involved. All of that is intake data: it routes the call and tells the fee earner how quickly to respond.
What should wait for the solicitor is anything with substance in it. Admissions. Medical detail. Financial disclosure. Allegations about third parties. Anything a caller says with the expectation of confidence.
The failure mode is not usually a handler prying. It is a handler being kind. Distressed callers volunteer a great deal, and the natural human response is to listen sympathetically and write it all down. A legal intake script has to give the handler a way to be warm while steering away from detail: acknowledge that it sounds difficult, explain that the solicitor will want to hear it properly and directly, and get the callback booked.
Then there is the question of where the message lands. A message containing case detail sitting in a shared inbox, an unencrypted SMS or a third party portal with loose access controls is a confidentiality issue regardless of how carefully the call was handled. Ask where messages are stored, who can read them, and how long they are retained.
Writing the escalation script
The escalation script is where the abstract principles turn into something a handler can follow at eleven at night without judgement calls.
Build it as a short, closed list of genuine emergencies. For most small firms that list includes: arrest, detention or an imminent police interview; a without notice injunction or freezing order, or notice of one; child protection or safeguarding concerns; an eviction, repossession or removal happening within hours; any court, tribunal or statutory deadline falling before the next working day; and a client in immediate danger. If it is on the list, the handler rings the duty fee earner directly and keeps ringing until someone answers.
Everything else is routine, and the script should say so explicitly. Case progress queries, billing questions, document requests, new enquiries, complaints, chasing an unanswered email. All of these get a message, a promised response window, and nothing more. Complaints deserve a slight variation: they should be logged properly and routed to whoever handles them, but they are not out of hours calls.
The list needs to be yours. A criminal practice's emergency list looks nothing like a conveyancer's. Immigration work brings detention and removal directions. Family work brings safeguarding. Commercial litigation brings deadlines and injunctions but rarely a two in the morning call. A vendor offering one generic legal script for all firm types has not thought about this.
Give the handler a second lever too: an "unsure" route. If a call does not clearly match a trigger but feels serious, the handler should have a named person to check with rather than guessing. Guessing produces both missed emergencies and needless midnight calls.
What SRA client care expectations mean at the phone
Nothing here is a compliance certification, and no answering service can give you one. But the SRA Standards and Regulations set expectations that are entirely relevant to how calls are answered.
Clients are entitled to information about the service they will receive, in a form they can understand. They are entitled to be kept informed. They are entitled to know how to complain. And the firm remains responsible for what is done on its behalf, which includes what a third party receptionist says while representing it.
Translated to a phone script, that means a handler should be able to tell a caller when someone will get back to them and actually be right about it, should be able to say how to raise a concern, and should never offer anything the firm has not authorised. No fee estimates. No comment on the merits of a case. No "you should be fine" reassurance. No suggestion that the firm can take the matter on before anyone has looked at it.
Missed and unlogged messages are the quiet compliance risk. A client who rings three times and hears nothing back has not been kept informed, and the firm cannot demonstrate otherwise if there is no record of the calls.
Vetting questions generic checklists do not ask
When you assess a provider, the standard questions about hours and answer times are fine but insufficient. Add these.
Ask what the handler is instructed to say before a conflict check has been run, and listen for whether they have a considered answer or are improvising.
Ask how they handle a caller who names the opposing party, and whether their system flags names against your existing matters at all.
Ask who else in your practice areas they answer for in your area, and whether calls could plausibly reach the wrong firm.
Ask how many handlers will cover your line and how the escalation list gets to a new starter at 3am.
Ask where message content is stored, who can access it, what the retention period is, and what happens to records for enquiries that never became instructions.
Ask what happens when their system goes down, and whether their contract addresses confidentiality and data processing in terms your COLP would accept. A firm with a court deadline needs a fallback, not an apology.
Small firms often start from a general provider and try to bolt legal requirements on afterwards. The broader framework in our guide to choosing an answering service for a small business still applies, but for regulated work the intake logic has to be built first and the coverage arranged around it.
Get the script right and the phone stops being a liability. The rules above are unglamorous, but they are the difference between a first responder who protects the firm and one who quietly creates work for it. If you want intake and escalation designed around how your practice actually operates rather than a template, that is exactly what Nimble Dingo's AI growth systems are built to do.