Skip to content
Velaris

Tutorial

How to automate inbox triage with an AI agent

A working triage setup: what to classify, what to automate, what must stay manual — and the archive-don't-delete rule that makes it safe.

Vithu ·

To automate inbox triage well, the goal isn’t an empty inbox — it’s an inbox where everything remaining needs you. That distinction decides the whole design: the agent’s job is to remove what doesn’t need a human and surface what does, never to decide something is unimportant and hide it.

Start by classifying, not acting

Run the agent in read-only mode for a week before it touches anything. It classifies every incoming message and labels it. You review the labels.

This does two things. You find out where it’s wrong while being wrong is free, and you discover that your real categories aren’t the ones you assumed. A useful starting set:

  • Needs a reply from me — a person, expecting an answer.
  • Needs an action, not a reply — a task disguised as an email.
  • FYI — read eventually, no response owed.
  • Automated, useful — receipts, deploy notifications, alerts.
  • Automated, noise — newsletters, digests, marketing.

The two automated buckets are where nearly all the volume is, and where nearly all the safe automation lives.

Automate the noise bucket first

Newsletters and marketing are the highest-volume, lowest-risk category — the right place to start.

Three actions, in increasing order of nerve:

  1. Label and skip the inbox. Nothing is lost, your inbox shrinks immediately. This alone is most of the felt benefit.
  2. Bulk archive anything older than a month in that bucket. Reversible, and clears the backlog.
  3. Unsubscribe from senders you never open. Outbound and effectively irreversible — this one needs approval.

That third step is where a good agent earns its place: it can identify which senders you never open, which is information you don’t have, then propose a list.

The rule that makes this safe: archive, never delete

Every destructive-looking action should be reversible.

Archiving is reversible. Labelling is reversible. Deleting is not, and no triage system should do it. If the agent is wrong about a message — and it will be, occasionally — the difference between archived and deleted is the difference between a search away and gone.

This applies to the summary too. When the agent reports “412 messages archived”, that number should be a link to the exact set. A number you can’t inspect is a claim you have to trust.

What must stay manual

Being explicit about what you don’t automate is what makes the rest trustworthy:

  • Replying on your behalf. Drafting, yes — sending, no. Tone and commitments are yours.
  • Anything financial. Invoices, payment requests, banking notifications go to a human, always.
  • Anything from a person you know, unless it’s clearly a newsletter. The cost of mis-filing a colleague’s message is much higher than the cost of leaving it.
  • First-time senders. No history means no basis for a confident call.

The setup, step by step

  1. Connect the mailbox with read access only.
  2. Run classification for a week. Review labels daily. Correct them — that’s your evaluation set.
  3. Turn on labelling for the two automated buckets once accuracy holds.
  4. Add archiving for the noise bucket, older than 30 days.
  5. Enable unsubscribe proposals with approval on each batch.
  6. Add a morning digest — what arrived, what was handled, what needs you.

Six steps, and steps 1–3 involve no risk at all. Most of the value lands by step 4.

What good looks like after a month

Not zero unread. The realistic outcome is that the inbox contains only the first three categories, the noise is labelled and out of sight, and there’s a daily digest telling you what happened.

The measurable win isn’t messages archived — it’s how many things you had to look at to find the ones that mattered. If that number hasn’t dropped substantially, the classification is wrong and no amount of automation on top will fix it.

Watch the failure mode too: if you find yourself checking the archived folder regularly, the agent is over-filing and should be pulled back a step. That’s a signal, not a nuisance.

Velaris runs triage exactly this way — watch it ask before unsubscribing, in the demo. See also: connecting Gmail to the tools you already use.