The Front Door Your Legal Team Already Has

By Jake Jones, Co-founder, Flank.

If you lead an enterprise legal team, your intake process is a mess. It’s a function of the chaos begotten by an ultra-fragmented, multi-national system. Messy is the nature of the beast and all the tools and services you’re evaluating are downstream of that mess. Every piece of work your team picks up and drops into their favourite word plugin has provenance in that mess.

A senior lawyer at a consumer goods company told us she kicks off each morning combing through dozens of new emails that landed in a shared inbox over the past sixteen hours. No forwarding instructions or intake tools could handle the nuance required to route each email to the right person or respond in the right way. NDA requests. Procurement queries. Policy questions. And for each category, a dozen sub-categories dependent on jurisdiction, deal size, how important the sender is. She sorts them into folders, forwards them to colleagues, flags those she will handle herself.

By mid-morning, she’s down four shots of coffee and hasn’t started any material legal work.

This anecdote is common. In almost every enterprise legal team we speak to, someone plays this role. Often it’s an entire team. They are the “human front door” of the department: the person who reads everything, decides where it goes, and carries the institutional knowledge of what matters and what doesn’t. The role is invisible to the rest of the business. It does not appear in any job description. But if that person goes on holiday, the team feels it within hours. Worst case, there’s not a single front door, there are many. Fragmented channels and frantically monitored email addresses.

The invisible bottleneck

The structural problem is not that the work is difficult. Most of what arrives in a legal inbox is classifiable. NDA requests do indeed look like NDA requests. Procurement approvals have a signature shape. A reasonably experienced legal operations person could write down the routing rules for 80% of it in an afternoon.

But that understates the complexity. The rules are not static. An NDA from a Fortune 500 counterparty routes differently from one sent by a startup. A procurement query mentioning the Singapore entity triggers different requirements from one out of Dublin. The same request type can mean different things depending on who sent it, what is attached, and which business unit it came from. The person doing the sorting is not applying a simple flowchart. She’s applying contextual judgment, built over years, one email at a time.

That is why this problem has resisted tooling. Intake portals and ticketing systems ask the business to classify its own requests, which it does badly. Chatbots handle the simplest queries but cannot parse a one-line email with a 47-page supply agreement attached and no context. The department ends up with a senior lawyer as the sorting layer because nothing else has been good enough.

It’s also why this problem is so dangerous. In many cases, the success of the entire system hinges on this single point of possible failure. Intake.

What a front door can look like

The first question enterprise legal teams ask us is whether their business stakeholders need to learn a new tool. The answer should be no. The whole point of a front door is that it sits in the channel the business already uses. For most departments, that is email.

What changes is what happens after the email lands. Instead of a lawyer reading and forwarding it, an agent classifies it against the department’s own rules and routes it. Some requests go to the department’s lawyers with a structured summary, a first-pass analysis, and the relevant context pulled together so the lawyer can act immediately rather than spending ten minutes working out what the request is actually asking. Others, the ones that are fully playbook-driven and low-risk, are handled end-to-end by agents and routed to a supervision queue for review before anything goes back to the business.

The business simply sends the same email to the same address they always have and get a faster, more consistent response.

I should be direct about two things this requires. First, the classification layer has to be as contextual as the person whose work it replaces, or it fails on day one. It needs to handle jurisdiction-specific routing, counterparty-dependent escalation, and ambiguous requests with incomplete information. If it cannot, it is a toy. Second, the emails and their contents have to stay inside the client’s infrastructure. For most enterprise buyers we speak to, particularly in regulated industries, the conversation stops before it starts if the data leaves the building.

What changes for the team

The lawyer’s morning changes. Instead of sorting sixty emails, she opens a dashboard where requests have already been classified. The straightforward ones have been handled and are waiting for her review. The complex ones are flagged with a summary and a recommended next step.

Here, the bottleneck isn’t just being shifted from sorting to reviewing. Reviewing a pre-classified, pre-summarised request with a first pass attached is a fundamentally different task from reading a raw email cold and working out what it is. The time taken differs wildly. The judgment required is on a different level, and it’s more focused. The senior lawyer is spending her forty-five minutes on the things that actually need her; training, experience, and all.

There is a second-order effect that matters just as much: data. For the first time, the department has a structured view of what is coming in. How many NDA requests per week. Which business units generate the most volume. How long each request type takes to resolve. Most legal departments don’t have this information today because the triage has always been manual and unrecorded. You might have a sense of where the bottlenecks are, where your expensive team is working on inexpensive work, but you can’t quantify this, you cannot bring it to your CFO and say, Look, see, here is where we need to optimise.

The practical takeaway

If your legal department is evaluating an agentic front door, the questions to ask are: does it work through the channels the business already uses, or does it require a new portal? Can it handle contextual routing, not just keyword classification? Does it route to your own lawyers when judgment is needed, with enough context for them to act immediately? Can you override any routing decision? Does the data stay inside your infrastructure? And does the business even notice the change?

The best front door is one that doesn’t ask the business to change their behaviour, at all. What changes is that the work is already understood, classified, and half-done (or more) by the time a lawyer ever sees it. This isn’t outsourcing. This is insourcing work to agents that sit inside your own building and operate under your own rules.

This is what we built Flank’s Legal Front Door to do.

If you would like to learn more, please see here.

—

[ This is a sponsored thought leadership article by Flank for Artificial Lawyer. ]