A personal injury firm can manage an unreachable-client exception with one source-linked contact record, approved channels, confidentiality limits, visible escalation triggers, and lawyer-controlled decisions. Support staff can document attempts and prepare the record. They should not treat silence as consent, disclose matter details to an unapproved person, decide withdrawal, or take another consequential legal step.
Scope: This is a jurisdiction-neutral legal-operations framework, not legal advice. The responsible lawyer must apply the engagement terms, controlling professional rules, court rules, deadlines, client circumstances, and applicable law.
Why ordinary communication tracking is not enough
Routine status updates and an unreachable-client exception solve different problems. A regular cadence tells a client what is happening. An exception begins when the firm needs the client’s response but cannot establish a reliable two-way connection.
The underlying evidence can fragment quickly. A call log shows a voicemail. An email platform reports delivery without confirming that the client read it. A text fails after a telephone number changes. Certified mail returns. A family member calls, but the file does not show permission to discuss the matter.
Public paralegal discussions describe clients who “went MIA,” disconnected phones, unanswered emails, and returned mail. Other contributors describe calls, texts, and emails that produced no response until a lawyer became involved. These observations identify operational pain. They do not prove what any firm must do.
The control objective is narrower: make the facts visible so the responsible lawyer can choose the next lawful action.
What the control record should contain
Open one exception record tied to the matter. Do not scatter its state among personal inboxes, sticky notes, and disconnected tasks.
Contact and preference facts
Record each client-provided telephone number, email address, mailing address, portal account, language preference, accessibility need, safe-contact restriction, and preferred channel. Link each fact to its source and last confirmation date.
Do not mark a channel “valid” merely because the system accepted a message. Use separate evidence states:
- attempted;
- technically delivered;
- failed or returned;
- acknowledged by the client;
- client identity verified; and
- response received and routed.
Alternate-contact authority
If the client has designated an alternate person, preserve the designation, permitted purpose, disclosure limit, effective date, revocation status, and lawyer-approved script. The record should not convert “emergency contact” into blanket permission to discuss the representation.
New York State Bar Association Ethics Opinion 1189 says New York lawyers may ask a client to designate an alternate contact and discusses limited disclosure when ordinary methods fail. That opinion is New York guidance, not a nationwide rule. It also recognizes that confidentiality can depend on context. Read NYSBA Opinion 1189.
Matter-state and decision facts
Show why a response is needed without embedding unnecessary confidential narrative in a broadly visible queue. Include:
- the responsible lawyer;
- the requested client input or authority;
- any lawyer-entered timing constraint;
- open court, carrier, treatment, discovery, or settlement event;
- last verified two-way communication;
- attempts and delivery evidence;
- confidentiality or safety restriction;
- next review time;
- lawyer instruction and acceptance; and
- resolution or closure evidence.
How the escalation workflow operates
1. Detect the exception
The firm should define operational triggers appropriate to its work. A trigger might be failed delivery, returned mail, an unanswered lawyer-requested decision, or repeated attempts with no acknowledgment. This article does not prescribe a universal number of attempts or days.
2. Verify the record before adding channels
Confirm that staff used the latest client-provided details, approved systems, appropriate language, and any documented safe-contact limits. Check for recent portal activity, returned correspondence, hospitalization information voluntarily provided to the firm, or another verified explanation.
Do not use an unapproved people-search result as if it were client authorization. Do not reveal the representation merely to test a possible number or address.
3. Reconcile contact evidence
Create a chronological view of every attempt. Preserve the content version, attachments, sender, recipient, timestamp, channel, delivery state, and response. Duplicate tasks should collapse into the same record instead of generating competing outreach.
4. Route the exception to the lawyer
The lawyer should see the matter event, evidence, failed channels, confidentiality limits, and proposed administrative next steps. The lawyer decides whether another communication is appropriate and what content it may contain.
ABA Model Rule 1.4 describes lawyer duties concerning communication with clients. It is a model rule; a firm must confirm the binding jurisdiction’s version. Review ABA Model Rule 1.4.
5. Use an approved alternate-contact lane
When the responsible lawyer authorizes it, support staff may use the recorded designation and approved minimal script. Staff should log exactly what was disclosed and what the alternate person reported. New information returns to the lawyer; it does not authorize the alternate person to direct the representation.
ABA Model Rule 1.6 addresses confidentiality of information and includes exceptions and authorization concepts. Binding rules and facts control. Review ABA Model Rule 1.6.
6. Hold consequential action for legal review
A failed-contact state must not silently become client consent. Place a visible hold on any lawyer-identified action requiring client instruction, authority, advice, notice, or a court determination. The lawyer decides whether and how the matter may proceed, including any withdrawal analysis or filing.
7. Record the resolution
When contact resumes, verify the person through the firm’s approved process. Record updated contact preferences, the client’s response, lawyer follow-up, and whether any pending action remains held. If the exception ends another way, preserve the lawyer’s instruction and final evidence.
Workflow at a glance
- Detect failed or unacknowledged contact
- Verify client-provided channels and restrictions
- Reconcile attempts and delivery evidence
- Route the exception to the responsible lawyer
- Use only an approved alternate-contact lane
- Hold consequential action pending legal review
- Verify restored contact and record resolution
Who owns each decision
| Control | Support or operations staff | Responsible lawyer | Technology |
|---|---|---|---|
| Contact facts | Enter source-linked facts | Set collection and verification policy | Preserve history and permissions |
| Attempts | Send approved communications and log evidence | Approve sensitive content and escalation rules | Capture delivery states without overstating them |
| Alternate contact | Confirm a recorded designation exists | Decide permission and disclosure scope | Restrict fields and retain audit history |
| Matter action | Assemble the exception packet | Decide advice, authority, filing, withdrawal, or other legal response | Apply a hold; never clear it independently |
| Resolution | Verify and document restored contact | Confirm legal follow-up | Close tasks only after required acceptance |
ABA Model Rule 5.3 describes lawyers’ managerial and supervisory responsibilities concerning nonlawyer assistance. Firms must apply the adopted jurisdictional rule and their circumstances. Review ABA Model Rule 5.3.
How technology can support the process
Technology can combine channel events, flag returned communications, maintain version history, calculate exception age, enforce role-based access, and route packets. It can also require lawyer acceptance before a hold changes state.
Automation should not infer consent from message delivery. It should not contact newly discovered people, broaden disclosure, decide that a client abandoned a matter, or initiate a consequential filing. Those steps involve facts, law, professional responsibility, and client interests that require lawyer judgment.
Security design should minimize what appears in shared queues. Use firm-approved systems, access controls, retention rules, and audit history. Confirm integrations before relying on them; a sync failure can make an active response look absent.
Which KPIs reveal control health
Metrics should reveal process health without creating a legal benchmark.
Measures to define
- Evidence-complete attempt rate: Percentage of logged attempts containing channel, recipient, timestamp, content version, and delivery state
- Exception age: Elapsed time since the exception entered its current lawyer-defined state
- Lawyer acceptance coverage: Percentage of consequential-action holds with a linked lawyer instruction or acceptance
- Reopened exception rate: Percentage of closed exceptions reopened because contact or decision evidence was incomplete
An accessible dashboard should show counts and aging by team, owner, evidence state, and escalation reason. Use text labels with color. Permit keyboard access to the underlying record. Keep confidential details out of overview cards.
Review queue indicators
- delivery evidence state
- confidentiality restriction
- lawyer acceptance
- consequential-action hold
- exception age
Which exceptions need immediate review
Route these conditions under the firm’s lawyer-defined priority rules:
- a lawyer-entered deadline or scheduled event is approaching;
- the firm needs client authority or instructions;
- mail returned and electronic channels also failed;
- an alternate person requests details beyond the approved script;
- the client previously identified safety or privacy restrictions;
- communications may be reaching a shared device or adverse person;
- a new address or number cannot be verified;
- someone reports incapacity, detention, hospitalization, or death;
- the client responds with a complaint, changed objective, or termination request; or
- the record and an external system show conflicting delivery states.
An exception label is not a legal conclusion. It tells the right lawyer where judgment is needed.
How to implement the workflow
- Map every contact channel and system of record.
- Define evidence states separately from task completion.
- Have counsel approve escalation triggers and message templates.
- Record client preferences, safety limits, language needs, and alternate-contact designations.
- Create role-based access for contact and matter details.
- Require a linked lawyer instruction for consequential-action holds.
- Test returned mail, failed SMS, bounced email, and conflicting-system scenarios.
- Train staff to disclose no more than the approved script permits.
- Audit closed exceptions for evidence and acceptance gaps.
- Revalidate the workflow against each jurisdiction and matter type.
This model fits firms with several teams, channels, and handoffs. It may be excessive for a small caseload managed directly by one lawyer in one complete system. It is not a substitute for legal analysis, client advice, court procedures, or emergency planning.
For related operational guidance, visit our personal injury legal operations resources. Firms evaluating structured administrative capacity can explore personal injury law firm support and supervised virtual legal assistant services. Any engagement should begin with lawyer-defined scope, access, escalation, and review controls.
Frequently asked questions
What should a personal injury firm record when calls, emails, texts, and mail go unanswered?
Record the source contact details, content version, sender, recipient, timestamp, channel, delivery evidence, acknowledgment state, restriction, owner, escalation, and lawyer instruction. Do not equate a sent or delivered message with verified client receipt.
When may support staff use a client-designated alternate contact?
Only within the firm’s lawyer-approved process and the recorded designation’s scope. The lawyer should determine what the applicable rules and circumstances permit. Staff should use minimal approved language and log the disclosure.
Can silence be treated as authority to proceed?
This workflow does not treat silence as consent or client authority. The responsible lawyer must decide what the engagement, governing law, professional rules, court procedures, and circumstances require.
Can an assistant decide that the firm should withdraw?
No. An assistant can assemble contact evidence and route the exception. A lawyer must analyze and direct any withdrawal-related action, including required client or court communications.
Should a firm prescribe the same attempt count for every matter?
Not as a universal legal rule. Firms can define operational triggers, but lawyers must account for jurisdiction, urgency, client restrictions, pending events, and matter-specific risk.
Sources and disclosure
- American Bar Association, Model Rules 1.4, 1.6, and 5.3. Model guidance only; adopted jurisdictional rules control.
- New York State Bar Association, Ethics Opinion 1189, May 22, 2020. New York ethics guidance only.
- Public community sources this workflow-SRC-001 through 003 informed pain language only and are not legal authority.
