← Back to library

Scope an email triage agent after a month's trial

Jarvis Specter, running several businesses and fielding up to 150 emails daily, let an OpenClaw agent named Donna triage three accounts for 30 days. Messages landed in four priority groups, urgent ones reached him as chat alerts, and routine answers were drafted for his approval. Tone, long threads and CC decisions failed, so he narrowed what it drafts.

  • OutcomeGet fast triage and routine drafts across several inboxes while keeping negotiations, sensitive relationships and CC choices with you.
  • SetupAn afternoon+
  • LevelIntermediate
  • CreditJarvis Specter
View original
Works with
OpenClawCustom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You get a high volume of mixed business email
  • Missing an urgent message is costly
  • You are willing to approve every send

Not for: Letting an agent send without review; Inboxes dominated by delicate relationships

What do you need, and what do you get?

You need

  • Read access to each mailbox
  • Notes on who matters and how you talk to them
  • A messaging channel for urgent alerts

You get

  • Every new message labeled by priority
  • Instant alerts for urgent items
  • Drafts for routine replies awaiting approval

How does it work, step by step?

  1. Define buckets and cadenceCheck mail on a schedule during work hours and sort into four categories.
  2. Alert on urgent onlyPush urgent items to a messaging app so nothing critical waits.
  3. Draft only the routineConfirmations, scheduling and templated answers get drafts; nothing is sent without approval.
  4. List what it must not draftNegotiations, close clients and suppliers, legal matters and anything needing CC decisions are flagged only.
  5. Write failure modes down firstDecide what a bad outcome looks like, such as wrong tone or a missed earlier agreement, before you start.

The prompt

Our own prompt, inspired by Jarvis Specter and written to work in OpenClaw and Custom agent. Values in lime are placeholders.

Prompt0 variables
Check my inboxes twice an hour while I am working. Sort each new email into urgent, important, informational or noise. Message me on [channel] for urgent ones with a one-line reason. Draft replies only for confirmations, scheduling and questions with a standard answer, and never send. For negotiations, legal matters, anyone on my relationships list, or any email where CC choices matter, flag it without drafting. Keep a log of your categorizations so I can correct them.

Inspired by Jarvis Specter: I Let an AI Agent Manage My Emails for 30 Days. Here's What Broke.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Tone notes in a memory file helped only partly; relationship voice is hard to encode.
  • Threads spanning several sessions lost details, such as a side agreement mentioned days earlier.

Our take

Jarvis Specter's write-up is the most useful kind: an honest list of what broke. Triage into priority groups and urgent alerts worked, and those are low-risk wins because a misfiled message is easily corrected. Drafting replies is where costs hide. A reply can be technically accurate and still wrong for the relationship, too blunt with a long-time client or too casual with a new one, and multi-day threads and CC decisions require context about people that an agent rarely has. His narrowed scope is a good default for anyone starting: let the agent sort and alert, and draft only routine, transactional answers such as confirming a time or sending a standard document. Write down before deployment what it must never draft, for example anything involving money disputes, staff matters or legal topics. Decide too what counts as failure, so a month-long trial ends with evidence rather than impressions. Keep every draft behind your approval, and review a sample of what it filed as low priority, since important mail quietly buried is the hardest failure to notice.

Where the time goes back: Inbox processing shrank from long sessions to short review passes, while urgent items arrived as alerts.

FAQ

How accurate was triage?
Roughly 85 percent right on day one, he estimates, and nothing urgent slipped through during the trial.
Did he keep it running?
Yes, with a narrower scope that lowered the hit rate on ambition but also the risk.

Source and credit

Inspired by Jarvis Specter. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
I Let an AI Agent Manage My Emails for 30 Days. Here's What Broke.
Creator
Jarvis Specter
Published on
DEV Community (dev.to)
Original date
Mar 8, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
OpenClaw
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Audit how you manage your agent team, not only the agents

Have your chief-of-staff agent review the last 30 days of how you delegated, clarified, interrupted, corrected, assigned, approved and followed up across your agent team, score eight management areas with evidence, list your three biggest weaknesses, and draft a seven-day improvement plan, without changing any bot, routine or instructions until you approve.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminPrompt✓ AI dry run

Brief an agent with nine fields, not a how-to

Before you hand a job to an agent, fill in nine short fields that name the result, the sources it may use, the deadline, what it may do alone, what needs your say-so, what it must never do, how to prove the work is finished, what to do when it gets stuck, and where to put the deliverable, then add a line that tells it to pick the simplest reliable method.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminPrompt✓ AI dry run

Brief your agent on the outcome, not every step

Hand a new job to your lead agent by describing the finished result instead of the steps, and have it confirm what success looks like, ask only for context it cannot find itself, pick the simplest dependable approach, state what it will do alone and what needs your approval, and check the result against your goal before calling it done.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminWorkflow✓ AI dry run

Map and trim workflows before adding AI

Before building AI into a company, map each workflow with the people who do it, cut needless steps and plan the system, then add automation on top.

Credit: Luke Pierce (@lukepierceops)

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Write your needs down before building a DIY agent server

Before following an AI through a self-hosted assistant setup, list what you need, try hosted options first, and set a stop point so the project does not become a second job.

Credit: u/No-Star7003 on r/AI_Agents

Minutes