Legal intake is the process a law firm uses to receive an inquiry, gather appropriate initial information, and move it to a documented next step. It can include administrative screening, consultation scheduling, record creation, and follow-up. A completed intake does not itself mean the firm has accepted representation.

Legal Intake Is Not the Same as a Message, Consultation, Conflict Decision, or Engagement
A message records enough information for someone to call back. Intake gathers the approved information and completes the administrative workflow needed for that callback or another next step. The difference may include matter-specific questions, safe-contact preference, scheduling, system writeback, task assignment, and a structured summary.
An intake is also not the legal consultation. A lawyer may later discuss strategy, rights, obligations, deadlines, or options. The intake path should avoid doing that work. It may record a date exactly as the caller states it and mark an urgency signal, but it should not calculate or confirm a legal deadline.
Preliminary screening is not a final conflicts check, legal-merit decision, or acceptance. Administrative criteria may determine which appointment type or review queue applies. Authorized lawyers and staff make the legal and business decisions under the firm’s rules. Engagement requires the firm’s actual acceptance process and any required agreement; a booked consultation is not representation.
The legal intake service versus answering service guide explores the message-taking boundary in detail.
The Eight Stages of a Complete Legal Intake Workflow
Not every inquiry needs every stage. An existing client asking for an office address may only need identity-aware routing and an approved answer. A new matter may require a conditional intake and consultation. A possible conflict signal may stop information gathering early. The workflow should expand only as the next administrative purpose requires.
Collect the Minimum Information Needed for the Next Decision
A general first-contact set may include the person’s name, reliable contact details, safe-contact preference, broad reason for reaching the firm, caller status, practice area, jurisdiction, and dates exactly as stated. The firm may add approved questions for its practices, booking criteria, referral sources, languages, and accessibility needs.
Use conditional branching so the caller is not asked irrelevant questions. Preserve “unknown,” “not provided,” and “caller declined” rather than forcing a guess. Confirm names, phone numbers, email addresses, dates, and appointment details. Explain why sensitive information is being requested when appropriate.
ABA Model Rule 1.18 addresses prospective-client information. Comment [4] advises a lawyer considering a matter to limit the initial consultation to information reasonably necessary for deciding whether to undertake it. A firm should use that principle with jurisdiction-specific counsel when designing disclosures, fields, access, retention, and stop conditions.
| Information type | Possible first-contact purpose | Control | Do not infer |
|---|---|---|---|
| Identity and contact | Create a callback path and distinguish records | Confirm spelling, safe channel, and permission rules | Representation or conflict clearance |
| Broad matter type | Choose the approved intake branch or destination | Use caller wording and preserve uncertainty | Legal claim, merit, or eligibility |
| Jurisdiction/location | Apply firm routing and scheduling criteria | Record what the caller states | Controlling law or venue |
| Dates/events | Surface a defined review signal | Do not calculate or promise a deadline | Timeliness or legal consequence |
| Other parties | Support the firm’s lawyer-controlled conflicts process | Stop under approved warning rules | A final conflict decision |
| Availability | Offer an eligible consultation | Use authoritative calendar and appointment rules | Firm acceptance or lawyer availability beyond confirmation |
Separate Administrative Screening From Conflicts and Legal Judgment
Administrative screening can apply clear rules the firm has approved: practice area, office or state served, new versus existing client, consultation type, required fields, availability, referral path, and when to escalate. It may identify an answer that needs human review; it should not decide whether a legal claim is valid or valuable.
Conflicts deserve a separate controlled process. Intake may collect the limited names or entities the firm permits, display approved warnings, and stop further collection when a trigger appears. An attorney or authorized conflicts process determines the result. The receptionist should not tell a caller that no conflict exists simply because a search returned no obvious match.
Use accurate labels in the record: “administrative criteria met,” “requires lawyer review,” “possible conflict signal,” “intake incomplete,” or “caller requested a person.” Avoid labels such as “good case,” “high value,” or “qualified legally” unless the firm has a precise, non-misleading administrative definition and authorized human review.
Make Follow-Up an Accountable Stage, Not a Hope
Every result needs a responsible destination. If the caller books, confirm the event and approved preparation instructions. If the caller needs review, create a task with context, priority, and response expectation. If no transfer recipient answers, return to the caller accurately and assign the fallback. If the firm declines or refers, use approved wording and record the disposition.
Track unresolved items by age and owner. Avoid sending repeated messages without a documented consent and communication rule. Confirm delivery states appropriate to the channel, and provide a route when a message fails or a caller cannot use the proposed channel.
Follow-up should not promise that a lawyer will call at a time the firm has not committed to, imply representation, or continue collecting sensitive facts indefinitely. The law-firm follow-up automation guide covers controlled reminders, tasks, and escalation.
Apply Prospective-Client, Confidentiality, Recording, and Emergency Controls
Use qualified jurisdiction-specific counsel to review professional duties, disclosures, recording and consent, confidentiality, data processing, accessibility, retention, vendor terms, and supervision. ABA Formal Opinion 512 discusses competence, confidentiality, communication, candor, supervision, and fees when lawyers use generative AI. It does not certify a vendor or replace state-specific analysis.
Limit access to what each role needs. Document retention and deletion, approved recording settings, correction, incident handling, system permissions, change approval, and human review. Recording is optional with TeleWizard. Do not describe encryption, access controls, or contracts as a universal compliance guarantee.
For an immediate U.S. emergency requiring police, fire, or ambulance assistance, direct the caller to 911 under approved wording. TeleWizard is not emergency dispatch. Test emergency statements, distressed callers, threats, silence, poor audio, uncertainty, advice requests, possible conflicts, outages, unavailable people, and failed system actions.
Build or Repair Legal Intake in Eight Steps
- Observe the current path. Sample calls and messages across hours, practices, languages, caller types, outcomes, and exceptions.
- Define the purpose. State what each intake path must complete and which legal decisions it must never make.
- Set minimum fields. Approve questions, branches, confirmations, missing values, warnings, and stop conditions.
- Map next actions. Define appointment, transfer, callback, task, decline, referral, and existing-client routes.
- Connect systems. Specify records, fields, permissions, calendars, ownership, acknowledgments, and recovery.
- Test ordinary and adverse cases. Include incomplete, duplicate, multilingual, sensitive, out-of-scope, emergency, and integration-failure scenarios.
- Launch one bounded path. Monitor a representative period before adding practices, channels, hours, or actions.
- Review and improve. Compare defined outcomes, document the version, change one controlled element, and retain rollback evidence.
This is a recommended planning sequence, not a guaranteed TeleWizard timeline or outcome. The law-firm intake process improvement guide provides a broader 30-day audit framework.
Measure Legal Intake From Response Through Documented Outcome
| Measure | Basic definition | Evidence | Common error |
|---|---|---|---|
| Answer rate | Eligible inquiries answered ÷ eligible inquiries received | Deduplicated channel records | Counting abandoned duplicates as separate opportunities |
| Completed intake | Usable approved intake records ÷ eligible intake starts | Required fields or valid missing statuses | Treating call duration as completeness |
| Eligible booking | Confirmed consultations ÷ inquiries eligible for the measured appointment | Authoritative calendar events | Counting a suggested time as booked |
| Connected-action accuracy | Correct completed actions ÷ audited action attempts | System outcome and review | Calling an API request a success |
| Follow-up ownership | Assigned actionable items ÷ items requiring follow-up | Correct owner, context, and due rule | Assuming a note creates accountability |
| Cost per completed intake | Defined operating cost ÷ completed usable intakes | Quote, labor, systems, review, and exceptions | Comparing cost per call across different scopes |
Clio’s official 2024 secret-shopper study covered 500 law firms and reported that 40% answered phone calls and 48% were essentially unreachable by phone. Those are general sampled-firm findings, not a TeleWizard benchmark or proof of conversion. Use them as a reason to inspect the firm’s own response and next-step data.
The intake KPI guide provides more detailed formulas and a 30-day scorecard.
Practice-Area Branch Example: Estate Planning Intake
The general legal-intake framework becomes useful when each practice branch identifies the current administrative decision, the minimum information needed, and the judgments reserved for lawyers. Estate planning is a good example because the first caller may be the person seeking help, a spouse or partner, an adult child, a caregiver, an agent, a fiduciary, or a professional referral source.
Attorney review is mandatory before operational adoption. Before a firm deploys this branch as policy, the firm must select the intended jurisdiction and have a qualified lawyer approve prospective-client warnings, conflict fields, client-identity and participant rules, capacity and influence escalation, document handling, engagement language, recording and messaging, and state-specific authority.
| General intake stage | Estate-planning example | Reserved decision |
|---|---|---|
| Orient | State the administrative receptionist role and that no legal or tax advice, document recommendation, or representation confirmation is provided | Engagement, legal advice, tax advice, and scope |
| Identify caller | Record who is calling, for whom, and the relationship in the caller’s words | Client identity, authority, capacity, confidentiality, and who may participate |
| Classify broadly | Capture create/update plan, review documents, probate/administration, trust administration, elder-law question, or other/unsure | Which instrument, proceeding, strategy, or remedy is appropriate |
| Collect minimum fields | Safe contact, state, broad request, approved names and relationships, caller-stated event/date, participant and consultation preferences, document categories | Conflict clearance, jurisdiction, capacity, legal urgency, document effect, tax consequence |
| Act | Offer an eligible consultation or route to a reviewed lawyer queue; record calendar or task acknowledgment | Acceptance, representation, deadline, or outcome |
| Recap and hand off | Confirm caller, relationship, broad request, date source, participants, missing fields, actual action, owner, and expectation | Any inference beyond the caller-provided and system-observed facts |
First contact should usually defer full asset values, account data, tax returns, medical records, diagnoses, detailed family conflict, beneficiary allocations, passwords, and complete document contents until a lawyer-approved stage establishes the purpose and secure method. Sequencing detailed data is not incomplete intake; it is controlled intake.
Keeping the example concise lets readers move to the specialized implementation resource without turning this foundational overview into a collection of full scripts.
Continue With the Guide for the Next Intake Decision
What Is Legal Intake? Frequently Asked Questions
Is legal intake the same as lead qualification?
No. Intake is the broader controlled process. It may include administrative preliminary screening, but final legal fit, conflicts, representation, and case decisions remain with authorized people.
Does an intake create an attorney-client relationship?
Not by itself. The firm should use approved warnings and its engagement process. A consultation booking or information submission should not be presented as acceptance or representation.
Can TeleWizard complete full legal intake?
Yes, within the firm’s approved workflow. It can gather permitted information, schedule, route, write to supported systems, create tasks, and escalate. It does not replace lawyer-controlled legal decisions.
Map your current intake stages before reviewing which steps TeleWizard could support. Review the TeleWizard options.
Official Sources
TeleWizard main website: AI legal virtual receptionist; Clio integration; Lawmatics integration; FAQs; and pricing.
Independent official sources: Clio 2024 Legal Trends Report resources; Clio App Directory; ABA Model Rule 1.18 and Comment [4]; ABA Formal Opinion 512; BLS May 2025 receptionists data; and 911.gov.


