On this page
A law firm's phone assistant can be evaluated for office information, callback requests, and limited intake approved by the firm. It should not independently advise a caller, assess the merits of a matter, calculate a legal deadline, or imply that representation has been accepted.
The first design decision is what the firm wants to learn before an attorney or trained intake professional takes over. More information is not automatically better, particularly before the firm's conflict and confidentiality procedures have been applied.
This guide is an operational planning aid. Applicable professional rules and the actual implementation require review by the responsible attorneys. Sources were reviewed on September 6, 2026.
Separate new enquiries from existing matters
Existing clients, prospective clients, opposing counsel, courts, vendors, and other callers need different routes. A generic “new lead” flow may mishandle a message about an active matter or a time-sensitive communication.
Identify the caller's requested team or purpose using the firm's approved questions. Do not disclose whether a person is a client or reveal matter information simply because someone knows a name.
For prospective clients, collect only the preliminary information the firm has authorized at that stage. The assistant should explain the actual next step without promising a consultation, engagement, or outcome that has not been approved.
Keep conflict review with the firm's process
A search that returns no matching name is not necessarily a completed conflict check. The firm may need related parties, former matters, different spellings, business relationships, and professional judgment.
Define what preliminary identifiers may be collected and which system or staff member performs the review. Do not let the assistant announce that the firm is conflict-free or has accepted the matter.
A useful sequence distinguishes enquiry received, preliminary review pending, consultation approved, and engagement accepted. The firm determines the actual states and wording.
Protect information before collecting a detailed narrative
ABA Formal Opinion 512 addresses duties including competence, confidentiality, communication, and supervision when lawyers use generative AI. It is model-rule guidance; the firm must assess the governing rules for its jurisdiction and circumstances.
Map the providers processing audio and text, retained records, staff access, and any connection to matter-management software. Determine approved use and necessary client communication or consent with the responsible attorney.
Do not promise that every call is privileged or that encryption alone resolves confidentiality obligations. Likewise, an automated statement that the call is “not legal advice” does not establish that the actual conversation stayed within scope.
Design the assistant's answers around office procedure
| Caller question | Bounded administrative response | Attorney-owned decision |
|---|---|---|
| Does the firm handle this practice area? | Approved description of services | Whether the specific matter is accepted |
| How do I request a consultation? | Explain the actual intake route | Approval and any engagement terms |
| What documents should I send? | Approved preliminary instructions | Which facts and documents are needed for the matter |
| What is my case worth? | Arrange professional review | Legal assessment and advice |
| What deadline applies? | Route promptly under the firm's process | Applicable law and deadline calculation |
When a caller provides a date or says a deadline is approaching, preserve it as a reported fact and send it to the designated team. Do not calculate the date independently or reassure the caller that waiting is safe.
Make consultation status accurate
A requested time is not a confirmed meeting, and a confirmed meeting is not an engagement agreement. The closing should state exactly which step was completed.
Calendar writes require an authorized operation and a verified result. A failed action should leave a visible staff-owned request rather than a false appointment confirmation.
For multi-attorney meetings, use the meeting coordination guide to define host availability and invitation states.
What QuickVoice currently supplies
The QuickVoice repository provides configurable agents, knowledge sources, phone connections, and call records. It requires technical implementation and does not supply the firm's professional judgment or conflict-review process.
The live MCP bridge restricts tools marked as writes, side effects, or requiring confirmation. Creating a matter, sending a private document, or changing a calendar needs a separately implemented permitted path.
Use synthetic matters for early evaluation. Review the call-data checklist against the firm's actual obligations before real client information is introduced.
Test boundaries as carefully as routine intake
Exercise existing-client messages, prospective enquiries, opposing-party calls, incomplete names, requests for advice, a reported deadline, and an unavailable staff destination.
Have responsible attorneys review the wording and the record produced. Track misrouted messages, overcollection, incorrect statements, unresolved handoffs, and staff follow-up effort. Do not count enquiries as retained clients or assume a particular revenue gain.
To assess a pilot, discuss one administrative intake route with the firm's approved questions, conflict process, data requirements, and attorney handoff responsibilities.
Rahul Agarwal
More industry guides guides