Law Firm Client Intake Automation: From Enquiry to Conflict Check

Law firm client intake automation turns a new enquiry into a structured record: the matter type, urgency, and every party name the conflict search needs. Software normalizes the names, runs the searches the system allows, groups the results and prepares a summary. A lawyer decides whether there is a conflict and whether the firm can act. The enquirer gets a prompt acknowledgement that makes clear no advice has been given yet.

Intake is where many firms lose time without noticing. A receptionist takes a few details and emails a fee earner, who calls back for the other side's name, then someone keys names into the practice management system one at a time. Meanwhile the prospective client is calling another firm. This post sets out a workflow from first contact to the moment a lawyer decides to open the matter.

For a wider view of automation in legal practice, see our law firms hub.

AI Automation for Law Firms, Explained Step by Step · 3:08 Subscribe

Why intake is harder than it looks

• Details arrive incomplete. The enquiry names the client but not the other side, a company but not its directors, or a property but not the seller.
• Spelling varies. "Smith & Co Ltd", "Smith and Company Limited" and "Smith Co" are the same entity to a person, not always to a search.
• Too much information too early. An enquirer pours out the whole story before anyone has checked whether the firm can act, which creates confidentiality risk.
• Urgency is hidden. A limitation date, a court hearing or an exchange deadline may be mentioned in passing.

The professional rules behind intake

Conflict and confidentiality duties exist everywhere, but the detail varies by jurisdiction. Some examples to check against your own rules:

• United States: state rules largely follow the ABA Model Rules. Model Rule 1.18 sets duties to prospective clients, and its commentary advises lawyers to limit initial information to what is reasonably needed to decide whether to take the matter, including checking conflicts. The ABA's first ethics opinion on generative AI stresses confidentiality, competence and supervision when using AI tools.
• England and Wales: the SRA Code of Conduct prohibits acting where there is a conflict, or a significant risk of one, except in limited circumstances, and protects client confidentiality. The SRA's conflicts guidance explains how to identify them.
• Canada: provincial and territorial law societies set conflict rules, largely based on the Federation of Law Societies' Model Code, and client identification and verification rules.
• Australia: the solicitors' conduct rules cover duties to current and former clients. From 1 July 2026, AUSTRAC's tranche 2 reforms extended anti-money laundering obligations to lawyers providing certain services, including customer due diligence.

Automation can make the firm's process more consistent. It cannot apply these rules on the firm's behalf.

The intake and conflict check workflow, step by step

1. Capture the enquiry in a structured way (automated)

Replace the free-text "tell us about your problem" box with a short structured form, and give reception a matching call note template. Ask for:

• the enquirer's name and contact details
• the type of matter, from a short list
• the names of all other parties: individuals, companies, and related people such as directors, spouses or sellers
• any dates the enquirer knows about, such as a hearing, a deadline or a completion date
• how they heard about the firm

Add a clear line asking the enquirer not to send detailed facts or documents until the firm confirms it can help. This protects them and the firm.

2. Classify and flag urgency (automated, reviewed)

The enquiry is classified by likely matter type and routed to the right team. Mentions of dates, hearings, limitation or deadlines are flagged for a person to look at the same day. The system flags; it does not calculate limitation periods or decide what is urgent.

3. Acknowledge the enquirer (automated)

Send a prompt acknowledgement explaining what happens next and when they will hear back. Make clear that no lawyer-client relationship exists yet and that nothing in the message is legal advice. Use approved wording only.

Because legal enquiries are a target for fraud, send from a properly authenticated domain. Check your setup with the free DMARC checker, and if a suspicious "client" email arrives, the email header analyzer shows where it really came from. Our guide to email security for solicitors covers the risks in more depth.

4. Build the party list (automated, reviewed)

Every party mentioned is extracted into a list. Names are then normalized:

• common company suffixes are standardized (Ltd, Limited, LLC, Inc, Pty Ltd)
• punctuation and "and" versus "&" variations are handled
• former names and trading names the enquirer gave are added
• duplicates are removed

For a quick manual clean-up, the free remove duplicate lines tool handles a pasted list of names. A person checks the final list before searching.

5. Run the conflict searches (automated, depending on access)

The list is searched against client, matter and party records in the practice management system, as far as the system's access allows. Many systems include conflict search features; the workflow uses them rather than replacing them.

6. Group and summarize the results (review)

Results are grouped into exact matches, possible matches and no match, each linked to the related matter. A short summary goes to the lawyer or risk lead with the underlying search results attached, so they can see the evidence rather than a conclusion.

7. The lawyer decides (person)

The lawyer, with the risk lead where needed, decides whether a conflict exists, whether any exception or informed consent applies under the local rules, and whether the firm will act. The decision and reasons are recorded on the intake record.

8. Next steps if the firm will act (automated, reviewed)

Only now does the workflow request identity documents, run any electronic ID checks the firm uses, and prepare a draft engagement letter from approved wording for the lawyer to review. If the firm declines, a polite, approved decline message is prepared for a person to send, without giving reasons that could reveal another client's confidential information.

Who does what

What good intake data looks like

A useful test: could a colleague who has never spoken to the enquirer run a complete conflict search from the intake record alone? If they would need to phone the enquirer for the other side's name, a company number or a former name, the form or call template needs another question. Review a handful of recent intake records each quarter and adjust the form based on what was missing.

Using AI in intake responsibly

AI is useful for extracting names from messy enquiries and grouping results, but treat its output as a draft. Regulators in several jurisdictions have warned that lawyers remain responsible for checking AI output. Practical safeguards:

• use only tools the firm has assessed for confidentiality and data location
• keep enquiry data out of public AI tools
• log what the tool produced and what a person changed
• never let a tool send anything to a prospective client that sounds like advice

Where to start

Start with the structured enquiry form and call template. Better data at the start makes every later step easier, even if the rest is still manual. Then add name normalization and grouped results.

Make It Flow maps how enquiries move through your firm today, from the phone to the matter opening, before suggesting tools. Many practice management systems already include intake and conflict features that are worth configuring properly. For other legal workflows, see our overview of AI for law firms. To discuss your intake process, contact us.

FAQ

What is law firm client intake automation?

It is using software to capture new enquiries in a structured way, flag urgency, acknowledge the enquirer and prepare the information needed for a conflict check. Lawyers stay in charge of deciding whether there is a conflict, whether the firm will act and anything said to the client about their position.

Can software run a conflict check?

Software can run searches against client and matter records and group the results, but a conflict check is more than a search. Deciding whether a conflict exists and whether the firm can act under the professional rules is a judgment for a lawyer and, where needed, the firm's risk lead.

What information should a law firm collect at intake?

Enough to check conflicts and route the enquiry: contact details, matter type, the names of all other parties and any key dates. Avoid collecting detailed facts or documents until the firm confirms it can act. Guidance such as ABA Model Rule 1.18 commentary supports limiting initial information.

Is it safe to use AI with prospective client information?

It can be, with care. Prospective clients are owed confidentiality, so use only tools the firm has assessed for security and data location, keep data out of public AI services, and have a person check the output. Professional rules and AI guidance where you practise should shape the setup.

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

There is no universal rule, but prompt acknowledgement matters because people often contact several firms. An automated acknowledgement within minutes, explaining what happens next and when, sets expectations. The substantive reply follows once the conflict check is complete and a lawyer has decided.

What should a law firm automate first in intake?

Usually the structured enquiry form and acknowledgement. They improve the quality of information from the first contact and give prospective clients a prompt, consistent response. Party list extraction and grouped conflict results are natural next steps once the data is structured.