This is a classic scenario for in-house Legal teams. A colleague in Finance needs a contract reviewed. They don’t know which system to use, which form to fill in, or exactly who to contact. So they do what anyone would: they send an email. Maybe it lands in a shared inbox, maybe not in the hands it should but all in all the result is the same. The email gets buried and lost under a dozen other threads. Three weeks later everyone is stressing for that deadline and no one knows where the request stands.
It it not legal’s fault, but the intake process is not cutting it. Luckily, it can be easily solved with the right system in place: one that turns emails into traceable and organized requests.
The gap no one talks about
Requests land in shared inboxes with no structure, no priority, and no visibility for anyone outside the legal team. Every email needs to be re-entered manually, attachments get lost in threads, and by the time context has disappeared into CC chains, there’s often no record of when the request arrived, who picked it up, or where it currently stands.
The result is predictable: Legal becomes a blocker. Business teams grow frustrated, legal teams lose time to administration, and the GC loses the visibility needed to manage demand, allocate resources, or report upward with confidence.
The problem is a lack of a proper channel.
What changes when emails become part of the intake process
In an ideal world, sending an email to the legal team would be enough. No one, from the initial requester to the legal team, would have to use workarounds to manually add requests to a workspace. Everything would run automatically. An email becomes a trackable request, assigned to an owner that all parties involved can work on from A to Z.
Look at it as an email that does considerably more than it ever has.
How it works
1. Submit a request
Anyone, from any team and department sends an email to the legal team’s shared address. There is no particular account required and attachments work fine. It can run from Outlook, Gmail or any other email provider, at this stage there is nothing new to learn.
2. Auto-capture
Now it gets interesting. From the moment the email arrives, it is converted into a structured request in DiliTrust Matter Management. The request has a unique ID, a status, a reporter, a due date, and a priority level. The best part? It appears immediately in the legal team’s intake queue, with no need to manually enter any of the request details.
3. Collaborate
It is then time to reply and qualify the incoming requests. With this feature, there is no need to move between tools to do so. The legal team can read, respond, and classify the request directly from DiliTrust Matters. All further messages will be centralised, timestamped, and linked to the request. This will also enforce a better legal work distribution balance across team members.
No more headaches from CC chains.
4. Connect
Now, what about the documents? When a request comes in with contract attachments, they can be saved directly to the CLM as new documents or as new versions of existing ones. The key detail here is that the Matter module and the contract repository stay fully connected. The document is exactly where it needs to be from the moment it arrives.
True benefits for all users
This intake system changes everything for all end-users:
This is exactly the kind of intake process Legal needs: one that stops it from being the department that delays or blocks requests, or, worse, makes them disappear.
The bigger picture
The DiliTrust Matter Management intake feature (available from June 2026) becomes the single entry point for all legal intake across the organization, connecting people, requests, and contracts in one place. The system meets users where they already work and follows their habits, not the other way around.
In the end, the email inbox is the starting point. Now it is also where the work begins, and where every step that follows can be traced
