How to Build an Email Triage System with Claude

Summary:

1. Build an email triage system that processes 127 emails into a one-page action list.
2. Create a rules file that controls how Claude categorizes and drafts replies.
3. Get copy-paste prompts for inbox triage and batch job applications.
4. Go from 90 minutes of morning email to 12 minutes of review.

I used to wake up to 127 emails. Not newsletters. Real emails: client questions, invoices, scheduling requests, follow-ups on threads I forgot about. Sorting through them took 90 minutes. By the time I finished, half my morning was gone.

Here’s what mornings look like now. I check my phone and open a one-page document Claude generated at 6am. Three urgent items. Eight that need my reply, with draft replies already written. Everything else sorted and archived. Review time: 12 minutes.

How does email triage with Claude Cowork actually work?

Claude opens your email client through Computer Use, reads each message from the screen, and categorizes it using rules you define. No API setup. No MCP plugins required. Claude literally looks at Gmail (or Outlook, or Apple Mail) the same way you would, except it processes 127 emails while you shower.

The trick that makes this reliable: you define the categories. Without rules, Claude decides what’s “urgent” on its own and gets it wrong half the time. With a rules file, it follows your logic every time.

How do you set up the rules file?

Create email-rules.txt on your Desktop. This is the brain of the system.

EMAIL TRIAGE RULES

URGENT (requires action within 4 hours):
- Any email from [your boss name], [key client names]
- Any email containing: "deadline," "today," "ASAP," "emergency"
- Any reply in a thread I started, waiting 3+ days

NEEDS MY REPLY (within 24 hours):
- Client questions about ongoing projects
- Meeting requests or scheduling changes
- Any email asking a direct question to me

FYI (read when I have time):
- Team updates and status reports
- Newsletters I actually read: [list specific ones]
- Tool notifications (Slack digests, calendar reminders)

ARCHIVE (do not need to see):
- Marketing emails and promotions
- Social media notifications
- Auto-generated receipts and confirmations

SKIP (do not read or categorize):
- Any email from [your bank], [doctor], [HR department]

Be specific. “Any email from Sarah” beats “any email from important people” because Claude doesn’t know who you consider important. List your top five senders by name. List the keywords that actually signal urgency in your world.

What’s the triage prompt?

Copy-paste this into Cowork. Modify the email client and file paths for your setup.

Read the file email-rules.txt on my Desktop. Then open Safari
and go to mail.google.com. Read all unread emails in my inbox.
For each email, categorize it using the rules in email-rules.txt.

For emails in "Needs My Reply," draft a reply based on the
email thread context.

Save a summary to my Desktop called "inbox-summary.txt" with:
- URGENT: sender, subject, why it's urgent
- NEEDS MY REPLY: sender, subject, draft reply to review
- FYI: sender and subject only
- ARCHIVE: count only

After creating the summary, archive all ARCHIVE category emails.

Here’s what happens. Claude opens Safari, loads Gmail, and starts reading from the top. Each email takes 10-15 seconds (screenshot, read, categorize). For 127 emails, that’s 20-25 minutes of Claude working. You do something else.

What do the draft replies look like?

This is where the time savings stack up. Claude reads the full email thread and writes a response based on the context. Say you get this:

From: David Kim
Subject: Re: Q3 proposal timeline

Hey, checking in on this. Think we can have the draft by
Thursday? If not, early next week works too. Also, can you
send the updated pricing sheet?

Claude’s draft in your summary:

DRAFT REPLY for David Kim - Q3 proposal timeline:

"Hi David, Thursday is tight but doable. I will have the
draft over by end of day Thursday. If anything changes I
will let you know by Wednesday. Attaching the updated
pricing sheet. Let me know if you have questions on the
new rates."

NOTE: Attach pricing sheet before sending.

Look, it’s not a Pulitzer. But it answers both questions (timeline + pricing sheet), includes a reminder about the attachment, and took Claude about 8 seconds. For 8 emails that need replies, that’s 8 drafts ready in your summary. Review time: 90 seconds per reply. Total: 12 minutes instead of 40-50 minutes composing from scratch.

What broke (and how I fixed it)

Auto-reply disaster. I set up a rule: “For scheduling confirmations, send directly without approval.” A client emailed to reschedule from Tuesday to Thursday. Claude saw “scheduling,” applied the auto-reply rule, and confirmed the original Tuesday time. Wrong answer. I showed up Thursday. She waited Tuesday. The fix: never auto-send to external recipients. Period. Not after the first week. Not ever, unless that specific category has two weeks of zero errors with manual approval.

Newsletter as urgent. Claude flagged a MailChimp newsletter as urgent because it contained the word “deadline” (for a sale). The fix: add specific newsletter sender addresses to the ARCHIVE list by name, not by keyword. marketing@company.com in ARCHIVE overrides the “deadline” keyword in URGENT.

Thread context missed in Apple Mail. Apple Mail collapses threads, and Claude read only the latest message instead of the full conversation. Draft replies missed context from earlier in the thread. The fix: add “Expand all conversation threads before reading” to the triage prompt if you use Apple Mail.

Which email client works best?

Client	Speed	Reliability	Notes
Gmail in Safari/Chrome	Fast	High	Best option. Consistent UI, clear buttons.
Outlook web	Fast	High	Cleaner than desktop Outlook for Computer Use.
Apple Mail	Medium	Medium	Thread collapsing causes context issues.
Outlook desktop	Slow	Medium	More UI elements = more screenshots per action. 30% slower.

Start with one email account. Multiple accounts in one client confuse Claude about which rules apply to which inbox.

What are real people asking about this?

From r/ClaudeAI and r/claude:

Real question	Answer
”I need this for Outlook. Does it exist?”	Yes. Computer Use works with any email client on screen. Outlook web is fastest.
”Is recurring tasks not possible on Chat?”	Not on Chat. On Cowork with scheduled tasks, yes.
”How are you actually using Cowork day-to-day?”	Email triage is the #1 use case. This article is the example.

A post titled “Hands down the best guide to Claude Cowork” hit 1,600 upvotes on r/ClaudeAI. The comments were people asking for exactly this workflow. The batch job application tweet hit 18,600 likes.

What does the morning summary actually look like?

This is what’s waiting on your Desktop at 6:25am:

MORNING INBOX SUMMARY
Processed: 127 emails

URGENT (3):
- Client X: deadline moved to Friday, needs confirmation TODAY
- Vendor Y: invoice dispute, $2,400 discrepancy
- Team lead: requesting status update before 10am standup

NEEDS YOUR REPLY (8):
- David Kim: Q3 proposal timeline (draft reply below)
- Sarah Chen: budget allocation question (draft reply below)
- [6 more with drafts]

FYI ONLY (47):
- Newsletter subscriptions, notifications, auto-receipts

ARCHIVED (69):
- Marketing emails, social notifications, spam

Three urgent items you need to act on. Eight drafts ready for your review. Everything else handled. That’s the deliverable.

How do you refine the rules over time?

Check category sizes every morning. Here’s the calibration checklist:

Signal	Problem	Fix
URGENT has 6+ items	Urgency rules too broad	Remove generic keywords, use specific sender names
ARCHIVE is under 40% of total	Archive rules too narrow	Add newsletter senders by email address
FYI has 5x more than REPLY	FYI is catching reply-worthy emails	Tighten the “direct question” rule
Same sender keeps miscategorizing	Rules don’t cover that sender	Add them explicitly to the right category

Accuracy started at 80% on day one (1 in 5 emails miscategorized). After a week of rule adjustments, it’s 95%. The remaining 5% are edge cases: emails from new contacts Claude has never seen, or ambiguous language where even a human would have to read the full message.

What about the batch job application workflow?

The viral tweet showed 50 applications in 30 minutes. Here’s the actual prompt. Start with 20, not 50.

Open Safari and go to [job board URL]. Search for [your job
title] in [your city or "remote"]. For each listing:

1. Open the listing, read the job description
2. Check if my resume (saved at [path]) matches 70%+ of
   the requirements
3. If it matches, click Apply
4. If there's a cover letter field, write one referencing
   2-3 specific requirements from the listing
5. Submit the application
6. Add a row to job-applications.csv on my Desktop:
   Company, Position, Date, Job Board, Status

Stop after 20 applications or end of results.

One practical tip the viral tweet didn’t mention: create the tracking spreadsheet FIRST. After two weeks of batch applications, you’ll have data on which job boards produce callbacks, which titles match your resume best, and which cover letter phrases correlate with responses.

What should you actually do?

• If you get 50+ emails per day: build this system today. The 90-minute-to-12-minute savings pays for your Claude subscription on day one.
• If you get fewer than 20 emails: use Claude Chat instead. Upload the important ones, ask for draft replies. Computer Use is overkill for small inboxes.
• If you use multiple email accounts: start with your highest-volume account. Add the second account after your rules are dialed in.
• If you want zero-touch automation: read the recurring tasks chapter. Schedule this prompt to run every morning at 6am while you sleep.

bottom_line

• The rules file is the whole system. Without it, Claude guesses. With it, Claude follows your logic. Spend 10 minutes writing good rules and you save 90 minutes every morning.
• Never auto-send to external recipients. Draft, review, approve. One wrong auto-reply costs more than all the time savings combined.
• Track your ratios. If category sizes drift, your rules need updating. Five minutes of rule refinement per week keeps accuracy above 95%.