Full article
Most intake problems start one step after the website form: when a vague enquiry lands on the wrong desk. In regulated work, that guess costs time and muddies accountability.
This rebuild proved a simpler point. Tighten the routing rule, keep early questions disciplined, and legal intake qualification gets cleaner without drifting into advice. No generative theatrics. Just a proper decision tree, an auditable trail, and fewer shrugged shoulders.
Signal baseline
One firm's shared spreadsheet had not been updated for three months. A compliance manager and a head of practice spent twenty minutes arguing over a web enquiry about a property boundary dispute that also mentioned a possible inheritance claim. That was the useful moment. The form was not the bottleneck. The routing logic after submission was.
A basic enquiry form usually asks for name, email, phone number, and a free-text summary. That creates two avoidable problems. Free text invites people to write a mini case history before the firm sets boundaries. Then the routing decision gets pushed onto a human reader who has to interpret a messy paragraph.
In this rebuild, the firm handled roughly 400 enquiries a month. Before the change, close to 30% needed a second routing pass because the first assignment was wrong. Legal intake qualification rate—enquiries correctly assigned and followed up within 24 hours—was just 62%.
Free-text capture feels flexible but the price is ambiguity. Structured capture feels narrower yet delivers a cleaner case-management handoff and a clearer audit trail. In regulated work, explainable routing beats vague friendliness every time.
What shifted in the rebuild
The design pulled away from open narrative capture and towards structured decision-tree qualification. Rather than a generic prompt, the journey asked short, closed questions that narrowed the matter type before inviting detail. Practical distinctions: is this about property, family, employment, or something else? Is there an existing will? Is the issue urgent? Is the enquiry for the person completing the form?
The tree ended with 12 branches covering the firm's five main practice areas and around 90% of normal intake volume. A deeper tree was possible, but every extra step raises abandonment and increases the chance of gathering material the firm does not need at first contact. Automation without measurable uplift is theatre, not strategy.
Two workshops did most of the heavy lifting. One with the compliance lead mapped risk points in the journey, and another with practice heads agreed routing destinations and edge cases. Holograph handled the implementation, but the useful decisions came from operational reality rather than software novelty.
In the first month after launch, form drop-off fell by 12% against the old free-text version. Mean completion time dropped from about four minutes to under two. More importantly, the routing rule beneath the tree reduced the number of ambiguous submissions reaching manual review. QuickThought legal intake delivered a cleaner handoff, not just a faster form.
The routing rule that cut ambiguity
The most effective change was not a new screen or a clever prompt. It was one rule: if a user selected a broad or uncertain matter path, the system had to ask two follow-up qualifying questions before the enquiry could move into case-management handoff. That sounds almost insultingly simple, but it worked.
Previously, the biggest failure point came from enquiries marked as 'other' or described in overlapping terms. Those records were pushed to a general queue, then reassigned after manual review. The extra pass added delay and created a familiar compliance risk: people trying to be helpful while lacking enough context or authority to respond cleanly.
By forcing two clarifying questions before handoff, the system narrowed the likely matter type and preserved a reason for the route taken. The rule did not pretend to replace judgement. It made the initial decision legible. If someone later overrode the route, they could see what the user had answered and why the system pointed the record to that team.
Balance is key. Add too few qualifiers and the route remains mushy. Add too many and you get a brittle journey that people abandon halfway through. We aimed for the minimum information needed to assign responsibly, not to open a full matter file. Date of birth, National Insurance number, and a complete chronology can wait. Early intake should support routing, not become a confession booth.
Who feels this most
Mid-sized firms feel this problem most sharply. A small practice relies on local knowledge and informal handoff, while a very large firm has a dedicated intake function. The awkward middle, roughly five to 20 partners, usually has enough specialism to need structured routing but not enough volume for a fully staffed intake desk.
That is where regulated lead routing stops being a marketing admin task and becomes operational governance. If an employment enquiry lands with conveyancing, response time slips and accountability blurs. Someone may reply off the cuff before the matter is properly qualified. None of that helps client confidence or improves compliance comfort.
One partner said after the change, 'I didn’t realise how often we were guessing until we stopped.' Plenty of firms run on goodwill and memory, mistaking that for process. Good people can keep a weak system alive for quite a while, but they cannot make it measurable.
Asking front-of-house staff to infer matter type from a dense paragraph is not efficiency. It is hidden rework. The proper question is whether the website can support first-pass assignment with enough confidence to reduce manual triage without inviting advice risk. That is what decision-tree qualification is built for.
What to do in practice
If you are rebuilding intake, start with routing logic and work outward. The form design follows the decision tree, not the other way round. Firms often reverse this and end up polishing the furniture while the plumbing leaks.
Map each practice area to a small set of qualification questions written in plain English. Test those questions with someone who is not legally trained. If they read like they are inviting legal advice, rewrite them. A decent qualification question narrows the issue without asking the user to perform legal classification.
Design for uncertainty instead of pretending it will not happen. 'I am not sure' is a valid user answer. The system should route uncertain cases to an appropriate review pool, not dump everything into a generic inbox. In this rebuild, one branch attracted 'none of the above' at around 40%. That told us the options were wrong, not the users. We changed the wording and abandonment on that branch dropped by roughly half.
Instrument the nodes. Track where people stop, which answers correlate with fast follow-up, and where human overrides keep happening. This gives you evidence for the next iteration. For example, the employment team received a spike of enquiries the tree had actually routed to property. The problem was a human assumption about what the records 'looked like'. We added a note to the reassignment step asking reviewers to confirm whether they wanted to override the tree’s recommendation. Just enough friction to make the second look deliberate. That changed the conversation from instinct to evidence.
Watchpoints for regulated teams
The biggest watchpoint is over-capture. Firms often respond to routing problems by asking for more data at the front door. Usually, it is just more clutter and more risk. If the immediate task is legal intake qualification, collect what supports assignment and first response. Leave full case histories for the stage where authority, consent, and purpose are clear.
The second watchpoint is governance drift. A routing rule that starts clean can become a patchwork once every exception gets its own workaround. Review the tree against operational data, not internal folklore. If a branch keeps producing overrides, investigate whether the wording is weak, the destination is wrong, or the team has not agreed the rule.
The third is vendor opacity. If your intake tool cannot show why a record was routed a certain way, be careful. In a regulated environment, black-box cleverness is not sophistication. It is a liability with nicer branding. Explainable decision paths, privacy-conscious data handling, and auditable handoffs beat synthetic charm every day of the week.
A structured intake journey will not remove judgement. Nor should it. The point is to reserve human judgement for the cases that genuinely need it, rather than wasting it on preventable ambiguity. The measurable trade-off is simple: a little more structure upfront in exchange for less rework, clearer ownership, and a calmer first response.
If your firm is still routing enquiries by reading free text and hoping for the best, there is a better way to build it. QuickThought gives regulated teams a practical route to cleaner qualification, clearer routing, and a more auditable handoff without drifting into AI advice theatre. To see what that looks like in your own intake flow, contact the QuickThought team today.
A side-by-side trial is often enough to show whether QuickThought is genuinely reducing friction or merely renaming it.
