Where It Earns Its Keep
For a lot of NT professionals, email and meetings are the work. Not the thing around the work, the work itself. An hour saved across email triage, meeting recap, and inbox catchup is an hour back on everything else.
Copilot in Outlook and Teams does three things well, reliably:
Summarise. Long email threads, long meetings, days of backlog.
Draft. Replies, meeting recaps, follow-up messages, status updates.
Find. Answer "what was the decision on X" from meetings and threads, without you scrolling.
Outlook and Teams are where Copilot pays for itself fastest, because email and meetings are where time leaks fastest.
Email Triage with Copilot
The first and best use. Instead of reading every email to figure out which ones matter, ask Copilot to do the triage.
What's actually important in my inbox right now
Open Copilot in Outlook or ask it via the chat pane, and get a prioritised view of the morning's load.
Look at the emails I received since yesterday afternoon. Group them into three buckets: urgent (needs a reply today), important but not urgent (this week), and informational (no action needed from me). Tell me what each urgent one is asking for.
What happened while I was away
The return-from-holiday inbox, made manageable.
I've been on leave for five days. Summarise what's happened in my inbox in that time. Highlight anything I need to act on, anything that was resolved without me, and any ongoing threads I should catch up on.
Catch up on one person's messages
Useful when one stakeholder has been active and you need to understand the whole conversation at once.
Summarise everything [person's name] has emailed me in the last two weeks. What's the current state of each topic, and what am I expected to do next?
Drafting Replies, with Tone Control
Copilot can draft a reply from the email thread you're looking at. The feature is built into Outlook's compose window. What makes the draft useful is telling Copilot the shape of the reply you want, not just "draft a reply".
A short, positive confirmation
Draft a reply confirming I can attend the 2 pm meeting on Thursday. Short, warm, one line asking whether a dial-in option will be available.
A polite no
Draft a reply declining this request. I can't take it on this month because I'm leading the digital rollout. Keep it professional, thank them for thinking of me, and suggest we revisit in July.
A firm but fair pushback
Draft a reply pushing back on the timeline. Explain that two weeks isn't workable given current staffing, propose four weeks as realistic, and offer a short call to talk through what's achievable in between. Firm but not combative.
A complicated reply you've been putting off
Draft a reply to this thread. The situation has changed since we last spoke, here's what's new [brief]. I need to explain the change, acknowledge it's frustrating, and propose two options for where to go from here.
First drafts almost always sound slightly too corporate or slightly too chipper. Don't just accept. Say "make it warmer", "less formal", "shorter", "drop the opening pleasantry". Third draft is usually the one to send.
Catching Up on a Long Thread
You've been CC'd late on a long back-and-forth. Instead of scrolling and reading every reply, ask for the summary you actually need.
Thread summary
Summarise this email thread. Tell me: what was the original question, what positions have been put by whom, where is it up to now, and what (if anything) am I being asked to do. Keep it under 150 words.
Decision tracker
Looking at this thread, list every decision that's been made or agreed, every action that was assigned, and anything that's still unresolved. Format as three short lists.
Who said what
Summarise the position each person has taken in this thread. For each person, one sentence on what they said and what they want. Tell me if anyone's position shifted during the conversation.
Meeting Recap and Action Items
For this to work, the meeting needs to have been recorded and transcribed in Teams, a setting your organisation may have on by default, or may leave up to the organiser. Once the transcript exists, Copilot can work miracles with it.
Standard recap after a meeting
Generate a recap of this Teams meeting. Include: key discussion points (not every utterance), decisions made, actions with owners, and anything that was deferred. Plain bullet points, not a transcript. Under 300 words.
Action items only, for a follow-up email
From this meeting transcript, pull out just the action items. For each one, tell me who owns it, what they said they'd do, and the timing if mentioned. Format it as a list I can paste into an email.
Quote-backed summary
Summarise this meeting by decision, not by speaker. For each significant decision, include a one-sentence summary plus the direct quote where it was made. Useful for records.
Recording and transcription rules vary. In Australia, recording a conversation generally requires notice to the other participants. Teams notifies when recording starts, but for external attendees or sensitive conversations, confirm expectations up front. Your organisation may also have policies about which meetings can be transcribed.
Catching Up on a Meeting You Missed
The single best Copilot feature for remote and regional work. You didn't make the meeting, or the internet dropped halfway through, or it was early and you were asleep. Catch up fast.
Quick catch-up
I missed this meeting. In under 200 words, tell me: what it was about, the three most important things discussed, anything that requires action from me specifically, and whether there's anything I should follow up on with someone.
Ask a specific question of the meeting
In this meeting, was there any discussion about the grant timeline? If so, summarise what was said and what conclusion (if any) was reached.
First-ten-minutes catchup
I joined this meeting 15 minutes late. Tell me what I missed in the first 15 minutes so I can pick up the thread without asking.
Turning a Meeting into a Briefing Note
Decisions made in a meeting often need to end up in writing, briefing a manager, updating a team, recording in a project file. Copilot can take a meeting transcript and produce a first draft of the note.
Briefing note from a transcript
From this meeting transcript, draft a one-page briefing note for my manager. Include: purpose of the meeting, key issues discussed, decisions made, next steps with owners, and any risks or concerns raised. Plain language, in our organisation's briefing style.
Team update from a meeting
Draft a short team update email based on this meeting transcript. The audience is my team of five, who weren't in the meeting. Focus on what affects their work in the next fortnight. Under 200 words, warm but professional.
Status update for a project tracker
Based on this meeting, update me on the current state of the [project]. Break it into: what's complete, what's in progress, what's new, and what's at risk. Short bullets, no fluff.
Chat-Based Copilot for Quick Q&A
The Copilot chat pane (accessible from within Teams, Outlook, or directly at copilot.microsoft.com signed in with your work account) is your go-to for questions that span your work, not just one document.
Things it can do that Word/Excel/PowerPoint Copilot can't:
- Answer questions across multiple files, meetings, and emails at once.
- Find things ("when did we last discuss the incident log? Who was in that meeting?").
- Pull together information from different corners of your tenant.
- Act as a general assistant for drafting, planning, research.
Cross-source search
Has our team discussed the new privacy policy anywhere in the last month? Search across emails, Teams chats, and meetings. Give me a short summary of what's been said and point me to where.
Project status across sources
Based on recent emails, meetings, and documents, what's the current status of the incident log migration project? Include what's done, what's next, and any risks that have been raised.
Prep for a conversation
I have a meeting tomorrow with [person]. Based on our recent emails and any meetings we've had, what's the current state of our conversation, and what should I come prepared to discuss?
When signed in with your work account, the same Copilot chat interface can see your organisation's content. When signed in with a personal account, it's just a general chatbot like ChatGPT. Watch which account you're in. The little profile picture at the top right tells you.
The Review Habit for Communications
More important in comms than in documents, because emails and meeting recaps go out to real people, fast, and your name is on them.
- Tone check. Does this sound like me, or does it sound like a generic bot? Adjust until it's your voice.
- Specifics check. Any names, dates, numbers, references. Verify the AI got them right, not plausible.
- Commitment check. Did the AI promise something on your behalf that you haven't actually agreed to? Pull it back if so.
- Discretion check. Does the message include anything that shouldn't be in writing, or shouldn't go to this audience?
- Length check. Almost always cut by 20 percent. AI drafts tend toward padding.
Copilot writes quickly. You are what makes the message yours.