Incoming mail in the DMS: one target system, one workflow
Contents
An incoming mail workflow into the DMS needs exactly one destination. An AI employee reads each arriving item, assigns it to the responsible department and creates the task in the DMS your administration already runs. It writes into no second system. What arrives in the DMS:
| What arrives in the DMS | Where it comes from |
|---|---|
| the document as a file | from the scan in the Poststelle (the mailroom team), an email or an upload |
| the assignment to a department | from the AI employee, against the list of classes agreed before the start |
| metadata: sender, date, subject, file reference | extracted from the item by the AI employee |
| one task for the department | through an access the DMS already has |
When the AI employee is unsure about an item, meaning its certainty falls below the agreed confidence threshold, it does not assign it. It hands it to a named person.
One target system, so the department looks in exactly one place
A workflow that distributes into several systems also distributes responsibility. If an item lands in the DMS, the finance system and a ticket system at once, someone has to check three places to say where it went and whether it arrived correctly.
That is why the AI employee writes into exactly one target system and nowhere else, not even back into a second one. For incoming post this is usually the DMS with the electronic file. The question of where an item went then has two answers that match: the task in the DMS and the entry in the decision log, with timestamp and reasoning.
If an item is later also meant to go into a specialist system, that is a second Vorgang (one intake, one task, one destination), with its own target system and its own hit rate. What has to be in place before the first Vorgang is covered in our page on the digital mailroom.
AI in the DMS means here: the AI employee works in front of the DMS
Many people take AI in the DMS to mean a feature built into the DMS and set up there. The AI employee is not that. It sits in front of the DMS: it reads the item before it arrives there and hands it over through an access the DMS already has.
The DMS stays as your organisation has set it up: file plan, permissions, retention and the steps that follow the task. Whether it comes with AI features of its own changes nothing. And whether your organisation works with d.velop documents, ELO or another DMS, what matters is the access, not the vendor.
What an operated AI employee takes on with documents, and what it does not, is covered in our page on intelligent document processing.
Four ways into the DMS, none of them custom development
The AI employee uses a route your DMS already offers. We agree which one in the first week with your IT or data centre.
| Access | How the item gets into the DMS |
|---|---|
| Standard API | The AI employee creates document, metadata and task through the DMS's programming interface. |
| Watch folder | It places file and metadata in a folder that the DMS watches and imports. |
| sFTP | It transfers file and metadata to a secured server from which the DMS collects them. |
| It sends file and metadata to a mailbox that the DMS processes. |
Custom development against a legacy system does not belong in a Pilotbetrieb, our fixed-price entry engagement. Your IT or data centre decides which permissions the access gets in the DMS. The AI employee needs no permission to delete, because it deletes nothing.
Agentivo builds and operates the workflow, not your IT
A workflow for incoming mail needs someone to define the classes, train the recognition and correct wrong assignments. With us, that is not your IT. Your Fachbereich, the department that owns the work, answers questions, and we build and operate the AI employee.
| Task | Who | When |
|---|---|---|
| Define classes and examples | your department answers questions, we write the classes down | week 1 |
| Provide access to the DMS | your IT or data centre | weeks 1 and 2 |
| Build and train the AI employee | Agentivo | week 2 |
| Acceptance against the agreed hit rate | Agentivo, on your real documents | week 3 |
| Review and correct wrong assignments | Agentivo | from week 3, in operation |
| Adjust classes when responsibilities change | Agentivo, once you tell us | in operation |
| Assign unsure cases | a named person in the department | from week 3, ongoing |
Your IT writes no scripts and maintains no rules. It provides the access and keeps control of the DMS. Every assignment the AI employee makes there is recorded with timestamp and reasoning in the decision log.
Digital archiving of incoming post stays with the DMS
The workflow ends with the task. What happens to the document afterwards is up to the DMS: filing under the file plan, retention periods, disposal. The AI employee delivers what archiving needs, the file and its metadata, and does not intervene after that.
For federal authorities, Section 6a of the federal E-Government Act (EGovG, German text) provides that they keep their records electronically and observe the principles of orderly record-keeping in line with the state of the art. How electronically signed documents keep their evidential value until the end of their retention periods is described by the BSI in Technical Guideline TR-03125 (TR-ESOR).
These requirements belong to the DMS and its archive, not to the AI employee. The workflow changes nothing about the archiving your organisation already has. It makes sure the assigned items arrive there with their metadata.
The workflow goes live only after acceptance
Before the workflow writes into your DMS in production, one number is fixed: the hit rate, the share of items the AI employee assigns correctly. It is agreed before the start and tested at acceptance in week three on real documents. Only then does the workflow go live.
In weeks four to seven it runs on real volume, and we operate it: we monitor and correct. At the end there is a written evaluation: hit rate achieved, cases processed, time saved. If the rate is missed, the Pilotbetrieb ends with no further obligation.
The five steps each item goes through on its way to the task are covered in our page on digital incoming mail. How a public administration chooses its first Vorgang is described in our page on mailroom automation.
Frequently asked questions
Do we need new software for incoming mail?
Not for the workflow. The AI employee writes through an existing access into the DMS your administration already runs. We build and operate it; your IT sets up no rules and trains nothing. Your organisation contributes two things: the department's answers in the first week and the access your IT or data centre provides.
Does this work with d.velop documents or ELO?
What matters is not the vendor but the access: standard API, watch folder, sFTP or email. If your DMS offers one of them, the AI employee can create the task there. Which access is set up in your organisation and which permissions it has, we clarify in the first week with your IT or data centre. Custom development does not belong in a Pilotbetrieb.
Does the AI employee also write into our specialist system?
Only if the specialist system is the one target system of the Vorgang. A Vorgang writes into exactly one system. If an item should also go into a specialist system or the finance office's system, that is a second Vorgang with its own hit rate, not an add-on to the first. That way every assignment stays verifiable in exactly one place.
Do deadlines and deletions in the DMS stay with people?
Yes. The AI employee classifies, extracts metadata, routes and creates the task. The department sets deadlines, and documents are deleted under the rules of your DMS and your retention regulations. Notices, approvals and payments stay with the people responsible for them. When the AI employee is unsure, it hands the case to a named person.
What happens when responsibilities change?
You tell us about the change, and we adjust the AI employee. We then keep checking the assignment on real volume. That is part of operation: monitoring, correcting, taking responsibility. The decision log keeps it traceable which assignments were made before and which after the change, each with timestamp and reasoning.
The next step
If your incoming post is distributed by hand today and then entered into the DMS, that is the Vorgang for a Pilotbetrieb: one intake, one task, one destination. Fixed price, agreed before we start. Seven weeks, four of them productive operation on your real documents.