Share concise email summaries with your team
Turn selected incoming emails into short summaries for colleagues who need shared customer or project context.
How this works
Turn selected incoming emails into short summaries for colleagues who need shared customer or project context.
Summarize selected email for colleagues while preserving the difference between quoted history and the newest request. Sharing should follow the intended audience and maintain the exact owner, deadline and decision being requested.
Before you start
Defined operating scope
Selected emails contain updates colleagues need without forwarding entire threads.
Required source material
Obtain Email messages; A team chat channel. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
The email reverses an earlier instruction. Summarize the latest change and identify the superseded request.
Prepare the inputs
- message_id
- Required
Mailbox and message identifier
Use the selected message or authorized filter.
- email_body
- Required
Current content and quoted thread
Separate latest text from earlier quoted messages.
- audience
- Required
Approved team destination
Confirm access to the underlying correspondence.
- summary_rules
- Required
Required decision and action fields
Define handling of attachments and sensitive details.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check message_id, email_body, audience, summary_rules before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected message_id and any missing required fields.
Retrieve a selected message from the inbox
- Retrieve the selected message and only the thread context needed to understand it; record attachment availability.
- Check the summary against the latest message and preserve negation and changed dates.
Checkpoint: A saved intermediate result for: Retrieve a selected message from the inbox.
Summarize its content with a language model
- Draft a concise summary containing the new information, requested decision, owners and stated deadlines.
- Verify that each action owner and deadline was explicitly stated or clearly marked unknown.
Checkpoint: A saved intermediate result for: Summarize its content with a language model.
Send the summary to team chat
- Prepare the message for the approved channel, retaining an authorized source link and recording delivery separately from drafting.
- Check the summary against the latest message and preserve negation and changed dates.
Checkpoint: A saved intermediate result for: Send the summary to team chat.
Reconcile the proposed result
- Check the summary against the latest message and preserve negation and changed dates.
- Verify that each action owner and deadline was explicitly stated or clearly marked unknown.
Checkpoint: The listed discrepancies have a named reviewer or an explicit unresolved status.
Package the result and unresolved work
- Define which correspondence the team may see and check that commitments and deadlines are preserved.
- Do not expand a selected-message request into monitoring the whole mailbox.
Checkpoint: A concise email summary in a team channel. Unresolved items remain visible in the review record.
Decisions along the way
The email reverses an earlier instruction.
Summarize the latest change and identify the superseded request.
A referenced attachment is unavailable.
State that its contents were not reviewed and avoid summarizing them.
The destination is not authorized for the correspondence.
Keep a local draft or prepare an appropriately reduced version for review.
What you will produce
email-summary-to-chat-result.json
JSONA concise email summary in a team channel. Label proposed and completed states separately.
Include: message_id · new_information · decisions_requested · actions · deadlines · attachment_gaps · status · evidence_reference · review_note
email-summary-to-chat-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving summary_rules.
Include: source_reference · question · owner · next_action
Check the result
- Check the summary against the latest message and preserve negation and changed dates.
- Verify that each action owner and deadline was explicitly stated or clearly marked unknown.
- Inspect message_id and email_body in both the original and output; confirm that record identity and interpretation survived the transformation.
- Define which correspondence the team may see and check that commitments and deadlines are preserved.
When something goes wrong
The email reverses an earlier instruction.
Summarize the latest change and identify the superseded request. Retain the affected evidence and recovery status.
A referenced attachment is unavailable.
State that its contents were not reviewed and avoid summarizing them. Retain the affected evidence and recovery status.
The destination is not authorized for the correspondence.
Keep a local draft or prepare an appropriately reduced version for review. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Share concise email summaries with your team for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Latest email E-9 changes a launch from Tuesday to Thursday. The quoted thread still says Tuesday and mentions an attachment that is absent.
Expected result
Synthetic expected result: Summary: launch moved to Thursday; earlier Tuesday date superseded; attachment unavailable. Do not present the attachment’s supposed contents as known.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure time to share an approved summary; omitted commitments in reviewed messages.
Stop or revise
The destination is not authorized for the correspondence. Pause affected records and apply this recovery: Keep a local draft or prepare an appropriately reduced version for review.
Keep the scope clear
- Do not expand a selected-message request into monitoring the whole mailbox.
- Sending summaries uses only the authorized audience and content scope.
Check before using
Define which correspondence the team may see and check that commitments and deadlines are preserved.
Business activities
- Deliver recurring client work
- Coordinate meetings and follow-ups
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Email messages · A team chat channel
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow