An email thread is a sequence of messages, not a single flat document. A prompt that summarizes or drafts a reply should receive message IDs, send times, authors, recipients, and thread relationships from the mail service. Parse quoted earlier text as a quotation, not as a new statement by the latest sender. Build a claim ledger that marks each item proposed, corrected, approved, or unresolved. The most recent message can clarify an older claim, but recency alone does not grant approval. If a reply is missing from the fetched thread, state that the record is incomplete before claiming agreement.
Make this comfortable
Email prompts: reconstruct the thread before drafting
Operational case
Aster Operations discusses a depot pilot with a vendor. The first email proposes 47 sites. A later message from the authorized program owner limits the approved pilot to 20 sites; the 47-site expansion remains a future proposal. A final vendor reply quotes the original 47-site text while asking about a meeting. A flat summarizer could mistake that quotation for a renewed approval. The prompt instead ties each claim to its message ID and asks the drafter to say '20-site pilot' while leaving expansion unresolved.
Message M-41: 47-site expansion proposed.
Message M-47: program owner approves 20-site pilot only.
Message M-52: quotes M-41; asks for meeting.
Current claim: 20-site pilot approved.
Unresolved: 47-site expansion; no renewed approval.Performance and operating cost
Sorting M messages by reliable timestamps is O(M log M), while walking provider-supplied thread order is O(M). Claim extraction adds review proportional to the number of substantive statements. Restrict retrieval to the relevant thread and referenced attachments; loading an entire mailbox increases privacy exposure and token cost. A short provenance ledger prevents a correction from disappearing when a long quoted chain dominates the prompt.
Common Mistakes
- Do not treat a quoted old proposal as a new decision.
- Do not infer approval solely from the latest message's position.
- Do not claim the thread is complete when a referenced reply is missing.
Connected lessons
- Prompt engineering applications
- Prompt Engineering
- Meeting minutes: separate decisions from proposals
- Context distillation: shorten input without losing governing exceptions
- Evidence IDs: make generated claims auditable against supplied records
- Email prompts: keep sender identity and message text separate
- Email prompts: verify attachment version and coverage
- Email prompts: review To, Cc, Bcc, and reply scope
- Email prompts: separate drafted commitments from sent messages
- Calendar prompts: resolve availability, zone, and duration
- Calendar prompts: distinguish create, update, and cancellation
- Calendar prompts: scope recurrence changes to the right instances
- Project: review an Aster vendor reply and invite
- Email and calendar prompt decisions
Continue with: Support prompts: reconstruct ticket identity and chronology.
prompt engineering
email calendar