In-house intake processes are messy. This is especially true at the enterprise level. Vendors rarely understand quite how chaotic intake and triage is, and they sell elegant solutions that would be a perfect fit, if only the way the business raised requests were so simple. But the reality is messy. I know this. You know this. The business doesn't care and attempts at making them care (form-based intake, change management, training sessions) have historically failed. The business will work the way the business works.
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 simple set of forwarding rules or intake form could handle the nuance required to ensure each request lands with the right person. There are procurement queries, policy questions, and, for each category, a dozen sub-categories dependent on jurisdiction, deal size, how important the sender is. This very senior lawyer sorts them into folders, forwards them to colleagues, flags those she will handle herself.
By mid-morning she hasn't started any material legal work.
It's a painfully common anecdote. In almost every team we speak to there is someone (often multiple people) playing this role. Often it's an entire team, a human front door to the department. It's a role invisible to the rest of the business, and it's impact isn't measurable. 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 isn't that the work is hard. 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 most of it in a single afternoon.
But that undersells 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 up over years, one email at a time.
This is why the 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 the 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 once 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 never encounters a portal. They never fill in a form. They send an email to the same address they always have and get a faster, more consistent response.
Let me be direct about two things this requires. First, the classification layer has to be as contextual as the person 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.
This isn't simply moving the bottleneck 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 is not the same. The judgment required is not the same. The senior lawyer is spending her forty-five minutes on the things that actually need her, not on the things that merely arrived in her inbox.
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 do not have this information today because the triage has always been manual and unrecorded.
The practical takeaway
If your legal department is weighing up an agentic front door, the questions worth asking 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 the business never notices. What changes is not how work arrives. It is that the work is already understood, classified, and half-done by the time a lawyer touches it. You are not outsourcing. You are not hiring. You are 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 see it: flank.ai.
