Key takeaways
- Keep one firm-owned document that every answerer works from: staff, the answering service and any automated assistant.
- Write practice areas the way callers describe them, and fee answers as approved wording to read, not paraphrase.
- Trained staff can field general fee questions, but fee negotiation and what services someone needs go to a lawyer[2].
- Give every section an owner and a review date; median job tenure is 3.0 years for workers aged 25 to 34[1].
The same question, four different answers
Ask four people at a small firm whether it handles a tenant's eviction case and you can get four answers. The receptionist says yes because she once booked one. The answering service says no because its notes date from two years ago. The website says “real estate matters”. The partner says only for tenants in two counties. Callers hear whichever answer the phone happened to reach. The fix is not more training. It is one written source every answerer works from, owned by someone with the authority to change it.
Turnover makes the problem worse every year. In January 2026 the median US worker had been with their current employer 4.1 years, but the median for workers aged 25 to 34 was 3.0 years and for those aged 20 to 24 just 1.5 years[1]. The people answering a firm's phones skew young, and what they have learned about handling calls leaves with them unless it is written down.
Source: U.S. Bureau of Labor Statistics, 2026[1]
Show the data
| Age group | Median tenure |
|---|---|
| 20 to 24 | 1.5 years |
| 25 to 34 | 3 years |
| 35 to 44 | 4.7 years |
| 45 to 54 | 7 years |
| 55 to 64 | 9.6 years |
| 65 and over | 9.9 years |
A call-handling knowledge base is narrower than a procedures manual and wider than a script. It holds the answers and decisions the phones need: what the firm takes and declines, what can be said about fees, where declined callers go, what counts as urgent and who gets it. Writing standard operating procedures covers how each task is done; the knowledge base covers what gets said.
What goes in it
Firm facts
Offices, hours, parking, who works where and how existing clients reach their team
Practice areas
What you take and decline, written in the words callers use
Fee language
Approved sentences about consultations and fee structures, read as written
Referral list
Where each declined matter goes, with the bar referral service as the default
Urgency and escalation
What counts as urgent, who gets it, the backup and the no-answer step
Never say
Legal advice, deadlines, outcome predictions and confirming who is a client
Six sections cover most of what a law firm's phones need. Keep each entry short enough to read during a call.
| Section | Owner | Review | Changes when |
|---|---|---|---|
| Firm facts | Office manager | Monthly | Hours, staff or offices change |
| Practice areas | Managing partner | Quarterly | The firm starts or stops a type of case |
| Fee language | Managing partner | Quarterly | Fee structure or consultation policy changes |
| Referral list | Partner for each practice | Quarterly | A contact moves, retires or stops taking a matter type |
| Urgency and escalation | Managing partner | Monthly | The on-call rota, phone numbers or urgent tests change |
| Never say | Managing partner | Twice a year | A rule, ethics opinion or complaint suggests a new line |
Practice areas in callers' words
Callers don't say “premises liability” or “post-judgment modification”. They say they slipped in a parking garage, or that their ex stopped paying support. Each practice-area entry should start with the phrases callers actually use, then give the firm's decision and the next step. Pull the phrases from a few weeks of messages and recordings; the method in FAQ pages built from what callers ask works here too.
Example entry. Caller says: “my landlord is trying to evict me”, “I got a notice to quit”, “they changed the locks”. Decision: the firm represents tenants in residential evictions in two counties and does not represent landlords. Next step: take the names for the conflict check, the county and the date on any court paper, then book a consultation. A hearing within seven days is urgent. A landlord caller is declined kindly and given the landlord-tenant referral entry.
Write the declines as carefully as the accepts. A plain list of what the firm doesn't take, with a reason a caller can hear (“we only act for the injured person in injury cases”), prevents the worst kind of call: the half-taken intake that raises someone's hopes and then stalls for a week.
Fee language people can say out loud
Fee questions come up on most first calls, and they are where improvised answers do the most harm. ABA Formal Opinion 506 says a lawyer may train and supervise nonlawyers to handle prospective-client intake, including initial facts, conflict checks and general questions about the fee agreement[2]. It also draws a line: if a prospective client asks what legal services they need, wants to negotiate the fee or wants the engagement agreement interpreted, the lawyer has to answer[2].
So the knowledge base holds approved sentences, word for word, for the general questions, and a handoff sentence for everything past the line. For example:
- “Injury cases are handled on a contingency fee. The attorney explains exactly how it works at the consultation, and that first meeting is free.”
- “Family-law consultations are charged. I can tell you the amount and book you in now.”
- “Whether you need a will or a trust is exactly what the attorney will go through with you. I'll note it so it's the first thing covered.”
- “I can't change the fee, but I'll pass your question to the attorney before your consultation.”
Mark every fee sentence as read-as-written. Paraphrased fee language is how a firm ends up with a caller who “was told it was free”. The tone side of this is covered in explaining fees during intake.
The referral list for matters you decline
Every decline should end with somewhere to go. The referral section lists, for each practice area, who the firm sends callers to, with a phone number checked in the last quarter, plus a default for everything else, usually the local or state bar's lawyer referral service. A caller turned away with nothing is more likely to call back angry, or to write about it.
Keep the list clear of anything that looks like a paid recommendation. California's Rule 7.2(b), for example, bars a lawyer from giving anything of value to a person for recommending the lawyer's services, subject to listed exceptions, and its comment says reciprocal referral arrangements must not interfere with the lawyer's professional judgment about referrals[3]. Note any reciprocal arrangement on the entry so the partner reviewing the list can see it. The full method is in building a referral-out list.
Urgency, escalation and the never-say list
The escalation section turns urgency into tests anyone could apply: a client in custody tonight, a hearing tomorrow morning, a protective order being served, an adjuster pressing for a recorded statement. Each test names who gets the call, the backup, and what the caller hears if nobody answers. The transfer, message or book rules lay this out as a one-page matrix.
The never-say list is short and absolute: no legal advice, no deadlines or limitation periods, no predictions about outcomes, no confirming to a third party that someone is a client. Florida Bar Opinion 24-1 points intake tools to Florida's earlier guidance on nonlawyer intake, which says the person doing an initial interview must identify their nonlawyer status, keep to factual questions, give no legal advice and refer legal questions to the lawyer[4]. Write the sentence the answerer says instead, so nobody is left improvising a refusal.
One source for staff, services and an SI Employee
The knowledge base pays off when every answerer uses the same version. Staff train on it. The answering service's instructions are generated from it rather than maintained separately, in the format set out in writing call-handling instructions. And if an SI Employee covers overflow or after-hours calls, its approved profile is built from the same entries: the greeting, the intake questions for each practice area, the matters the firm declines and the escalation tree (what it does).
That last reader needs the tightest boundaries. A Stanford study found general-purpose chatbots hallucinated between 58% and 82% of the time on legal queries[5]. An automated answerer should work only from the firm's approved text, say plainly when it doesn't know and take a message. California's 2026 guidance names autonomously facilitating client intake as an example of agentic AI and says a lawyer's supervision must match the system's level of access and autonomy[6]. A knowledge base with owners and review dates is what that supervision looks like on paper.
- Caller
- SI Employee
- Your team
01Caller
Caller asks something new
“Do you handle security deposit disputes?” Nothing in the knowledge base covers it.
02SI Employee
No guess, a message
The answerer says the team will confirm, then takes details and a callback time.
03Your team
Logged as a gap
Someone adds the question to the weekly gaps list, with the call summary.
04Your team
Owner writes the answer
The practice-area owner approves the wording and the next step, with a date.
05Your team
Every answerer updated
Staff notes, service instructions and the automated profile change the same day.
Example loop. Review the gaps list weekly for the first three months, then monthly.
The estate planning example shows the same discipline on a small scale: six pre-consultation questions approved by the attorneys and asked the same way on every call, whoever or whatever answers.
Building the first version in two weeks
Days 1 to 3: collect
Pull the answering service's account notes, the receptionist's cheat sheets, the website FAQ and fifty recent messages. Every answer the firm gives today is somewhere in that pile.
Days 4 and 5: list the questions
Group what callers ask into the six sections. Most small firms end up with forty to eighty entries.
Days 6 to 9: write the entries
Caller phrases, the decision, the next step and, where it matters, the exact words to say. One entry per question, short enough to read mid-call.
Day 10: partner review
The managing partner approves fee language, declines, the referral list and the never-say list. Nothing goes live unapproved.
Days 11 to 14: publish and test
Replace the old notes everywhere at once, then run test calls against the new version through every answerer.
Where it lives matters less than there being only one copy. A shared document with a heading for each of the six sections, searchable from the receptionist's screen, is enough for most firms. Avoid printing it: paper copies are the stale versions that keep getting quoted after an update. The answering service and any automated profile get an export of the approved version, never a parallel draft, and every export carries the version date.
Put a version date at the top and keep a short change log. When a caller complains that they were told something wrong, the first question is which version was in use that day, and the log answers it in seconds.
Example: a four-lawyer firm with family-law and injury practices builds its first version from 50 recent messages and its answering service's account notes. It ends up with 62 entries: 9 firm facts, 21 practice-area entries including 8 declines, 7 fee sentences, 11 referral contacts, 9 escalation tests and 5 never-say lines. The gaps list adds 14 entries in the first month and 4 in the third, which is the curve to expect as the common questions get covered.
Frequently asked questions
How long should a call-handling knowledge base be?
Long enough to cover what callers actually ask and short enough to search mid-call. Forty to eighty short entries is typical for a small firm. If an entry runs past a paragraph, split it.
Who should own the knowledge base?
One person with the authority to approve changes, usually the managing partner or the office manager, with a named owner for each section. Changes to fee language, declines and escalation need a lawyer's sign-off.
Can we just give the answering service our website FAQ?
No. The website is written for prospects deciding whether to call. The knowledge base adds internal handling: who gets which call, what never gets said and where declined callers go. Build the website FAQ from the knowledge base, not the other way round.
What can staff say about fees?
Trained, supervised nonlawyers can handle general questions about the fee agreement under ABA Formal Opinion 506. Fee negotiation, interpreting the agreement and what services the caller needs go to a lawyer[2].
How do we keep an automated assistant inside the knowledge base?
Give it only approved text, test it with off-script questions before it takes real calls, and review its calls. Supervision should match how much the system does on its own[6].
References
U.S. Bureau of Labor Statistics (2026). Employee Tenure in 2026 (Table 1: median years of tenure with current employer by age) (opens in a new tab) ↑
American Bar Association Standing Committee on Ethics and Professional Responsibility (2023). ABA Formal Opinion 506: Responsibilities Regarding Nonlawyer Assistants (opens in a new tab) ↑
The State Bar of California (2026). California Rules of Professional Conduct (2026) (opens in a new tab) ↑
The Florida Bar (2024). Florida Bar Ethics Opinion 24-1 (opens in a new tab) ↑
Stanford Institute for Human-Centered Artificial Intelligence (HAI) (2024). AI on Trial: Legal Models Hallucinate in 1 out of 6 (or More) Benchmarking Queries (opens in a new tab) ↑
The State Bar of California, Standing Committee on Professional Responsibility and Conduct (2026). Practical Guidance for the Use of Generative Artificial Intelligence in the Practice of Law (opens in a new tab) ↑