The average executive spends 28% of their workday on email. Most of that time is spent on decisions that could be made in seconds — if you had a system. Claude is that system.
This isn't about writing better emails (that's covered in the Email That Gets Replies playbook). This is about processing your inbox faster, prioritizing ruthlessly, and getting through communication overhead so you can do actual work.
The Batch Processing Workflow
Dump your inbox batch
Copy-paste 10-20 emails at once. Don't process them one at a time — batching is the whole point.
Claude triages
Priority ranking, suggested action (reply/delegate/defer/archive), and draft replies for anything that needs one.
You review and send
Quick scan of Claude's triage, edit any drafts that need your touch, and clear the batch.
Repeat 2-3x per day
Instead of checking email constantly, process in focused batches.
The Master Triage Prompt
Set this up in a Project with your communication style and common contacts preloaded.
Here are [number] emails I need to process. For each one:\n\n1. **Priority:** Urgent (needs response within 2 hours) / Important (today) / Normal (this week) / Low (whenever) / Archive (no action needed)\n2. **Category:** Client / Team / Partner / Admin / Newsletter / Spam\n3. **Action:** Reply now / Delegate to [suggest who] / Schedule for later / Archive\n4. **If reply:** Draft a response in my voice (direct, warm, concise — no corporate language)\n\nGroup your output by priority so I can work through Urgent first.\n\nAdditional context:\n- My role: [your role]\n- People who always get priority: [list key people]\n- Things I delegate: [what goes to your team]\n- My current top priorities: [what you're focused on this week]\n\nEmails:\n[paste all emails]
Pro Tip
Set up a Claude Project called "Email System" with your communication style, key contacts, and delegation rules. Once configured, you just paste emails and Claude's triage gets better every time because it already knows your preferences.
Priority Framework Customization
Help me build a personal email priority framework. Here's how I think about email importance:\n\n**Always urgent (respond within 2 hours):**\n[list — e.g., anything from customers with open issues, board members, my direct reports about blockers]\n\n**Important but not urgent (same day):**\n[list — e.g., partnership opportunities, team updates that need feedback]\n\n**Can wait (this week):**\n[list — e.g., vendor proposals, meeting requests, non-urgent internal threads]\n\n**Auto-archive (no response needed):**\n[list — e.g., newsletters I actually read, FYI-only CCs, automated notifications]\n\n**Never respond to:**\n[list — e.g., cold outreach from vendors, unsolicited pitches]\n\nTurn this into a clear set of rules I can paste into my Email Project instructions so Claude applies these priorities automatically every time I batch-process emails.
Reply Templates for Common Patterns
Instead of drafting from scratch every time, build a library of reply patterns Claude can adapt.
Someone wants to schedule a meeting with me. Context:\n\nWho: [who's asking]\nWhat they want to discuss: [topic]\nMy assessment: [do I want this meeting or not?]\n\nIf yes: Draft a reply that's warm, gives 2-3 time options this week, and asks them to send a calendar invite.\n\nIf no: Draft a polite decline that doesn't burn the bridge. Suggest an alternative if appropriate (async, email thread, delegate to someone else on my team).\n\nIf maybe: Draft a reply asking for a brief agenda or one-paragraph summary of what they want to cover, so I can decide if a meeting is the right format.
I received an email that I should delegate to someone on my team.\n\nOriginal email:\n[paste email]\n\nDelegate to: [team member name and role]\nContext they need: [anything the team member should know]\n\nDraft two messages:\n1. Reply to the sender: 'I'm looping in [name] who handles [area] for us — they'll take it from here.' Keep it 2 sentences max.\n2. Internal message to [team member]: Forward the email with context about what I need them to do, any deadline, and any guidance on how to handle it.
Long Email Summarization
When you get a 2,000-word email that needs a response but you don't have time to parse every detail:
I received this long email and need to respond quickly:\n\n[paste the email]\n\nGive me:\n1. **TL;DR** (2-3 sentences — what is this person actually asking?)\n2. **Key decisions needed** (if any — what do they need from me specifically?)\n3. **Hidden asks** (anything buried in the middle that I might miss on a skim)\n4. **Draft reply** (concise, addresses their actual ask, under 100 words)\n\nDon't summarize every paragraph. Tell me what matters and what I need to do.
Read the 1,500-word email carefully. Spend 10 minutes understanding it. Spend another 10 minutes drafting a thoughtful reply. Total: 20 minutes.
Weekly Communication Review
Once a week, take stock of your communication patterns.
Here's a summary of my email activity this week:\n\n[paste a summary — number of emails received/sent, any patterns you noticed, anything that took too long]\n\nHelp me audit:\n1. **Time sinks** — What types of emails took the most time? Can any be templated, delegated, or eliminated?\n2. **Missed responses** — Am I dropping any threads? (Check if there are emails I received early in the week that I haven't addressed)\n3. **Delegation opportunities** — What am I personally replying to that someone on my team could handle?\n4. **Process fixes** — Are there recurring email types that indicate a process problem? (If I'm getting the same question 5 times, the answer should be documented somewhere)\n5. **One change for next week** — What's the single highest-impact change to my email habits?
The VIP Communication System
For your most important relationships — board members, key clients, investors — you need a different system.
Help me set up a VIP communication tracking system. My VIP contacts:\n\n[list 5-10 key people and your relationship with them]\n\nFor each person:\n1. Suggested communication cadence (how often should I proactively reach out?)\n2. A 'touchpoint prompt' — a quick message template I can send when I haven't been in touch for a while (not generic, tailored to each relationship)\n3. Topics to reference (their interests, recent wins, things they care about)\n\nAlso: create a simple tracking format I can update weekly — who I've contacted, who I owe a response, who I should proactively reach out to.
Scenario
You come back from a 4-day vacation to 247 unread emails. You have 90 minutes before your first meeting. How do you process all of them?
Slack and Teams Messages
The same principles apply to your messaging apps.
Here are messages from several Slack channels and DMs that I need to process:\n\n[paste messages with channel/person labels]\n\nFor each:\n1. Does this need a response from me specifically, or can someone else handle it?\n2. If I need to respond: draft a concise reply (Slack replies should be 1-3 sentences, not email-length)\n3. If it's FYI only: just note 'No action needed'\n4. If it's a thread that's gotten out of control: summarize the thread and suggest how to resolve it (usually a decision or a meeting)\n\nSlack tone: casual, brief, use reactions where a response isn't needed.
Real example
“I went from spending 2 hours a day on email to 30 minutes. The trick was batching — process everything at 8am, noon, and 4pm with Claude, and close email the rest of the day. My team thought I was more responsive, not less, because every email got a clear, complete response instead of a rushed one-liner.”
— VP of Sales
Managing a team of 12 with 150+ emails per day
Common Mistakes
Don't paste sensitive emails without thinking. Customer data, financial details, legal communications, HR issues — be thoughtful about what you process through Claude. Use your company's data policies as the guide.
Don't auto-send without reviewing. Claude drafts the replies; you review them. A 15-second scan catches tone issues, missing context, or responses that need your personal touch. The time savings come from not writing from scratch, not from skipping review.
Don't abandon your system after one good day. The value compounds over weeks. By week 3, Claude knows your priorities, your voice, and your patterns. Week 1 is the worst it will ever be.