EDGECASTS
← Back to library
beginner Communication Email 14:22 · Apr 16, 2026

Inbox to Zero Before Coffee

Hand your morning inbox to an AI that reads every email, drafts the replies, and leaves you three decisions only you can make. Triage done before your coffee cools.

● Coming this week

EPISODE UPLOADING

Recording is in the can; we're cutting and uploading it now. Chapters, prompts, and the full transcript are below; read ahead and we'll drop you an email the moment the video lands.

Get the drop notification →

Steal these

THE PROMPTS

One click and they’re on your clipboard. Paste into Claude, ChatGPT, Gemini. Whatever you pay for. Run the workflow you just watched.

01

Triage system prompt

Claude Sonnet 4.5
You are an executive email triage assistant. For each message I paste, output a single JSON object:

{
  "category": one of ["decide", "reply", "forward", "file", "ignore"],
  "one_line": a plain-English summary under 120 characters,
  "reason": why you chose that category, under 200 characters,
  "deadline": an ISO date if one is implied, otherwise null,
  "people": an array of full names (not email addresses) who need to know
}

Do not explain. Do not preamble. Just the JSON object.
02

Reply draft template

GPT-5
Draft a reply to the email below in MY voice.

My voice: direct, warm, two-to-five sentences, lowercase "i" only in informal threads, never uses "circling back" or "touching base" or "just checking in".

Do not make up facts. If you need information I haven't given you, end the draft with a bracketed [need: …] note. Sign off with just my first name.

EMAIL:
<<paste the email here>>
03

The three-decision filter

Claude Sonnet 4.5
I have run triage on my inbox. Below is the JSON array of all "decide" emails from this morning. Pick the three most consequential, ranked by the asymmetry between cost-of-waiting and cost-of-deciding-wrong, and return them as:

1. [subject]: [one-line summary]: [what I should think about for 60 seconds before replying]

Ignore urgency theater. A loud email is not automatically a big email.

DATA:
<<paste the array of "decide" items here>>

Use these anywhere. If they end up in a client deck, "borrowed from EdgeCasts" in the footer is how we keep the lights on.

Full transcript +
You are not an email server. Stop pretending to be one. Most of us spend the first ninety minutes of every workday doing a job we were never hired for: reading, sorting, and routing email. The actual work gets pushed to the afternoon, where it competes with the crash. In this workflow we hand the first two passes to a model. The triage prompt classifies every email into one of five buckets (decide, reply, forward, file, ignore) with a one-line summary and a reason. That alone saves most of the hour. Then we layer a draft-generation prompt on top of the "reply" bucket. The drafts never get sent automatically. They land in your Drafts folder, waiting for you to read, adjust, and send. The review is your actual job. You look at the three "decide" emails, you read the pre-drafted replies, and you ship. Ten minutes. One note on voice. Models drift. Every two weeks, run the "does this sound like me" test: paste a draft to a colleague who knows your writing and ask them to rate it. If they can't tell, ship it.

You're not an email server. Stop pretending to be one. This workflow turns your first hour of the day into ten minutes of decisions, with drafts already queued for the forty-seven replies you weren't going to write well anyway.

Why this lands

Inbox-zero purists will tell you the answer is discipline. It isn't. The answer is delegation, and for the first time, you have a delegate that works for fractions of a cent per email and never asks for a raise. The catch is the delegate is bad at tone and can't read your mind. That's what the prompts below are for.