Short answer: a law firm intake form should ask for only what you need to call someone back: name, phone, email, and a brief matter type. Add conflict-check fields only when your practice needs them before a call. Pair the form with a plain disclaimer, routing by practice area, an instant auto-reply that sets expectations, quiet spam filtering, and secure handling of every submission.
The online form is where a website visitor becomes a lead with a name and a phone number. It is also where many firms lose people without ever knowing it, because an abandoned form leaves no trace. The form looked reasonable to whoever built it. To a stressed person on a phone, it looked like homework.
This guide covers the form itself: which fields to include, what to say around it, what happens after someone presses submit, and where the data goes. The page the form sits on is its own topic, which we cover in our guide to law firm contact page design.
What the web form is for (and what it is not)
Firms often confuse the website form with full client intake. Full intake is a structured conversation run by a trained person: facts of the matter, dates, opposing parties, deadlines, documents, conflict check, fee discussion. The website form is not that. Its only job is to capture enough to start that conversation, which means a way to reach the person and a rough idea of what the matter is about.
When a firm tries to make the web form do the whole intake, it gets long, it asks for sensitive details before anyone has checked for conflicts, and fewer people finish it. When the form is short, the intake conversation happens where it should: on the phone, with someone who can ask follow-up questions and hear the answers.
Which fields to include
Here is our field-by-field recommendation for a typical law firm intake form, with the reasoning for each.
| Field | Include? | Reason |
|---|---|---|
| Name | Yes, required | You need to know who you are calling |
| Phone | Yes, required | Most legal intake happens by phone, and speed matters |
| Yes, required | Needed for the auto-reply and as a fallback contact | |
| Matter type | Yes, short dropdown | Routes the lead to the right person; keep options to plain-language categories |
| Brief note | Optional, short | Lets people add context, but label it to discourage confidential detail |
| Opposing party name | Only if you need it | Useful for an early conflict check in practices where conflicts are common |
| Preferred contact time | Optional | Helpful for people who cannot take calls at work |
| Consent to text messages | Only if you text leads | Texting leads has its own consent considerations; ask explicitly |
| Date of incident, county, insurer | No | Collect these on the call, where a trained person can ask properly |
| Detailed case description | No | Adds friction and invites confidential information before a conflict check |
| How did you hear about us | No | Use tracking data instead of asking the visitor |
The minimum: name, phone, email, matter type
Four fields are enough to call someone back and route them correctly. Use the right input types so phones show the numeric keypad for the phone field and the email keyboard for email. Let the browser autofill name and contact details. Label fields above the input, not inside it as placeholder text that disappears when someone starts typing.
Conflict-check fields, only when needed
Some practices benefit from an early conflict check: family law, where the other spouse may have already called; business disputes, where the firm may represent the other company; small-town practices where everyone knows everyone. In those cases an optional “name of the other party” field lets intake run a quick check before the callback. If your practice rarely has conflicts at this stage, leave it out and run the check on the call.
Why a short form wins
Every field is a small decision and a small effort. For someone calm at a desk, a long form is just tedious. For someone who has just been arrested, injured, or served with papers, typing on a phone with shaking hands, each extra field is another chance to give up and call the next firm on the list. Required fields that ask for information the person does not have handy (a claim number, an exact date) are especially costly, because they stop the visitor completely.
The information you drop from the form is not lost. Your intake team collects it on the callback, and collects it better, because a person can clarify, reassure, and ask the follow-up question a form cannot. The short form trades nothing of value for more completed submissions. For the wider set of changes that lift lead volume, see our guide to law firm website conversion rate.
The disclaimer next to the submit button
Every intake form should carry a short, plain notice that submitting it does not create an attorney-client relationship and that the visitor should not include confidential information yet.
The context is ABA Model Rule 1.18 on duties to prospective clients. Someone who consults a lawyer about possibly forming a relationship can become a prospective client, and information they share can create confidentiality duties and, in some situations, conflicts that limit whom the firm can represent later. The comments to Rule 1.18 note that a consultation is more likely to have occurred when a lawyer’s advertising invites people to submit information about a potential matter without clear warnings limiting the lawyer’s obligations. A form that asks for a detailed case narrative with no warning is exactly that invitation.
Keep the notice short and put it directly above the submit button, where people actually look. A required checkbox acknowledging it is common, though a clear sentence does most of the work. Label the optional note field to match: “Briefly, what is this about? Please do not include confidential details.” This is not legal advice; check your state bar’s rules and your ethics counsel on exact wording.
Routing by practice area
The matter-type dropdown is what makes routing possible. A personal injury inquiry can go to the injury intake team, a probate question to the estate planning paralegal, and a criminal matter to whoever is on call, all automatically. Most form plugins and CRMs can send submissions to different email addresses or pipelines based on a single field.
Keep the options in plain language that a client would use (“car or truck accident,” “divorce or custody,” “arrested or charged with a crime”) rather than internal practice group names. Include an “other or not sure” option that routes to a general inbox someone checks, so nobody gets stuck because their problem does not fit a category. If you handle only certain matters, the dropdown also quietly signals what you do and do not take.
The instant auto-reply
The moment someone submits, two things should happen: they land on a thank-you page, and they receive an email confirming the message arrived. Both should say who will contact them, roughly when, and what to do if the matter is urgent (call this number). The email should also repeat the reminder not to send confidential information by reply.
Make the auto-reply read like it came from a person at the firm, with the firm’s name, phone number, and address, and send it from a monitored address on your own domain rather than a no-reply one. Set up email authentication (SPF, DKIM, and DMARC) for the sending domain, so the confirmation does not land in spam, which would undercut the whole point.
Speed to lead
People with legal problems often contact more than one firm, and the firm that calls back first gets the first real conversation. A form submission that sits in a shared inbox until someone gets around to it on Monday is a lead handed to a competitor. Decide who owns new submissions during business hours and after hours, set a callback standard your team can meet, and make sure submissions trigger an immediate notification to that person, by email, text, or CRM alert.
Measure it. Track how many form leads arrive, how quickly each gets a first call, and how many become consultations. Our guide to law firm website conversion tracking covers how to record form submissions properly, and our piece on how to get more clients as a lawyer covers the intake side of the equation.
Handling spam without hostile captchas
Law firm forms attract spam: SEO pitches, bot submissions, the occasional scam. The instinct is to add a visible captcha, but a picture puzzle between a frightened person and your firm is a poor trade. Start with methods that ask nothing of a human. A honeypot field (hidden from people, filled in by bots) catches a lot. Invisible, score-based checks such as reCAPTCHA v3 or Cloudflare Turnstile run in the background. Server-side filtering can flag submissions containing links or known spam phrases for review rather than rejecting them outright.
If you do need a visible challenge, use one that only appears when traffic looks suspicious. And never silently discard flagged submissions; send them to a folder someone reviews, because a real client occasionally trips a filter.
Where the data goes, and securing it
Know exactly where each submission travels. Common setups send it to an email inbox, a CRM or legal intake tool, the form plugin’s own database on your web server, or several of these at once. Each copy is a place where personal information sits, and each needs protecting.
The site must run on HTTPS throughout. Limit who has access to form entries in the WordPress dashboard or form tool. If the form plugin stores entries on the server and you also send them to a CRM, consider whether you need both copies, and delete old entries on a schedule. Keep plugins updated, because form plugins are a common target. Your hosting environment matters here too, which we cover in our guide to law firm website hosting. Finally, make sure your privacy policy accurately describes what the form collects and where it goes.
Test the whole chain regularly. Submit a test inquiry every month or so and confirm that the notification arrives, the auto-reply sends, the entry reaches the CRM, and the routing works. Forms break silently after updates, and nobody notices until someone asks why leads dried up.
Frequently asked questions
What fields should a law firm intake form have?
Name, phone, email, and a short matter-type dropdown are enough. An optional brief note and, where conflicts are common, an optional other-party field can be added. Collect detailed facts on the callback instead.
Does a law firm intake form need a disclaimer?
It should have one. A short notice that submitting the form does not create an attorney-client relationship, and that visitors should not include confidential details yet, helps manage prospective client duties under ABA Model Rule 1.18. Check your state bar’s rules for specifics.
Should I ask for a description of the case on the form?
Not a detailed one. A long required description adds friction and invites confidential information before a conflict check. An optional short note, labeled to discourage confidential detail, is enough.
How do I stop spam without a captcha?
Use a honeypot field, an invisible score-based check such as reCAPTCHA v3 or Cloudflare Turnstile, and server-side filtering that flags suspicious submissions for review. Show a visible challenge only for suspicious traffic, if at all.
What should happen after someone submits the form?
They should see a thank-you page and receive an auto-reply saying who will contact them and when, with a phone number for urgent matters. Internally, the right person should be notified immediately so the callback happens fast.
The short version
Keep the intake form to name, phone, email, and matter type, and add conflict fields only where your practice needs them. Put a plain disclaimer by the submit button, route by practice area, send an instant auto-reply that sets expectations, call back fast, filter spam quietly, and know and protect every place the data lands. Then test it monthly.
If you want us to test your forms and the path to them, request a free law firm SEO audit.
