Law Firm Client Intake Process: A Step-by-Step Workflow

Law Firm Client Intake Process: A Step-by-Step Workflow

A law firm client intake process should move every inquiry to a recorded outcome. The person schedules a consultation, is waiting on a named next step, is declined under firm policy, receives an approved referral path, or becomes a client after the firm completes its legal review and engagement process.

Most intake systems do not fail because the firm forgot to buy software. They fail in the gaps between a phone call, an intake form, a conflict check, a consultation, and an engagement letter. Each step may have an owner. The whole outcome usually does not.

The result is familiar: a voicemail sits until lunch, the prospective client repeats the same facts to three people, a consultation gets scheduled before the firm has enough information for its conflict procedure, and nobody can tell whether yesterday's inquiries were resolved.

This guide gives small law firms the stages, ownership rules, measurements, and control fields needed to carry an inquiry from first contact to a recorded outcome.

The short version: fix these eight things first

Use this as a first-pass audit of your current process:

1. Give every open inquiry an owner, next action, and due time.
2. Limit the first form or call script to information the firm has approved for routing and its conflict procedure.
3. Write down what must happen before anyone may offer a consultation time.
4. Separate scheduling questions from questions that require legal judgment.
5. Give lawyers a short decision request instead of forwarding the whole intake thread.
6. Record every message, status change, appointment, and disposition in one controlled record.
7. Test the workflow with fictional inquiries before connecting it to live channels.
8. Measure stage age, missing controls, and finished dispositions rather than raw lead count.

If the firm cannot answer who owns an inquiry and what happens next, automation will only move the confusion faster.

Define what "done" means before you automate intake

A new inquiry is not finished when someone answers the phone. It is finished when the operational record has one clear disposition:

1. Consultation scheduled after the firm's required preliminary steps.
2. Waiting on the prospective client, with the exact missing item and follow-up date recorded.
3. Waiting on lawyer review, with a decision-ready brief and deadline.
4. Declined under an approved rule, with the approved communication sent and recorded.
5. Referred through a firm-approved process.
6. Engaged after the firm completes its required review, agreement, and onboarding steps.
7. Closed after the approved no-response sequence.

"Open" is a temporary state, not an outcome. Every open record needs an owner, a next action, and a due time. Without those fields, the firm has a list of inquiries rather than an intake process.

Where manual intake breaks

The breakdown often starts with a harmless shortcut.

A receptionist takes a name and phone number on paper because another call is waiting. A lawyer asks for "a little more detail" by email. The prospective client sends a long account with names, dates, medical details, business records, or strategy. Someone starts checking calendars before the firm has completed its normal conflict procedure. A follow-up task lands in one person's private inbox.

Nothing looks catastrophic on its own. The operational risk comes from accumulation:

• information is captured before the firm has decided what it needs;
• the same facts are stored in several places;
• staff cannot see which step is blocking the matter;
• routine scheduling waits on a lawyer who is reviewing a separate question;
• prospects receive inconsistent updates;
• the owner reviews activity counts instead of finished outcomes.

The software may show 19 new leads. It does not tell the managing partner that four lack opposing-party names, two are waiting on a practice-area decision, one needs a conflicts decision, and twelve have already reached a clean next step.

Collect enough information, then stop

Legal intake is different from ordinary sales intake because duties can arise before a person becomes a client.

ABA Model Rule 1.18 defines a prospective client as someone who consults with a lawyer about possibly forming a client-lawyer relationship. It also addresses the use and disclosure of information learned during that consultation and the conflicts that can follow from receiving significantly harmful information.

That makes "tell us everything" a poor opening instruction.

The initial intake should collect the minimum information required by the firm's approved process to identify the person, route the inquiry, and begin the appropriate conflict procedure. The ABA's overview of client intake and conflict checks says the needed information commonly includes the potential client's identity, area of law, general nature of a contentious matter, and relevant adverse-party information. It also says the conflict check should occur before legal advice and before signing an engagement letter.

Your exact fields depend on jurisdiction, practice area, and firm policy. A restrained first-pass form might ask for:

• full legal name and approved contact details;
• how the person found the firm;
• broad matter type;
• opposing parties and other names required by the firm's conflict procedure;
• relevant jurisdiction or venue, when needed for routing;
• an urgent date stated by the person, without the system interpreting it;
• preferred contact method;
• a short neutral description with a clear warning not to send documents or a full narrative yet.

The intake system should not decide that a deadline is valid, that a claim has merit, or that the firm represents the person. It should record what the person said and move the record to the right next step.

Give one AI employee responsibility for keeping intake moving

A form collects answers. A chatbot handles a conversation. An AI intake employee keeps the administrative process moving from first contact to a finished disposition.

The trigger can be a call, voicemail, web form, email, referral entry, or approved message channel. From there, the AI employee:

1. Creates or matches the contact record.
2. Checks for duplicate inquiries without merging uncertain identities.
3. Collects only the approved first-pass fields.
4. Asks focused follow-up questions when a required field is missing.
5. Classifies the inquiry for routing using firm-approved categories, not a legal conclusion.
6. Starts the firm's conflict-check procedure or packages the required data for the authorized reviewer.
7. Offers consultation times only when the firm's stage rules allow it.
8. Sends confirmations and approved reminders.
9. Handles routine questions from written firm policy.
10. Updates the CRM, calendar, intake status, and communication record after each action.
11. Continues unaffected work when one issue needs review.
12. Closes the record with a disposition and a complete activity trail.

This matters because intake unfolds over hours or days. A person may return a missing name at 7:14 p.m., ask to move the consultation the next morning, then send an unrelated legal question. The employee should complete the scheduling change, preserve the question, and route only the legal issue. The entire intake should not freeze because one action needs lawyer judgment.

This is the same distinction explained in what an AI employee is: the job is not answering one prompt. The job is carrying work to completion across systems and time.

What one small-firm setup looks like

Consider a five-person employment firm using a website form, shared intake inbox, CRM, conflict-review queue, and calendar. This is an illustrative setup, not a client result.

A website inquiry arrives at 6:42 p.m. The form includes the person's legal name, contact details, broad matter type, employer name, and an unverified date the person believes is urgent.

The AI employee creates the CRM record and checks for possible duplicates. It finds none. The firm's intake policy also requires the names of individual supervisors for its conflict procedure, so the employee asks only for those names. It does not request a full account or documents.

The person replies at 7:10 p.m. The employee updates the same record, packages the approved fields for the conflict-review queue, and marks consultation scheduling as paused. It sends the firm's approved acknowledgment, which makes clear that submitting information does not mean the firm accepted the matter.

The next morning, the authorized reviewer selects "clear to schedule" under the firm's process. The employee records that status, offers three times from the approved calendar, books the selected slot, and sends the preparation instructions.

Then the person asks, "Should I sign the severance agreement before Friday?" The employee does not answer. It sends the lawyer a short brief with the question, the unverified Friday date, the scheduled consultation, and a link to the intake record. The appointment remains booked while the legal question waits for the lawyer.

If the CRM is unavailable during any of these steps, the employee should not create a shadow record and keep going. It should stop the affected update, retry under the firm's outage rule, preserve the received message in the approved fallback, and alert the named owner if the recovery window expires. When service returns, it reconciles the record before sending another message.

That is the level of detail to test. "Automate intake" is not a workflow. Triggers, fields, allowed actions, stop conditions, system writes, and recovery steps are.

Use six stages with explicit exit rules

Stage names should tell the team what happens next. "New," "working," and "hot" are too vague.

Stage 1: inquiry received

Entry: a new contact arrives through an approved channel.

The AI employee records the source, time, contact details, and the minimum first-pass information already provided. It sends the approved acknowledgment without implying that the firm accepted the matter.

Exit: the record is either closed as invalid or duplicate, or it has enough verified information to enter preliminary screening.

Stage 2: preliminary information incomplete

Entry: one or more required routing or conflict-check fields are missing.

The employee asks only for those fields. The task names the missing item, next contact time, channel, and closure rule. Do not use a generic "follow up" task.

Exit: required fields are complete, the person declines to provide them, or the approved no-response sequence ends.

Stage 3: firm review required

Entry: the record is ready for a lawyer or other authorized reviewer under firm policy.

The reviewer should not receive a forwarded email with "thoughts?" The employee sends a short brief:

Decision needed by 2:00 p.m.: May intake proceed to consultation scheduling? Prospective client: Jordan Lee. Matter category: employment. Names collected for the firm's conflict procedure: Jordan Lee, Northlake Services LLC, and Casey Morgan. Urgent date stated by caller: August 18; not verified. No documents collected. The person asked whether the firm handles this category. Decision options under intake policy: proceed to consultation scheduling, request one named item, decline, or refer. Source record: [link].

Exit: the authorized reviewer selects a permitted next step and the employee records it.

Stage 4: consultation scheduling

Entry: the firm's preliminary requirements are satisfied and scheduling is allowed.

The employee offers approved times, confirms the selected slot, sends the firm's approved preparation instructions, and records attendance status. If the person asks for legal advice while scheduling, that question becomes a separate exception. The scheduling work continues.

Exit: consultation completed, canceled with a next action, missed with an approved follow-up, or closed.

Stage 5: post-consultation decision

Entry: the consultation occurred and the lawyer records the approved disposition.

The employee completes the administrative branch: send the approved engagement package, request a permitted missing item, deliver the firm's decline communication, initiate an approved referral, or schedule a later follow-up. It does not choose whether the firm accepts the matter.

Exit: engaged, declined, referred, deferred to a date, or closed.

Stage 6: engagement handoff

Entry: the firm's required acceptance and agreement steps are complete.

The employee creates the onboarding tasks, confirms the responsible lawyer and staff, records the communication plan, and ensures the intake record points to the new matter. It should never leave two disconnected records that force staff to rebuild the history.

Exit: the matter team has the complete approved intake package and a named first action.

Keep lawyer judgment where it belongs

The earlier article on AI for law firms without practicing law provides a broader responsibility matrix. For intake, the division is straightforward.

The AI employee can own administrative continuity: collecting approved fields, checking completeness, asking routine questions, scheduling when permitted, sending approved communications, updating systems, and tracking each record to an outcome.

A lawyer or other person authorized by the firm decides matters such as:

• whether a conflict exists and what response the rules require;
• whether the firm will accept or decline a representation;
• whether a deadline or legal position is valid;
• what legal advice to provide;
• whether an exception to firm policy is appropriate;
• what jurisdiction-specific duties apply.

The controls sit behind the workflow. Staff should not have to approve every reminder or calendar change. They should see the items that require professional judgment, with the facts already organized.

The ABA's 2024 summary of Formal Opinion 512 on lawyers' use of generative AI applies existing duties including competence and confidentiality to the technology. Model Rule 1.6 addresses unauthorized disclosure and access, while Model Rule 5.3 addresses responsibilities concerning nonlawyer assistance.

Those are model rules, not a universal implementation policy. Before connecting an AI employee to live intake, the firm should identify the controlling rules, ethics opinions, engagement language, vendor terms, retention rules, security requirements, and supervision duties for its jurisdiction and practice.

Copy this intake control sheet

Create these fields in the system that will serve as the operational source of truth:

Identity and source

• Intake ID
• Date and time received
• Source channel
• Full legal name
• Contact details
• Preferred contact method
• Duplicate-check status

Preliminary matter information

• Broad practice-area category
• Neutral short description
• Jurisdiction or venue stated by prospect
• Adverse and related names required by firm policy
• Urgent date stated by prospect
• Document collection allowed: yes/no
• Required field completeness: complete/incomplete

Workflow control

• Current stage
• Stage-entry time
• Current owner
• Next action
• Next action due
• Last meaningful contact
• Contact permission or restriction
• No-response attempt count
• Exception type
• Source-record link

Review and disposition

• Conflict-procedure status, without exposing restricted analysis
• Authorized reviewer
• Decision requested
• Decision due
• Reviewer disposition
• Consultation status
• Final intake disposition
• Closure reason
• Engagement or matter record link

Do not expose sensitive conflict analysis to everyone who can see the intake pipeline. Store only the status and operational next step where broader visibility is necessary. Apply the firm's access policy to the underlying review.

Use this exception brief

Every escalation should fit this structure:

Decision needed: the exact question the authorized person must answer.

Needed by: the time and the operational reason.

Verified facts: only facts checked against the source record.

Prospect-stated facts: claims or dates that have not been legally verified.

Actions completed: acknowledgments, information requests, scheduling holds, or system updates already finished.

Permitted options: choices already defined by firm policy.

Paused action: the one action waiting on the decision.

Work still moving: every unaffected action the employee continues.

Source: a direct link to the controlled record.

That format saves the lawyer from reconstructing the intake and makes the decision auditable.

Roll it out in four controlled steps

1. Map one intake path

Choose one practice area and one inquiry source. Write the current stages, required fields, decision owners, messages, closure rules, and systems. Do not begin with every practice area and channel.

2. Write authority and exception rules

List the routine actions the employee may complete. Then name the events that require legal or policy judgment. Use examples from actual intake history, stripped of client and prospective-client information during design unless the firm has approved how that data is handled.

3. Test with synthetic records

Create fictional inquiries that cover missing names, duplicate contacts, urgent stated dates, rescheduling, no response, a legal question inside a scheduling message, and a matter the firm does not handle. Verify that the employee updates every system and pauses only the affected action.

4. Run a limited supervised pilot

Use one approved channel and a narrow volume. Review the final records, not only the messages. Check whether each inquiry has a disposition, whether exceptions reached the right person, and whether the activity trail matches what actually happened.

Expand only after the workflow passes those checks.

Measure finished intake, not message volume

Track the operating result each week:

• inquiries received;
• records with a final disposition;
• open records missing an owner, next action, or due time;
• median time spent in each stage;
• records returned for missing required information;
• consultations scheduled, completed, canceled, and missed;
• exception count by type;
• decision turnaround time;
• engagement handoff defects;
• records closed under the no-response rule.

Do not set a universal benchmark from this article. Establish a clean baseline, find the stage where work accumulates, and improve that stage. A faster first response is useful only if the record reaches a correct next step.

Common mistakes

Asking for a full story too early

Long free-text forms create noise and may collect information beyond what the firm needs at the first stage. Use restrained fields and progressive collection based on the firm's approved process.

Calling routing a legal conclusion

An administrative category such as "employment inquiry" helps assign work. It does not determine merit, deadlines, conflicts, or advice.

Automating messages without owning replies

A reminder sequence that sends messages but leaves responses in an inbox gives the team more work. The operating owner must classify the reply, complete routine actions, update the record, and route true exceptions.

Scheduling before stage requirements are clear

Calendar availability is not the only condition. Write down when scheduling is allowed and what must happen first.

Forwarding raw exceptions

A lawyer should receive the decision, verified facts, options, deadline, and source link. Raw transcripts and screenshots make the lawyer redo the intake work.

Measuring leads instead of outcomes

A growing lead count can hide a stalled process. Review dispositions, stage age, missing controls, and handoff defects.

Build the workflow around your firm's rules

A dependable law firm client intake process gives every inquiry an owner and a clean next step without turning administrative work into legal judgment. The technology matters less than the operating design: minimum necessary collection, explicit stage exits, direct system updates, exception-only escalation, and a recorded disposition.

ComfortGrowth AI builds managed AI employees around the systems and policies a firm already uses. See how that applies to AI employees for law firms, or request a free business audit and intake workflow map. We will map where inquiries stall, which routine actions can be owned end to end, and which decisions must stay with the firm.

This article provides an operations framework, not legal advice. A firm should have qualified counsel review the workflow against the rules, opinions, laws, contracts, and professional duties that apply to its work.