08.09How-to guide
How to collect client facts before a first legal consultation
An AR Labs guide for small law firms: collect a prospective client's facts before the first consultation, conflict check first, no advice, a person deciding.
Steps
- What goes wrong at the front door
- Rules to settle before changing anything
- What existing tools already do
- Step 1: Separate quick routing from fact collection
- Step 2: Place the conflict check before the detailed account
- Step 3: Define the facts each practice area needs
- Step 4: Write the boundary into the process
- Step 5: Collect facts through a secure, mobile-friendly form
- Step 6: Review, confirm and hand to a lawyer
- Step 7: Measure both problems
- Choosing how far to go
Before you start
- Who it is for
- Small law firms
- Steps
- 7
- Reading time
- 9 min
- Checklist items
- 24
The printed copy keeps the steps and checklists and leaves out the rest of the site.
This guide from AR Labs is for partners, practice managers and intake staff at small law firms who want to improve legal client intake. The first call with a prospective client often falls to a paralegal or a lawyer with case work waiting, and much of it goes on facts a form could have collected. The guide shows how to collect a prospective client's facts and documents before the first consultation, so the lawyer's time goes on the matter itself. It covers factual pre-intake only. Nothing in it is legal or regulatory advice, and the process it describes never gives any: it gathers facts and passes everything to people at the firm who decide what happens next.
It applies our general method for mapping a business process before automating it, and rests on practitioners' posts in public legal forums and the vendors' own pages. We have not built an intake system for a law firm. Professional rules differ by jurisdiction, so every step that touches confidentiality, conflicts or the start of a client relationship must be checked against the rules that apply to your firm.
What goes wrong at the front door
Practitioners in public legal forums describe the problem from several sides. Paralegals in one discussion described colleagues spending hours a day on initial intake calls, with reception overflow interrupting work on active cases; a legal assistant at a four-lawyer firm described 15 or more calls an hour at busy times. A solo family-law practice paying for online advertising described answering many calls to find one serious client, with much of the volume from people seeking free advice. A small personal-injury firm that audited its own phone records found it was losing callers who reached voicemail. Lawyers discussing intake forms report that forms sent by email or as downloadable PDFs take a long time to come back, are awkward to complete on a phone, and raise security concerns.
Two problems are mixed together here. One is coverage: nobody answers, so callers go elsewhere. The other is qualification: someone answers, but a skilled person spends the call collecting basics or discovering the matter is outside the firm's work. Practitioners are also clear that people calling a law firm are often stressed, and some reject automated answering outright, so any change has to keep a person reachable.
flowchart TD
P["Prospective client calls or emails"] --> A["Receptionist or paralegal answers"]
A --> L["Long call: story, facts, questions"]
L --> Q{"Paralegal: our kind of matter?"}
Q -->|"unclear"| F["PDF form emailed; slow to return"]
F --> Q
Q -->|"no"| X["Call ends; time spent"]
Q -->|"yes"| C["Conflict check run after the full story"]
C --> K["Lawyer consultation; basics asked again"]A common current flow: the detailed account comes before the conflict check, and the lawyer re-asks the basics.
Rules to settle before changing anything
Professional conduct duties, including confidentiality and conflicts of interest, can apply from the first contact with a prospective client, before the firm agrees to act. Rules also govern when a lawyer-client relationship begins and what staff who are not lawyers may say. Data-protection law applies to the personal information an enquirer gives you. Check the rules that apply to your firm, with your regulator's guidance or your compliance lead, before deciding what to collect, when, and through which tools. Tell enquirers in plain words what you collect and why. Anything a vendor stores for you remains information you are responsible for.
What existing tools already do
Legal answering services and legal intake software already cover parts of this. Smith.ai, for example, describes an AI receptionist that answers calls, screens callers against the firm's criteria and books consultations, with integrations including Clio, and live receptionists available as an add-on (Smith.ai AI receptionist). LawDroid offers chatbots for law-firm websites aimed at intake and at triaging enquiries (LawDroid). Many practice-management systems include online intake forms, and general form builders support conditional questions and file upload.
What remains is each firm's own design: which facts matter for each practice area, the order of collection, where the conflict check sits, and who decides.
The path the steps below build reverses the current order shown above. Seven stops run from enquiry to first consultation: the conflict check comes second, before anyone hears the full story, and three decisions, marked with flags, stay with people at the firm.
Step 1: Separate quick routing from fact collection
What to do. Split first contact into two parts. Routing answers three questions: is this a kind of matter the firm handles, is it urgent, and how should this person be contacted. Fact collection gathers the details for a lawyer, and happens only for matters that pass routing and the conflict check.
Why. Routing is short and can be done by reception, a form or an answering service. Fact collection takes longer and is wasted on matters the firm will not take.
Example. "Which of these best describes your matter? Family, wills and estates, employment, something else." "Is there a court date or deadline in the next 14 days?" "Best way and time to reach you?"
- Routing questions written and short
- Urgent matters go straight to a named person
- Out-of-scope enquiries get a polite reply, with a referral source if you have one
Step 2: Place the conflict check before the detailed account
What to do. Decide with the partner responsible for compliance where your conflict check sits in intake. A common order is to collect only the names of the people and organisations involved and the enquirer's own details, run the check, and take the detailed account only after it clears. Confirm that this order, and the wording you use, fit the rules that apply to your firm.
Why. Every detail the firm hears before a conflict is found is detail it then holds. Collecting names first keeps that to a minimum. Lawyers in public forums also raise the concern that intake forms can leave an enquirer unsure whether they have become a client; how and when to address that is a question for your firm's rules, not for an intake tool.
Example. "Please give the full names of the other people or organisations involved, such as the other party or their employer. Please do not describe your matter yet."
- Position of the conflict check agreed by a partner against your firm's rules
- Names collected before any detailed account
- Conflict check run on every enquiry that passes routing
Step 3: Define the facts each practice area needs
What to do. For each practice area, list the facts a lawyer needs before a first consultation: the parties, the key dates, where events happened, what has happened so far, any documents, and what outcome the person is hoping for. Ask each lawyer to approve their list.
Why. A lawyer-approved list makes intake consistent whoever collects it. Dates and places bear on deadlines and jurisdiction, but deciding what they mean is the lawyer's job: the form collects them and does not interpret them.
Example. For an employment matter: employer name, job title, start and end dates, the date of the event complained about, whether any internal process has started, and copies of the contract and any letters.
- Fact list per practice area, approved by a lawyer
- Dates collected, not interpreted
- Documents requested by type
Step 4: Write the boundary into the process
What to do. Write down what intake must never do: give or imply legal advice, assess the strength of a matter, quote fees beyond your published terms, or promise representation. Add a plain statement of what the form or call is for, a way to reach a person at every point, and, if any part is automated, a statement saying so. A partner approves the wording against your firm's rules.
Why. The boundary protects the prospective client and the firm. Even reassurance can be heard as advice, so intake keeps to facts. Stating the boundary also answers the trust concern practitioners raise: people know what this step is and is not. Some people will not use an automated route, and they may be the ones who most need a call, so a person stays reachable.
Example of the kind of statement a firm might adapt. "This form collects information so a lawyer can prepare for your consultation. It does not give legal advice. To speak to someone now, call [number]."
- Boundary written and approved by a partner against your firm's rules
- Statement shown before any questions
- Route to a person on every screen and in every script
- Automation disclosed where used
Step 5: Collect facts through a secure, mobile-friendly form
What to do. Replace emailed or downloadable PDFs with a secure web form that works on a phone, branches by practice area, and accepts document uploads. Send the link after the conflict check clears. Let the person save and return. Ask only for the documents on the lawyer's list, and before choosing a tool, confirm where it stores submissions and that this meets your confidentiality and data-protection obligations.
Why. A secure web form sent at the right moment is quicker to complete than an emailed PDF and keeps documents out of email. Documents an enquirer sends may be confidential, so the tool that holds them is part of your firm's information handling, not a convenience outside it.
Example. After the conflict check, the intake assistant texts a link. The form shows only the employment questions, asks for the contract as an upload, and ends with a review page.
- Secure web form replaces emailed PDFs
- Branches by practice area
- Upload, save-and-return and review page available
- Tool's storage checked against your confidentiality and data-protection obligations
Step 6: Review, confirm and hand to a lawyer
What to do. An intake staff member reads each submission, checks it against the practice-area list, asks for anything missing, and writes a short factual summary. The summary goes to the prospective client to confirm, and then to the lawyer. The lawyer decides the next step.
Why. Confirmation catches errors before the consultation, and the lawyer keeps every judgement about the matter.
flowchart TD
P["Prospective client: call, form or message"] --> R["Routing: matter type, urgency, contact"]
R -->|"out of scope"| O["Polite reply and referral"]
R --> N["Names of parties only"]
N --> C{"Staff run conflict check"}
C -->|"conflict"| D["Declined under firm's procedure"]
C -->|"clear"| F["Secure form by practice area"]
F --> S["Staff review; factual summary"]
S --> V{"Client confirms or corrects summary"}
V --> L{"Lawyer decides: consult, request more, decline"}The target flow. Diamonds are decisions made by people: staff, the client, and the lawyer.
Example. The summary lists the facts and dates given, the documents received, and one line on what the person wants. The lawyer reads it before the consultation and starts from it.
- Every submission reviewed by a person
- Factual summary confirmed by the prospective client
- Lawyer decides every next step
- Declined enquiries handled under your firm's usual practice
Step 7: Measure both problems
What to do. Track missed calls and abandoned forms (coverage), and the share of consultations with matters the firm takes on, plus time spent collecting basics (qualification).
Why. The numbers tell you which problem you actually have, and each needs its own fix. Missed calls need coverage, such as overflow answering. Unsuitable consultations need better routing questions.
- Missed calls and abandoned forms counted
- Consultations that became matters counted
- Routing questions revised from the results
Choosing how far to go
| Approach | What it involves | Good fit when | Limits |
|---|---|---|---|
| By hand | Routing script, names-first conflict step, lawyer-approved fact lists, summary template | Low volume; experienced intake staff | Staff time; consistency on busy days |
| Configure an existing tool | Intake forms in your practice-management system or a secure form builder | You already have practice-management software | Forms collect what you ask; a person still reviews |
| Connect tools | Form submissions creating matters in practice management; overflow answering service writing into the same system | Details are re-typed between systems | Vendor data handling must meet your obligations |
| Build custom | A guided conversation that asks follow-ups when a factual answer is unclear and drafts a summary for the client to confirm | Measured gaps remain in the facts collected | Strict boundary required: facts only, no advice, disclosed, person always reachable |
AR Labs offers this kind of discovery and design work to owner-run firms; more about us is on the about page.