Book a time with our legal AI experts for a personalized demo of our autonomous agents. The demo itself only takes 15 minutes and you can deep dive into the use cases most relevant for you, whether it's drafting SoWs, reviewing NDAs, or completing infosec forms.
Product/Legal front door
The legal front door.
One front door for everything the business sends legal. The agent picks up each request, resolves what it can, and routes the rest, all inside your existing email.
Legal front door · legal@northwind.com
Live · TodayNDA request, Halden Systems
Drafted from the sales template with the counterparty details filled in, and returned to Tom in 12 minutes. Logged and filed.
Resolved autonomouslyOutlook
MSA redlines, Taylors Ltd!
Two clauses outside house positions. Categorised, context extracted, urgency flagged, and routed to the right lawyer.
Routed to Priya Shah
Policy question, expense approvals
Answered from the policy stack in three minutes. The requester never left Teams.
Resolved autonomouslyMS Teams
Go to the front door inbox ›
Intake today
14 requests picked up
9 resolved autonomously
4 routed with context
1 escalated for review
See the demand dashboard ›
Where requests arrive
Outlook
MS Teams
Slack
01 · The problem
Legal has no front door.
Requests arrive by email, in Teams and Slack, by phone and in hallways. There is no single place where inbound work lands, no consistent triage, and no visibility on what is coming in or how long it waits.
NDA request, Halden Systems
Forwarded from sales to a personal inbox
MSA redlines, Taylors Ltd
Sent to the wrong lawyer, bounced twice
DPA for Pantry Hub
Second request for the same document
Policy question, gifts limit
Asked in a corridor, never logged
Nobody can see this queue. It lives across four inboxes, two chat threads, and a hallway conversation. The business waits without knowing where their request stands.
Why tooling hasn't fixed it
Shared inboxes, ticketing systems, and intake forms organise the queue, but they don't reduce the work. Someone still has to read, categorise, and route every request. That someone is usually a lawyer.
02 · How it works
Intake, resolve, route.
An agent embedded in your legal team's email reads every request, identifies the work type, and gathers anything missing. Standard requests are resolved end to end; everything else is routed with context attached. Nothing changes for anyone sending a request.
TB
Tom Becker · Enterprise Sales
NDA before the Halden Systems call
Hi Legal, we have a discovery call with Halden Systems on Thursday and they want an NDA in place first. Can you sort one? Happy to send details if you need anything.
The front door picks it up
Identifies the request type · pulls the counterparty from Salesforce · drafts from the sales template · 12 min
L
Legal · via Flank
Re: NDA before the Halden Systems call
Hi Tom, here is the mutual NDA drafted from the sales template with Halden Systems' details filled in: standard two-year term and our house confidentiality positions. Ready to send for signature.
Halden-Mutual-NDA-v1.docx
Tom never leaves his inbox. Standard requests come back resolved in minutes. Complex or unusual work reaches the right lawyer already categorised, with context extracted and urgency flagged.
The work around the work
The agent also acknowledges the request, logs the matter, and files the documents in the right place. The tasks that consume hours of a legal team's day without anyone calling them legal work.
03 · Visibility
A live picture of legal demand.
Every request through the front door is categorised, timestamped, and tracked. For the first time, your team gets a live dashboard of what the business is actually asking for.
Week 42. 118 requests through the front door. 61% resolved autonomously, median pickup 40 seconds. MSA reviews are this week's bottleneck.
Requests by work type
Volume
118this week
Pickup
40smedian
Resolved
61%end to end
Routed
39%with context
Work type
Handled by
Count
Status
NDAs
Template-driven
34
·
Policy questions
Answered from the policy stack
28
·
MSA reviews
Longest time in queue
21
Bottleneck
Procurement
DPAs and vendor terms
18
·
The shape of demand, quantified for the first time. What comes in, how long it waits, where it goes, and which work types are candidates for end-to-end execution.
The insight most teams don't have
Until you can see what is hitting the inbox, you can't decide where to invest your team's time, which work to keep in-house, and which work to delegate. The front door turns a blind inbox into a data-driven operating model.
04 · Expansion
Start with triage. Expand when you're ready.
The front door delivers immediate value as a triage and routing layer. Once the dashboard shows which work types are high-volume and repetitive, the agent can take them end to end: drafting, reviewing, and applying your playbook, with finished work clearing through a supervision queue.
ExecutionNDAs · agentMSA review · routedPolicy Q&A · agent
NDA drafting switched to execution
The dashboard showed 34 template-driven NDAs a week. The agent now drafts them end to end; your team reviews only what gets flagged.
ApproveRequest changes
You decide the pace. Some teams expand within weeks, others take longer. The decision is made on your own data, not a sales pitch.
05 · What doesn't change
Your email. Your playbooks. Your control.
The front door operates inside your environment. It is not an external service that pulls work out of your building; it is an embedded capability that works on your terms.
Your emailMicrosoft Exchange, your existing addresses
Your playbooksYour templates, terms, and fallback positions
Your supervisionYour lawyers, a partner firm, or Flank's team
Your dataSOC 2 Type II · your region · no training
Change managementNone
The key distinction
Traditional outsourcing takes work out of your building. The front door keeps it in. The labour is offloaded to agents. The work stays in your environment, on your playbooks, under your control.
06 · Getting started
Live in two to four weeks.
We run a parallel period before anything goes live: the agent processes inbound work alongside your existing process, and nothing reaches the business until you're satisfied. Timelines adjust to your pace; the goal is confidence, not speed.
Week 1: scoping
Map which addresses receive work, what types of requests come in, and how routing works today
Week 2: integration and testing
Connect Exchange and run the agent in parallel; you see everything it does before the business does
Weeks 3-4: live
Requests triaged, categorised, and routed; the dashboard starts populating
FAQ
No. Flank front door agents integrate securely with your existing Outlook mailbox via Microsoft Exchange. The business emails legal the way they always have.
Yes. Our agents integrate with Jira, and custom integrations are available on request.
You provide plain-text instructions describing where different topics should go; the system also accepts spreadsheets. Changing the routing later is an edit, not a project.
The integration itself can be completed within 72 hours. We suggest an initial testing period of one to two weeks to dial in the triage and routing instructions before going live.
Emails are stored only as needed to operate the system, and emails that are filtered out are not stored. We have zero-data-retention agreements with all our LLM providers, and our agents run at banks and global enterprises.
Yes. They live in Flank Record, our system of record. Agents capture each executed contract at signature, extract the key terms, and a human supervisor confirms the data. You query the whole estate in plain language, with nothing for your team to build or maintain.
