Inbox triage with reply drafts in your voice: Multi-Step Agent Workflow for Claude Code, Codex or ChatGPT

Triages up to 30 pasted emails, flagging phishing and payment-change scams first, then drafts replies, delegation notes and scheduling answers in your voice without inventing commitments.

Prompt

Installs to .agents/skills/inbox-triage-with-reply-drafts-in-your-voice-multi-step-agent-wo/

mkdir -p .agents/skills/inbox-triage-with-reply-drafts-in-your-voice-multi-step-agent-wo && curl -sL "https://prompts-gpt.com/prompts/inbox-triage-with-reply-drafts-in-your-voice-multi-step-agent-workflow-for-claude-code-codex-or-chat/raw" -o .agents/skills/inbox-triage-with-reply-drafts-in-your-voice-multi-step-agent-wo/SKILL.md
SKILL.md
Preview
---
name: inbox-triage-with-reply-drafts-in-your-voice-multi-step-agent-wo
description: "Triages up to 30 pasted emails, flagging phishing and payment-change scams first, then drafts replies, delegation notes and scheduling answers in your voice without inventing commitments."
---

# Inbox triage with reply drafts in your voice: Multi-Step Agent Workflow for Claude Code, Codex or ChatGPT

Triages up to 30 pasted emails, flagging phishing and payment-change scams first, then drafts replies, delegation notes and scheduling answers in your voice without inventing commitments.

## Prompt

```
---
name: inbox-triage-reply-drafts
description: Triages up to 30 pasted emails, flagging phishing and payment-change scams first, then drafts replies, delegation notes and scheduling answers in your voice without inventing commitments. Nothing is sent. Use when asked to run the "Inbox triage with reply drafts in your voice" workflow.
---

# Inbox triage with reply drafts in your voice

Triages up to 30 pasted emails, flagging phishing and payment-change scams first, then drafts replies, delegation notes and scheduling answers in your voice without inventing commitments. Nothing is sent.

## Inputs

Ask for any of these that the user hasn't given:

- `emails` (e.g. "Paste up to 30 emails separated by ---, each with From, Subject, Date and body. e.g. From: Dana Lee <dana@northwind.vc> | Subject: Board deck | Date: Nov 14 | Can you send the Q3 deck before Wednesday's call?")
- `my_role` (e.g. "Founder and CEO of a 12-person B2B invoicing startup")
- `vip_list` (e.g. "Dana Lee (lead investor), Sam Ortiz (co-founder), anyone from Globex or Initech (top customers)")
- `voice_samples` (e.g. "Paste 2–3 emails you sent recently, e.g. 'Hi Dana, yes, deck is coming Tuesday. One question on the format: full or summary? Thanks, Alex'")
- `rules` (e.g. "Invoices and vendor billing go to Mia (finance). Partnership requests go to Raj. No calls on Fridays. Never agree to discounts by email.")
- `availability` (e.g. "Tue 18 Nov 14:00–16:00 CET; Thu 20 Nov 10:00–12:00 CET")

## Steps

Run the steps in order. Refer to saved results by name. Don't skip a step that says STOP.

1. **Paste the batch** — Start: Paste `emails` with `my_role`, `vip_list`, `voice_samples`, `rules` and `availability`.
2. **Split and number the batch** — Split `emails` on '---', From/Subject/Date lines, greetings and signatures; number E1, E2… in order. Per email: From (name, address), Reply-To if different, Subject, Date, latest message only (drop quoted history below 'On … wrote:', noting 'thread of N'). Don't summarise.
List guessed boundaries under 'Split check'. Over 30 emails: keep the 30 most recent (first 30 if undated); list the rest under 'Deferred' with sender and subject. Save the result as `batch`.
3. **Label each email** — Give each email in `batch` one label, in this order of precedence:
1. suspicious: asks for logins, codes, gift cards, urgent payment or new bank details; or the From domain doesn't match the claimed sender, or Reply-To differs. Applies even to apparent `vip_list` senders: spoofed VIPs are the usual pattern.
2. delegate: someone in `rules` handles this kind of mail
3. schedule: meeting request or time negotiation
4. reply-needed: waits on an answer only you can give
5. FYI: useful, no action
6. unsubscribe: newsletters or marketing you never act on
7. ignore: spam or cold pitches irrelevant to `my_role`
VIPs are never ignore or unsubscribe.
Table: ID | From | Subject | Label | Reason (quote the deciding words or address detail) | Delegate to. Save the result as `labels`.
4. **Score priority** — Score reply-needed, delegate and schedule emails in `labels`. Urgency 1–5 (5 = deadline within 48h or someone blocked on you; 3 = this week; 1 = none). Importance 1–5 (5 = `vip_list`, revenue, legal or your prior commitment; 3 = team or partner; 1 = nice to know). Priority = urgency × importance, with quoted evidence; highest first, older wins ties.
Output: suspicious emails under 'Check before anything else', the table (Rank | ID | From | Label | Urgency | Importance | Priority | Evidence), then 'Do first': top 3 IDs, one line each. Save the result as `ranked`.
5. **Learn the voice** — From `voice_samples`, write a voice guide of up to 8 bullets, each with a short quote: typical length, exact greeting and sign-off, sentence length, formality, how requests and 'no' are phrased, frequent phrases, things never done (exclamation marks, emojis, 'Hope this helps'). With fewer than 2 samples, say first that it's low-confidence. Save the result as `voice`.
6. **Draft in parallel** — Launch these as parallel subagents in one message, then wait for all of them. Using `ranked`, `labels` and `batch`, write in the voice guide `voice`, for your label only, highest priority first, never for suspicious emails. Commit to no date, time, price, discount, deliverable or decision absent from the email, `rules` or `availability`; use placeholders like [CONFIRM: renewal price]. Start each draft with the email ID and a 'Re: …' or 'Fwd: …' subject. If none have your label, write 'None.' Save the result as `drafts`.
   - **Replies**: Label reply-needed. Answer every question in order, near the voice guide's typical length.
   - **Delegation notes**: Label delegate. A forward note to the person named in the rules (what's needed, by when if stated, context), plus a one-line reply naming who follows up, if the sender expects one.
   - **Scheduling replies**: Label schedule. Offer 2–3 slots only from `availability`, each with weekday, date, time and timezone (also in the sender's timezone if stated), within `rules`. If none fits, say so and ask for their options.
7. **Voice and fact review** — Check each draft in `drafts` against its original in `batch`, the `voice` guide and raw `voice_samples`:
1. Remove, or replace with [CONFIRM: …], any date, time, price, number, attachment, promise or decision not in the email, `rules` or `availability`.
2. Rewrite sentences that don't match the samples (length, greeting, sign-off, formality, banned phrases).
3. Check every question is answered or clearly deferred.
Return the corrected drafts in order, then 'Changes': ID – what changed and why. Save the result as `reviewed`.
8. **Final draft check** — Review loop (max 3 passes): 1. Each draft starts with an email ID and a 'Re:' or 'Fwd:' subject.
2. No filler: 'I hope this email finds you well', 'Just circling back', 'Please don't hesitate to reach out', 'Hope this helps'.
3. Replies under 150 words unless answering 3+ questions.
4. Unknown facts use [CONFIRM: …], never 'XX', 'TBD' or made-up figures.
5. Delegation notes name one person and one ask.
6. Scheduling replies offer 2–3 slots with weekday, date, time and timezone, or ask for options.
7. A 'Changes' list ends it. Save the result as `reviewed`.
9. **Build the digest** — Digest from `ranked`, `labels` and `reviewed`, under 400 words plus table:
1. Check before anything else: each suspicious email, next step 'Do not reply or click links. Verify with the sender through a phone number or address you already have, then report as phishing'.
2. Do first: top 3, one line each.
3. All emails by priority: Rank | ID | From | Subject | Label | Priority | Next step ('Send draft', 'Forward to <name>', 'Archive', 'Unsubscribe', 'Verify and report').
4. Counts per label.
5. Every [CONFIRM: …] with its ID.
6. Deferred emails and 'Split check' notes from `batch`. Save the result as `digest`.
10. **Review the digest and drafts** — STOP and ask the user to approve before continuing: Review `digest` and the drafts in `reviewed`; fill every [CONFIRM: …] before sending. Approve for the copy-ready set, or edit first.
11. **Copy the digest and drafts** — Finish: Return `digest` and `reviewed`.

## Done when

Every step has run, each approval was given, and you've reported what was produced and where it was saved.
```

## Usage Notes

Run it in Claude Code or Codex: save as .claude/skills/inbox-triage-reply-drafts/SKILL.md (or .agents/skills/ for Codex) and say "run the Inbox triage with reply drafts in your voice workflow"; parallel steps run as subagents. Or paste it into ChatGPT or Claude and answer its questions. It asks for: emails, my_role, vip_list, voice_samples, rules, availability. Build or run it step by step at prompts-gpt.com/workflows/inbox-triage-reply-drafts.

Example output

At a glanceEmails per triage label (8 emails)Phishing attempt E4 flagged first, before any replies
  • Suspicious: 1
  • Reply needed: 2
  • Schedule: 1
  • Delegate: 2
  • Unsubscribe: 1
  • Ignore: 1

Example for: 8 pasted emails, CEO of a 12-person B2B invoicing startup, VIPs Dana Lee and Globex, finance mail to Mia, slots Tue 18 Nov and Thu 20 Nov CET.

Digest

Check before anything else

  • E4, "Dana Lee" <dana@northwind-vc.co>, Urgent: updated wire details. The domain doesn't match northwind.vc, and the email asks for "new bank details before 5pm." Do not reply or click links. Verify with Dana by a phone number you already have, then report it as phishing.

Do first

  1. E1: Globex says "renewal paperwork blocked on your sign-off by Friday."
  2. E2: Dana Lee wants the Q3 deck "before Wednesday's call."
  3. E6: Initech wants a call this week.

All emails by priority

RankIDFromSubjectLabelPriorityNext step
—E4"Dana Lee" (spoofed)Urgent: updated wire detailssuspicious—Verify and report
1E1Priya Nair, GlobexRenewal termsreply-needed25Send draft
2E2Dana LeeBoard deckreply-needed20Send draft
3E6Tom Reyes, InitechQ1 rollout callschedule15Send draft
4E3Lumen HostingInvoice #4471delegate9Forward to Mia
5E7Kai BrandtPartnership ideadelegate6Forward to Raj
—E5SaaS WeeklyIssue 112unsubscribe—Unsubscribe
—E8Growthly10x your pipelineignore—Archive

Counts per label: suspicious 1, reply-needed 2, schedule 1, delegate 2, unsubscribe 1, ignore 1.

CONFIRM items

  • E1: [CONFIRM: renewal price]
  • E2: [CONFIRM: deck send date]

Deferred: none. Split check: the boundary between E5 and E6 was guessed from a "Sent from Outlook" line.


Reviewed drafts

E1 — Re: Renewal terms
Hi Priya,
Thanks for flagging this. The renewal stays at [CONFIRM: renewal price] for 12 months, and I'll sign once legal clears it. One question: should the PO go to you or to procurement?
Thanks, Alex

E2 — Re: Board deck
Hi Dana,
Yes, the deck is coming [CONFIRM: deck send date], ahead of Wednesday. Do you want the full version or the summary?
Thanks, Alex

E6 — Re: Q1 rollout call
Hi Tom,
Happy to talk. Here are two options:

  • Tue 18 Nov, 14:00 CET (08:00 EST)
  • Thu 20 Nov, 10:00 CET (04:00 EST)
    If neither works, send me a couple of times that suit you.
    Thanks, Alex

E3 — Fwd: Invoice #4471
Mia, could you review and pay the Lumen Hosting invoice due 30 Nov? Thanks.

E7 — Fwd: Partnership idea
Raj, Kai Brandt is proposing a referral partnership. Could you assess it and reply to him directly?
Reply to Kai: Thanks, Kai. Raj will follow up.

Changes

  • E1: Removed "10% loyalty discount" (rules say no discounts by email) and replaced a guessed price with [CONFIRM].
  • E2: Removed "Tuesday," which wasn't in the email or availability.
  • E6: Dropped a Friday slot (rules say no calls on Fridays) and added EST times.
  • All drafts: Removed exclamation marks to match the voice samples.

Waiting for approval. Fill every [CONFIRM: …] item, then approve to get the copy-ready set, or edit first. Nothing has been sent.

Written by AI from this prompt. Your results will vary.

Run it in Claude Code or Codex: save as .claude/skills/inbox-triage-reply-drafts/SKILL.md (or .agents/skills/ for Codex) and say "run the Inbox triage with reply drafts in your voice workflow"; parallel steps run as subagents. Or paste it into ChatGPT or Claude and answer its questions. It asks for: emails, my_role, vip_list, voice_samples, rules, availability. Build or run it step by step at prompts-gpt.com/workflows/inbox-triage-reply-drafts.

Make it repeatable

Keep using this prompt without pasting it in every time.

Prompt details

By
Prompts-GPT editors
Published
How prompts are written and checked

Did this prompt work?

Keep exploring

More in Multi-Agent Pipelines