How to Use Muse to Triage Your Inbox
Forward email to Muse, get a sorted inbox with drafted replies, and approve what goes out. How inbox triage works and the guardrails that keep it safe.
By Professor Muse4 min read
Email is the perfect agent task: high volume, clear rules, and most of it does not need you. Muse can read a connected inbox, sort what matters from what does not, draft the replies, and hand you a short list of decisions. You stay the sender of record on everything that leaves. Done well, it turns email from an open loop into a short daily ritual.
One caveat before the how-to: at Connect on September 23, Meta announced Muse would get an email address of its own, so you could forward messages to it or add it to threads. Meta has not published a rollout date. What follows describes the triage pattern as Meta has presented it; some steps depend on features still rolling out.
The short version
- Connect your inbox read-only first. Let Muse summarize and sort before it ever drafts a reply.
- Triage means three buckets: needs you, draft a reply, archive or delete.
- Nothing sends without your approval (Sentinel enforces that). Review every draft before it goes out.
- Never route password resets or verification codes through the agent.
Start Read-Only
Connect the inbox with read access (here’s how connectors work) and ask for a daily digest for a few days: what arrived, what looks urgent, what can wait. Check the summaries against the actual inbox. You are calibrating two things at once: whether Muse reads priorities the way you do, and whether you trust its judgment enough to give it the next rung. If the digest misses something important, say so immediately. Early corrections shape its model of your priorities more than later ones.
The Three Buckets
Good triage sorts every message into one of three outcomes:
- Needs you. Anything with real stakes or real ambiguity: a client escalation, a bill that looks wrong, a message where the right answer depends on judgment only you have. Muse flags these and gets out of the way.
- Draft a reply. The routine majority: meeting confirmations, thank-yous, scheduling, “sending that over today” messages. Muse writes the draft in your voice and queues it for approval.
- Archive. Newsletters you never open, notifications, receipts, threads that resolved themselves. Muse files or deletes them under rules you set.
Tell Muse your rules explicitly: “Newsletters older than a week get archived. Anything from my boss or my kid’s school gets flagged. Draft replies to scheduling emails but never send them.” The rules are the product. The model just executes them. If a message does not fit a bucket, the rules need work. “Needs you” is not a junk drawer; if everything lands there, your rules are too timid.
Check the Archive
Triage makes mistakes, and the mistakes cluster in the archive. Once a week, skim what got filed away. You will find the newsletter you actually wanted, the receipt for something you need to return, the thread that looked resolved but was not. Each find is a rule improvement: “always flag receipts over $200,” “never archive anything from the school.” The archive review takes ten minutes and it is where the system gets smarter. An agent you never audit is an agent you cannot trust.
The Approval Habit
Every draft gets your eyes before it sends. This is the load-bearing wall of the whole setup. Read the draft, check the recipient, then approve. It takes seconds per message and it is the difference between delegation and abdication. If a draft is wrong in the same way twice, fix the rule behind it instead of fixing the draft again.
Two things deserve special care. First, the agent should never see password resets or verification codes. The mailbox connector strips those out, because an inbox that can reset your other accounts is a master key. Do not forward them anyway. Second, be careful what the agent learns from your email history. Old messages contain the kind of personal context that is gold for impersonation, so keep sensitive accounts on a shorter leash or out of reach entirely.
Make It a Routine
The best version of this is boring: a morning digest waiting when you wake up, drafts queued for the routine replies, and a flagged list of five or fewer things that genuinely need you. Ask Muse to learn the patterns: which senders always matter, which threads you always ignore, how you like bad news delivered. Refine the rules monthly. Inboxes drift, and triage rules should drift with them. Add an evening shutdown: a two-line summary of what got handled and what is waiting for morning. It closes the loop, and it means Monday never starts with archaeology.
Done right, inbox triage buys back the most expensive minutes of the day: the ones you currently spend deciding what your email means instead of doing the thing it asks for.
