The queue is opt-in notified, always-on visible. A sidebar badge and a “X offen — Entscheidungen ausstehend” dashboard card always show the count; an email/in-app ping on new decisions is a separate toggle in notification settings (Benachrichtige mich, wenn eine Entscheidung ansteht), off by default.
What lands here
Any action a matched category wants to run that isn’t yet trusted enough to auto-fire: forwarding an email, sending or auto-replying, filing a ticket, archiving, marking read, moving to a folder, or a hard delete. Each is a suggestion with a preview — a forward shows its recipient and note, a ticket shows its subject/priority/assignee, a reply shows the drafted text. Actions from the same inbound email are grouped into one chain card — the email’s subject, sender, category, and confidence appear once, followed by one row per pending action in execution order.Deciding on an action
Each row offers three choices:Ja
Approve. The action executes immediately with the previewed content.
Anders
Re-route: pick a different recipient, assignee, or priority before it runs. Hidden for actions with no re-route target (archive, permanent delete).
Ignorieren
Decline. An optional free-text reason helps the AI learn — see below.
Edit before you approve
For forwards, sent emails, and auto-replies, the row shows a snippet of the drafted text with Nachricht ansehen & bearbeiten. That opens a split view — the sender’s original message on one side, your editable draft on the other — so you can rewrite the note or reply body without losing context. Confirming there (Freigeben & senden) approves with your edited text; it’s the same approval as clicking Ja on the row.Resolved history
Below the open queue, Erledigte Entscheidungen lists what you’ve already approved or ignored, each with Details ansehen for the full record: why the AI classified it that way, what happened, and who approved or ignored it and when. Nothing here is a silent auto-fire — only decisions an operator actually made show up, so the history reads as a decision log, not a raw activity dump.How this feeds learning
An Ignorieren with a reason, or an Anders correction (a different recipient, assignee, or priority than the AI proposed), is remembered — this is the light learning loop covered in Learning from corrections. It doesn’t retrain a model; it keeps a short memory of recent corrections that gets fed back into future classifications for that categorizer.How this connects to automation
Every Ja (and every Anders) on the same rule counts toward that rule’s trust. Approve it enough times and InboxMate offers to promote it to run automatically, no more suggestions. You can watch that progress for every rule — and promote deliberately — on the KI-Reife tab; the full graduation path, including which actions can graduate and which never can, is covered in KI-Reife.Clicking In Flow ansehen on a chain opens the categorizer editor traced to the email that produced it, so you can see exactly which rule matched and adjust it if the AI got it wrong.