Some inboxes aren't busy. They're complicated.
Busy is fine. Busy means the same question 40 times and you can copy a saved reply. Complicated means every email needs a judgment call before anyone can type a word.
This one belongs to a competitive mahjong league that runs in 60 cities. Open it on any given morning and you get, in no particular order:
"Can I change my prize?" — sure, probably.
"My score isn't showing up." — need more info.
"What happens if we only have three players?" — the four-player rule, again.
"Someone in this league is definitely cheating." — that one's for a human.
Rules questions, score bugs, refund asks, timezone confusion, and accusations, all in the same pile. Ten-plus hours a week, and most of those hours weren't spent typing. They were spent deciding what kind of email this is before typing.
Here's the part that matters: the assistant I built never sends an email. Not one. It reads each message, sorts it, and writes a first draft. A person reviews, approves, sends. The league still talks to its players. That didn't change.
So the first thing I built wasn't the drafts. It was the list of things it is never allowed to touch.
Cheating allegations: always a human.
Refund and money disputes: always a human.
Anyone mentioning a family emergency: always a human.
Those go straight to the team with no draft attached, because the wrong first sentence on one of those does more damage than a slow reply ever could.
Everything else — the four-player rule, the score explanation, the timezone mix-up — gets a first pass written and waiting. The team does a 30-second review instead of a 6-minute write from a blank box.
And every email they edit before sending becomes a new example the assistant learns from. It gets better because they touch it, not in spite of it.
Before: 10 hours a week in the inbox.
After: under 1.
About 9 hours a week back. Not from answering faster. From never starting at zero.
It doesn't answer your people. It writes the boring half of every reply, so nobody is staring at a blank box at 9pm deciding whether "my score is wrong" is a bug or a fight.
The takeaway isn't "get an inbox assistant." It's that the useful part of any automation is the line you draw around it. Decide what a person must always handle. Then let the boring half of everything else get pre-written.
So here's the one thing worth doing this week. Open ChatGPT or Claude and paste this:
Here are the last 20 emails I replied to (paste them, names removed). Sort them into two lists: ones where a first draft could be written before I read them, and ones a human must handle from the first word. For the second list, tell me the rule you used to spot them.
The second list is your escalation rule. The first list is your 9 hours.
—Sarah
Reply 1 if your inbox is the complicated kind.
Reply 2 if you want the "what not to automate" breakdown.
