Jun 5 • General discussion
Workflow of the Week: Email Thread Reply Draft
Workflow of the Week: Turn a Long Email Thread Into a Reply Draft
Long email threads are where AI can help quickly, but only if you keep control of the final message.
Use this when a customer, vendor, or team thread has too much history and you need:
- a short summary
- the real next decision
- a safer reply draft
- a list of what to verify before sending
Do not paste private customer details, passwords, payment info, contracts, HR issues, legal advice, or confidential screenshots into a public AI tool.
Start by cleaning the thread:
- customer names become Customer A
- emails become [email removed]
- phone numbers become [phone removed]
- addresses become [address removed]
- invoice/account/payment details get removed
Then use this prompt:
Help me turn this long email thread into a safe reply draft.
Context:
- My role: [your role]
- Relationship: [customer/vendor/team/internal]
- Goal of the reply: [what needs to happen next]
- Tone: clear, calm, professional, no overpromising
Email thread, with private details removed:
[PASTE CLEANED THREAD]
Return:
1. Five-bullet summary of what happened
2. The main decision, question, or next step
3. Missing information I should verify before sending
4. A draft reply I can edit
5. Any risky promises, assumptions, or private details I should remove
Rules:
- Do not invent dates, prices, approvals, policies, or commitments.
- If something is unclear, ask a question instead of guessing.
- Keep the reply short.
- Make it clear what I need to verify before sending.
Example:
If a vendor says delivery is “probably next week” and a customer asks if the schedule is confirmed, the safe reply is not:
“We will have this delivered next week.”
The safer reply is:
“Thanks for checking in. I am confirming the latest delivery timing now. I do not want to give you a date until I have the updated vendor confirmation. I will follow up by tomorrow morning with the confirmed next step.”
Human approval rule:
Before sending, check whether AI invented a date, price, refund, discount, policy exception, approval, or promise.
If it did, revise before sending.
Try it this week. Then use the pinned Post Your First AI Task thread to share a sanitized version of what the email was about and what you had to verify before sending.
Outside references:
OpenAI prompt engineering guidance
Anthropic guidance on reducing hallucinations
NIST AI Risk Management Framework
0
0 comments
Workflow of the Week: Email Thread Reply Draft