Hand the morning inbox to an agent: it files and labels, it never deletes
Ben Patterson（PCWorld 撰稿人；据采集站转述）PCWorld · Date not disclosed
Read originalSaved text / editorial summary
采集站 agentusecases.ai 的编辑摘要（原帖 pcworld.com 在本次采集时返回 HTTP 403，以下为转述而非引文）：一名 PCWorld 撰稿人在一个单独的 Gmail 账号上测试，而不是自己的工作 Outlook。他在 Claude 的 Cowork 标签页里设了一条早间自动化：检查过去 24 小时的邮件，把会话标注为 Important 或 Archiveable，归档 Archiveable 的那些，并给收据打标签；它还会写一份分拣摘要，并为商务与学校联系人起草回复，亲友邮件留给他本人。结果是一天后收件箱变小、未读数下降、少量收据已归位，但 Claude 尚未起草任何回复，属早期报告、承诺有后续。已知的安全边界：Claude 的 Gmail 集成未经批准只能起草不能发送；可以丢弃邮件但不能永久删除，被丢弃的邮件保留 30 天。
Business model
A PCWorld writer handed the most draining part of the morning to a personal agent: a daily automation in Claude's Cowork tab scans only the last 24 hours of mail, marks each thread Important or Archiveable, files the archiveable ones, labels receipts, writes a triage summary and drafts replies to business and school contacts, leaving friends and family to him. After one day the inbox was smaller and the unread count lower, and not one reply had been drafted. What is worth copying is not the automation but three boundaries: test on a separate account, draft-only never send, and no permanent deletes - even trashed mail stays recoverable for about 30 days.
The proposed value is a restricted permission model: approve a read-only list before filing or labelling, keep sending and deletion with the human, and audit the result. Misclassification remains possible even when filing is reversible. The source gives no measured reduction in email volume or time spent, and reports no drafts on day one.
Workflow
- Start on a throwaway or secondary account, never the main work mailbox.
- Fix the taxonomy at two or three labels, with the rule for each written down.
- Limit the scan window to the last 24 hours, never the whole mailbox.
- Run the first pass read-only: a table of sender, subject, time, proposed label and one-line reason.
- Route anything ambiguous into a separate needs-my-call list, including anything about payments, contracts or account security.
- Only after you approve the list do filing and labelling run, and you should still be able to see which messages it will touch.
- Split drafting from sending: it writes short drafts marked unsent, and you press send.
Adaptation plan
The report gives no hours saved, no mail volume, no error rate and no cost, and it is explicitly an early report with a follow-up promised. The original article could not be read at collection time (HTTP 403), so all specifics come from the discovery site's editorial summary. The workflow, prompt and pitfalls here are AgentFlow's proposals, untested.
Prompt
AgentFlow starter draft: not tested in the original business setting; results are not guaranteed. Synthetic examples do not verify the author’s revenue.
You are an inbox triage assistant. Your goal is to cut my morning load. You may label and file. You may not delete or send. [INPUT] Account: [account name - must be a test or secondary account] Window: the last 24 hours, read and unread Allowed labels: Important / Archiveable / Receipts Leave to me: personal mail from friends and family - do not label and do not draft [EXECUTION STEPS] 1) First return a read-only table: sender, first line of subject, time, proposed label, one-line reason. Change nothing yet. 2) Put anything you are unsure about into a separate needs-your-call list, stating why: first-time sender, looks like a bill but no amount shown, subject does not match body, and so on. 3) Only after I approve the table, run two write actions: label and file the Archiveable items, and label anything with an invoice or payment proof as Receipts. 4) Then give a triage summary: total, count per label, count needing my call, and what you skipped and why. 5) After the summary, draft replies for Important mail from business or school contacts, under 120 words each. Drafts only. [OUTPUT] - Read-only table with columns: sender / subject / time / proposed label / reason. - A separate needs-your-call list, each entry with the reason it is uncertain. - A triage summary with counts and a skip log. - Drafts, each marked DRAFT - NOT SENT. [HUMAN CONFIRMATION] - Nothing is labelled or filed until I approve the read-only table. - Deleting, permanent deleting, unsubscribing, setting auto-replies and sending are all forbidden. Request them instead. - Anything about payments, contracts or account security must not be filed automatically. [SYNTHETIC EXAMPLE - not real data, format only] Input: 37 messages in the last 24 hours on the test account Output (extract): | Registrar office | Grade submission deadline | 06:12 | Important | hard deadline stated | | Online store | Your invoice is ready | 07:03 | Receipts | PDF invoice attached | | Industry weekly | Twelve stories this week | 07:40 | Archiveable | subscription, no action | | Unknown domain | Partnership invitation | 08:15 | Needs your call | first-time sender, body mentions payment | Summary: of 37, Important 6, Archiveable 24, Receipts 4, needs-you 3; filed 24 after approval; 2 drafts written, none sent.
Running costs and pitfalls
The report gives no hours saved, no mail volume, no error rate and no cost, and it is explicitly an early report with a follow-up promised. The original article could not be read at collection time (HTTP 403), so all specifics come from the discovery site's editorial summary. The workflow, prompt and pitfalls here are AgentFlow's proposals, untested. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.
