Law Firm Intake Automation: Route Every Inquiry the Same Day

Law firm intake automation is the set of rules and software that moves every new inquiry from a web form, email, phone message or chat to a named person on the same business day. It does not replace the attorney who decides whether to take the matter. If you run the office at a firm in Medford, Burlington County or across the Philadelphia metro, you probably are the intake team. This guide shows how to route inquiries to one owner, keep attorney review in place, and decide whether to add a legal CRM module or build a system around your own process. Start with the queue, not the tool.

1. What law firm intake automation covers, and what it leaves alone
2. Where same-day response breaks in a small firm
3. Building the intake workflow: one queue, one owner, one deadline
4. Where attorney review stays: what AI drafts and what a person approves
5. Intake forms and Rule 1.18: wording and timing
6. Subscribe to a legal CRM add-on or build a custom intake system
7. Website inquiry pages that feed the queue
8. Rollout: training the front desk and the first 30 days
9. What we cannot tell you yet
10. Frequently Asked Questions
11. Next step

What law firm intake automation covers, and what it leaves alone

Intake is the stretch between "someone reached out" and "an attorney has the facts and a decision is made." Automation helps with four jobs inside that stretch. It captures the inquiry, assigns it, acknowledges it, and reminds someone when nothing has happened. Everything else is a human call.

Here is the practical split.

• Capture: every channel writes to one record. Web form, email to the intake address, voicemail transcription entered by the front desk, and chat all land in the same place.
• Route: a rule assigns an owner and a backup based on matter type, time of day and who is out.
• Acknowledge: the person gets a short message saying the firm received the inquiry and when to expect a reply. It does not say the firm will take the matter.
• Remind: if the inquiry sits past the firm's own deadline, the system escalates to the backup and then to the office manager.

It leaves alone the conflict decision, the fee conversation, the engagement letter and any statement about the person's legal rights. Those belong to attorneys. A system that blurs that line is a risk, not a time saver.

Several terms show up in this guide. A CRM (customer relationship management system) is a database of people and conversations with rules attached. A queue is the single list of inquiries waiting for action. A service standard is a written deadline, such as "reply the same business day." Search results for legal client intake software tend to blur these together. We keep them separate because each one fails in a different way.

If you want to see how a full custom build connects intake to conflict review, engagement, matters, deadlines and billing, our custom law firm CRM and workflow software page lays out the scope. For this guide, the focus is the front end: getting each inquiry in front of the right person fast.

Where same-day response breaks in a small firm

The common vendor message is "respond instantly." That is a goal, not a plan. In a firm of two to ten people, the failure is rarely speed. It is that nobody was clearly responsible when the inquiry arrived.

Four places an inquiry goes missing

These are the gaps we see described again and again in small-office workflows, and each one is a design question rather than a software question.

1. Split inboxes. The web form goes to a shared mailbox, the phone goes to voicemail, and a referral emails an attorney directly. Nobody sees all three.
2. The 6 p.m. gap. An inquiry that arrives after the office closes waits for morning, and the morning list is already full.
3. Weekends. A Saturday inquiry on a form is acknowledged by an auto-reply, and then nothing happens until Monday. Whether that is acceptable depends on the matter.
4. The owner is out. The person who normally handles intake is at a hearing, on vacation or sick. No backup is named, so the queue stalls.

Most vendor intake pages describe an instant reply. They rarely say who gets the alert at 6 p.m., who covers on a weekend, or who is the backup. Those answers are the workflow.

About response-time benchmarks

You will see response-time targets in vendor and agency blogs, usually a handful of minutes up to an hour. In the pages we reviewed, we did not find a stated method behind them: no sample, no definition of "response," no split by matter type. We do not repeat those numbers here as if they were established. We cannot confirm how they were measured, so we treat them as vendor opinion.

What you can do is set your own standard and measure against it. A tiered standard works better than one number, because a person calling about an arrest or a court deadline is not in the same position as someone asking about a will update. The table below is a template. The numbers are examples for your managing partner to change, not industry benchmarks.

Example service standard by urgency (set the numbers with your managing partner)

Urgency tier	Example matter signals	Example standard	After hours
Urgent	Hearing or filing date within days, detention, emergency order	Human contact within the hour during business hours	Alert to on-call person's phone; backup if no reply
Standard	New dispute, estate, business or family matter with no immediate date	Human reply the same business day	Acknowledgement now; first in queue next morning
Low urgency	General question, document request, existing-client item	Reply within one business day	Acknowledgement now; routine queue

Note that the form cannot decide urgency alone. A required field asking "Is there a court date or deadline in the next 14 days?" gives the system a signal. A person still confirms it.

Building the intake workflow: one queue, one owner, one deadline

A good law firm intake workflow fits on one page. If you cannot draw it on one page, your team will not follow it in week three. The full step-by-step version, including the web form, email, phone message and chat handling, is in our same-day intake map for law firms. Here is the shape of it.

Step 1: put every channel into one queue

List every way a prospective client can reach you today. For most small firms that is a contact form, a general email address, the main phone line, direct emails to attorneys, referrals, and sometimes a chat widget or text. Each channel must end in the same record.

Phone is the hard one. Voicemail does not write itself into a database. Decide who logs each message, and by when. If that is the front desk, the rule is "log it before the next call," not "log it at the end of the day."

Step 2: name an owner and a backup per matter type

Assign by matter type, not by who is free. An estates inquiry goes to a named paralegal or intake coordinator. A litigation inquiry goes to someone else. Each has a named backup. Write the names into the routing rule, then put the rule on a single page the whole office can read.

Add one more rule: an inquiry with no owner goes to the office manager. That is the safety net, and it is also the number you will report weekly: inquiries that had no owner for more than a set window.

Step 3: send one acknowledgement

One message, sent immediately, saying three things: we received your inquiry, here is when a person will reply, and sending this message does not create an attorney-client relationship. The wording of that last line is for your ethics counsel to approve. Do not let a vendor template stand in for that review.

Step 4: attach a deadline and an escalation

Each queue item carries a due time based on the service standard above. If it passes, the system alerts the backup. If it passes again, it alerts you. That chain is what turns "we respond fast" into a thing you can check.

We built a similar pattern for wholesale operations. WRAPT, the lead-to-delivery operations platform we built, runs a nine-stage pipeline with a client portal and an omnichannel support hub, including the TAMI web-chat agent. A law practice is a different business with different rules, but the principle carries over: every item has a stage, an owner and a next step on screen.

Where attorney review stays: what AI drafts and what a person approves

The objection we hear most from small firms is reasonable: "I do not want software making decisions about prospective clients." Good. It should not. The design question is which steps are drafts and which are approvals, and where overrides are recorded.

Adoption data suggests small firms are cautious here, and that is not unusual. The U.S. Census Bureau reports that Census Bureau's Business Trends and Outlook Survey analysis (May 2026) found less than 20% of firms with four or fewer employees reported using AI between December 2025 and May 2026. That figure covers all industries. We do not have a law-firm-only number, so do not read it as one.

Measuring AI use is also less settled than it sounds. Census changed the wording of its AI question in late 2025, and a Federal Reserve Board note on monitoring AI adoption (April 2026) compares how different surveys arrive at different adoption estimates. When a vendor quotes a much higher figure, check the survey's method before you repeat it.

A draft-versus-approved map for intake

Our rule is simple. The system may draft or sort. A person approves anything that goes to the prospective client beyond the standard acknowledgement, and anything that affects whether the firm takes the matter.

Intake steps by who acts: system, draft for review, or human decision

Intake step	What the system does	Who approves	Logged
Acknowledgement	Sends a fixed, pre-approved message	Wording approved once by the firm	Time sent
Summary of the inquiry	Drafts a short summary from the form or chat text	Intake owner reads against the original	Edits made
Matter-type tag	Suggests a tag from the text	Intake owner confirms or changes it	Suggested versus final tag
Urgency flag	Raises a flag on keywords or the deadline field	Person confirms the urgency tier	Overrides
Conflict check	Prepares names for search	Attorney or designated staff decide	Result and reviewer
Accept, decline or refer	Nothing	Attorney	Decision and date

The override log matters as much as the draft. If staff change the matter-type tag 30% of the time, the suggestion rule is wrong and you need to retrain it. That number would be yours, from your own queue. We are not quoting a benchmark.

What a legal intake chatbot should and should not do

A legal intake chatbot on your site should collect a name, contact details, a short description, and the deadline field. It should say it is not a lawyer and that no attorney-client relationship exists. Then it should create a queue item and stop. It should not assess the strength of a case, suggest a course of action, or promise a callback time the firm has not committed to.

Take care with what you let it collect. Prospective clients sometimes type sensitive facts into a chat box. The more detail the box invites, the more your firm holds before a conflict check. The next section covers that.

Our AI workflow automation work is built around approvals and exception handling for this reason. The system proposes; a person with the right authority disposes. For a deeper walk through each step, see what AI drafts at intake and where an attorney reviews it.

Intake forms and Rule 1.18: wording and timing

Rule 1.18 of the ABA Model Rules of Professional Conduct addresses duties to a prospective client, including confidentiality of what someone tells you before you take the matter. Each state adopts its own version. New Jersey and Pennsylvania firms should read their own state rule, and confirm specifics with their ethics counsel or state bar. We are not lawyers and this is not legal advice.

The operations point is narrower. The form decides how much a prospective client tells you before anyone has run a conflict check. That is a design choice you control.

What a short form should ask

Client intake forms for law firms work best in two stages. Stage one is minimal: name, phone, email, matter type from a list, preferred contact method, and the deadline question. Stage two is the longer questionnaire, sent after the conflict check clears and an attorney agrees to proceed.

• Ask at stage one: who you are, how to reach you, the general category of the matter, and any date within the next two weeks.
• Names for the conflict check: many firms ask for the opposing party's name early, because the conflict search needs it. Whether to ask on the first form is a decision for your ethics counsel.
• Hold back for stage two: detailed facts, medical or financial specifics, and documents.

Wording that belongs on the form

Put a plain-language notice next to the submit button. It should say that submitting the form does not create an attorney-client relationship, that the firm may not be able to take the matter, and that the person should not send confidential details until the firm confirms. It should also say what to do if there is an urgent deadline: call. Have your counsel write or approve the actual sentences.

The ABA also issued Formal Opinion 512 on lawyers' use of generative AI tools, which touches on confidentiality and client information. If any part of your intake sends prospective-client text to an AI service, ask your ethics counsel whether and how that opinion and your state's rules apply, and ask the vendor in writing where the text goes and whether it is retained. We cover the practical form wording in our guide to prospective-client intake forms and confidentiality.

When to route to a lawyer first

Set a rule for inquiries that skip your form. If someone emails a long account of the facts to the general inbox, the intake owner should not reply on the merits. The rule can be as short as: forward to a named attorney, send the standard acknowledgement, and stop. Write it down so nobody improvises at 5:45 p.m.

Subscribe to a legal CRM add-on or build a custom intake system

Clio Grow, Lawmatics and MyCase each describe their own intake features on their own pages. That is useful for learning what the tools do. It is not a comparison, because each page is written by the vendor, and none says who owns the forms, data and integrations if you leave. We cannot give you current vendor prices from this article: pricing is typically per user or by quote, changes often, and we did not retrieve current list prices for this guide. Get written quotes.

Compare a first-year total, not a monthly fee

A per-user monthly number tells you little. For a firm of eight, build the first-year picture from these lines:

• Subscription fees for every seat that touches intake, plus any add-on or module fee.
• One-time setup or onboarding, if charged.
• Integrations: your website form, phone system, calendar, e-signature and billing tool. Ask which are included and which cost extra.
• Staff time to configure, train and fix it. This is real, even though it never appears on an invoice.
• The cost of leaving: how you export forms, contacts, notes and automation rules.

When subscribing makes sense

Subscribe if your process already looks like the vendor's default. You get a tested product, support, and updates. If your matter types are few, your routing is simple, and your team already uses the platform for matters and billing, an add-on is usually the faster route. That is a real advantage and we will say so plainly.

When a custom build makes sense

Consider building when your routing rules, conflict review steps or intake forms differ from the defaults. Also consider it when you want to own the forms, the data and the integrations under your project agreement. A custom intake system can connect to your calendar and email, route by your own matter types, and keep a draft-and-approve log shaped to your review steps. Our custom CRM development work is scoped that way.

On cost, our published custom-app tiers run from $15,000 to $100,000+, and the starting ranges on iolab.co/pricing are the figures to use. Where an intake system lands depends on how many channels, integrations and review steps it has. Hosting, third-party subscriptions and ongoing support are scoped separately and are not part of the build price. We would rather show you that boundary than hide it.

Ownership checklist to complete before you sign either way

Question	Ask the vendor or builder
Forms	Can we export every form and its logic in a usable format?
Data	Do we own contacts, notes and logs, and can we export them in bulk?
Integrations	Who holds the API keys and accounts for phone, calendar and e-signature?
Automation rules	Are routing rules documented in a form a new vendor could read?
AI features	What text goes to which service, is it retained, and who reviews output?
Exit	What does leaving cost, and how long does a migration take?

The full decision, including how to price each side with sources and dates, is in our comparison of legal intake software and a custom CRM. Buying typically takes several weeks of demos, quotes and trials, so start before your budget year does. We cannot tell you the exact length for your firm.

Website inquiry pages that feed the queue

Intake starts before the form. The page a prospective client lands on shapes who submits, what they type and how urgent it is. If your site sends everything to one generic "Contact us" form, your queue fills with unsorted messages.

For a firm in Medford or elsewhere in Burlington County, the page work has three parts.

• Practice-area pages with their own short form. A divorce page and an estate planning page should each submit with the matter type already set. That removes one step for the intake owner.
• Local pages that name the places you serve. Mention Burlington County, Camden County, Philadelphia and the courts and towns you actually appear in. Do not list places you do not serve.
• Required fields kept to a minimum. Name, a way to reach them, matter type and the deadline question. Every extra required field loses some submissions. We do not have a figure for how many, and you should be suspicious of anyone who offers one without a method.

Decide where each submission lands before you design the page. A form that emails an attorney's personal inbox defeats the one-queue rule. Route it to the queue, and let the system notify the owner.

Search visibility is a separate job, and we cannot promise any ranking. What we can do is structure pages around the questions prospective clients actually ask, and connect form submissions to attribution so you know which page produced which inquiry. That is what our SEO and content work built around service intent and lead attribution is for. Your Google Business Profile also matters for local searches, and our Google Business Profile audit checklist covers the fields to check. The page-level detail is in our guide to website contact forms and intake pages for South Jersey firms.

Rollout: training the front desk and the first 30 days

Most intake articles stop at "turn it on." You are the one who has to run it Monday morning, so here is a rollout sequence for the person who runs it daily.

Before launch

1. Write the one-page workflow: channels, owners, backups, service standard, after-hours rule.
2. Get written approval of the acknowledgement and form notice from the managing partner and, as needed, ethics counsel.
3. Test every channel with a dummy inquiry. Submit the form, send the email, leave a voicemail and open the chat. Confirm each one lands in the queue with the right owner.
4. Run a drill on the backup rule: mark the owner as out and confirm the item moves.

Training the front desk

Keep it to three habits. Log every phone message before the next call. Never answer on the merits. Never leave an item without an owner. Give people the one-page workflow and a short list of "what to say" for the phone, written by an attorney. Short training sticks better than a long manual.

The first 30 days

• Week 1: check the queue three times a day. Look for inquiries with no owner and fix the routing rule that missed them.
• Week 2: compare AI-suggested tags and summaries with what staff changed. Read the override log.
• Week 3: review after-hours items. Did the weekend and evening rule work, or did items wait too long?
• Week 4: report to the managing partner. Keep it to one page.

The weekly report needs a few numbers, all pulled from the system rather than recalled from memory: time to first contact, inquiries with no owner, consult-booked rate, and source by channel. The details are in the seven intake numbers an office manager can report each week. We will not tell you what good looks like in numbers, because you do not yet have a baseline. Your first month creates it.

If you are curious how a similar "route every lead to an owner" rule works in another field, see our post on lead routing rules in real estate follow-up. The industry differs, but the owner-and-backup idea transfers.

What we cannot tell you yet

A few honest limits. We do not have a sourced benchmark for law firm lead response time, and we did not find a vendor figure with a stated method. We do not have a law-firm-specific AI adoption number, only the all-industry Census data above. We did not retrieve current vendor price lists for this guide, so confirm quotes yourself. And we cannot tell you how your state's rules apply to your intake form. Your ethics counsel or state bar can.

What we can say is how to structure the work: one queue, a named owner and backup, a written service standard by urgency, a draft-and-approve map with an override log, and an ownership checklist before you sign anything.

Frequently Asked Questions

What is law firm intake automation?

Law firm intake automation is software that captures new inquiries from your web form, email, phone messages and chat, puts them in one queue, assigns each to a named person, and sends a first acknowledgement. It handles routing and reminders. Conflict checks, fee discussions and the decision to accept a matter stay with attorneys and staff.

How fast should a law firm respond to a new inquiry?

There is no single sourced benchmark we can point you to. Vendor blogs publish targets measured in minutes, usually without saying how they measured. A better approach is a written standard by matter type: a fast target for urgent matters, same business day for the rest, and a named backup for evenings and weekends. Your managing partner sets the numbers.

Can a legal intake chatbot give legal advice or accept a client?

It should not. A legal intake chatbot should collect contact details and a short description, state plainly that it is not a lawyer and that no attorney-client relationship exists yet, and hand the conversation to a person. Exact disclaimer wording and what to collect before a conflict check are questions for your firm's ethics counsel or state bar.

Should a small firm buy legal client intake software or build a custom law firm intake system?

Buy when your process already matches a vendor's defaults and you can live with per-user pricing. Build when your routing, conflict review or forms differ from those defaults, or when you want to own the forms, data and integrations. Compare a first-year total with setup, integrations and staff time, not the monthly price alone.

Prices in this article are starting ranges published on iolab.co/pricing. Hosting, third-party subscriptions and ongoing support are scoped separately in your proposal.

Next step

If you run intake for a small firm and want to talk through the queue, the owner and backup rules or a build-or-subscribe decision, contact us. We can look at how your firm handles inquiries today and say plainly whether an add-on or a custom build fits. You can see what we cover for firms on our law firm software page, and the buy-or-build detail is in our subscribe-or-build comparison. We write general information about software and operations. Legal and ethics questions go to your own counsel.