11/18/2026
7 Instructions for Court and Opposing-Counsel Calls to a Small Law Firm
Court and opposing-counsel calls need a professional-contact route, not a prospective-client questionnaire. These seven instructions help an AI receptionist identify the stated role, capture a concise reason for the call, and follow the firm's transfer or message rules.

By Michael Brunman, Co-Founder & CEO of Clerx, Former Litigator
Court and opposing-counsel calls need a professional-contact route, not a prospective-client questionnaire. An AI receptionist should identify the caller's stated role, capture a concise reason for the call, follow the firm's transfer or message instructions, and avoid disclosing matter information or making commitments it is not authorized to make.
For a solo attorney, this can be a decisive buying concern. Missing a potential client is costly, but putting a court clerk through a long lead-qualification script creates a different operational problem. A firm evaluating automated answering needs to test both experiences.
The seven instructions below define a practical branch for professional callers. They are recommended operating rules for the firm to approve, not legal advice or a claim that software authenticates a caller merely from the organization they name.
Why professional calls deserve their own branch
A small consumer-facing firm may use one telephone number for prospects, current clients, courts, government offices, opposing counsel, referral lawyers, and vendors. Answering the call is only the first step. The next question must fit the caller's purpose.
The broader law-firm call-routing guide identifies these categories. This article goes deeper on a narrow deployment question: what should the assistant do when the caller says they are contacting the firm in a professional role?
ABA Model Rule 1.6 is relevant to protecting information. Model Rule 5.3 addresses responsibilities regarding nonlawyer assistance. These are model-rule references for the responsible lawyer's review, not a universal script that satisfies every jurisdiction or communication scenario.
1. Recognize the stated role before collecting a story
Begin with the caller's name, organization, intended recipient, and broad purpose. Once the person identifies a court, attorney's office, or another professional role, stop asking whether they need to hire the firm.
Suggested wording is brief: “Thank you. Which attorney or team are you trying to reach, and what should I tell them the call concerns?” The firm can approve variations for its own work.
Do not require a court clerk to select the firm's practice area or explain how they found the website. Those questions belong to a different intake purpose. Similarly, do not put an opposing lawyer through a consultation-booking flow because the caller mentions a family or probate matter.
Clerx's inbound receptionist supports configured routing instructions. The firm's demonstration should show that this branch actually replaces the new-prospect questions for the relevant caller.
2. Treat the caller's identity as reported, not verified
A caller saying they are from a court does not establish authentication. Capture their stated role and callback details, but do not disclose information from the firm's records merely to help confirm who they are.
The firm should decide how its people verify a professional contact when verification is needed. That may involve using a known channel or another approved process. The assistant should not invent a verification method or claim a successful identity check from caller ID alone.
A suitable summary can say, “Caller stated they are contacting the office from the court clerk's office.” It should not silently turn that into “verified court instruction.”
The receptionist security checklist is useful during purchasing. Ask which information the assistant can access, what it may reveal, and how staff review uncertain calls. Do not assume that an integration makes all matter details appropriate to discuss.
3. Collect the minimum useful routing context
Professional callers may supply an attorney name, a reference, a short message, and a callback number. The firm should define what it needs to locate the work without asking for an unnecessary account of the underlying dispute.
If a caller begins giving substantive information, the assistant can preserve the broad purpose and follow the approved transfer route. It should not cross-examine the caller or interpret the legal significance of the message.
A professional-contact branch may use fewer questions than new-client intake. That is a sign of appropriate design, not necessarily a loss of structure.
The intake question framework provides a useful principle: collect information because it serves the next authorized action. Do not ask every caller every question simply because the form has a field for it.
4. Set a real priority rule and a reachable destination
The responsible lawyer should identify which professional calls receive an attempted transfer, which go to a designated team, and which can be handled as messages. “Court call” should not be a vague label with no destination behind it.
Different requests can have different urgency. The assistant should follow the firm's explicit triggers rather than decide what is legally urgent from a stressed voice or a reference to a case. Preserve the caller's stated timing, including uncertainty, without calculating a deadline or assuring the caller that it can wait.
The warm-transfer decision guide helps distinguish transfer, booking, and message outcomes. For professional calls, the important question is whether the intended person or backup is actually available under the firm's coverage plan.
Do not promise immediate access to an attorney if the destination regularly goes unanswered.
5. Avoid substantive commitments and disclosures
Reception should not accept a proposed settlement, agree to a scheduling change on an attorney's behalf, confirm a legal position, or supply matter information outside the approved scope. The assistant can record a request and identify the person authorized to respond.
A caller asking whether the firm agrees to a new date may need a prompt human response. That does not authorize the assistant to give the answer. Similarly, “please confirm you received this” can involve a different action from actually acknowledging receipt through the firm's legal process.
ABA Model Rule 4.2 addresses certain communications with represented persons. Its application belongs to the lawyer. The operational implication here is narrow: do not let a generic receptionist script improvise substantive communications with adverse or represented parties.
Keep a route for callers whose role is unclear or changes during the conversation. A professional title should not bypass the firm's safeguards.
6. Define the failed-transfer and after-hours response
A transfer attempt is not a completed handoff. Specify what happens if the attorney is in court, the office is closed, or the backup does not answer. The assistant should explain the actual available next step.
Suggested wording might be, “I can record your message for the team and follow the firm's contact instructions.” The approved version should identify a realistic response expectation where one exists. It should not guarantee that someone has seen the message.
The caller-requests-a-human guide distinguishes human-contact routes. Human fallback in this article means the firm's people or its separately arranged coverage. It does not imply that Clerx supplies a staffed human answering team.
For urgent exceptions, the firm needs a reachable, maintained process. Adding more emphatic language to a message does not repair an unavailable destination.
7. Keep the message separate from a new sales lead
A court or opposing-counsel interaction should not inflate the firm's prospect count or start an ordinary marketing follow-up. Staff need to see its role, purpose, timing as reported, transfer result, and unresolved request.
Decide which supported record or notification route holds that information. The integration should be demonstrated for the intended workflow rather than assumed to update every existing matter correctly.
The intake metrics guide helps distinguish interactions from opportunities. A higher number of records is not automatically more potential clients.
If the system cannot classify these calls in the desired destination automatically, document the staff review step before deployment. A workable manual exception process is better than a silent category error that the team discovers later.
Test this branch before routing the public number
Use fictional professional calls in the firm's go-live testing. Try a court clerk asking for a specific lawyer, opposing counsel requesting a callback, an unknown caller claiming to represent another party, and a person who refuses to provide much detail.
Inspect the entire result. Did the assistant stop asking prospect questions? Did it state uncertainty accurately? Did it attempt the right destination? If the transfer failed, did the caller hear a truthful explanation? Can staff find the resulting message?
Do not use a real matter or impersonate a real court contact for an unnecessary test. A fictional reference and the firm's approved scenarios are enough to evaluate the operational branch.
Keep one owner for professional-routing changes
A lawyer's availability, backup person, or office number can change. Review those settings when the underlying staffing arrangement changes, not only when a caller complains.
The script-change approval process helps prevent inconsistent instructions across staff and channels. Have the responsible person approve the professional-call branch, including what reception must not say.
The firm's response ownership policy should also explain how pending messages are reviewed. A professional call should not depend on someone noticing an item in a sales queue by chance.
Measure wrong routing, failed transfers without clear next steps, and messages requiring correction. These are proposed quality checks, not published Clerx results or a guarantee that every call will be handled without error.
Handle limited information without improvising
Some professional callers will give only a name and a request to speak with the lawyer. The assistant should not manufacture a case description to satisfy a required intake field. Record the limited information, follow the approved destination, and let staff decide whether more detail is needed. If the caller declines to leave a message, preserve the actual outcome. Do not label the interaction a completed handoff merely because the system answered and asked its questions.
Frequently asked questions
Should court callers complete new-client intake?
They should follow the firm's professional-contact branch. Ask the information needed to reach the appropriate person rather than running a prospective-client questionnaire.
Can caller ID prove someone is from a court?
Do not treat it as conclusive authentication. Capture the stated identity and follow the firm's approved verification process when one is needed.
Can an AI receptionist discuss an existing case with opposing counsel?
Only operate within the firm's approved scope. Substantive communications, disclosures, and legal commitments should reach the authorized lawyer or team.
Does every professional caller need an immediate transfer?
The responsible lawyer should define the priority and destination for each type of request. Do not promise an immediate handoff when nobody is available to receive it.
What if the caller reports an urgent date?
Preserve what the caller says and follow the firm's escalation instructions. The assistant should not calculate legal deadlines or decide that a delay is safe.
Should these calls create marketing leads?
Ordinarily they serve a different business purpose. Decide the supported record and review route deliberately so professional interactions are not treated as new prospects by mistake.
Does human fallback mean Clerx provides live receptionists?
No such claim is made here. The fallback should identify the firm's people or its separately arranged service and reflect their actual availability.
What is the most useful demo scenario?
Use a fictional professional caller, then follow the call through routing, failed-transfer behavior, and the message staff receive. Inspect the real outcome rather than a generic feature list.
About the author
Michael Brunman is Co-Founder & CEO of Clerx, helping law firms improve client intake and communication. A former litigator, software engineer, and McKinsey consultant with an MBA from Harvard Business School, he brings legal, technical, and business experience to the challenges of running a law firm.
Recommended Posts
11/21/2026
Clerx vs Specialty Answering Service: Legal AI Intake, Live Reception, and Hybrid Options
Compare the actual intake workflow, human fallback, legal-software handoff, and complete cost rather than reducing this choice to AI versus people.
11/20/2026
Lawmatics Form Submission vs AI Field Updates: Why an Intake Automation May Not Run
Information can arrive successfully while the event your next workflow expects never occurs.