AI Prompts to Triage a Full Inbox in One Sitting

The triage problem is easy to describe and painful to live with. You have two hundred unread emails, no clear idea which five need a reply today, and two bad options: open each one and spend the morning reading, or skip the inbox and risk missing whatever is urgent. The right ai prompts to triage your inbox solve this by classifying every thread in a single pass and handing you a shortlist instead of a pile.

This guide is that prompt set. If you only want one thing to paste, start with Prompt 0, a single prompt that does the whole job. Below it you will find a bucket-definition prompt that teaches the model your classification system, a one-line-per-thread scan, a filter that surfaces only what needs you today, and a prompt that drafts the delegate messages. The prompts work in ChatGPT, Claude, Gemini and Microsoft Copilot, and in any assistant that can read your mailbox directly, which removes the copy-paste step.

Prompt 0: the one-paste version#

If you will not set up a multi-step session, use this single ChatGPT prompt to sort my inbox style. It defines the buckets, fixes the table format and tells the model to output nothing else. Paste it, then paste your sender, subject and snippet list underneath. Use it when you want a sorted table in one go and do not need to tune the buckets.

The multi-prompt version below does the same job with more control. Run it when the one-paste output files too many threads in the wrong bucket, because separating the definitions from the scan makes each rule easier to tighten.

What do you need before running an inbox triage prompt?#

Two things have to be in place before the prompts can produce a useful result.

The first is a set of triage buckets that match how you actually deal with email. The prompts below default to four: Reply now (needs your response today or tomorrow), Read and decide (worth reading, no urgent reply needed), Delegate (needs action but not from you) and Archive (newsletters, notifications, receipts and CC threads with no direct ask). These defaults suit most inboxes and sharpen when you tune them to your role. A recruiter might add a Candidates to advance bucket. A founder might split Reply now into Investor-priority and Other. Spend two minutes naming your own buckets, because the model applies them exactly as written.

The second is what you paste. If your assistant cannot connect to your mailbox, you are working from text you copy yourself. Copy the sender, the subject line and the first line or two of each unread thread, one thread per line. You do not need full email bodies for triage, since subject lines and snippets classify most threads, and leaving bodies out also limits how much real correspondence you send to a third party. Redact client names and figures that the model does not need to see.

How do you define your triage buckets for the AI?#

Run this first in the session, before anything else. It is a system-level instruction that defines your buckets in one message, so you do not have to re-explain your rules inside every scan.

The ESCALATE bucket does quiet but important work. It gives the model a safe exit for threads it cannot confidently classify from a subject line and snippet. A wrong REPLY NOW costs you time, while an honest ESCALATE costs you nothing, because you review it manually, the same as you would have without triage.

What is the prompt to scan your whole inbox in one pass?#

Once the model has your bucket definitions, the scan prompt does the work. Run it right after Prompt 1, in the same session, and paste your sender, subject and snippet list under it. The output is a table with every thread classified in a single pass and a one-phrase reason so you can spot disagreements at a glance.

The sort order matters. Asking for REPLY NOW first and ARCHIVE last puts the threads that need you at the top of the response, before you scroll through the noise.

How do you use AI to triage which messages need a reply?#

The scan gives you a sorted table. Prompt 3 narrows it to the threads that need a reply, ranked by consequence, with a suggested first move for each. Run it right after the scan, since the model already has the triage in context.

The TRUE URGENT rule is worth keeping even when your REPLY NOW list is short. When a large inbox produces eight or ten REPLY NOW threads, re-ranking by consequence separates the five highest-stakes items from the rest, so the list does not feel equally urgent and you do not start at the wrong end.

For the DELEGATE threads, a fourth prompt drafts the forwarding message for each one. These are two sentences each, direct, written to a capable colleague, with no explanation of why you are delegating. The model does not need to know the recipient, so it uses a placeholder you fill in before you send. Run it last, once you are happy with the buckets.

What do you do when the triage prompt gives bad results?#

Four failure modes come up often, and each has a direct fix.

The model files everything in ARCHIVE. This usually means the ARCHIVE definition is too loose or the snippets are too short to classify. Tighten the rule by adding 'CC only with no specific ask directed at me', so the model is not tempted to file anything ambiguous there. Paste longer snippets too, fifty words rather than twenty. When the model cannot see a clear ask, it defaults to the lowest-friction bucket.

The model puts too many threads in REPLY NOW. The REPLY NOW definition is probably too broad. Add an explicit constraint: 'REPLY NOW means there is a specific question or request directed at me, with a real consequence if I miss it today. Do not use it for FYIs, newsletters, or threads where I am CC'd.' That one rule removes most false positives.

The output loses its table format partway through. This is usually a context-length problem. Break the list into chunks of twenty to twenty-five threads, run the scan in two passes and merge the rows. Adding 'output only the table with exactly these columns: Bucket, From, Subject, Why, no other text' also locks the structure across a longer paste.

The model invents urgency that is not in the snippet. A dramatic subject line can trigger REPLY NOW even when there is no ask. Reinforce the escalation rule: 'if you cannot see a specific request or deadline in the snippet I gave you, use ESCALATE.' An honest ESCALATE is always better than a confident wrong classification.

Does this prompt work differently in ChatGPT, Claude, Gemini, and Copilot?#

The bucket and scan prompts work across the major chat assistants. What differs is how each one handles structured output and whether it can read your mailbox without a paste. Product names, plan requirements and connector names change often, so check each vendor's own help page before relying on a row.

One limitation applies to every chat assistant in that table: it does not keep your inbox between sessions. Every new conversation starts from zero, so the paste-and-classify loop resets each morning. You can process a backlog in one sitting, but ongoing triage needs a fresh copy each time. That is the reason an assistant connected to your mailbox beats a chat window for recurring triage. The prompts are no sharper, but the mail does not have to move.

Is there a faster way that does not require pasting anything?#

The paste loop has a ceiling. It cannot process mail that arrives after you started the session, it resets every morning, and it multiplies across several accounts. When the manual prompt set starts to feel like its own inbox problem, move to an assistant that connects to your mailbox. One route is to connect an AI assistant to your mailbox over MCP. AI Emaily's own MCP server is included on the Autopilot and Team plans. Another is to use a client that does the triage itself, and the roundup of tools that triage for you compares them.

We build AI Emaily, an AI-native email client for Gmail, Outlook and Microsoft 365, iCloud, Yahoo, Fastmail and other IMAP accounts. It sorts incoming mail as it syncs, with no daily export. You set your Personal Context and priority rules once, and the assistant applies them as mail arrives. In Copilot mode the AI drafts replies and holds them in a queue, and nothing is sent until you approve it. Autopilot, on the Autopilot and Team plans, handles routine mail within the rules you define, with undo and a full audit trail on every action. There is a 7-day free trial on Pro and Autopilot, and the pricing page shows what each plan includes.