Turning Long Outlook Threads Into Clear Next Steps With Copilot
A deal thread that's been going for three weeks and eighteen messages usually has the actual state of the deal buried somewhere in the middle, not the top. Someone agreed to a discount in message six, a stakeholder raised a security question in message eleven that never got a clean answer, and the most recent message is the prospect's assistant asking to reschedule a call, which tells you nothing about where the deal actually stands. Copilot in Outlook (which needs a plan that includes it, not just basic Copilot Chat) can read the whole thread, and its built-in "Summary by Copilot" box gives you a short summary with citations back to the messages, but a specific extraction prompt is what pulls that state out, but only if you ask for something more specific than "summarize this." For the general summarizing and drafting features, Copilot in Outlook: Drafting Replies and Summarizing Threads That Actually Help covers the basics; this article is about one specific use of it, turning a messy thread into next steps you can act on.
If you're new to Copilot generally, the Beginner's Guide to Copilot is worth reading first.
Why "summarize this thread" isn't enough
A plain summary request gives you a shorter version of the thread, which is a real improvement over reading all eighteen messages, but it's still organized the way a summary is organized: chronologically, evenly weighted, prose. What a salesperson actually needs from a long thread isn't a shorter story, it's an extraction: what was promised, by whom, what's still open, and what happens next. Those are different outputs, and asking for the first one won't get you the second.
Read this email thread and pull out three things separately: every commitment either side has made (who committed to what, and when), every question that was raised but never clearly answered, and the single most recent ask from the prospect. Don't summarize the conversation generally, just extract these three categories.
”Input
18-message Outlook thread
Three weeks of back-and-forth: pricing discussion, a security question, a rescheduled call, and a discount offer buried in the middle.
Commitments made
Who promised what, and when, on both sides of the deal.
Open questions
Anything raised but never clearly answered, like the unresolved security question from message eleven.
Most recent ask
What the prospect actually needs from you right now, separate from the deal's older history.
A real thread, worked through
Take a realistic version of that eighteen-message thread, condensed here to the five messages that actually matter:
Outlook
The thread, condensed to the messages that carry the deal's actual state, illustrated
Aug 3, You to prospect: Given the timeline, we could do a 10% discount if we can get this closed by end of Q3.
Aug 11, Prospect's security lead: Before we go further, does this support SSO? Our IT policy requires it for anything touching customer data.
Aug 11, You: Good question, let me check with our team and get back to you on that.
Aug 19, Prospect: Following up on timing, any update on the SSO question?
Sept 15, Prospect's EA: Can we move Thursday's call to Friday instead? Something came up on our end.
Notice what's missing: nobody ever answered the Aug 19 follow-up. The thread just moved on to scheduling, which is exactly how a real unresolved question survives thirteen more messages without anyone circling back to it.
Running the extraction prompt above against that thread produces something like this:
| What it found | Detail |
|---|---|
| Commitment made | 10% discount, contingent on closing by end of Q3, offered Aug 3 |
| Open question | Whether the product supports SSO, raised Aug 11, never answered, followed up on Aug 19 with no reply on file |
| Most recent ask | Move Thursday's call to Friday (Sept 15), unrelated to either the discount or the SSO question |
Why this worked: the prompt asked for three separate categories instead of one blended summary, which is what let the SSO question surface as its own line item instead of getting folded into "the thread also touched on technical requirements" the way a general summary would flatten it. Separating "most recent ask" from "still open" is what stops the newest message, which is pure logistics, from crowding out the oldest unresolved one, which is the actual blocker.
Tip
If the SSO question surfaces as unresolved, that's your actual next action, not the reschedule. A long thread's most recent message is often its least important one; it's frequently just logistics. Don't let recency stand in for priority when Copilot presents its findings back to you.
Next move: turn those three findings into next steps you can actually act on before the Friday call:
| Action | Owner | Due |
|---|---|---|
| Answer the outstanding SSO question from Aug 11 | You | Before Friday's call |
| Confirm the Friday reschedule | You | Today |
| Decide internally whether the 10% Q3 discount still stands | You and deal desk | Before it's confirmed to the prospect in writing |
| Send a reply covering the SSO answer and the new call time | You | End of day |
From extraction to a next-steps email
Once you have the three categories, the natural next prompt turns them into something you send, not just something you read.
Based on the commitments and open questions you just pulled out, draft a short reply to the prospect that does two things: answers the SSO question (yes, we support SAML-based SSO on our Business plan) and confirms the Friday reschedule. Keep it under 100 words, don't mention the discount since that's still under internal discussion.
”Naming what to leave out is as important as naming what to include. Copilot has no way to know the discount is still being discussed internally unless you say so, and a draft that casually confirms an internal-only detail to the prospect is a genuinely costly mistake in a sales context, not just an awkward one.
Verify commitments against your own memory, not just the draft
Copilot is reading the same thread you are, which means it can also miss something ambiguous, like a commitment made verbally on a call and only half-referenced in a later email. Before sending anything that confirms a price, a date, or a scope commitment, check it against your own recollection or your CRM record of the deal, especially for anything that happened outside of email.
Making this a habit, not a one-off rescue
The version of this workflow worth building into a routine is running the extraction prompt at the start of any call prep for a deal that's had more than a handful of back-and-forth messages. Two minutes before a call, ask Copilot for the commitments and open questions on that thread, and you walk in with an accurate state of the deal instead of a memory of it that's already a week stale. It's a smaller habit than it sounds, and it's the difference between a call that starts by re-litigating what was already agreed and one that starts from where the deal actually stands.
Ask for commitments, open questions, and the most recent ask separately, not a general summary
Treat the newest message as the newest, not automatically the most important
Tell Copilot explicitly what internal context to leave out of a prospect-facing draft
Verify any commitment against your own memory or CRM before confirming it in writing
Official sources
Checked on September 21, 2026. Features, plans and names change often, so the vendor's own pages are the final word.