Step 1 — 08:30, clear the backlog first
Delegate the email cleanup that eats the first 30 minutes after sign-in to Cowork: triage, priorities, and unanswered-reply tracking.
▶ What you learn — Cowork takes not “summarize this” but “classify and organize this.” This is where the difference between a reading tool and an acting agent first appears.
08:30. You are Ava Nakamura, a sales rep at Aurora Dynamics. Email piled up overnight, today’s calendar is packed, and Teams has messages waiting for replies.
1-1. Inbox triage
Scenario 1
📌 What is happening
Twenty emails arrived overnight. Only two are truly urgent, but they are buried among newsletters. This takes 20–30 minutes every morning.
- 🎯 Expected output
- Flag urgent emails · Archive newsletters · 3-line summary
- 💡 Efficiency point
- A person must open emails one by one to judge urgency. Cowork sees sender, subject, and body together, and does not stop at classification; it actually handles them.
- ⚠️ What to check
- Check that it only classifies and archives, without sending anything.
Review only 20 emails from the last 24 hours. Flag urgent items and archive newsletters.
Summarize the result in only 3 lines. Do not draft replies.
✅ Result check
- 2 urgent emails — Rajiv Menon (Meridian Bank) incident follow-up, Ingrid Bauer (Halcyon Energy) RFP question deadline
- 6 newsletters archived
- Summary is within 3 lines
If you need drafts, continue with — “Draft 3-sentence replies only for the 2 items you just marked urgent. Do not send them.” It is faster than asking for everything at once.
1-2. Today’s top three priorities
Scenario 2
📌 What is happening
Email is organized, but “so what should I do first?” remains. Calendar, inbox, and Teams are in separate windows.
- 🎯 Expected output
- Three priorities with evidence, one line each
- 💡 Efficiency point
- This is the first time Cowork reads calendar + email + Teams together. People lose context while moving across three windows.
- ⚠️ What to check
- Check whether each item includes evidence for "why it is number 1."
Look at today's calendar, important unread emails, and Teams messages I have not replied to.
Tell me only my top 3 priorities for this morning, one line each. Add one line of evidence each. Do not draft anything.
✅ Result check
- Is the 14:00 Meridian Bank QBR included as a priority?
- Did it find 4 Teams messages waiting for a reply?
- Does each item include evidence (which email or which event)?
1-3. Things I sent but never got a reply to
Scenario 3
📌 What is happening
Received email is visible, but email I sent that never got a reply is not. This is the most common leak in sales.
- 🎯 Expected output
- One table of unanswered emails
- 💡 Efficiency point
- This is work people structurally miss. Even in Sent Items, you must check each thread for a reply. Cowork compares at the thread level.
- ⚠️ What to check
- Check that it does not create drafts when you did not ask for them.
Make a table of only the emails I sent in the last week that have not received a reply.
Use 3 columns: recipient / organization / what I am waiting for. Do not draft anything yet.
✅ Result check — You should see 4 unanswered items.
| Recipient | Organization | Waiting for |
|---|---|---|
| Peter Novak | Kestrel Logistics | Contract response |
| Claire Dubois | Ironwood Consulting | Resource confirmation |
| Diego Ferrer | Internal CSM | Solstice renewal data |
| Yuki Tanaka | Internal Finance | Q3 numbers confirmation |
If you need a follow-up — “For the Peter Novak item only, draft a polite follow-up.” This is much faster than drafting all 4 at once.
What you verified in this step
- ✅ It does real actions such as archive and flag, not just classification
- ✅ It reads three repositories at once: email, calendar, and Teams
- ✅ External actions require approval
- ✅ Short prompts and follow-up expansion are faster
Go to Step 2 — 30 minutes before the meeting, create a briefing.