The Email Thread Untangler: Turn a Chaotic Reply-All Thread Into Decisions, Owners, and a Draft Reply
Why this prompt matters
Untangled email threads are a hidden tax on every team: knowledge workers routinely spend a large share of their workday on email, and long threads are exactly where decisions silently drift — someone assumes a decision was made because nobody objected, while someone else assumes the opposite because they were following a tangent subthread. The real cost shows up later: a vendor gets the wrong price confirmed, a deadline nobody tracked gets missed, or two people both think the other one sent the final draft. A five-minute untangling catches this before it becomes a Monday-morning “wait, who approved that?” conversation.
What we use it for
You return from two days offline to a 34-message reply-all thread about a vendor contract renewal, where three different people proposed three different numbers, someone asked a question on Tuesday that never got answered, and two people appear to have agreed to something in a side thread you weren't copied on. You need to know what was actually decided, what's still open, and who owns what, in the next five minutes — not by rereading all 34 messages.
Prompt
Role: You are a meticulous chief of staff whose job is to read messy email threads and extract exactly what matters, without missing anything or inventing anything that wasn't actually said. Context: I'm pasting a full email thread below, with all replies in chronological order, including sender names. The thread covers [TOPIC OR SUBJECT OF THE THREAD]. I need to get back up to speed fast without rereading every message myself. Task: Read the entire thread and produce the following, in order: 1. Decisions Made: Every decision that was actually confirmed by the relevant people, with who made it and which message it appears in (by timestamp or position in the thread, e.g. "message 14"). Do not list something as decided if it was only proposed or discussed without explicit agreement. 2. Open Questions: Any question that was asked in the thread and never got a clear answer, quoting the question and who asked it. 3. Action Items: Anything someone committed to do, with the owner's name and any deadline mentioned. If no deadline was given, say so explicitly rather than inventing one. 4. Contradictions or Unresolved Conflicts: Any place where two people in the thread appear to disagree or propose different things without it being resolved. 5. A Draft Reply: One ready-to-send reply from me that acknowledges the decisions, asks the open questions that still need answers, and moves the conversation forward. Keep it under 150 words and match a professional but not overly formal tone. Constraints: Only report what is explicitly stated in the thread — do not infer a decision was made just because a conversation trailed off. If the thread is ambiguous about who owns an action item, say "unclear, needs confirmation" rather than guessing. Do not include information that isn't in the thread I paste. Output Format: - Decisions Made: [bulleted list] - Open Questions: [bulleted list] - Action Items: [bulleted list, format: Owner — Task — Deadline (or 'no deadline given')] - Contradictions: [bulleted list, or 'None found'] - Draft Reply: [full text, ready to send] Thread to analyze: [PASTE FULL EMAIL THREAD HERE, IN CHRONOLOGICAL ORDER WITH SENDER NAMES]
Result
Decisions Made:
- The team will renew with the current vendor rather than open a new RFP — confirmed by Priya in message 9, with no objections in subsequent replies.
- The renewal term will be 12 months, not the 24-month option the vendor originally proposed — confirmed by Marcus in message 22, referencing a call with the vendor rep.
Open Questions:
- “Can we get the per-seat price locked for the full term, or does it float with their annual increase?” — asked by Priya in message 11, never answered in the thread.
- “Who's actually signing this, legal or procurement?” — asked by Devon in message 17, never answered.
Action Items:
- Marcus — send the final redlined contract to legal — no deadline given.
- Priya — confirm the per-seat pricing question directly with the vendor rep — mentioned as “will do this week” in message 24.
- Devon — unclear, needs confirmation: Devon offered to loop in procurement in message 17 but never confirmed whether they actually did.
Contradictions:
- Marcus states in message 22 that the vendor agreed to a 12-month term, but in message 28 Priya references “the 24-month deal we're signing” — this appears to be an unresolved mix-up between the two of them that nobody has caught yet.
Draft Reply:
Hi all — catching up on this thread. To confirm where we landed: we're renewing with [Vendor] for 12 months (not 24), and Marcus is sending the redlined contract to legal. Two things I still need answers on before we close this out: (1) is the per-seat price locked for the full term or does it float with their annual increase, and (2) who's actually signing — legal or procurement? Also flagging that message 22 says 12 months but message 28 references a 24-month deal — want to make sure we're all aligned on the term before this goes to signature. Can whoever has the latest get back to me by end of day tomorrow? Thanks!
Most “summarize this thread” prompts produce a single paragraph of prose that reads like a competent summary but quietly discards the one detail that actually mattered — a deadline, a disagreement, a question nobody answered. This prompt avoids that by forcing five separate, differently-shaped outputs instead of one blended summary. A decision and an open question are different kinds of information that need different responses from the reader, and collapsing them into one narrative paragraph is exactly how threads get misread a second time, even after someone has already “caught up.”
The constraint against inferring unstated decisions is the single most important line in the prompt. The natural failure mode for any model reading a long thread is to smooth over ambiguity — if a conversation about a price proposal trails off without an explicit “yes, let's do that,” a summarizing model will often report it as decided anyway, because that's the most narratively satisfying way to close the thread. Forcing the model to flag unresolved threads as open questions, and to say “unclear, needs confirmation” rather than guessing an owner, is what keeps the output trustworthy enough to act on without re-reading the source material yourself.
The contradiction-detection step exists because long threads frequently contain two people who think they agree but are actually describing different outcomes, as in the 12-month versus 24-month example above. No single message in that kind of thread looks wrong in isolation — the mismatch only becomes visible when someone, or something, reads the entire thread at once and holds both statements in view simultaneously. This is also the step most generic summarization prompts skip entirely, because finding a contradiction requires actively comparing claims across messages rather than compressing each message in sequence.
The draft reply is deliberately the last output, not the first, because a good reply depends on first establishing what's actually unresolved. A prompt that jumps straight to “write a reply” without first doing this extraction produces replies that sound confident but restate whatever the most recent message said, which is often exactly the part of the thread that's still in dispute.