Email Triage: The Complete Guide

Email triage is sorting incoming messages by what they need from you (a reply, a handoff, a calendar slot, a folder, or nothing) before you spend real attention on any of them. Done by hand, it's a daily ritual. Done with filter rules, it's brittle. Done with a verdict layer, it becomes a background process that costs, in one builder's report, 3.5 cents for 500 emails.

The manual methods

The classic framing is four actions: delete it, do it, delegate it, or defer it. Pair that with the two-minute rule from Getting Things Done: if a reply takes under two minutes, send it now rather than filing it for later.

Time-boxed triage sessions help too. Two or three passes a day beat a permanently open inbox.

Manual triage breaks on volume. At a few hundred messages a day, the triage itself becomes the job.

Rules and filters

Filters route by sender, subject, and keywords. They're excellent for known senders and newsletters, and useless for decisions that depend on what a message actually says. "Is this customer angry enough to escalate?" isn't a keyword. Rules versus verdicts maps where filters stop and judgment starts.

The AI email triage layer

AI email triage asks closed questions about each message:

• Does this need a reply from me?
• Is it urgent?
• Which lane: sales, support, billing, personal, or newsletter?
• Is it a meeting request?

Each answer comes with a probability. High-confidence answers act (label, route, file). Low-confidence ones stay in the inbox for you.

The receipts: 500 emails for 3.5 cents and the 1,500-message inbox run, both as reported by their builders. The site's pattern page is email classification, and the meeting-request triager handles the calendar lane specifically.

Design rules for AI email triage

• Never auto-delete or auto-reply on a lone verdict. Labels and folders are reversible; deletions and sent mail aren't.
• Keep a "not sure" lane and actually read it.
• Send only what the question needs. Subject and body text, not attachments or full thread history, when you can avoid it.
• Review misroutes weekly and fix the question wording that caused them.

Shared inboxes and teams

On support@ and sales@ inboxes, triage becomes routing: the question shifts from "what do I do with this?" to "who owns this?" At that point it's ticket triage in all but name, and the ticket triage guide takes over.

Frequently asked questions

What is email triage?

Sorting incoming messages by the action they need before reading them in full, so attention goes to what matters first.

Can AI triage my email safely?

With guardrails: no irreversible actions on a single verdict, a review lane for uncertain messages, and minimal data sent. Check your email and model providers' terms too.

How much does AI email triage cost?

One builder reported 3.5 cents for 500 emails with one question each. More questions per email scale the cost linearly.

Is AI email triage the same as spam filtering?

Spam filtering is one question about unwanted mail. Triage asks several questions about wanted mail.

What's the fastest way to start AI email triage?

Export a few hundred emails and classify them as a CSV, then compare with your own judgment on a sample. More on the model in what Jev is.