How Executive Assistants Can Finally Conquer Email Overload with AI

Most “AI for inbox” advice treats email like a single problem. For an executive assistant managing two inboxes, your own and your executive’s, it’s two problems with completely different rules. Replies you send from your account are yours. Replies you send from your exec’s account aren’t. The line between what AI can draft, what only you should send, and what your exec personally has to write is the rule that actually keeps you out of trouble. Get that wrong and the time you saved on triage costs you a year of trust.

McKinsey’s State of AI 2025 found that 88% of organisations use AI somewhere, but only 7% have it fully scaled. The gap usually isn’t tooling, it’s policy. Same with your inbox. The tool is the easy part.

A delegation tier list, before any prompt

Sit down with your exec and agree, in writing, on three categories.

• Auto-handle: emails you reply to in your name without asking, e.g. routine scheduling requests, FYI threads where you’re cc’d, internal logistics.
• Draft and clear: emails where AI drafts a reply, you review, and your exec sees the draft before it goes (board-adjacent, sensitive client matters, anything involving a number or commitment).
• Hands-off: emails where AI must not draft anything, period. Personal correspondence, performance feedback, anything that could end up in a deposition.

Write this list down. It becomes the policy block at the top of your AI prompts, and the principle that decides whether a model gets to touch a thread.

Inbox A: your own

Your own inbox is where AI gets full leash. Open Microsoft Copilot, Gemini inside Workspace, or ChatGPT (with email pasted in or via a connector) and run a triage prompt:

“Triage my unread emails. Output a table: Sender | One-line summary | Priority (urgent / today / this week / FYI) | Suggested action

For ‘urgent’ and ‘today’, also draft a reply under the table, numbered to match. Voice: friendly, brisk, EA voice. Don’t draft replies for FYI items, just confirm I can archive.

If anything looks like it should be forwarded to my exec rather than handled by me, tag it ‘escalate’ instead of giving a priority.”

You scan the table in 90 seconds, accept the drafts that look right, edit the ones that don’t, send. Six or seven replies handled in the time it used to take to read them.

Inbox B: your exec’s

Different rules. The model never sends from the exec’s account. Drafts only, always reviewed, and the prompt makes the constraint explicit:

“I’m triaging my exec’s inbox. Delegation policy: Auto-handle (I reply in my name): [PASTE LIST] Draft and clear (AI drafts, I review, exec sees before send): [PASTE LIST] Hands-off (don’t draft anything): [PASTE LIST]

For each unread email below, classify it into one of those three buckets. For ‘auto-handle’ items, draft a reply from me. For ‘draft and clear’, draft a reply in my exec’s voice [PASTE EXEC VOICE CARD] but mark it clearly ‘FOR EXEC REVIEW’. For ‘hands-off’, do not draft, just summarise and flag.

[PASTE OR ATTACH UNREAD EMAILS]”

You’re using the same model on the same inbox, but with completely different posture. The “FOR EXEC REVIEW” tag is the safety rail. It means even if you accidentally hit send too fast, the recipient sees a draft marker rather than receiving an unreviewed reply on the exec’s behalf.

The summary thread your exec actually reads

Once a day, run this against the exec’s inbox:

“Summarise the activity in [EXEC]‘s inbox over the last 24 hours. Group by:

1. Decisions waiting on them (one line each, with deadline if any).
2. Heads-up items they should know about but don’t need to act on.
3. Stuff I’ve already handled in their name (one line, so they’re not surprised if it comes up).

Keep total length under 200 words. They’ll read it in a 90-second window between meetings.”

That third bucket is the political smart move. An exec who learns about your handled-in-their-name actions secondhand from the recipient is unhappy. An exec who reads them in the morning briefing is reassured.

The failure mode that costs trust

The single biggest mistake EAs make with AI in an exec’s inbox is letting a model auto-reply in the exec’s voice without a review step. It will eventually get something wrong. A name. A meeting time. A commitment to a deal that wasn’t made. The recipient won’t know it was AI; they’ll think your exec made a verbal commitment in writing. By the time you find out, the damage is rebuilt-relationship-grade.

The protection is structural, not vigilance. Don’t connect a tool that can send autonomously to an exec’s account. Use AI for drafting only, and let the actual send button stay manual. The minute you save on hitting “approve” is not worth the year you’ll spend explaining the one time it went wrong.

A counterintuitive note on volume

Most EAs measuring “inbox time saved” measure the wrong thing. Cutting your own triage from 90 minutes to 30 is real, but it’s not the headline saving. The headline saving is in your exec’s time, because every email you handle in their name is one they don’t have to read. If you triage your exec’s inbox down from 60 unread to 6 worth their attention, you have given them an hour of their day back. That hour is worth ten of yours. Track that metric, not yours.

Two things to keep human

Personal correspondence. Anything labelled urgent by HR or legal. The first is privacy. The second is liability. AI doesn’t go near either. If you ever find yourself drafting “the company is no longer pursuing the [TOPIC]” through ChatGPT, stop, close the tab, and call legal. AI is a productivity tool, not a substitute for the person in the room who knows the actual stakes.

What email becomes

The work shifts from typing replies to writing rules. The first month you set up the dual-inbox system, you’ll spend more time tweaking the delegation policy and the voice cards than you will saving. Month three, the system runs cleanly, and you find that the part of your day you used to lose to email is back, available for the work that’s actually hard to delegate: anticipating, prioritising, and protecting your exec’s attention. That’s the work that made the role indispensable in the first place. AI just got the typing out of the way.