Full article
Overview
Most firms do not lose intake momentum because their lawyers lack expertise. They lose it in the gap between a website enquiry arriving and someone deciding what should happen next. That gap is usually filled with inboxes, hand-offs and a fair bit of hopeful interpretation. It is slow, difficult to measure and, in regulated environments, a bit too easy to get wrong.
The practical fix is not a shinier form or a chatbot with delusions of grandeur. It is a structured intake model: capture the right signal, triage with clear logic, route to the right team and package the result so a fee earner can act without first untangling a wall of text. Simple enough to explain over a cup of tea; rigorous enough to stand up operationally.
Signal baseline
Last Tuesday, in Sussex, with the March wind doing its usual best to rattle the window frames, I was speaking to a practice manager in Manchester about a commercial property enquiry that had sat in a generic inbox for nearly 48 hours. It landed late on Friday, disappeared into Monday’s rush and was only picked up on Tuesday. By then, the prospective client had instructed another firm. No drama, no mystery: just a slow system producing a predictable result.
That pattern is common because the underlying design is common. A web form drops plain text into a shared mailbox. Someone in operations reads it between other jobs, tries to judge urgency and subject matter, then forwards it to the department they think is right. If the recipient is in court, in a meeting or simply missing context, the enquiry stalls again. Then come the follow-up questions for basic facts that could have been captured earlier.
The trade-off is obvious. Manual triage can feel flexible, but flexibility without structure usually means delay and inconsistency. For the firm, that pushes up administrative cost and increases the odds of mishandling personal data. For the prospective client, it feels like sending a message into the void. If a platform cannot explain its decisions, it does not deserve your budget; the same goes for an intake process run on guesswork.
What is shifting
The useful shift is from passive data capture to structured qualification. A legal website should do more than collect contact details and hope for the best. It should help determine, at the first interaction, whether this is the right matter, the right team and the right next step.
In practice, that means four linked stages.
The trade-off here is between richness and drop-off. Ask too little and your routing becomes sloppy. Ask too much and people abandon the journey. Between 08:30 and 10:00 last month, I tested a draft intake flow and managed to make the second question do the work of three; completion rates improved simply because the path stopped feeling like homework. Fancy that.
- Capture: start where intent is strongest, usually on a practice area page or a clear enquiry entry point. The aim is to replace the dead-end “contact us” experience with guided input that confirms why the person is there.
- Triage: ask the minimum viable set of questions needed to decide what happens next. New or existing matter. Broad area of law. Any live deadline. Whether the person is seeking advice for themselves or on behalf of an organisation. That is legal intake qualification in its useful form: not a bulky questionnaire, just enough structured signal to act sensibly.
- Route: apply rules the firm has already agreed. A time-sensitive dispute might trigger same-day escalation to a named team. A routine conveyancing enquiry might be queued into a standard workflow. A matter outside scope can be declined politely and, where appropriate, signposted elsewhere.
- Package: deliver the result in a format a human can use quickly: key facts, stated urgency, source page, route taken and any caveats. No scavenger hunt required.
Who is affected
Fee earners feel the change first. Instead of opening an email full of half-formed narrative and missing essentials, they receive a structured summary that tells them what the matter appears to be, how it was classified and what should happen next. The trade-off is that they give up a little ad hoc discretion at the front door in exchange for cleaner inputs and less low-value sorting. Most people take that deal quite happily.
Operations and compliance teams gain something even more valuable: visibility. Once the intake journey is structured, you can measure it. How many enquiries came in by practice area this week? How long did qualification take? Which routes produced the most follow-up work? Where do people abandon the flow? Automation without measurable uplift is theatre, not strategy.
Clients notice the difference as speed and certainty rather than as software. They get an immediate acknowledgement, clearer expectation-setting and fewer repetitive questions. In regulated settings, that matters because confidence is built by competent handling, not by flashy interfaces. A prompt, well-routed first response suggests the matter will be handled carefully later on too.
How to build the model without creating more faff
Start by mapping the current journey exactly as it happens, not as the process manual claims it happens. Include inboxes, spreadsheets, call-backs, internal forwarding rules and every awkward exception. Put timings against each step where you can. Even a fortnight of observed data is more useful than a polished assumption.
Then define qualification criteria by practice area. What is the least information needed for a safe, commercially sensible routing decision? For example, employment and family enquiries often need different first questions and different urgency triggers. A generic flow for everything may be easier to launch, but it usually performs worse because the logic becomes mushy.
Next, design the decision logic and the fallback paths together. This is where firms often trip up. They map the happy path and forget the edge cases: conflicted parties, vulnerable users, or matters that do not fit the available categories. A human backstop is not a nice extra; it is part of the system. If someone needs to step out of the structured flow, they should not have to start from scratch.
Finally, decide what success looks like before you ship. Useful measures usually include time from enquiry to first meaningful response, proportion of enquiries fully qualified at first pass, and routing accuracy. Give the model 30 days, compare it with your baseline and adjust. Build, ship, test, repeat. Less romance, better operations.
A practical intake model will not solve every operational weakness in a firm. It will, however, remove a stubborn category of avoidable delay and make the next step clearer for everyone involved. If your team wants to see what that looks like in the wild, review one live intake journey with QuickThought and we will show you where time, clarity and compliance are currently leaking out. It is a straightforward session, grounded in your actual process, and you should leave with a short list of sensible fixes worth shipping first.
