Quick answer: Before booking a legal consultation, an AI receptionist should confirm the caller's name and safe callback method, the type of legal help needed, a brief summary of events, when and where it happened, who is involved, whether they already have a lawyer, and any urgent deadlines or safety risks.
Every missed or mishandled intake call is a lost matter, or a new risk. An AI voice agent can answer around the clock, but only if its script is built for legal ethics rather than generic lead capture.
Law firm intake has a constraint most industries don't. Under ABA Model Rule 1.18, a person who consults a firm about possible representation becomes a prospective client. The firm owes that person confidentiality even if it never takes the case.
That duty applies however brief the conversation is. Comment 4 to the rule advises lawyers to limit the initial consultation to information that reasonably appears necessary to decide whether to take the matter.
ABA Formal Opinion 510, issued in March 2024, sharpened that advice. It encourages lawyers to request the minimum information reasonably necessary and to warn prospective clients against sharing more than is asked.
The stakes are real. If a lawyer receives information that could be significantly harmful to the prospective client, the lawyer may be barred from representing the other side in that matter. Without reasonable precautions, the conflict can spread to the entire firm.
So the best legal intake questions do two jobs at once. They collect enough to run conflicts, route, and book, and they stop before callers reveal strategy, admissions, or settlement thinking.
Important: AI screening does not create an attorney-client relationship and does not replace attorney judgment. The AI legal receptionist gathers facts. A licensed attorney decides whether the firm accepts the matter.
1. What is your name and safest callback method?
Why it matters: Identity is the foundation of every conflict check, and a reliable callback number keeps a qualified lead from going cold. "Safest" matters too. In family, domestic violence, and employment matters, a voicemail can put a caller at risk.
Sample dialogue:
AI: "Before we begin, may I have your full name and the best number to reach you?"
AI: "Is it safe for us to leave a voicemail or send a text to that number?"
Information to capture:
Full legal name, spelling confirmed, plus any other names used
Primary phone number and email address
Voicemail and text permissions, and preferred call times
Follow-ups: If the caller hesitates, offer alternatives: a different number, email only, or a specific time window. If someone calls on behalf of a relative, record the caller and the potential client separately.
Escalate when: The caller signals fear of being overheard or says someone monitors their phone. Flag the record "no voicemail" and route it to a staff member for a discreet callback plan.
2. What type of legal assistance do you need?
Why it matters: Practice-area intent drives routing. It tells the system which attorney calendar to use, which follow-ups apply, and whether the matter falls outside what the firm handles.
Sample dialogue:
AI: "In a few words, what kind of legal help are you looking for? For example, an injury, a family matter, a business dispute, or something else?"
AI: "And which state is this matter in?"
Information to capture:
Practice area and subtype, such as a car accident versus a workplace injury
State or jurisdiction
Whether the caller is the potential client, a family member, or a business representative
Follow-ups: For vague answers like "I got sued," ask one clarifying question: "Is this about money, property, family, or your job?" Stay at the category level, not the detail level.
Escalate when: The matter is outside the firm's practice areas or jurisdictions. The AI should decline to book without commenting on the merits and offer the firm's standard referral resource, such as a bar referral service.
3. Can you briefly explain what happened?
Why it matters: Attorneys need enough context to decide whether a consultation is worthwhile. This is also where over-collection risk peaks, because callers naturally want to tell the whole story.
Opinion 510 recognizes that a modest factual inquiry is reasonably necessary. A detailed probe of likely success or damages, however, generally is not. A short summary is the target.
Sample dialogue:
AI: "In two or three sentences, what happened? Please keep it brief for now. The attorney will go through the details with you. I'm not a lawyer and can't give legal advice."
Information to capture:
A one-paragraph summary in the caller's own words
The outcome they want, such as compensation, a custody arrangement, or contract enforcement
Follow-ups: Ask only clarifying questions that affect routing or eligibility. Avoid questions about motive, private views on fault, or what the caller would accept to settle. In the record, write what the caller reported ("caller reports being terminated after raising a safety concern"), not a legal conclusion.
Escalate when: The caller starts sharing admissions, strategy, or highly sensitive personal details. The AI should gently interrupt, explain that an attorney will cover specifics, and flag the transcript for attorney review.
4. When and where did the incident occur?
Why it matters: Dates and locations shape jurisdiction, venue, and time limits. They also help an attorney gauge urgency before the consultation begins.
Sample dialogue:
AI: "When did this happen? An approximate date is fine."
AI: "Where did it take place? The city and state are enough."
Information to capture:
Date or date range, marked as exact or estimated
City, county, and state
For ongoing situations, the start date and whether it is continuing
Follow-ups: If the caller is unsure, help anchor the date: "Do you remember the month, or whether it was before or after a holiday?" For multi-location events, capture the primary location only.
Escalate when: The date is old or the caller mentions a filing date, notice, or deadline. Flag it for prompt attorney review. The AI should never say whether a claim is too late. That is a legal judgment.
5. Which people or organizations are involved?
Why it matters: This is the conflict-check question. Opinion 510 acknowledges that identifying other relevant parties, witnesses, and counsel is ordinarily necessary to screen for conflicts of interest.
Sample dialogue:
AI: "To make sure our firm can help, I need the names of the other people or companies involved. Who is on the other side?"
AI: "Is anyone else directly involved, such as an insurance company, an employer, or a family member?"
Information to capture:
Full names of adverse parties, with spelling confirmed
Businesses, insurers, employers, and government agencies
Related parties, such as spouses or co-owners, and opposing counsel if known
Follow-ups: Ask for spelling and any former names or business aliases. Unknown names are fine. Record them as unknown rather than guessing.
Escalate when: The conflict system returns a possible match. Pause the booking, tell the caller the firm will follow up shortly, and route the record to a conflicts reviewer. Never reveal who the existing client is.
6. Are you already represented by an attorney?
Why it matters: Representation status changes how the firm should proceed. The caller may want a second opinion, may be switching lawyers, or may have counsel the firm needs to account for.
Sample dialogue:
AI: "Do you currently have a lawyer helping you with this matter?"
AI (if yes): "Are you looking for a second opinion, or thinking about changing attorneys?"
Information to capture:
Yes, no, or unsure
Name of the current attorney or firm
Purpose of the call: second opinion, change of counsel, or an unrelated matter
Follow-ups: If the caller is represented on a different matter, note it and continue. If they are unsure, for example after talking with an insurer's lawyer, record "unclear" for attorney review. Do not ask the caller to repeat advice their current lawyer gave them.
Escalate when: The caller has counsel in the same matter. Route the call to an attorney or intake supervisor to apply firm policy before anything is booked. The AI should never advise a caller to fire or ignore their lawyer.
7. Are there urgent deadlines, hearings, or safety concerns?
Why it matters: Some matters can't wait for the next open slot. Court dates, response deadlines, eviction notices, and threats to personal safety need faster handling than standard booking.
Sample dialogue:
AI: "Do you have any upcoming court dates or deadlines, or have you received papers that need a response?"
AI: "Are you safe right now?"
Information to capture:
Next hearing date and court, if any
What papers were received, and when
Any immediate safety risk
Follow-ups: Ask the caller to read dates directly from their documents rather than estimating. Remind them to keep all paperwork for the consultation.
Escalate when: Anyone is in immediate danger. Direct the caller to 911 first. Hearings or deadlines inside the firm's defined window should trigger a live transfer or same-day attorney callback. The AI should never tell a caller they have "plenty of time."
How the consultation booking workflow should run
A well-designed legal voice agent follows the same sequence on every call, so nothing important depends on the caller's memory or the time of day.
Greet the caller, disclose the AI, state that it is not a lawyer, and ask for recording consent.
Ask the seven questions, keeping each answer to what is reasonably necessary.
Run a conflict check on the names from Question 5.
Route by practice area, jurisdiction, and urgency.
Book the right attorney's calendar, or hold the slot until conflicts clear.
Confirm by the caller's approved channel, and say whether the slot is confirmed or awaiting staff approval.
Give the attorney a structured summary with the transcript.
One timing detail matters: send document-upload links only after conflicts clear. Collecting medical records or contracts first can expose the firm to exactly the information Rule 1.18 aims to limit.
What the AI receptionist asks vs. what the attorney covers
Intake topic | AI receptionist captures | Leave for the attorney consultation |
|---|---|---|
Identity | Name, safe callback, contact permissions | Engagement and identity verification |
Matter type | Practice area and jurisdiction | Legal theories and claims |
Facts | Two-to-three-sentence summary | Full narrative, documents, admissions |
Timing | Incident date and location | Statute of limitations analysis |
Parties | Names for the conflict check | Liability assessment |
Representation | Current counsel and purpose of call | Second-opinion advice |
Urgency | Court dates, deadlines, safety risks | Emergency motions and strategy |
Outcome | What the caller wants | Case value, settlement range, fees |
Safeguards every legal voice agent needs
Conflict-check safeguards
Run conflicts before a booking is final. Use exact and fuzzy name matching, include related entities, and keep a human reviewer on every potential match. A name match is a flag, not a decision, and a clean result is not proof of clearance. The AI should never confirm or deny whom the firm represents.
AI disclosure
Tell callers at the start that they are speaking with an AI assistant. It is the honest default, and some states are beginning to require it. Utah, for example, amended its AI law in 2025 and requires licensed professionals to disclose generative AI use in certain high-risk interactions (see Utah S.B. 226 (2025)).
Pair that disclosure with a plain non-representation statement: the assistant is not a lawyer, cannot give legal advice, and booking a consultation does not mean the firm has agreed to represent the caller.
Rule 1.18's commentary supports this. It indicates that inviting information without clear, understandable warnings is more likely to create a consultation and the duties that come with it. A disclaimer alone cannot guarantee that no duties arise, so the script and the conduct both matter.
Recording consent
Recording laws vary by state. California Penal Code § 632, for example, prohibits recording a confidential communication without the consent of all parties. Several other states also require all-party consent.
The practical answer is a recording announcement at the start of every call, plus a human callback option for callers who decline. Do not treat agreement to speak with an AI as agreement to be recorded. Ask counsel to confirm the requirements for each state you take calls from.
Secure data handling
Intake data is confidential from the first sentence. ABA Formal Opinion 512 applies its confidentiality analysis to prospective-client information and warns that self-learning generative AI tools can expose what users enter.
Ask vendors directly whether caller data trains their models. Then require encryption in transit and at rest, role-based access, audit logs, defined retention periods, and contractual limits on data use.
Supervision doesn't disappear with automation. Opinion 512 applies lawyers' supervisory duties under Rules 5.1 and 5.3 to generative AI tools, so an attorney should own the script, the escalation rules, and regular transcript reviews.
Human handoffs
Define handoff triggers in advance: emergencies, near-term hearings, conflict hits, distressed callers, represented parties, and any request to speak with a person. Make the transfer warm, so the caller never has to repeat their story.
An inbound voice agent that transfers calls with the full conversation history attached lets staff pick up exactly where the AI stopped.
Sample conversation: a realistic intake call
This illustrative call uses a fictional firm and caller to show the seven questions working together in under three minutes.
AI: "Thanks for calling Harbor Point Law. I'm the firm's AI assistant, and this call is recorded for intake. Is that okay?"
Caller: "Yes, that's fine."
AI: "Thank you. I'm not a lawyer and can't give legal advice, and scheduling a consultation doesn't mean the firm has agreed to represent you. May I have your full name and best callback number?"
Caller: "Dana Ruiz, 555-0142."
AI: "Thanks, Dana. Is it okay to text or leave a voicemail at that number?"
Caller: "Text is fine."
AI: "What kind of legal help are you looking for, and in which state?"
Caller: "I was hurt in a car accident in Texas."
AI: "I'm sorry to hear that. In two or three sentences, what happened? The attorney will go over details with you."
Caller: "Someone ran a red light and hit my car. I've been seeing a doctor for my back."
AI: "When and where did it happen?"
Caller: "August 28, in San Antonio."
AI: "Who else was involved? The other driver's name, and any insurance company?"
Caller: "The driver was Mark Ellison. His insurer called me last week."
AI: "Do you currently have a lawyer for this accident?"
Caller: "No."
AI: "Any court dates, deadlines, or safety concerns I should know about?"
Caller: "No, but the adjuster wants a recorded statement."
AI: "Thanks, I'll flag that for the attorney. One moment while I check our availability. I can offer Thursday at 2 p.m. or Friday at 10 a.m."
Caller: "Thursday works."
AI: "You're booked for Thursday at 2 p.m. You'll receive a text confirmation shortly."
Notice what the AI didn't do. It didn't advise Dana about the recorded statement, estimate her claim, or ask for medical records. It flagged the issue and left legal judgment to the attorney.
Many firms would go one step further. Because the caller mentioned an insurer asking for a statement, their rules might hold the booking for a same-day human callback instead of offering an ordinary slot. Build that choice into your escalation rules before launch.
Implementation checklist for law firm intake automation
Map practice areas, jurisdictions, and out-of-scope referral language
Draft AI disclosure, non-attorney, and non-representation scripts, and have an attorney approve them
Configure recording consent for every state you take calls from
Cap Question 3 at a brief summary and script polite interruptions for oversharing
Connect conflict checking to party names before bookings confirm
Define urgency windows for hearings, deadlines, and safety issues
Set human handoff triggers and after-hours escalation contacts
Confirm vendor encryption, access controls, retention, and model-training terms
Send document-upload links only after conflict clearance
Review transcripts weekly during the first month and tune the script
For the full call journey in a personal injury practice, see AI voice intake for personal injury law firms.
Turn every intake call into a well-screened consultation
The right seven questions give attorneys what they need to decide quickly while protecting callers and the firm. The script, safeguards, and handoffs matter as much as the technology answering the phone.
LuMay's legal AI receptionist template includes a non-attorney disclaimer, an existing-attorney check, emergency redirects, and human attorney escalation. It lists practice-system integrations such as Clio, PracticePanther, and Filevine, which you should confirm during scoping. You can also explore the broader LuMay Voice Agent platform.
Want to see it handle your practice areas and screening rules? Book a voice agent demo and walk through a live intake flow with the LuMay team.
This article provides general information, not legal advice. Ethics rules and recording laws vary by jurisdiction, so confirm requirements with your state bar and counsel.
