---
title: "Inbox triage with human approval"
description: "Have incoming messages sorted by category and urgency, summarized and given a draft reply. Sending is done by a person, not by the workflow."
source_name: "Gen8"
source_url: "https://gen8.app/en/mogelijkheden/inbox-triage/"
site_home: "https://gen8.app/"
source_description: "Managed AI service for SMEs. We set up, connect and manage; you stay in control."
locale: "en"
copyright: "© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft"
published_at: "2026-09-13T00:00:00.000Z"
modified_at: "2026-10-22T13:46:59.896Z"
---
# Inbox triage with human approval
## A shared mailbox that is already sorted before anyone opens it
A shared mailbox costs the most time before anything is answered: reading, working out what it is about, deciding who picks it up. This workflow does that preparation. Each message gets a category, a short summary, an urgency level and, where possible, a draft reply. Sending remains human work.
[Book an introduction]()
- Scoping first, then a proposal
- EU hosting
- You stay in control
![A stack of five green rounded rectangles runs via three lines to two dark green circles and one orange circle.]()
September 13, 2026 · Email
**Route:** native
**Control:** human approval
**Systems:** Gmail, Outlook
## From signal to proposal
The workflow reads new messages in the mailbox you have released. For each message it determines what it is about according to your own categories, how urgent it is according to your own rules, and which department or person normally handles it. It adds a summary of two or three lines, so nobody has to read the whole message to decide what to do with it.
For recurring questions it also prepares a draft reply, based on the texts and sources you have designated. That draft sits in the mailbox and only goes out when an employee sends it. Whatever the workflow cannot place with certainty, it marks as unknown rather than filing it somewhere.
## Step by step
1. ArrivalA new message in the shared mailbox or under the label you have released.
2. SortCategory, urgency and the department that normally handles it, according to the rules you have set.
3. SummarizeTwo or three lines that let an employee decide without reading the whole message.
4. DraftFor known questions, a draft reply built from your own texts, with the source it is based on.
5. Human decidesThe employee sends, edits or deletes the draft. Every choice is recorded in the log.
## Where it stops
The workflow sends nothing. It does not delete messages and does not archive on its own, because a message wrongly set aside costs more than an unsorted one. It does not invent answers to questions for which there is no source: then there is no draft, only a notification. It reads only the mailbox you have released, not employees’ personal mailboxes. And it does not override your urgency rules.
## What we can demonstrate
For [Gmail]() and for [Outlook mail]() the platform has its own integrations, in both cases including preparing a draft and without send permission. What is configured per organization is the triage itself: your categories, your urgency rules and the sources a draft may be written from. The broader framework is in [processing emails automatically]().
## Frequently asked questions
Can the workflow send on its own under certain conditions?
That is a different setup, with a conversation of its own. In this design, sending has deliberately remained a human action.
What happens to a message that fits nowhere?
It is marked as unknown and goes into the normal queue. It is not forced into a category.
Does the workflow read personal mailboxes?
No. Only the shared mailbox or the label that has been explicitly released.
Where are the messages processed?
Processing takes place in the EU, and a log is kept of every step.
## Bring one process.
Together we assess whether this workflow fits your situation, the management its route requires and where people must keep making decisions.
[Book an introduction]()
- Reply within one business day
- No obligation