DiliTrust
White paper

Your Legal Front Door Is Only As Good As What’s Behind It

A request tells you who asked and why. It doesn’t tell you who can sign, for which entity, or under which board resolution. That answer comes from your data.

Book a demo Download the white paper
What a request tells you
Subject: URGENT, contract for our Spanish subsidiary
  • Who asked
    Sales director, Southern Europe
  • Why
    The customer wants to sign by Friday
  • Which entity
    Not stated
    Missing
  • Who can sign, and up to what amount
    Not in the request
    Missing
  • Which board resolution covers it
    Not in the request
    Missing
Sound familiar?

A sales director forwards an email with “urgent” in the subject line.

Someone from procurement catches a lawyer at the coffee machine.

The CFO’s assistant sends a Teams message about a subsidiary contract.

By Friday, the legal team has answered most of them, but nobody can say how many there were.

Requests arrive from every direction, and Legal has no view of its own workload, let alone a way to show the business what it handled.

More requests for the same team, and a C-suite that doesn’t see the value

63%

of CLOs expect headcount to stay flat. Operational efficiency is their top priority (53%).[1]

86% vs 17%

86% of GCs see Legal as a significant contributor to the business. Only 17% of the C-suite agree.[2]

60%

of legal departments will use AI-driven intake by 2029, answering half of requests without human intervention, Gartner predicts.[3]

The gap

A request tells you who asked and why. The answer needs more

What the answer needs

  • Who has signing authority for this subsidiary?
  • Which board resolution approved the deal?
  • Who signed it off, and when?
  • What did we agree with this supplier last time?

That information already exists, in the contracts, entity records and board decisions your team manages every day. It’s just rarely within reach when the request lands, or kept current enough to rely on. So one person becomes the bottleneck everyone emails about signing authority. The contract waits, and so does the deal behind it.

AI can draft, review and summarize legal work in seconds. What it can’t do is tell you whether it’s right.

Answering half of all requests without a lawyer only works if the data is right. AI models keep getting better and harder to tell apart, and companies can switch between them as they improve. So the difference comes from the data the model works from. A request is where the need for that data starts. It’s not where the data lives.

23%

of legal departments scored high on digital readiness in a 2025 Gartner survey.[4] A front door built on scattered data doesn’t solve the problem. It moves the queue somewhere more visible.

The usual answers

“Isn’t a shared mailbox enough?”

A shared mailbox can be part of the process, but tools have their limits.

Shared mailbox

Works

At low volume. And email is where people actually write: many won’t switch to a new tool for a quick question.

Breaks when

Volume spikes. Requests slip, nobody knows who picked what up, and there’s no data to show the CFO what Legal handled this quarter.

Keep the channel. Structure what happens after the email arrives.

Ticketing tool

Works

Knowing who asked, and when.

Breaks when

You need to know which entity the request concerns, or who can sign for it. That’s legal data, and IT service desks weren’t built to hold it.

Tracking a request isn’t the same as being able to answer it.

AI intake agent

Works

Answering some requests on its own.

Breaks when

The data underneath isn’t current. Automating on top of unreliable data just makes mistakes faster.

An agent is only as good as the data it works from.

Before choosing a tool

4 questions to ask of your front door

Test the approach you have today, including the tools already in use.

  1. 1. Does it meet people where they already write?

    If the business has to learn a new process, it will keep emailing your lawyers directly.

  2. 2. Can Legal own and track every request?

    Every request has an assigned owner, priority, status and record of what was submitted.

  3. 3. Does the request lead into the work?

    A question that becomes a matter or touches a contract should move into that work without being retyped.

  4. 4. Is the data yours?

    The requests, decisions and documents your team builds up should stay under your control, auditable and portable, and separate from whichever AI model you use this year.

White paper

Want the full test, and the reasoning behind it?

  • The 4-question test, with what to fix first
  • Why a shared mailbox, a ticketing tool and an AI agent each fall short
  • The data a lawyer needs to answer a request
Download the white paper
Intake in DiliTrust Matter Management

How Intake answers the first 3 questions

Email stays the way in. What changes is what happens after the email arrives.

Step 1

The business emails a dedicated legal address

No account to create, and no new tool to learn.

Step 2

Each email becomes a structured request

The sender gets a confirmation that Legal received it.

Step 3

Legal owns it

Assign it, set priority and status, and reply from the same email thread.

Step 4

The request leads into the work

Save attachments to contracts, and turn a request that becomes real work into a matter.

With DiliTrust you own your data.

No model training is performed by DiliTrust without the customer’s consent. Our model partners do not use customer data to train their models, and customer data is not shared across clients.

Intake is included in Matter Management, and your admin activates it in the app. DiliTrust also covers your entities and delegations, and your board meetings and resolutions.

Frequently asked questions

What is a legal front door?

A legal front door is the entry point the business uses to ask the in-house legal team for help. It works when Legal can see, own and track every request that comes through it, and when each request connects to the work that follows, such as a matter or a contract.

What’s the difference between legal intake and a legal front door?

Legal intake is the process of capturing and routing requests to Legal. A legal front door is the single entry point the business uses to start that process. It only works if Legal can see, own and answer what comes through it.

What information does Legal need to answer a business request?

More than the request contains. Beyond who asked and why, a lawyer often needs to know which entity is involved, which contract applies, who has signing authority and which board decision covers the deal. That information usually sits in the legal team’s own contract, entity and governance data.

Can AI answer legal requests without a lawyer?

Gartner predicts that by 2029, 60% of legal departments will use AI-driven intake systems that answer half of requests without human intervention. That only works when the AI draws on current, reliable legal data. On top of scattered or outdated data, automation repeats errors faster.

How does Intake work in DiliTrust Matter Management?

Business users email a dedicated legal address, with no DiliTrust account needed. Each email becomes a request Legal can assign, prioritize and turn into a matter. Intake is included in Matter Management. See how it works.

The front door decides how the business experiences Legal.

What stands behind it decides whether Legal can answer and prove it did. See how your team could run requests matters and contracts in a demo.

Already using Matter Management? Intake is already in your license. Ask your admin to switch it on under Requests and Discover Intake.


Sources