A legal answering service can welcome callers, capture contact information, identify a general matter type, route existing clients, and schedule an approved consultation. It should not tell a caller that the firm represents them, assess the merits of a claim, calculate a filing deadline, or give legal advice. Those boundaries are central to a trustworthy law firm answering service.
This guide offers operational questions and tests, not legal, ethics, privacy, or compliance advice. Professional duties and advertising rules vary by jurisdiction and practice. Have responsible lawyers and qualified counsel approve the workflow. Begin with the AI receptionist implementation guide, then compare service models and contract terms in the phone answering service buyer’s guide.
Define what the legal receptionist may and may not do
Write a permitted-scope statement in plain language. It might authorize the receptionist to provide published office information, collect a prospective client’s basic details, record an existing client’s request, and offer approved consultation times. It should list prohibited outcomes just as clearly.
- Do not state or imply that an attorney-client relationship exists.
- Do not evaluate a caller’s rights, strategy, likely result, or case value.
- Do not calculate, interpret, or promise action on a legal deadline.
- Do not promise that the firm will accept a matter or keep a consultation time until the actual workflow confirms it.
- Do not collect a complete sensitive narrative before the firm has determined what intake is appropriate.
- Do not reveal whether a named person or company is a client unless the firm has expressly authorized the response.
Use approved fallback language: the service can record a question for review, but cannot answer it as legal advice. If a caller needs immediate legal help or faces a possible deadline, the script should explain the actual staffed route without guessing how much time remains.
Build conflict-aware intake without promising representation
A legal intake service should collect only the information the firm has approved for the stage. Many firms need the prospective client’s name, reliable callback details, general matter category, opposing or related party names for a conflict process, relevant jurisdiction, and a concise description. The exact fields vary, and more detail is not automatically better.
Make the sequence explicit:
- Identify the firm and explain the purpose of the call.
- State approved limitations before requesting sensitive detail.
- Collect identity and conflict-check fields in the firm’s chosen order.
- Stop or reroute according to the firm’s conflict workflow.
- Collect only the remaining fields authorized for that outcome.
- Read back critical names, numbers, dates, and email addresses.
- Explain the next step without implying engagement.
Do not design the receptionist to decide whether a conflict exists. It can support the firm’s intake process, but a firm-approved system or person must own that determination. Test alternate spellings, former names, organizational parties, and multiple people in one matter.
Protect confidentiality and minimize sensitive data
The American Bar Association’s Model Rule 1.6 addresses confidentiality of information. ABA model rules are not themselves the law in every jurisdiction, so firms must review the rules and authorities that apply to them. Use the issue as a concrete vendor-review prompt rather than relying on a generic statement that calls are “secure.”
Map every place call information travels: carrier, recording, transcription, model processing, summary, email, text, CRM, case-management system, backup, support access, and analytics. Ask which people and subcontractors can access each copy, how access is logged, where data is stored, how long it remains, and how deletion and export work.
Collect the minimum useful information at the correct stage. A short initial description may be enough to route a lead for lawyer review. Detailed facts, documents, identification numbers, payment details, or privileged communications may require a separate authorized channel. Disable recording or transcription for workflows where the firm decides it is inappropriate.
Handle urgent calls and potential deadlines safely
Callers may mention a hearing, arrest, court date, notice, limitation period, threat, or other urgent event. A receptionist should not convert those statements into legal conclusions or compute deadlines. Build approved keyword and intent triggers that route the call or message with an urgency label, while making clear that delivery does not establish representation or guarantee a response by a particular time.
Document the primary destination, staffing hours, retry sequence, secondary destination, message method, and final caller wording. Test the workflow after hours and while the main recipient’s phone is unavailable. If the firm provides an emergency contact route for existing clients, verify identity and route according to the firm’s rules without exposing confidential client status.
Distinguish a high-priority message from an emergency service. For threats to immediate safety, the firm should approve appropriate public-emergency language. The receptionist should not keep a distressed caller in an extended marketing intake or attempt crisis counseling beyond that approved direction.
Create routing that reflects the real firm
A law firm may route by new versus existing client, practice area, location, court, language, attorney, or matter status. Use categories callers understand rather than forcing internal department names. Ask one question at a time, and do not make a caller repeat facts merely because a transfer failed.
| Caller type | Receptionist outcome | Fallback |
|---|---|---|
| Prospective client | Conflict-conscious intake and approved next step | Review request without promise of representation |
| Existing client | Verify and route under firm policy | Protected message to the assigned destination |
| Court, counsel, or vendor | Capture identity and route by firm rules | Complete message with verified callback |
| Unsupported practice area | Use approved neutral wording | No improvised referral or legal opinion |
| Potential urgent matter | Trigger approved priority path | Disclose the actual delivery and response expectation |
For multilingual intake, determine whether the entire workflow or only the greeting is available in each language. The bilingual answering service guide explains how to test translated policies, names, handoffs, and language-specific gaps.
Keep published information accurate and qualified
Give the attorney answering service approved office hours, holiday exceptions, locations, practice areas, consultation-request rules, accessibility details, payment methods, and routing contacts. Separate factual information from advertising copy. A phrase such as “aggressive representation” should not be converted into a promise about approach or outcome.
The ABA’s Model Rule 7.1 addresses communications concerning a lawyer’s services. Again, the applicable requirements come from the relevant jurisdiction. Have the firm approve every description, comparison, testimonial reference, fee statement, and consultation claim used by the receptionist.
Attach an owner and review date to high-impact knowledge. When a lawyer leaves, office closes, fee changes, or practice area is paused, update the authoritative source and test the caller response. Keep a rollback version and an audit record of who approved the change.
Test a law firm answering service with difficult cases
Use fictional callers and matters in an isolated environment. Do not put real client information into a demo. Include straightforward leads, existing-client calls, potential conflicts, unsupported practice areas, emotionally distressed callers, unclear deadlines, misspelled party names, background noise, corrections, and a failed transfer.
Score whether the service:
- Used the firm’s approved limitation language naturally
- Captured conflict-check names and callback details accurately
- Avoided promising representation, advice, deadlines, or outcomes
- Sent the intake to the right practice and geographic destination
- Protected information when identity or client status was uncertain
- Explained whether a consultation was requested or confirmed
- Recovered from an unavailable calendar, CRM, or attorney
- Escalated according to the documented urgent-call rule
Use the NIST AI Risk Management Framework to structure ongoing AI governance, measurement, and change control. It is not a legal-industry certification. The responsible lawyers must decide whether the evidence supports the intended use.
Compare cost against qualified follow-up
A low per-minute rate can hide incomplete intake, duplicate records, poor conflict fields, or messages that nobody owns. Define a useful outcome: a lead contains the approved minimum fields, reaches the correct review queue, and receives an accurate expectation. Track repair time and missed follow-up alongside service fees.
Normalize subscription, included usage, overages, setup, integrations, phone charges, custom workflows, human-agent premiums, and contract terms. Use the cost calculator and quote checklist, and require a demonstration in the real intake system.
Start with a controlled call group, keep human review, and make rollback easy. Review outcomes daily during the pilot. Fix recurring problems at the source—knowledge, intake order, route, or staffing—rather than layering vague instructions onto the greeting.
Use a firm-approved launch checklist
- Approve permitted actions, disclaimers, and prohibited responses.
- Define conflict fields and the point where intake stops or changes.
- Map urgent, existing-client, new-lead, and failed-transfer routes.
- Review vendors, data flows, access, retention, and contracts.
- Approve all practice, consultation, and fee descriptions.
- Run fictional test matters through the real downstream systems.
- Pilot narrowly and expand only after lawyer review of evidence.
Explore Receptionist Max’s call-handling features and knowledge configuration workflow. If the scope fits, create an isolated workspace for test calls. The firm remains responsible for approving its use, supervising workflows, and meeting applicable professional and legal obligations.
Sources and further reading
- American Bar Association: Model Rule 1.6, Confidentiality of Information
- American Bar Association: Model Rule 7.1, Communications Concerning a Lawyer’s Services
- National Institute of Standards and Technology: AI Risk Management Framework
- National Institute of Standards and Technology: Cybersecurity Framework
Last editorial review: August 2026. This educational guide is not legal, ethics, privacy, security, or compliance advice. Rules differ by jurisdiction; obtain review appropriate to your firm and intended use.
This guide provides general operational information, not legal, medical, accounting, or regulatory advice. Requirements vary by industry and location; verify the rules that apply to your business.
