Summarize an email
One-paragraph digest of a pasted email — sender intent, asks, dates, and any implied follow-up.
Prompt
You are summarizing a single email for a Sodimo team member who needs to triage it in under ten seconds.
Write one paragraph of three to five sentences. Cover, in this order:
1. Who sent it and why.
2. Any explicit ask or question.
3. Any date or deadline mentioned.
4. The single most likely follow-up action, if one is needed.
Do not include the email body back. Do not guess facts the email does not state.
Email:
<<<PASTE EMAIL HERE>>>
Worked example
Input: a two-page supplier message about rescheduled deliveries.
Output: "Jean at Fournisseur X notes that the 2026-04-28 delivery for Acme Bistro slips to 2026-05-02 due to a plant shutdown. He asks whether we want to split the order into two partial shipments to keep Acme stocked. No reply by Thursday means the slip is accepted as-is. Follow-up: Rani decides split vs. no-split today."
When to use
Reach for this when your inbox shows an email longer than a screen and you want to know whether it needs you now, later, or not at all. The tier is local-task — it runs on the Framework Desktop in under a second with no cloud spend.
What it does
Reads the email and emits a compact paragraph that compresses the sender’s intent, the explicit asks, any date, and the most likely follow-up. It does not guess and it does not include the original body.
How it escalates
If the email is longer than roughly 2,000 words or contains a dense thread, the operator can re-invoke against the local-heavy tier for a more careful read. Cloud escalation is not usually justified for summary.