What should never go through a law firm contact form

This is not legal advice, and your own bar’s rules and ethics opinions govern — they vary by state and they change. What follows is about form design, which is the part a web person actually controls.

The common approach is a large “tell us about your case” box with a disclaimer underneath. That gets the order backwards: the disclaimer is trying to undo something the form just asked somebody to do.

What happens when somebody types their case into your form

They are not a client. There is no engagement, no conflict check, nobody has agreed to anything. And your firm now holds a detailed account of their situation, including who is on the other side.

Two practical problems follow. If your firm already acts for that other side, or later wants to, having received the detail can complicate matters considerably. And whether the sender’s expectation of confidentiality carries any weight is a question with different answers in different jurisdictions — which is not a question anybody wants to be researching after the fact.

None of that is exotic. It is the routine reason firms have intake procedures at all. The website is simply the one intake channel that was designed by somebody who was not thinking about it.

Why a disclaimer only goes so far

Disclaimers are worth having. Ethics opinions in several states discuss them and they do real work: they set expectations, and where the reader has clearly assented to them they can matter.

What they cannot do:

• Un-receive the information. Once it is in your inbox, it is in your inbox.
• Work when nobody read them. Small gray text under a submit button is not assent in any meaningful sense.
• Cover the email address printed on the same page, which somebody will use instead, with no disclaimer anywhere near it.

A disclaimer is a warning sign. It is not a fence.

The design fix: ask for less

The single most effective change is removing the field that invites the story.

What a firm’s contact form actually needs:

• Name
• Phone and email
• Matter type — a short dropdown of practice areas
• Preferred contact time
• Optionally: how they found you

What it does not need: a large empty box labeled “tell us about your case.” If some free text is unavoidable, constrain it — a short field with a low character limit, labeled to ask for a topic rather than a narrative, with placeholder text that models the expected answer (“landlord dispute”, “estate planning question”).

This is not a loss of information. Everything the firm needs to conduct a proper intake gets collected on the phone, by somebody who can run the conflict check first — which is how intake was supposed to work before web forms invited people to skip the queue.

Click-through assent, as a design pattern

Where a disclaimer is used, several ethics opinions favour a mechanism where the visitor has to take an action to proceed rather than merely scroll past.

As a design pattern that means: readable text at a normal size, positioned before the send button rather than after it, with a checkbox the visitor has to tick, and a submit button that stays disabled until they do. It is slightly more friction and that is the point — friction is what distinguishes assent from decoration.

What the wording should say is a question for your firm’s counsel, not for a web developer. Look at published examples on established firms’ sites for the shape of it, then have your own drafted. We build the mechanism; the words are yours.

Where the submission goes afterwards

Rarely considered and part of the same exposure.

• Who receives it? A shared inbox that half the office can read is a different risk from a monitored intake address.
• Is it forwarded anywhere? Automatic forwarding to personal addresses is common and rarely reviewed.
• Is it stored in the website? Many form plugins keep every submission in the site’s database indefinitely. That is a permanent, searchable archive of prospective client information sitting on a web server.
• How long is it kept? Email retention is usually “forever” by default.
• Who else has access? Your web developer probably has administrator access to the site holding that database.

A short retention setting and switching off database storage of submissions are both small configuration changes with real effect.

A short spec to hand your web person

1. Remove the free-text case description, or constrain it to a short topic field.
2. Collect name, contact details, matter type, preferred contact time.
3. Place the firm’s disclaimer text — supplied by the firm — above the submit button, at readable size, with a required checkbox.
4. Do not store submissions in the website database; deliver them to a monitored address.
5. Confirm the address, and that messages actually arrive, by testing it.
6. Apply the same thinking to any chat widget or call-back form, which are usually forgotten.

What this is not

Not legal advice, and not a substitute for your bar’s rules. Requirements and ethics opinions differ by jurisdiction and change over time; your own counsel decides what your site says and what your intake requires. We build the form to the specification a firm approves — that is where our part starts and stops.

Common questions

Does a website disclaimer prevent an attorney-client relationship?

It helps set expectations and ethics opinions in several states discuss them, but it does not un-receive information somebody has already sent. Whether a disclaimer is effective varies by jurisdiction and by whether the visitor clearly assented to it.

What should a law firm contact form ask for?

Name, phone, email, matter type and a preferred contact time. That is enough to return the call and run a conflict check first, which is what intake procedures exist to do.

Should a law firm contact form have a message box?

If it has one, constrain it: a short field asking for a topic rather than a narrative, with a low character limit and placeholder text modeling the expected answer. A large empty box invites exactly what you do not want.

Where should form submissions be stored?

Deliver them to a monitored address rather than storing them in the website database. Many form plugins retain every submission indefinitely, which leaves a searchable archive of prospective client information on a web server.