Research question: How much should a nonlawyer answering agent collect before a law firm performs its own conflict review and decides whether to speak with a prospective client?

The first call creates tension between access and restraint. A firm needs enough information to identify the people and matter involved. The caller often wants to explain the entire dispute. Collecting a long narrative before the firm checks conflicts may expose information that the firm did not need and cannot use. Collecting too little can produce duplicate callbacks and an unreliable search.

Methodology and evidence scope: This review uses the American Bar Association's Model Rules 1.18, 1.6, and 5.3, along with Formal Opinion 492. These are influential professional-responsibility sources, but jurisdictions adopt and interpret their own rules. The material does not establish a universal intake form and is not legal advice. Each law firm must have qualified counsel set its policy.

Prospective-client information can matter before engagement

ABA Model Rule 1.18 addresses duties to prospective clients. Its text and comments show why a conversation can create responsibilities even when no lawyer-client relationship follows. Model Rule 1.6 addresses confidentiality, and Rule 5.3 addresses lawyer responsibilities regarding nonlawyer assistance. Formal Opinion 492 discusses prospective-client communications and the significance of information solicited through a lawyer's electronic presence.

The operational inference is that an intake channel should not invite unlimited facts before the firm decides what it needs. A greeting that says "tell us everything that happened" creates a different information flow from a structured request for names, general matter type, opposing parties, jurisdiction, deadline awareness, and safe callback details.

An answering service cannot decide whether a legal conflict exists. It can capture the identifiers the firm has specified and route them to the designated reviewer. The firm owns the search logic, treatment of related entities and aliases, waiver decisions, and any conclusion about representation.

Design the first layer around identification

A restrained intake starts with the caller's name and contact preference, then asks for only the matter identifiers the firm requires. Depending on practice, that may include business entities, adverse parties, related people, case number, court or agency, and a broad matter category. The exact fields should come from the firm.

Names require careful read-back. Legal entities may have punctuation, trade names, subsidiaries, or similar spellings. The agent can ask the caller to spell a name and state the relationship in ordinary terms. The agent should not decide that two entities are legally the same or that one can be omitted.

Dates need similar discipline. A caller may mention a hearing, response date, limitation concern, closing, or other time-sensitive event. The agent should capture the date and the caller's description, mark it under the firm's urgency rule, and avoid calculating a deadline or telling the caller how much time remains. "Caller reports a hearing on September 2" preserves the fact reported. "The filing deadline is September 2" may be a legal conclusion.

The script should interrupt oversharing politely. An agent might say that the firm first needs basic names and matter information and that a lawyer will decide the next step. This is not a guarantee that a lawyer will accept the matter or return the call by a specific time unless the firm has authorized that promise.

Disclaimers do not replace workflow controls

A non-engagement statement can clarify the channel, but it cannot retrieve information already collected or correct a message sent to the wrong recipient. Operational controls still matter: limited fields, approved destinations, access restrictions, retention rules, and a process for accidental disclosures.

The answering service should know which statements it may make. It can explain that it is collecting preliminary information for review. It should not say that the firm represents the caller, that the matter is strong, that a conflict is cleared, or that the caller can rely on a legal deadline calculation. It should not recommend strategy or advise the caller to contact another party.

If the caller describes imminent physical danger or another emergency, the firm needs a prepared instruction that distinguishes emergency resources from legal intake. The answering agent applies that instruction without attempting to assess legal merits.

Quality review can test whether the agent used the approved greeting, captured required identifiers, read back critical spellings, limited narrative, flagged a caller-reported date, selected the correct practice route, and avoided engagement or advice language. It can also test whether the message reached the authorized conflict-review group.

The audit should not score whether the firm made the correct conflict determination. That is outside the answering service's competence and evidence. Nor should reviewers search the broader client database unless access and purpose authorize it.

A useful disposition set distinguishes preliminary intake received, more identifiers needed, sent for conflicts review, attorney review requested, outside stated practice area, and emergency instruction provided. Final representation status belongs in the firm's system. Connecting these stages requires controlled identifiers and access.

Scenario tests can reveal script pressure points. Use fictional parties and matters, and prevent tests from entering a real lead or consultation workflow. One scenario might include a caller who begins volunteering strategy; another might contain several related companies; a third might report a near-term court date. The test asks whether the agent returns to the approved intake, not whether the agent solves the matter.

Facts, analysis, and uncertainty

The facts are what the cited rules and opinion state within their scope. The design recommendations are operational analysis derived from the risks those sources describe. A specific jurisdiction may treat prospective-client information, screening, consent, nonlawyer services, advertising, and record retention differently.

Even a well-designed first layer cannot eliminate all risk. Callers may disclose sensitive facts before the agent can redirect them. Names may be incomplete or false. A conflict database may not contain every related party. The phone system can also route recordings, transcripts, or voicemail copies outside the intended intake record.

Sources reviewed

Limitations

ABA Model Rules are models, not the governing law in every jurisdiction. Formal Opinion 492 focuses on prospective-client communications and does not certify any answering workflow. This review does not cover privilege law, conflicts doctrine in detail, multijurisdictional practice, advertising rules, data breach duties, or litigation holds.

There is no source-backed ideal number of fields or maximum call length. A practice handling organizational investigations may need different identifiers from a neighborhood estate-planning practice. Firms should document their choices and have counsel review them.

Evidence-led conclusion

The evidence favors a limited first layer that identifies the caller, involved parties, broad matter, caller-reported timing, and safe callback route without soliciting a full case history. AnsweringServiceStaff can execute that structured capture and deliver it to the firm's authorized reviewer. The firm must decide conflicts, engagement, advice, and deadline treatment. Keeping those roles separate improves both caller clarity and the quality of the record presented for legal review.