Create one contact record before anyone responds. Match the caller and claim to the matter, classify the request, and apply a counsel-approved response boundary. Administrative staff can capture facts and handle permitted logistics. Questions involving advice, strategy, liability, valuation, negotiation, disclosure, or uncertainty move to a named lawyer and stay open until that lawyer accepts them.
Scope: This is an operational control, not legal advice. Supervising counsel defines who may communicate, what information may be disclosed, which subjects require a lawyer, and how local law and professional rules apply. A logged call does not prove an insurer received, accepted, or acted on anything.
Why adjuster contacts become control failures
An insurer call rarely arrives as a perfectly framed task. The caller may omit a client name, use a different claim identifier, request a status update, ask for records, raise coverage, mention an offer, or combine logistics with a substantive question.
The first worker then faces several decisions at once. Who is calling? Which matter is involved? Is the caller authorized? What may the worker confirm? Does the question require counsel? Who owns the callback? What evidence closes it?
Community discussions show how inconsistent these boundaries feel in practice. Some staff describe taking only a file note. Others handle administrative exchanges while lawyers step in for approval or negotiation. Another account describes uncertainty after an unexpected disclosure question. These sources are unverified discovery material, not proof of proper practice. They do reveal a useful design requirement: a firm needs a visible boundary before the conversation becomes improvised.
The answer is not to send every contact blindly to a lawyer. That creates a second forwarding queue and can hide unaccepted work. The answer is not to let every worker answer from experience. That makes individual confidence the control. The better unit of work is one identified contact tied to one matter, one request class, one permitted response path, and one evidenced closure.
Define one controlled contact record
Create the record at the first inbound call, voicemail, email, letter, portal message, or planned outbound contact. Preserve the original communication when the channel allows it.
The record should contain:
- matter identifier and responsible attorney;
- insurer, caller, role, department, and verified callback channel;
- claim or reference number exactly as received;
- direction of contact and original channel;
- date, time, receiver, and source artifact;
- concise factual request in the caller's terms;
- identity and matter-match state;
- request classification and response-authority code;
- information requested or supplied;
- any counsel-approved script, template, or instruction used;
- assigned owner, acceptance time, next action, and review date;
- escalation reason and attorney decision when required;
- outgoing response evidence and closure reason;
- reopen history when facts or instructions change.
Keep three concepts separate.
| State | Operational meaning | Evidence | It does not prove |
|---|---|---|---|
| Captured | The original contact exists in the queue | Channel artifact or time-stamped note | Correct caller or matter |
| Matched | Approved identifiers connect the contact to a matter | Match fields and reviewer | Authority to disclose or answer |
| Classified | The request has a permitted route | Request and boundary code | That the classification is legally correct |
| Accepted | A named owner has taken responsibility | Acceptance event | That a response occurred |
| Responded | An approved response was transmitted | Sent artifact and version | Receipt, agreement, or legal effect |
| Closed | The permitted endpoint has evidence | Closure reason and review | That the insurer completed its next step |
Do not use “handled” as a universal state. It hides whether someone only took a message, answered a permitted question, escalated a substantive issue, or confirmed the next action.
Run the routing workflow
1. Capture before answering beyond the approved greeting
Use a standard opening that identifies the firm and the worker's role. Do not confirm representation, client data, incident facts, or claim information until the firm's identity and matter-match conditions are satisfied.
If the caller refuses identifying information, record the refusal and offer a counsel-approved message path. Pressure from a caller does not expand the worker's authority.
2. Match the caller and matter
Collect the insurer, caller name, role, callback details, claim number, named insured or claimant as permitted, and stated purpose. Compare them with the authoritative matter record.
Treat a near match as unresolved. A changed adjuster, shared claim number, mistyped name, merged insurer, third-party administrator, vendor, or unidentified department can create ambiguity. Route the mismatch rather than guessing.
3. Classify the request
Counsel should maintain a short, versioned classification set. A useful starting structure is:
- message or callback request;
- approved scheduling or contact-detail logistics;
- status category permitted by counsel;
- request for an already approved document;
- new document or information request;
- coverage, liability, causation, damages, strategy, or legal-position question;
- offer, demand, counter, release, authorization, or settlement subject;
- possible deadline or urgent fact;
- complaint, threat, dispute, or unusual conduct;
- possible privacy, security, or wrong-matter event;
- uncertain or mixed request.
The list is not a statement of law. It is a firm control that counsel adapts to the matter, jurisdiction, stage, staffing model, and local rules.
4. Apply the response-authority boundary
Map each request class to one of three outcomes.
Permitted administrative response: the worker may use current, counsel-approved facts or a versioned script. Examples should be set by the firm, not copied from another practice.
Capture and escalate: the worker records the question without analyzing or answering it. A named lawyer receives the original wording and context.
Stop and protect: the worker ends substantive discussion and routes a possible wrong-matter, unauthorized-disclosure, security, or other high-risk exception under the firm's incident procedure.
The ABA Model Rule 5.3 comments discuss instruction and supervision of nonlawyers inside and outside a firm. The ABA rules are models; jurisdictional adoption and interpretation vary.
ABA Model Rule 5.5 says a lawyer must not assist another in unauthorized practice. That model-rule statement supports keeping legal analysis and judgment with authorized counsel. It does not supply one nationwide task list for administrative staff.
5. Minimize and approve disclosures
Do not treat matter access as permission to disclose every visible field. Counsel should define the permitted information set by request type and recipient.
ABA Model Rule 1.6 addresses information relating to representation and reasonable efforts to prevent unauthorized access or disclosure. Local professional rules, law, client instructions, agreements, and matter facts control the actual decision.
When the worker is uncertain, the correct operational state is not a creative answer. It is an identified question with an accepted escalation owner.
6. Obtain accepted escalation
Sending an email or forwarding a voicemail is not acceptance. Assign the contact to a named attorney or counsel-approved queue. Require an acceptance event, a next action, and a review time.
Preserve the original question. Summaries help routing, but they should not replace the source communication when wording matters.
If an attorney returns instructions, link them to the exact contact. Distinguish a one-time direction from a reusable script. Only counsel or the authorized procedure owner should promote a one-time answer into standard guidance.
7. Respond from the approved record
Use the confirmed channel and current approved instruction. Record who responded, when, by what channel, and with which version or source artifact.
Do not turn a requested callback into an undocumented side conversation. Add any new question as a new request item or linked child contact. Mixed conversations often need more than one closure state.
8. Reconcile the next action
Close the firm-owned contact only when its permitted endpoint is evidenced. That may be a completed approved response, an attorney callback, a routed document task, a recorded refusal, or another counsel-defined result.
If the insurer promises an action, store it as a reported external next step. Create the firm's own review date. Do not mark the external action complete until evidence arrives.
Workflow at a glance
- Capture the original contact
- Verify caller and callback channel
- Match the claim to one matter
- Classify each request
- Apply the counsel-approved response boundary
- Answer permitted logistics or obtain attorney acceptance
- Preserve the approved response
- Reconcile firm and external next actions
Separate responsibilities
| Activity | Administrative or virtual legal assistant | Supervising attorney | Legal operations owner |
|---|---|---|---|
| Capture contact | Preserve identifiers, wording, channel, and artifact | Define required fields | Monitor completeness |
| Match matter | Use approved identifiers; flag ambiguity | Decide uncertain representation or disclosure issues | Maintain matching rules |
| Classify request | Apply defined codes without legal analysis | Define and approve boundaries | Version the classification map |
| Respond | Handle only approved administrative subjects | Answer legal, strategic, negotiation, or uncertain issues | Sample response evidence |
| Escalate | Assign source communication and context | Accept, decide, and document instruction | Monitor age and rejected handoffs |
| Close | Attach permitted completion evidence | Approve counsel-only closure states | Reconcile open next actions |
A remote assistant does not become the adjuster's substantive counterpart by having system access. The value lies in reliable capture, routing, documentation, and follow-through under supervision.
Design technology around the boundary
Phone, voicemail, email, portals, case management, and task tools can each hold part of the history. Choose one authoritative contact record. Link source artifacts instead of copying sensitive content into uncontrolled reminders.
Useful controls include:
- caller and domain verification fields;
- claim-number normalization without overwriting the received value;
- possible-matter-match warnings;
- role-based matter access;
- request classification with version history;
- prohibited-response banners for lawyer-only classes;
- approved scripts tied to owner and version;
- one-click escalation with acceptance tracking;
- immutable call and email notes;
- response artifact linkage;
- follow-up dates separated from external promises;
- overdue and rejected-assignment alerts;
- audit exports and reopen reasons.
Transcription can assist capture, but it creates another information copy. Counsel should approve consent, access, retention, verification, and deletion rules before use. A generated summary must not replace the original or manufacture certainty.
Measure the workflow
Define measures before setting targets. The values below are intentionally unverified.
Measures to define
- Matter-match exception rate: Share of adjuster contacts that cannot be matched using approved identifiers at first review
- Escalation acceptance time: Elapsed time from lawyer-only classification to named attorney acceptance
- Boundary override count: Contacts where the original classification or permitted-response path was changed after review
- Closed-with-evidence rate: Share of closed contacts containing the required response or closure artifact
Pair timeliness with accuracy and boundary measures. A fast but unmatched or unauthorized response is not success.
Review queue indicators
- caller identity confidence
- matter match status
- request authority class
- attorney acceptance age
- disclosure exception state
- firm and external next actions
An accessible dashboard should offer a table view, text labels, keyboard navigation, readable contrast, and mobile stacking. Color must never be the only status cue.
Handle failure modes and exceptions
The caller will not identify the matter
Record the available details and refusal. Use the approved message route. Do not search aloud through client names or confirm possible matches.
One call contains administrative and substantive questions
Split the requests. Complete the permitted logistics only if counsel's procedure allows it. Keep the substantive item open for attorney acceptance.
The worker answered before recognizing the boundary
Preserve the actual communication. Do not rewrite the note to look compliant. Route the event under the firm's correction or incident procedure and let counsel decide the response.
The adjuster changes
Verify the change through an approved channel. Preserve the previous contact history and effective date. Do not silently replace one identity with another.
The lawyer does not accept the escalation
Keep it visible. Escalate according to the backup-owner rule. A forwarded voicemail without acceptance remains open work.
The insurer promises a callback or document
Record the promise as reported, including who made it and when. Set a firm-owned review date. Do not describe the promised action as complete.
The contact may involve a deadline
Administrative staff should capture the exact statement and source. Counsel decides the legal significance, calculation, response, and calendar treatment.
The wrong matter may have been disclosed
Stop ordinary handling and preserve evidence. Use the firm's privacy or security escalation. Do not investigate beyond assigned authority or promise an outcome.
Implement the control
- Inventory every channel through which adjuster contacts arrive or leave.
- Name the system that owns the authoritative contact record.
- Have counsel define identification and matter-match requirements.
- Create a short request taxonomy using actual firm contacts.
- Map each class to permitted response, lawyer escalation, or protective stop.
- Version approved scripts and prohibit uncontrolled personal templates.
- Require named acceptance for lawyer-only work.
- Define response, external-promise, closure, reopen, and incident evidence.
- Pilot with a bounded matter group and sample every exception.
- Train with mixed and ambiguous calls, not only clean examples.
- Review access, retention, transcription, and remote-work controls.
- Revise the boundary when counsel, jurisdiction, staffing, or channels change.
Before launch, compare this workflow with the firm's representation-letter dispatch control. The two records may share identifiers, but they should not collapse into one generic “insurance task.”
Decide when this model fits
This design fits a firm with recurring adjuster communications, defined matter ownership, counsel willing to document response boundaries, and a system capable of acceptance and audit history.
It does not fit a firm expecting an assistant to decide legal positions, negotiate independently, improvise disclosure rules, or close work from memory. It also cannot fix unreliable matter data, absent attorney coverage, or unapproved communication channels by itself.
For broader workflow context, review our personal injury legal operations resources.
How Remote Legal Team LLC can support the administrative layer
Remote Legal Team LLC can discuss a supervised operating model for bounded administrative work such as capturing contacts, matching approved identifiers, applying firm-defined classifications, maintaining queues, preserving artifacts, and monitoring accepted follow-ups.
The firm supplies the systems, permissions, procedures, training, supervision, and attorney decisions. Fit, security, jurisdictional requirements, and task boundaries require firm review. No outcome, response time, or compliance result is promised.
Explore supervised virtual legal assistant support for the administrative layer of a lawyer-controlled workflow.
Frequently asked questions
What should my personal injury law firm record before anyone returns an adjuster call?
Record the caller, insurer, role, verified callback channel, claim identifier, stated matter, exact request, source artifact, and matter-match status. Add the responsible attorney, request class, permitted-response path, assigned owner, and review time. Do not treat the record as permission to disclose or answer.
How should my personal injury law firm close an adjuster follow-up when the next step requires attorney approval?
Require a named attorney to accept the source communication and decide the next action. Close the contact only with counsel-defined evidence, such as the attorney's completed response or a linked approved task. Forwarding alone is not closure.
How can my personal injury law firm distinguish administrative questions from lawyer-only questions?
Have supervising counsel approve a versioned classification map using the firm's real work. Staff apply the map without legal analysis. Coverage, liability, strategy, valuation, negotiation, disclosure decisions, deadlines, offers, releases, and uncertain mixed requests should follow counsel's designated path.
Can a virtual legal assistant negotiate with an adjuster?
This workflow does not assign independent negotiation or legal judgment to a virtual assistant. Counsel defines lawful roles and retains substantive decisions, authority, and supervision.
Does a sent email prove the adjuster completed the next step?
No. It may prove transmission if the artifact is reliable. Record delivery, response, promise, and external completion as separate states. The firm should keep its own review date until evidence supports closure.
Sources and disclosure
- American Bar Association, Model Rule 1.6: Confidentiality of Information. Current page accessed September 13, 2026. Model rule; local adoption and interpretation vary.
- American Bar Association, comments to Model Rule 5.3: Responsibilities Regarding Nonlawyer Assistance. Current page accessed September 13, 2026. Model rule commentary; local law controls.
- American Bar Association, Model Rule 5.5: Unauthorized Practice of Law; Multijurisdictional Practice of Law. Page dated April 17, 2019; accessed September 13, 2026. Model rule; jurisdictional law controls.
- this workflow-SRC-001 to 003, public community discussions captured September 13, 2026. Discovery only; roles and claims unverified.
- this workflow-COMP-001 to 003, competitor and adjacent-page capture. Discovery only; not proof for legal or service claims.
Last updated: September 13, 2026.
