# Legal Intake Service: How Calls Move from Hello to Attorney

> [llms.txt](https://www.lighthouselegal.ai/llms.txt)

See how a legal intake service answers inquiries, gathers case details, screens prospects, and routes qualified callers to your firm, step by step.

URL: https://www.lighthouselegal.ai/learn/legal-intake-service

[Learning center](https://www.lighthouselegal.ai/learn)

November 14, 2026

## Legal Intake Service: How Calls Move from Hello to Attorney

See how a legal intake service answers inquiries, gathers case details, screens prospects, and routes qualified callers to your firm, step by step.

-   legal intake service
-   law firm intake
-   client intake process
-   personal injury intake
-   call screening

It's 8:40 p.m., your staff have gone home, and a driver with a swollen wrist after a rear-end collision is calling injury firms. In this hypothetical evening, the driver reaches voicemail at the first two offices, then calls yours. What happens next depends on more than whether someone answers. Your firm needs usable facts, a clear handoff, and someone responsible for the next step.

### What a Legal Intake Service Is and Why It Matters

A **legal intake service** is a dedicated first line for new matters, human, AI-powered, or hybrid, that answers inquiries, asks the firm's intake questions, records structured answers, screens against firm-specific criteria, and routes appropriate callers to an attorney or intake specialist.

A plain answering service might leave you a name, number, and message. An intake service should leave you a **reviewable record and a specific destination** for the inquiry. That difference matters when an evening caller needs more than reassurance that someone will eventually call back.

#### The telephone access gap

In its secret-shopper study of **500 U.S. law firms**, [Clio's 2019 Legal Trends Report](https://www.clio.com/wp-content/uploads/2019/10/2019-Legal-Trends-Report.pdf) found that **56%** of calls were answered by a person, **73%** were answered or returned, and **27%** of firms remained unreachable by phone. In the comparable study of **500 firms** published in **2024**, [Clio's client-intake findings](https://www.clio.com/guides/client-intake-legal-trends/) reported **40%** answering, **52%** answering or calling back, and **48%** effectively unreachable.

**Law-firm telephone responsiveness in Clio secret-shopper studies**

| Study year | Calls answered by a person | Answered or later returned | Effectively unreachable |
| --- | --- | --- | --- |
| 2019 | 56% | 73% | 27% |
| 2024 | 40% | 52% | 48% |

These results establish an access problem, not a guaranteed improvement from any particular product. Answering the telephone is only the beginning. Staff still need enough information to understand the inquiry and act on it.

Lighthouse Legal builds AI voice agents that answer law firms' calls, screen new inquiries, and connect qualified callers with an attorney. When evaluating that category, IamVera.AI's guide to [compare client engagement AI platforms](https://iamvera.ai/blog/vetting-ai-client-engagement-engine-law-firm/) offers a useful starting point for organizing vendor questions.

The division of responsibility should remain simple: **the service handles intake logistics and documentation; the firm retains legal judgment**.

### How a Legal Intake Service Handles a New Call

A useful intake workflow gives the caller a clear experience while producing a record staff can use. For the evening collision caller, that means moving from a greeting to a documented next step without turning the conversation into an automated legal consultation.

The workflow below separates answering, information capture, screening, routing, logging, and follow-up.

![A diagram illustrating the six-step workflow of a legal intake service handling new client phone calls.](https://cdnimg.co/11a2db61-834c-48a5-b6b6-a28a4c32e2c5/80948015-6141-4593-b2fb-894b82d2f7cc/legal-intake-service-workflow-diagram.jpg)

#### From greeting to handoff

1.  **Answer with the firm's greeting.** The service receives a forwarded call or the intake selection from the firm's phone menu, with coverage configured for nights, weekends, holidays, and busy periods. Our AI receptionist answers forwarded calls with the firm's greeting and can conduct intake after a menu choice using the firm's own questions.
    
2.  **Identify the caller and the matter.** Ask for the caller's name, a reliable callback number, and a short description of what happened before collecting a lengthy account. Classify the inquiry into the appropriate script, such as a car crash, slip and fall, dog bite, or medical malpractice inquiry, so the caller isn't asked unrelated questions.
    
3.  **Collect the case details.** Follow the firm's question order: incident date, location, reported injuries, treatment, and any additional required fields. If the caller doesn't know an answer, preserve that uncertainty rather than filling the gap with an assumption.
    
4.  **Screen against the firm's criteria.** Apply approved rules for practice area, service geography, incident timing, and conflict-check names, then assign a working label such as qualified, needs attorney review, or not a fit. A rule that raises a deadline or conflict concern should direct the matter to human review, not produce a legal conclusion.
    
5.  **Route or wrap up.** Transfer qualified and high-priority callers to the designated attorney or intake specialist, create review tasks for uncertain matters, and close unsuitable inquiries politely under firm policy. Save the record even when the transfer fails, so staff can continue from the last completed answer.
    

A transfer should include context, not just a ringing telephone. Our explanation of [warm transfers versus cold transfers](https://www.lighthouselegal.ai/learn/warm-transfer-vs-cold-transfer) helps teams decide how the receiving person gets the caller's details before taking over.

#### What staff receive

For every call we handle, staff receive a **recording, transcript, and report**, including intake fields and a quick summary. The summary should make the immediate action obvious, while the transcript lets a reviewer check the caller's exact account and identify questions that remain unanswered.

Caller-facing preparation can also help set expectations. For a Houston inquiry, The Law Office of Bryan Fagan, PLLC's resource to [prepare for your Houston injury consultation](https://www.houstonaccidentlawyers.net/2026/08/07/houston-accident-lawyer-free-consultation/) can support preparation for the later attorney conversation, rather than replace the firm's intake script.

> **Practical rule:** End the call with an accurate next step, not a vague promise that someone will be in touch.

A finished intake record opens the firm's review. It doesn't automatically accept the case, even when the caller has answered every question.

### The Case Details an Intake Service Collects

Start with **the caller's name and a reliable callback number**. If the connection drops before anything else is captured, those fields give the team a way to recover the conversation. Record permission and preferences for follow-up alongside them.

The [Retell AI personal-injury intake guide](https://www.retellai.com/blog/personal-injury-intake) identifies identity, contact details, matter type, incident date and location, reported injuries, treatment, and additional review information as the foundation of a factual intake record. Keep the incident description concise and caller-centered, rather than asking the service to analyze liability.

#### Build the review record field by field

Use this table as a mark-up checklist during configuration. Its settings are a practical starting point, not a claim that every injury firm should require the same information.

**Intake fields and why firms collect them**

| Field | Why the firm needs it | Commonly set as |
| --- | --- | --- |
| Caller name | Identity, records, and conflict checks | Required |
| Callback number | Reliable follow-up route | Required |
| Matter type | Selects the intake script and screening rules | Required |
| Incident date | Deadline and timeliness review | Required |
| Incident location | Jurisdiction, venue, and team routing | Required |
| Injury description | Severity and practice-fit screening | Required |
| Medical treatment | Shows hospital or urgent-care visits and ongoing care | Often required |
| Follow-up permission | When and how the firm may contact the caller | Often required |
| Insurance information | Claim context for review | Optional |
| Police or incident report | Verification material for the review | Optional |
| Prior attorney involvement | Avoids duplicate representation | Optional |
| Other parties involved | Conflict screening | Optional |
| Email and referral source | Written follow-up and marketing attribution | Optional |

**Date and location deserve careful confirmation.** They tell staff which jurisdictional and deadline questions need review and may determine which team receives the file. Ask the caller to distinguish where the accident happened from where they live.

Treatment needs similar precision. A hospital visit that already happened, an appointment scheduled for later, and an intention to seek care are different facts. Record what the caller reports, including whether care is ongoing, without treating a planned visit as completed treatment.

#### Give every question a purpose

Mark questions **Required, Optional, or Disabled** in your script specification. Required means the workflow must ask and flag an unanswered field, not that the caller must invent an answer before receiving help.

In our intake, **Client Name and Phone Number stay required**; other fields include Date of Accident, Incident Location, Medical Treatment, Email, and Referral Source. Our [personal-injury intake questions guide](https://www.lighthouselegal.ai/learn/personal-injury-intake-questions) can help you turn the field list into caller-friendly wording.

We provide intake fields, a quick summary, and the full transcript. A reviewer should be able to find both the captured facts and the **missing facts the firm still needs**, reducing avoidable callbacks for basic information.

### Screening Labels and Who Owns Each Outcome

**Qualified is a workflow label, not a legal opinion.** Before using it, define what it means at your firm. A caller may match your practice area but need another team because of location, or appear suitable while lacking a fact required for review.

The [GB Advisors law-firm intake guide](https://www.gb-advisors.com/blog/law-firm-client-intake) describes case fit as dependent on practice area, geography, matter type, timing, economics, workload, and internal acceptance policy. Use those actual firm criteria, not generic injury thresholds borrowed from another practice.

#### Apply the firm's rules without deciding the merits

Say a caller was rear-ended in a suburb across the county line. Your second team covers that location, so the location answer directs the record there for review. Another firm without that coverage could label the identical inquiry not a fit for its practice.

Neither outcome establishes whether the caller has a meritorious claim. The difference is **which firm can review the matter under its operating rules**. Likewise, a possible deadline concern belongs with an attorney, not an automated acceptance or rejection rule.

Our customizable questions and screening criteria are set for each firm. We collect the details that firm needs and connect qualified callers to its team, but completing our intake doesn't mean the firm has accepted the case.

#### Assign an owner before the first live call

[Thoughtly's legal-intake workflow guidance](https://thoughtly.com/blog/ai-agents-legal-intake-consultation-scheduling) emphasizes named destinations for qualified callers, review tasks for uncertain matters, and preserved intake information when transfers fail. During onboarding, assign responsibility for all those outcomes rather than assuming a shared inbox is sufficient.

**Screening outcomes, actions, and owners**

| Screening outcome | What the service does | Who owns the next step |
| --- | --- | --- |
| Qualified and high priority | Transfers live to the on-duty attorney or intake specialist with details attached | Attorney or intake specialist on duty |
| Uncertain or incomplete | Creates an attorney-review task recording the unresolved field or rule | Named attorney reviewer |
| Not a fit for the firm | Ends with a documented, polite close under firm policy | Intake manager spot-checks |
| Caller asks for a person | Transfers immediately to staff | Any available team member |
| Transfer fails or call drops | Saves the last intake state and creates a callback task | Assigned backup owner |

For each queue, write down the **response expectation, monitoring responsibility, and backup coverage**. An urgent qualified caller needs a live destination; an unresolved geographic question needs a reviewer who understands the coverage rules. Those aren't interchangeable assignments.

A request for a person should trigger an immediate transfer attempt, not another round of screening. If nobody answers, preserve the request and place the callback with the assigned backup owner. Record the caller's follow-up preference and use only the approved contact path when permission exists.

> Missing information should produce a visible review task, not an invisible rejection.

#### Measure the handoff, not just the answer

Review **transfer success, callback speed, and time from qualification to human contact**. Use call timestamps and routing records to distinguish a conversation that reached staff from one that merely attempted a transfer.

Also examine false negatives: callers classified as unsuitable who should have reached review. The [ABA's discussion of AI-driven client intake](https://www.americanbar.org/groups/law_practice/resources/law-practice-magazine/2025/march-april-2025/laws-new-first-impression-transforming-client-intake/) warns that automated decisions need monitoring for bias and unintended disadvantage.

Keep **not qualified**, **insufficient information**, and **unable to reach** separate in reporting. Sample records involving language difficulty or incomplete answers so efficiency doesn't come from excluding callers who need help communicating.

Your [legal intake professionals](https://www.lighthouselegal.ai/learn/legal-intake-professionals) should own this review process. Automation can apply written rules, but someone at the firm must remain responsible for whether those rules are working appropriately.

### One Injury Caller's Path Through Intake

Consider **Maria, a fictional caller**, who is rear-ended on a Friday night and calls at 9:05 p.m. The service answers with the firm's greeting, captures her name and callback number, and identifies the inquiry as a rear-end collision.

Maria gives the incident date and suburb where it happened. She reports neck pain and says she plans to visit the emergency room over the weekend. The intake record distinguishes **reported symptoms** from **planned treatment**, so the reviewer won't mistake her intention for a completed visit.

#### The location changes the destination

The suburb is outside the firm's primary county but inside the metro area covered by its second team. The script flags that location because this firm requires the second team to review those inquiries.

Maria's record receives a **needs-attorney-review** label. Assuming no urgent escalation trigger is present, the service creates a Monday-morning review task for that team, attaching the summary and full transcript rather than rejecting her inquiry.

> **The turning point:** Maria's location changes who reviews the file. It doesn't decide whether her claim has legal merit.

The closing message explains that the designated team will review the information. Nobody promises representation, predicts a recovery, or tells Maria that the firm has accepted her case.

#### What the reviewer can act on

The reviewer receives a usable sequence: who called, how to reach her, what happened, where it happened, what symptoms she reported, and what treatment remained only planned. The unresolved question is explicit: whether the second team will accept the matter for further evaluation.

Separately from this fictional scenario, Chandler Conway Law collected **4 key intake facts** for firm review using our service and filtered out **47% of callers as irrelevant** using those details. Those are individual customer results, not a universal screening target or a reason to reject borderline inquiries.

Maria's example illustrates the more important operational test: did the service preserve the fact that mattered and place it before the right person? A complete record is useful only when someone receives and acts on it.

### What a Legal Intake Service Does Not Do

An intake service isn't an automated attorney. It can capture facts, apply documented screening rules, and organize handoffs, but the firm must reserve advice, representation decisions, and legal analysis for its lawyers.

The [ABA Model Rules document hosted by the USPTO](https://www.uspto.gov/sites/default/files/documents/AbavsUSPTO.pdf) addresses lawyers' communication and supervisory responsibilities. Design the intake record so an attorney can review what the caller said, what the service communicated, and what remains outstanding.

**What the intake service does and does not do**

| The service does | The service does not |
| --- | --- |
| Captures facts in the firm's own schema | Give legal advice or judge the merits |
| Screens against the firm's documented criteria | Promise representation or accept a case |
| Routes callers to people and creates review tasks | Calculate limitation deadlines |
| Escalates uncertainty, distress, language gaps, or emergencies | Create an attorney-client relationship |

#### Verify safeguards alongside the script

[ABA Formal Opinion 512](https://www.americanbar.org/content/dam/aba/administrative/lawyers_professional_liability/fall-2025-lpl-conference/3-when-will-lawyers-ever-learn-generative-ai/aba-formal-opinion-512.pdf) identifies confidentiality, competence, communication, and supervision duties relevant to generative AI. Before launch, document these controls:

-   **Caller disclosure and consent:** How AI use is explained and recording or transcription consent is handled.
-   **Data handling:** Ownership, storage, access, encryption, training use, retention, and deletion.
-   **Human intervention:** Escalation for uncertainty, distress, language difficulty, missing critical facts, or possible emergencies.
-   **Auditability:** Timestamps, transfer attempts, human interventions, vendor access, and incident-response responsibilities.

Our firm customers own their call data. Our agent follows the firm's criteria, never gives legal advice, and transfers to a person when asked; the firm should also approve its emergency and failed-transfer procedures.

The comparison below provides a shareable boundary summary for staff.

![A comparison chart outlining what a legal intake service does versus what it does not do.](https://cdnimg.co/11a2db61-834c-48a5-b6b6-a28a4c32e2c5/96565ade-5f7d-49ca-a3a6-0668a3a47157/legal-intake-service-comparison-chart.jpg)

Our outputs are **working aids only**, not legal advice, legal opinions, factual findings, or admissible evidence. Recordings and transcripts support review; they don't establish that every captured statement is accurate.

We cover nights, weekends, overflow, and routine screening. That extends the intake team's coverage rather than replacing the people who make decisions.

### How to Bring a Legal Intake Service Into Your Firm

Start with a coverage gap you can describe, such as unanswered evening inquiries. Then use a limited launch to check the entire path from greeting to completed follow-up.

#### A controlled launch sequence

1.  **Write your rules.** Document intake questions, practice areas, geography, and matters you decline. Flag legally complex scenarios for review; the [Law Office of Bryan Fagan on immunity](https://www.texaspersonalinjury.net/cprc-101-051-limited-waiver-for-texas-school-districts/) is an example of legal context that belongs with counsel, not an automated merits decision.
2.  **Name destinations.** Assign qualified transfers, uncertain files, and backup callbacks to specific people.
3.  **Choose coverage.** Decide between after-hours, weekends, staffed-hours overflow, or continuous answering, then configure forwarding and menu options.
4.  **Test the record.** Bring your current questions to our demo, use made-up case details, and review the transcript and report against your field list.
5.  **Pilot narrowly.** For example, try two evenings a week from 6 to 9 p.m. Review every recording before expanding.
6.  **Review weekly.** Sample transcripts, resolve misclassifications, and confirm that missed-transfer callbacks occurred.

The launch checklist also helps staff confirm the script and handoff together.

![An infographic titled How to Bring a Legal Intake Service Into Your Firm, featuring a 5-step launch plan.](https://cdnimg.co/11a2db61-834c-48a5-b6b6-a28a4c32e2c5/061fcb0d-c789-4f5f-9f38-72e674c00f68/legal-intake-service-launch-plan.jpg)

We offer a free trial and a demo agent at **+1 (681) 376-0380** that you can call as a fictional personal-injury client. Use invented details, then inspect what the conversation produced.

Pick one gap, such as nights, and close it this month. Expand only after the records and handoffs meet your firm's standards.

* * *

Lighthouse Legal offers customizable AI voice agents that collect personal-injury intake details, screen against your firm's criteria, and connect qualified callers with your team. Visit [Lighthouse Legal](https://lighthouselegal.ai) to bring your current intake questions to a demo and test how a fictional call moves from greeting to attorney review.

[Book a demo](https://www.lighthouselegal.ai/#book-demo) [See how it works](https://www.lighthouselegal.ai/#how-it-works)
