How to summarize an email thread without losing the latest position
A thread summary helps someone understand what happened and what still needs a response. The useful result explains the current state, rather than giving equal weight to every repeated quotation.
Start with the right material.
- What you provide
- one expanded email conversation.
- The intended result
- Save a summary separating decisions, open questions and latest request.
How the workflow works.
Read the messages in order, identify changes of position and separate resolved points from open questions. Attribute important commitments to their speaker, especially when several participants discuss the same next step.
What to check in the result.
Check the latest message before relying on the summary. Earlier proposals may have been replaced, and a statement that someone will investigate is different from confirmation that the issue is solved.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.