LuMayEverything AI. One Platform.
Products
Specialized AI solutions
AI products for business functions, industry workflows, and enterprise operations.
Production ReadyLuMay Legal Agents(Lexintis)Legal ops, compliance, billing, and document intelligence.
Production ReadyLuMay Voice Agents(Voxentis)Conversations, orchestration, actions, and follow-up.
HealthcareIntake, scheduling, care, and clinical operations.
Financial ServicesBanking, insurance, compliance, and finance workflows.
ManufacturingQuality, supply chain, operations, and field service.
Explore All ProductsFlexible deployment across SaaS, Azure, private cloud, hybrid, and on-prem.
Don't see your use case? Choose a suitable product or bring your workflow. We'll build it quickly.Book a Demo
Platform
Built once · governed · deployed anywhere
The runtime, connectors, governance, and analytics behind every LuMay agent.
Core Agent EngineRuntime for every AI agent.
Orchestration EngineCoordinates agents, approvals, and actions.
Connectors & AdaptersConnects systems, data, documents, and voice.
Security & GovernanceAccess, audit, privacy, and human review.
Deployment & AnalyticsDeploy anywhere. Measure ROI from week one.
Explore PlatformOne enterprise AI operating layer. Any deployment.
Need help turning workflows into AI agents?Book a Platform Call
Services
Generative AI · agents · enterprise · advisory
Build, integrate, and run AI with engineering and advisory support.
Generative AI DevelopmentCustom generative apps and copilots.
LLM DevelopmentFine-tuned, domain-specific models.
RAG DevelopmentGrounded retrieval over your own data.
AI Agent DevelopmentTask and workflow agents in production.
AI Automation ServicesAutomate manual, repetitive operations.
AI Integration ServicesConnect agents to systems and data.
Explore All Services
New to AI?Not sure where to start? We'll map your first use cases.Book Discovery
Pricing
SaaS · your cloud · on-prem · air-gapped
Plans, packaging, and deployment options for every team size.
Product PlansPer-agent plans and what's included.
Services PricingAdvisory, implementation, and support.
AI AcademyTraining and enablement programs.
Deployment OptionsSaaS, your cloud, on-prem, air-gapped.
Explore Pricing
Need a custom quote?Talk to a pricing expert for volume or enterprise terms.Contact Sales
Company
Mission · people · community · ecosystem
Who we are, how we work, and the partners we build with.
About LuMayCompany story, mission, and platform vision.
Leadership TeamExecutive and AI delivery leaders.
Advisory TeamStrategic advisors and industry experts.
Culture & ValuesHow LuMay builds, serves, and scales.
Life at LuMayHow teams work, learn, and grow.
CareersBuild the next generation of enterprise AI.
Explore Company
Build · partner · growWant to build, partner, or grow with LuMay?Contact LuMay
Resources
Proof · insights · learning · explore
Proof, frameworks, and learning to evaluate and adopt enterprise AI.
Case StudiesCustomer outcomes and production AI examples.
GalleryDemos, screenshots, and product visuals.
Success StoriesBusiness wins, adoption, and ROI proof.
LinkedIn PostsLatest updates and insights.
NewsletterEvents, milestones, and enterprise AI updates.
Explore Resources
Not sure where to look?Tell us the problem and we'll point you to the right resource.Talk To Us
Book demo
Book demo
LuMay logo

Building the Autonomous Workforce behind every Business Function.

sales@lumay.ai
+1 (320) 228-4730
ISO 27001 CertifiedSOC 2 Type II Certified

Platform

  • Agentic Core
  • Our Agents
  • Pricing & Engagement
  • Architecture
  • Deployment

Solutions

  • LuMay Legal Agents (Lexintis)
  • LuMay Voice Agents (Voxentis)
  • Insight Agents
  • Workflow Automation Agents
  • All Agents

Services

  • Generative AI Development
  • LLM Development
  • RAG Development
  • AI Agent Development
  • AI Automation Services
  • AI Integration Services
  • All Services

Resources

  • Case Studies
  • Blog
  • ROI calculator
  • Enterprise AI Framework
  • Trust & Security
  • AI Governance Framework
  • Learning Hub

Company

  • About
  • Leadership
  • Advisory Team
  • Partnerships
  • Life at LuMay
  • Careers
  • Contact

Request an AI Summary

Learn more about how LuMay is transforming enterprise AI adoption for leading businesses.

ChatGPTClaudePerplexity

Make LuMay a Preferred Source

QR code linking to lumay.ai
©2025 - 2026 LuMay Inc · All rights reserved
PrivacyCookiesTermsTrustLLM PolicyE-Verify
SOC 2 Type II & ISO 27001 Certified
Home>Blogs>How AI Legal Intake Works: Screening, Conflicts, Documents, and Attorney Handoffs

How AI Legal Intake Works: Screening, Conflicts, Documents, and Attorney Handoffs

Editorial Team

Sarath Babu

Content Writer and SEO Specialist at Lumay

Creates insightful content on SEO, AI-powered marketing, digital growth, and emerging technologies. He simplifies complex topics into practical, research-backed guidance.

Editorial Team

Written by

Sarath Babu

Palanisamy

Palanisamy

CEO and Founder at LuMay

27+ years leading enterprise-scale AI, data, and systems architecture initiatives, delivering mission-critical platforms focused on trust, governance, and reliability.

Palanisamy

Reviewed by

Palanisamy

Published date: October 13, 2026

Expert Verified14 min read

Summarize with AI

ChatGPTPerplexityClaudeGeminiGrok
Editorial Team
Editorial Team

Voice Agent Expert

Table of Contents
1. The Short Answer2. Why Legal Intake Is Worth Fixing First3. The AI Legal Intake Workflow, Step by Step4. 1. Incoming Call and Disclosure5. 2. Initial Screening6. 3. Client Qualification7. 4. Preliminary Conflict Information8. 5. Document Requests9. 6. Secure Information Handling10. 7. Appointment Scheduling11. 8. Structured Attorney Handoff12. AI-Assisted Conflict Screening vs. Attorney-Led Conflict Determinations13. What AI Intake Does Not Do14. It Doesn't Establish the Attorney-Client Relationship15. It Doesn't Give Legal Advice16. It Doesn't Replace Judgment or Supervision17. Example: One After-Hours Call, End to End18. Implementation Considerations19. Key Risks and the Controls That Address Them20. Operational KPIs to Track21. Test AI Intake Against Your Own Script22. Frequently Asked Questions
How AI Legal Intake Works: Screening, Conflicts, Documents, and Attorney Handoffs

How AI Legal Intake Works: Screening, Conflicts, Documents, and Attorney Handoffs

October 13, 2026 · LuMay AI

The Short Answer

AI legal intake uses a voice or chat agent to answer prospective-client inquiries, collect facts against firm-defined screening criteria, gather the names needed for a conflict check, request documents through secure channels, book consultations, and hand a structured summary to staff. Attorneys still clear conflicts, decide whether to accept a matter, and give all legal advice.

Most firms don't lose prospective clients to weak lawyering. They lose them in the first ten minutes, when a call rolls to voicemail or a web form sits unread overnight.

AI intake closes that gap without changing who makes legal decisions. This guide covers the full workflow, where the ethical lines sit, and the numbers that show whether it's working.

Why Legal Intake Is Worth Fixing First

Many firms simply aren't answering. For its 2024 Legal Trends research, Clio had a third-party research company contact 500 law firms as prospective clients. Forty-eight percent were unreachable by phone, and only 33% replied to email.

Intake is also where ethical exposure begins. Someone who consults your firm about a possible matter is generally a prospective client under ABA Model Rule 1.18, and what they share stays protected even if you never take the case.

So the goal isn't just answering more calls. It's answering every call consistently, collecting the right information (and not too much), and getting a clean record to a lawyer quickly.

The AI Legal Intake Workflow, Step by Step

A well-built AI intake flow runs through eight stages. Each one has a clear owner, and an attorney owns every decision that requires legal judgment.

1. Incoming Call and Disclosure

The agent answers immediately, day or night, and identifies itself as an automated assistant for the firm. Florida Bar Ethics Opinion 24-1 says client-facing AI chatbots must disclose that they are an AI program, not a lawyer or firm employee.

The opening also sets expectations: the call doesn't create a representation, the agent can't give legal advice, and the caller can ask for a person. Emergencies route straight to 911 or a staff line. A workable opening line:

“Thank you for calling [Firm Name]. I'm an AI intake assistant, not an attorney. I can collect basic information for our legal team and help schedule a consultation. Please share only what I ask for at first.”

2. Initial Screening

Next, the agent identifies the matter type: practice area, location, rough dates, and whether the caller already has a lawyer.

These questions filter out matters the firm can't take before anyone collects sensitive detail. Florida's opinion suggests screening questions that limit the conversation when a person is already represented.

3. Client Qualification

For matters that pass screening, the agent asks the firm's own qualification questions. In personal injury, that may be injuries, treatment, and insurance. In employment law, it may be employer size and termination date.

The output is a recommendation with reasons, not a verdict. Borderline, urgent, or unusual matters go to a person instead of being declined automatically.

4. Preliminary Conflict Information

The agent collects the names a conflicts check needs: the caller, opposing parties, related companies, insurers, and other known participants. It confirms spellings, because speech recognition can confuse similar names, trade names, and corporate abbreviations. It should not invite the full story yet.

Every automated search should end in one of three states:

  • Possible match: stop further sensitive intake and route the record for lawyer review.
  • No automated match: record the result as provisional, never as “conflict cleared.”
  • Unable to search: flag the system failure internally and queue a manual check.

6. Secure Information Handling

Transcripts, recordings, and uploads all hold confidential prospective-client information. ABA Model Rule 1.6(c) requires reasonable efforts to prevent unauthorized disclosure or access.

ABA Formal Opinion 512 applies that duty to generative AI. It tells lawyers to understand a tool's terms of use and privacy policy before client information goes in. In practice, that means encryption, role-based access, set retention periods, and no vendor model training on intake data.

7. Appointment Scheduling

Qualified callers book a consultation from the attorney's real availability. The agent confirms the time, sends reminders, and logs the booking on the intake record.

Scheduling should never imply the firm has accepted the matter. And an urgent flag shouldn't disappear just because a slot was booked; it needs its own alert and an owner.

8. Structured Attorney Handoff

Instead of a voicemail, the attorney receives a structured record: contact details, matter type, key dates, screening answers, conflict names and match status, documents received and missing, qualification notes, and the transcript. A good record also separates what the caller actually said from what the system inferred, and lists low-confidence details and unanswered questions.

The attorney accepts, declines, refers, or asks for more. People whose matters are declined should receive a clear non-engagement message.

StageAI agent handlesFirm staff or attorney handles
Answer and discloseAnswers 24/7, states it is AI, offers a personApproves disclosure wording
ScreeningAsks scripted eligibility questionsWrites the criteria
QualificationScores against firm rules, shows reasonsReviews and decides
ConflictsCollects names, runs a preliminary match, flags hitsClears, declines, or seeks consent
DocumentsSends secure links, tracks receiptReviews contents
SchedulingBooks from real availabilityHolds the consultation
HandoffDelivers structured record and transcriptAccepts, declines, or refers

AI-Assisted Conflict Screening vs. Attorney-Led Conflict Determinations

An AI agent can support conflict screening. It cannot decide whether a conflict exists. This is the line firms most often blur.

The agent can capture party names and spellings, related entities, and aliases, then query the firm's conflicts database and flag exact or near matches.

It can't judge whether a match is a real conflict, whether matters are substantially related, or whether consent or screening would cure the problem. Those questions turn on Model Rules 1.7, 1.9, 1.10, and 1.18. They belong to a lawyer.

AI-assisted screeningAttorney-led determination
PurposeSurface possible matches earlyDecide whether representation is permitted
InputsNames, entities, matter typeFull conflicts report and rule analysis
Output“Possible match, review needed”Clear, decline, or seek informed consent
Nature of the workAdministrative supportProfessional judgment
AccountableSupervising lawyerLawyer

Two habits keep this boundary safe.

Collect only what's needed before clearance. ABA Formal Opinion 510 advises gathering only information reasonably necessary to decide whether the firm can and will take the matter. Over-collecting early can disqualify the whole firm from a later adverse matter.

Log every prospective client promptly. Oregon State Bar Formal Opinion 2026-208 notes that disqualifying information received through a chatbot can bar adverse representation. It advises entering prospective clients into the conflict system promptly.

What AI Intake Does Not Do

Three boundaries hold no matter which tool you choose.

It Doesn't Establish the Attorney-Client Relationship

Only the firm can agree to represent someone. But an agent that sounds too much like a lawyer can create the impression that it already has.

Florida's opinion warns that a welcoming chatbot can create a prospective-client or lawyer-client relationship without the lawyer knowing. Oregon's opinion notes that the relationship can turn on the client's reasonable belief. Clear disclaimers and attorney review of every intake record reduce that risk.

It Doesn't Give Legal Advice

“Do I have a case?” and “What's it worth?” are legal questions. Opinion 512 states that lawyers may not leave it to generative AI alone to advise clients. The agent should acknowledge the question and save it for the consultation.

It Doesn't Replace Judgment or Supervision

ABA Formal Opinion 506 lets trained, supervised nonlawyers handle intake tasks such as gathering information and running an initial conflict check. The prospective client must still be able to speak with the lawyer.

Apply the same standard to an AI agent. Opinion 512 also expects managing lawyers to set firm AI policies and vet vendors' security and confidentiality practices. Oregon adds a human point: a chatbot may miss signs that a caller is in distress, so build an escalation path for it.

Example: One After-Hours Call, End to End

At 8: 40 p.m., Dana calls an employment law firm after being let go that afternoon. Here's how a well-configured agent handles it.

  1. The agent answers, says it's an AI assistant that can't give legal advice, and offers a staff callback.
  2. Screening confirms the job was in the firm's state and Dana has no lawyer.
  3. Qualification captures the employer, its approximate size, Dana's role, and a two-sentence summary of why Dana believes the firing was retaliatory.
  4. Dana names the employer, its parent company, and a former manager. The preliminary check flags the parent company as a possible match.
  5. The agent texts a secure link for the termination letter.
  6. Because of the flag, it doesn't book a consultation. It tells Dana someone will follow up the next business day.
  7. At 8:30 a.m., the supervising attorney reviews the record and clears the flag: the existing client is an unrelated affiliate.
  8. Staff call Dana and book the consultation.

Nobody promised representation, nothing was advised, and a lawyer answered the conflict question. (Illustrative scenario, not a client case study.)

Implementation Considerations

The technology is the easy part. Most of the work is deciding, in writing, how your firm wants intake to run.

  • Map today's process. Note who answers, what they ask, and where records land. Automating an unclear process only makes it consistently unclear.
  • Write criteria per practice area. Define eligibility, qualification factors, and escalation triggers, and have a supervising attorney approve them.
  • Define escalation triggers. At minimum: the caller asks for a lawyer; an emergency, safety concern, or imminent deadline; a criminal, detention, or restraining-order matter; a distressed caller; a conflict match; a legal question outside approved responses; or a request the agent can't understand.
  • Have ethics counsel review the scripts. Disclosures, non-engagement language, and call-recording notices vary by state.
  • Connect your systems. The handoff should land in your practice management system or CRM and query your conflicts database. Confirm which integrations are native and which are custom work.
  • Vet the vendor. Opinion 512 points to enforceable confidentiality terms, breach notification, and data retention after the contract ends. Oregon adds the underlying software and APIs a vendor relies on.
  • Pilot narrowly and test failure modes. Start with after-hours calls or one practice area, and have staff review every transcript for the first few weeks. Test what happens when an integration is down, a caller refuses recording, or a name can't be understood. A system that fails safely beats one that finishes every call by guessing.

Key Risks and the Controls That Address Them

Every risk below has a practical control. None of them require avoiding AI; they require designing for it.

RiskWhat can go wrongControl
Implied representationCaller believes the firm took the caseDisclaimers, non-engagement letters, attorney review
Legal adviceAgent answers “do I have a case?”Scripted deflection to the consultation
Over-collectionDetailed facts taken before conflicts clearLean script, conflict names first
Data exposureIntake data used for vendor training or leakedContract terms, encryption, access controls
Inaccurate recordsMisheard names or invented detailsTranscript links, uncertainty flags, staff QA sampling
Missed urgencyDistressed or vulnerable caller not escalatedEscalation triggers, human callback
Silent rejectionGood matters declined by rigid rulesHuman review of declines and edge cases

Operational KPIs to Track

Measure a baseline for at least two weeks before launch, then compare. These metrics show whether AI intake is improving speed, quality, and control.

KPIHow to measure itWhat it tells you
Answer rateInquiries answered ÷ inquiries receivedWhether calls still go unanswered
After-hours captureCompleted intakes outside office hoursValue of 24/7 coverage
Intake completion rateCompleted records ÷ started conversationsWhere callers drop off
Time to attorney reviewIntake complete to first attorney actionHandoff speed
Conflict flag rate and clearance timeFlags per 100 intakes; hours to clearConflicts workload and bottlenecks
Consultation booking and show rateBooked ÷ qualified; attended ÷ bookedScheduling quality
Signed-matter conversionEngagements ÷ qualified intakesBusiness impact
Attorney override rateRecommendations changed by attorneysWhether criteria need tuning
Record accuracyErrors found in sampled QA reviewsData quality
Escalation rateCalls handed to a personCoverage gaps and caller needs

A rising override rate is a useful signal, not a failure. It usually means your criteria need adjusting.

Test AI Intake Against Your Own Script

LuMay AI Voice Agents handle inbound calls with configurable call flows, a knowledge base, custom guardrails, and handoff to a person. LuMay's Legal AI Receptionist template applies that to personal injury intake. It gives a non-attorney disclaimer, checks for existing counsel, screens the case, books consultations, and texts secure document upload links.

Firms that need attorney approval before a matter opens can look at LuMay Intake Flow, part of the LuMay Legal Agents platform. Governance controls are described on LuMay's security and governance page. For a comparison of options, see LuMay's guide to AI client intake tools for personal injury firms.

The best test is your own intake script. Book a voice agent demo and walk through a real call scenario with the team.

Frequently Asked Questions

Everything you need to know about Voice Agent

1. What is AI legal intake?

It's the use of a voice or chat agent to answer prospective-client inquiries, collect screening and conflict information, request documents, book consultations, and pass a structured record to the firm. Lawyers make every legal decision.

2. Can an AI intake agent create an attorney-client relationship?

It shouldn't, and the firm alone decides whether to represent someone. Because a relationship can turn on a caller's reasonable belief, use clear disclaimers, avoid lawyer-like assurances, and have an attorney review each intake.

3. Can AI run a conflict check?

It can run a preliminary check by collecting party names and flagging possible matches in your conflicts database. A lawyer must decide whether a conflict exists and how to resolve it.

4. Does a “no match” result mean the firm has no conflict?

No. It only means that search found nothing under its settings and data. Aliases, related entities, and incomplete records can still hide a conflict, so the result stays provisional until a lawyer reviews it.

5. Is it ethical for law firms to use AI for client intake?

Generally yes, with safeguards. ABA Formal Opinion 512, Florida Opinion 24-1, and Oregon Opinion 2026-208 all permit AI use subject to competence, confidentiality, and supervision. Check your own state's rules.

6. Does an AI intake agent have to say it's AI?

Florida Opinion 24-1 requires client-facing chatbots to disclose that they are an AI program, not a lawyer or employee. Oregon's opinion treats nondisclosure as a possible misleading communication. Disclosing is the safe default everywhere.

About the Editorial Team

Sarath Babu

Sarath Babu

Content Writer and SEO Specialist at Lumay

Creates insightful content on SEO, AI-powered marketing, digital growth, and emerging technologies. He simplifies complex topics into practical, research-backed guidance.

Palanisamy

Palanisamy

CEO and Founder at LuMay

27+ years of experience leading enterprise-scale AI, data, and systems architecture initiatives, delivering mission-critical platforms with a strong emphasis on trust, governance, and reliability.

Make LuMay a Preferred Source

SHARE

Table of Contents

The Short AnswerWhy Legal Intake Is Worth Fixing FirstThe AI Legal Intake Workflow, Step by Step1. Incoming Call and Disclosure2. Initial Screening3. Client Qualification4. Preliminary Conflict Information5. Document Requests6. Secure Information Handling7. Appointment Scheduling8. Structured Attorney HandoffAI-Assisted Conflict Screening vs. Attorney-Led Conflict DeterminationsWhat AI Intake Does Not DoIt Doesn't Establish the Attorney-Client RelationshipIt Doesn't Give Legal AdviceIt Doesn't Replace Judgment or SupervisionExample: One After-Hours Call, End to EndImplementation ConsiderationsKey Risks and the Controls That Address ThemOperational KPIs to TrackTest AI Intake Against Your Own ScriptFrequently Asked Questions

Ready to Get Started?

Deploy enterprise agentic AI in under four weeks with LuMay.

Get Demo

7. How much information should the AI collect?

Only what's reasonably necessary to decide whether the firm can and will take the matter, consistent with ABA Formal Opinion 510. Capture conflict names first, and save the detailed narrative for after clearance.

8. Can the AI tell a caller whether they have a case?

No. Assessing a claim's merits is legal advice. The agent should acknowledge the question and route it to the attorney consultation.

9. How are documents collected securely?

Through encrypted upload links tied to a specific intake record, with role-based access and defined retention. Confirm in the vendor contract that intake data isn't used to train models.

10. Who is responsible if the AI makes a mistake?

The firm. Under Model Rule 5.3 and Opinion 512, lawyers must supervise the tools and vendors they use, just as they supervise nonlawyer staff.

11. What KPIs show AI legal intake is working?

Answer rate, intake completion, time to attorney review, conflict clearance time, booking and show rates, signed-matter conversion, attorney override rate, and record accuracy. Compare each against a pre-launch baseline.

12. Will AI intake replace intake staff?

Usually not. It handles volume, after-hours coverage, and data capture. Staff and attorneys handle judgment, exceptions, conflicts, and the relationship with the client.

Related Articles

AI Voice Intake for Personal Injury Law Firms: From First Call to Attorney Handoff

October 2026

AI Voice Intake for Personal Injury Law Firms: From First Call to Attorney Handoff

How AI voice intake works for personal injury law firms, from the first ring to attorney handoff: disclosures, urgency detection, conflict checks, summaries, ethics guardrails, and KPIs.

7 Legal Intake Questions an AI Receptionist Should Ask Before Booking a Consultation

October 2026

7 Legal Intake Questions an AI Receptionist Should Ask Before Booking a Consultation

The seven intake questions an AI legal receptionist should ask before booking a consultation, with sample dialogue, escalation triggers, and the Rule 1.18 safeguards that protect callers and the firm.

AI Receptionist vs Law Firm Answering Service: Cost, Coverage & Escalation

October 2026

AI Receptionist vs Law Firm Answering Service: Cost, Coverage & Escalation

Compare AI receptionists and human law firm answering services on cost, 24/7 coverage, intake, escalation, confidentiality, and legal ethics, with worked pricing scenarios.

Recent Posts

  • 7 AI Tools for Contract Risk Flagging in First-Pass Legal Review (2026)
  • 7 Enterprise Integration Platforms for Connecting AI to ERP and CRM
  • Custom RAG vs Managed RAG: Which Delivery Model Fits Your Enterprise?
  • 9 Requirements for Integrating AI with Legacy Enterprise Systems
  • 7 Vector Databases Compared for Enterprise RAG Applications
  • 8 Data Readiness Checks Before Building Enterprise Generative AI
  • 7 Best AI Client Intake Tools for Personal Injury Law Firms in 2026
  • RAG vs Fine-Tuning: Which Approach Fits Your Enterprise AI Project?
How AI Voice Agents Take Restaurant Phone Orders: Menus, Modifications, and Staff Handoffs
  • 7 LLM Evaluation Tools Compared for Enterprise AI Teams