← Back to the Copilot Adoption Hub

Author: Lukáš Barda · Updated November 2, 2026

Scenarios and prompts from the Copilot in Outlook webinar. We’ll show how to quickly understand a long thread, write a reply for different recipients, improve a weak email and pull tasks out of your communication. Copy the prompts and try them on your own mailbox.

Before you start:
  • You’ll find Copilot in the new and classic Outlook, in Outlook on the web and also in Copilot Chat.
  • Enter prompts about a thread with the email open, so Copilot knows which conversation you mean.
  • Always read and check a draft email before you send it.

Tip: After pasting, rewrite the text in [square brackets] to fit your situation – e.g. with a colleague’s name or a folder name.

Working with your whole mailbox

Copilot doesn’t just work with a single email. It can go through your whole mailbox and calendar and even help with Outlook settings.

Week summary

Summarize my emails from this week, only the unread ones I received. Give me a short summary of these emails in one paragraph and a list of tasks in a table showing who wanted what and when it’s due.

Out of office

Set up an „out of office“ automatic reply for the rest of the week in the calendar.

Meeting time

Find a suitable time for a meeting this week with [colleague’s name].

Mail rule

Create a rule for incoming emails: highlight everything from [sender] in red.

Folder rule

Create a rule for incoming emails in the folder [folder name]: highlight everything from [sender].

Universal prompt template

Works for any email or thread. Fill in what you need and leave the rest to Copilot.

Template

Read or process [type of communication]. Recipient: [audience] Goal: [what the recipient should understand, decide or do] Focus on: [key facts, risks, tasks, deadlines] Output: [length, structure, tone] Check: Don’t make up missing information. Separate confirmed facts from suggestions. Flag unassigned owners, deadlines and decisions.

1

Long thread → quick understanding of the situation

A long email thread arrives. Several people have replied, some of the information is contradictory and an important request is hidden in the middle.

Prompt 1

Summarize this email thread in five points. Split the information into: – the current situation, – confirmed decisions, – open questions, – tasks and owners, – deadlines. Don’t make up information that isn’t in the thread.

Prompt 2

What is expected of me according to this thread? For each request, state: – who raised it, – what exactly they’re asking for, – whether a deadline is given, – whether anyone has already responded to it.

Prompt 3

Which information in the thread is contradictory or ambiguous?

You don’t have to read the whole thread from the beginning. In a moment you know what was decided, what’s open and what’s expected of you.

2

One situation → three different replies

The content of the reply is the same, but you’d write it differently to a customer, to the internal team and to management. The audience changes the result.

Prompt 1 · Basic reply

Draft a reply to this email thread. Goal of the reply: – confirm that we’re dealing with the situation, – briefly explain the current status, – state the next steps, – clearly name what we still need from the recipient. No more than 180 words. Don’t make up missing facts.

Prompt 2 · For the customer

Rework the reply for the customer. Use a calm, professional and helpful tone. Don’t commit to anything or any deadline that isn’t confirmed in the thread.

Prompt 3 · For management

Rework the reply for management. Use this structure: – situation, – impact, – risk, – recommendation, – decision required. No more than 120 words.

Prompt 4 · For the internal team

Rework the reply for the internal team. Focus on: – who does what, – by when, – what needs to be verified, – what we’ll communicate to the customer afterwards.

The same facts, three different emails – each one exactly for the person who will read it.

3

Weak draft → usable email

You’ve already written the email, but it’s too long, defensive, unclear and missing a concrete next step.

Sample weak email to try
Sample email

Subject: Current status of resolving the deployment issue Hello everyone, I would like to take this opportunity to inform you about the current status of resolving the issue that appeared after the last system deployment last week and that has been discussed quite intensively across teams in recent days. Based on the information so far and consultations with colleagues from IT, the vendor and several other stakeholders, we have identified several possible causes. At this point, however, we are unfortunately still unable to confirm with certainty which of them is the main cause of the situation. A more detailed analysis and verification of the individual hypotheses is currently under way. At the same time, we have introduced several temporary measures intended to minimize the impact on users. It should be emphasized, however, that these measures are not a long-term solution and some of them may affect how comfortable the system is to use. We have also asked the vendor to provide additional materials and technical support. We believe that thanks to this cooperation we will be able to understand the problem better and propose an appropriate solution. In the coming days we will continue analyzing the situation and as soon as further information is available, we will inform you without delay. If you have any questions, please contact me or colleagues from the project team. Thank you for your cooperation and patience. Best regards, Lukáš

Prompt 1 · Review

Review this email from the recipient’s point of view. Find: – unclear wording, – unnecessary details, – wording that may come across as defensive, – a missing decision or call to action. Don’t rewrite the email yet.

Prompt 2 · Rewrite

Rework the email so that it’s brief, factual and professional. Use this structure: 1. why I’m writing, 2. what’s important, 3. what I propose, 4. what I need from the recipient. No more than 150 words.

Prompt 3 · Mobile version

Also create a short version suitable for reading on a mobile phone. Keep all the important facts and the action required.

Copilot isn’t just an author. It’s also an editor and critic of your work emails.

4

Email → tasks, priorities and follow-up steps

It’s not enough to read a thread and reply. You need to pull the work out of it – who does what, by when, and what’s most urgent.

Prompt 1 · Tasks

Find all tasks and commitments in this thread. Create a table: – task, – owner, – deadline, – status, – source part of the email. If the owner or deadline isn’t stated, mark it as unassigned.

Prompt 2 · Priorities

Which three items need the fastest response? Judge only by the information in the thread: – an explicit deadline, – impact on the customer, – blocking further work, – a request for a decision. Don’t create a priority if it can’t be supported by the source.

Prompt 3 · Follow-up

Draft a short follow-up email that: – summarizes the agreed steps, – asks the owners to confirm, – points out missing deadlines. Don’t present suggestions as already confirmed decisions.

In a few minutes, a long thread gives you a task table, priorities and a ready follow-up.

5 rescue prompts

If the result doesn’t look right, try one of these follow-up prompts:

How do you know?

Which specific information in the thread did you base your answer on?

Facts only

Limit the result to information supported by the content of the emails.

Facts vs. suggestions

Separate the facts from the communication from your own suggestions.

Timeline

Put the information in chronological order and point out any changes in decisions.

What’s missing?

What is missing or ambiguous in the available communication?

Frequently asked questions

Where do I find Copilot in Outlook?

Copilot is in the new and classic Outlook and in Outlook on the web. You can also use Copilot Chat to work with your whole mailbox and calendar.

How do I summarize a long email thread with Copilot?

Open the thread and ask for a summary split into the current situation, decisions, open questions, tasks and deadlines. Add that it shouldn’t make up information that isn’t in the thread.

Can Copilot write a reply to an email?

Yes. Write who the reply is for – a customer, management or the team – and what goal and length it should have. Always read and check the draft before you send it.

How do I pull tasks out of emails?

Ask Copilot for a task table with owner, deadline and status. Have it mark missing owners and deadlines as unassigned. Then have it draft a follow-up email.

Lukáš Barda – AI and Microsoft Copilot trainer. He helps companies and their teams bring AI into everyday work in a practical, clear way, without unnecessary jargon. AI and Copilot training