Home / Blog / Law firm web inquiries: a reply in 5 minutes without inviting a conflict

Law firm web inquiries: a reply in 5 minutes without inviting a conflict

Many law firm web inquiries wait hours or get no reply. Cheap fixes first, then an auto-reply with intake and booking links that doesn't invite conflicts.

By · Published · 8 min read

Someone fills in the contact form on your website at 9:40 p.m. They were just served with an eviction notice and the hearing is Thursday. Your inbox shows the form the next morning, under a newsletter and two court notifications. By then they've filled in three other firms' forms.

An automated reply can answer them within seconds. It can send your intake form and consult booking link, flag the hearing to you, and politely turn away matters you don't handle. The law-firm part is what the reply must avoid doing. It mustn't invite the person to pour out their case before you've checked conflicts, and it mustn't suggest you've taken them on. This post covers what the response-time studies found, the cheaper fixes to try first, how to word the reply, and what our recipe does and doesn't do.

Not legal advice. We build and test automations; we're not lawyers. This is a plain-English summary of primary sources, checked on October 27, 2026. Your state's version of the rules controls. Ask your state bar's ethics hotline if you're unsure.

How fast do law firms answer web inquiries?

Two recent secret-shopper studies, both from companies that sell to law firms:

  • Clio (practice-management vendor), 2024. Shoppers emailed 500 firms, and only 33% responded, down from 40% in 2019. Of the firms that did respond, 84% did so within eight hours. Only 18% of responses gave clear next steps or cost information. That's from Clio's press release on the 2024 Legal Trends Report.
  • Hennessey Digital (law-firm marketing agency), 2025. The agency sent fictitious website inquiries to 1,333 US firms in the first quarter of 2025, sampling personal injury, criminal defense and other practices. Results from its 2025 Lead Form Response Time Study:
    • 25% responded in under 5 minutes, up from 13% in 2021
    • the median response time was 13 minutes
    • 26% didn't respond at all, counting anything after 7 days as no response

The two studies disagree a lot. The firms differ (Hennessey's published firm lists are dominated by personal-injury practices), the years differ, and so do the channels (email versus web forms). Neither study is a measure of your firm. Neither one shows that a five-minute reply wins more signed cases, and we haven't found a source that does, so we don't claim it. What they do suggest is that many firms leave inquiries waiting for hours or never answer, and a prompt, useful reply can stand out.

Try the cheaper fixes first

  1. Look at what your form does now. Many website form builders can email the submitter a confirmation. Even a plain "we got this, we reply within one business day, here's our phone number" beats silence. Add the cautions in the next section.
  2. Use what Clio already gives you. If you're on Clio Grow (included in the Elite plan and an add-on for Core and Signature, per Clio's pricing page), its Automated Workflows include a "Screening inbox leads" template. Once you apply it to a matter, it emails an appointment booking link, then sends an intake form after the person books. Clio also lets you add a task step, such as a conflict check, that pauses the workflow until someone marks it done. Clio also documents lead notifications and intake form links, which Clio says stay valid for 14 days. If that covers you, you may not need anything else. Clio's pricing page also lists Grow AI phone, web and email agents, billed per matter hired. We haven't tested them.
  3. Route the form to a phone, not just an inbox. A push notification for new leads does more than a faster auto-reply if what's missing is someone reading it.
  4. Then automate the routing. An outside workflow earns its keep when you need rules Grow's templates don't cover. Examples include a different reply for urgent matters, declines for practice areas you don't handle, and existing clients who use the form being sent to the attorney instead of intake.

What the reply must and mustn't do

Don't invite the case story. Under Model Rule 1.18, a person who consults you about possibly hiring you is a prospective client. You can't use or reveal what they told you, and if they told you something "significantly harmful", you can be disqualified from representing the other side. Comment 2 is the one that matters for web forms. A consultation is likely to have occurred if a lawyer, "through the lawyer's advertising in any medium, specifically requests or invites the submission of information about a potential representation without clear and reasonably understandable warnings and cautionary statements that limit the lawyer's obligations". Comment 4 says to limit the initial consultation "to only such information as reasonably appears necessary" to decide on conflicts and whether to take the matter.

In practice:

  • Keep the form short. Ask for name, contact details, the other party's name for conflicts, and the type of matter. Leave out a big "describe your situation" box.
  • Put the warning on the form and in the reply. Say that contacting you doesn't create an attorney-client relationship, and ask people not to send confidential details yet.
  • Leave the substance for after the conflict check.

Don't mislead. Rule 7.1 bars false or misleading statements about your services. Say "we'll review your inquiry", not "we'll get you results". If the reply says an attorney will call within a set time, make sure that happens.

A reply is generally not a solicitation. Rule 7.3 Comment 1 says a communication "in response to a request for information" is not a solicitation. In Florida, the written-solicitation requirements don't apply to communications "at a prospective client's request" (Rule 4-7.18(b)(3), unofficial copy). Those carve-outs appear to cover a reply; check your own state's version. A drip campaign of follow-ups to people who never booked is a different question. Our checklist for automated texts covers how states treat outbound messages.

Treat urgency as a person's job. An automated reply can't judge whether "court date Thursday" is urgent in your practice. What it can do is spot obvious words and alert you. The reply itself should tell the person to call.

Decline cleanly. If you don't handle the matter, saying so and pointing to the bar's lawyer referral service is more useful than sending a booking link to a consult that won't happen.

What the reply looks like

This is the email our inquiry auto-reply and intake recipe sent in its test run, half a second after a mock form submission. The firm and names are invented.

Subject: Next steps with Harbor Point Law

Hi Jordan,

Thanks for reaching out to Harbor Point Law. Here's how to get started:

  1. Fill in our short intake form (about 5 minutes): https://harborpointlaw.example/intake?email=jordan.blake%40example.com
  2. Book a consultation with Dana Whitfield: https://calendly.com/harborpointlaw-example/consult

Please don't send confidential details by email yet. Contacting us does not create an attorney-client relationship; that only starts once we've checked for conflicts and you've signed an engagement agreement.

Harbor Point Law +15555550160

It names a responsible lawyer and the firm and gives a number. It points to the intake process instead of asking questions, and it carries the 1.18-style cautions. It doesn't say anything about the merits.

What it costs

Illustrative arithmetic from the recipe page, not a measured result. At 80 inquiries a month, the replies, attorney alerts and booking notes fit inside Resend's free tier of 3,000 emails a month. Calendly Standard is $10 per seat per month. That's about $10 a month, plus n8n (free if you self-host, or from EUR 20 a month on n8n Cloud) and the Clio plan you already pay for. If Clio Grow's built-in workflow already does what you need, the extra cost is zero.

How our recipe handles this, and what it doesn't

The law-firm inquiry auto-reply and intake recipe takes a website form submission. It checks Clio to see whether the sender is an existing client, then does one of four things:

  • New inquiry in a practice area you handle: replies with your intake form and booking link and creates a Clio Grow lead.
  • Urgent wording (such as a hearing, an eviction or a deadline this week): the reply says to call now, and you get an URGENT alert.
  • Practice area you don't handle: a polite decline with a bar referral link and no booking link.
  • Existing client: goes to the attorney, not into intake.

It also handles the background work:

  • It drops bot submissions caught by a honeypot field.
  • It sends one reply if someone submits twice.
  • It checks Calendly's webhook signature before adding bookings to the Clio calendar, without duplicates.
  • It waits and retries when Clio rate-limits it.
  • It uses no AI model. Every decision is a written rule you can read.

How it was tested. We ran 10 scenarios on October 27, 2026, and all 10 passed. Clio Manage, Clio Grow, Calendly and the email sender were replaced by a local mock server built from their official API docs. No real email was sent, and the recipe has not been run against a live Clio or Calendly account. The Clio and Calendly field names come from those vendors' documentation.

What it doesn't do:

  • No conflict check. The reply says so and invites no confidential details. Someone still has to run conflicts before the consult.
  • The urgency check is a keyword list. It will miss urgent inquiries phrased differently, so read every new inquiry yourself.
  • Its "already replied" memory resets if you re-import the workflow.
  • It isn't set up for Clio's Canadian region or for Canadian rules.
  • It doesn't make your wording compliant in your state.

If your missed contacts come in by phone rather than web form, see missed-call text-back for law firms and whether missed-call texting is legal. Everything we've built for firms is on the law firms page.

Sources

All checked October 27, 2026.

The recipe for this problem

Found an error or a better source? Corrections policy. More articles on the blog.