7 Microsoft Copilot Meeting Prompts I’d Save for Teams

A meeting ends.

Everyone says thanks. Teams closes. Five minutes later, three people have three slightly different versions of what was decided. One person thinks Sarah owns the follow-up. Sarah remembers saying she would look into the issue. Someone else is waiting for Finance. The deadline mentioned halfway through the call never made its way into anyone’s notes.

Then somebody opens Copilot and asks: “Summarize this meeting.” Copilot produces a neat recap. Useful? Yes. But I think that is one of the least interesting ways to use Copilot in a meeting.

When I teach Microsoft Copilot, meeting recap is usually one of the first things people try because the value is immediate. Nobody particularly enjoys taking notes while also trying to participate in a meeting. The problem comes when recap becomes the entire workflow. You finish a meeting with a nice summary, then still have to figure out: what did we decide? What did we not decide? Who committed to what? Which deadlines were real commitments versus dates someone casually mentioned? Where were we disagreeing without saying we disagreed? What information was missing? And what needs to happen before everyone gets dragged into another meeting about the same thing?

That is where I think Copilot becomes much more useful. The transcript is not only something to summarize.

So instead of giving you thirty clever meeting prompts, I would save seven. They cover the questions I find myself wanting before, during and after a meeting. And each prompt has a job.

Before we get to the prompts, check one setting

This is the boring part that can ruin the whole workflow if nobody checks it.

Copilot in Teams can work during a meeting without a saved transcript under some meeting settings. But if you want to ask Copilot questions about what happened after the meeting ends, Microsoft says live transcription needs to have been turned on.^[1] Copilot’s post-meeting answers then draw from the transcript and meeting chat.

So if you regularly finish a meeting and think “I’ll ask Copilot about that afterward,” make sure transcription is part of the meeting setup.

Recording and transcription are also not the same thing. You do not necessarily need a recording just to have a post-meeting transcript available.

One more limitation catches people: Microsoft’s current documentation says Copilot will not work inside meetings hosted outside your organization.^[1] If a customer or vendor owns the external Teams meeting, do not plan your Copilot workflow around having full meeting Copilot available there.

A quick check before trusting any of the seven prompts below on a meeting that actually matters:

• Confirm live transcription was on if you’ll need a post-meeting prompt, not just Copilot active during the call
• Join on time, or within five minutes, if the catch-up notification matters to you specifically
• Remember external meetings are excluded entirely, so don’t plan a client call around any of this

I would check those things before an important meeting rather than learning about them afterward.

Think of Copilot as three different meeting assistants

This is the mental model I use.

Before the meeting, Copilot helps me arrive prepared. During the meeting, Copilot helps me understand and steer the conversation. After the meeting, Copilot helps me turn conversation into decisions, commitments and follow-through.

That is much more useful than thinking: meeting ends, generate summary.

Prompt 1: Prepare me for the meeting, not just the agenda

This is the one I would use before a recurring project meeting or internal decision meeting.

You can use Copilot in the meeting chat before the meeting begins. What Copilot can pull from will depend on the information available in that chat and your Microsoft 365 environment, so I would not assume Copilot knows something simply because the information exists somewhere in the company.

The usual prompt is “prepare me for this meeting.” That tends to produce broad background. I want something much more decision-focused.

Use this instead

That last sentence matters. Meeting preparation gets dangerous when AI quietly turns an inference into a fact. If Copilot says “the team plans to launch on October 15,” I want to know whether someone committed to October 15 or whether Copilot inferred that date from surrounding discussion. Those are not the same thing.

When I would use this

Recurring project meetings, leadership meetings, steering committees and decision meetings where the problem is not remembering the agenda. The problem is remembering the history sitting underneath the agenda.

Prompt 2: I joined late. Tell me what I need to contribute now.

Microsoft already helps here. If you join more than five minutes after a meeting starts and Copilot is active, Teams can proactively offer to catch you up.^[1]

That catch-up is useful. But sometimes I do not need a general summary. I need to know: what conversation am I walking into? So I would follow with something like this.

Use this

The difference is subtle but useful. “Summarize what I missed” gives me history. “Tell me what I need to contribute now” gives me situational awareness. That is usually what I need when I arrive twelve minutes late and everyone else is already halfway through an argument.

Prompt 3: We have ten minutes left. What still needs to be resolved?

This might be my favourite prompt in this guide. Not because the prompt itself is sophisticated. Because the timing changes the meeting.

Most teams use Copilot after the conversation. Try using Copilot before the conversation ends. Picture a 60-minute meeting. At minute 50, ask this.

Now you can use the remaining ten minutes to close the gaps. This is a much better use of AI than producing a beautiful summary of an incomplete meeting afterward. I think this is one of the most useful shifts teams can make with meeting AI:

Microsoft is moving further in this direction with its Facilitator agent. Facilitator can generate live notes, track decisions and open questions, work from the meeting agenda and help teams monitor agenda progress during the conversation.^[4] If your organization has Facilitator available, use those capabilities too.

The prompt above remains useful because you are asking a more specific closing question: what are we about to walk away without resolving?

Prompt 4: Turn the meeting into a decision and action brief

Now the meeting is over. This is where I would replace “summarize this meeting” with a much better default prompt.

Use this

That final sentence is one of my favourite recap tests. I do not want a transcript compressed into six paragraphs. I want to know: what changed because we had this meeting? Did we decide something? Did someone take ownership? Did a risk emerge? Did something become blocked? Did an open question move closer to resolution? If the answer is no, maybe the meeting itself needs work.

The owner trap

Pay particular attention to this line: “List the action, owner and deadline only when those were explicitly agreed.”

AI-generated action items can sound much firmer than the conversation was. Imagine Sarah said “I can check with Legal.” That may mean Sarah agreed to own the action. Or Sarah may have been offering one possible next step while the group continued talking. Before circulating the recap, someone who attended should verify consequential owners, dates and decisions.

Microsoft makes the same broader point in its meeting documentation: AI-generated meeting content can be incomplete or inaccurate and should be checked.^[1]

Prompt 5: What did I commit to?

This one is selfish. I mean that positively.

After a busy meeting, I often care less about every detail of the recap than I care about: what am I now on the hook for? So ask directly.

Use this

That last instruction is doing a lot of work. There is a meaningful difference between “Sana will send the revised proposal by Friday” and “Sana may want to update the proposal.” Both might lead Copilot to associate your name with the proposal. Only one is a commitment.

This prompt is especially useful when your day contains six meetings and, by 4 p.m., you can no longer remember whether you promised to send something or merely thought about sending something.

Prompt 6: Where are we talking past each other?

Microsoft itself suggests asking Copilot questions such as “Where do we disagree on this topic?” during Teams meetings.^[1] I would take that idea one step further.

Because disagreement in meetings rarely arrives neatly labelled: “Hello everyone, I disagree with Priya for the following three reasons.” More often two people keep talking around each other. One person is arguing about cost. Another is arguing about speed. One is discussing what customers want now. Another is protecting what the product needs to become next year. Everyone sounds like they disagree because they are answering different questions.

Use this

That is more useful than “Person A disagrees with Person B.” Now Copilot is helping you identify the shape of the disagreement. Is this an evidence problem? A priority problem? A risk problem? A timing problem? Once the team knows that, the next conversation can be much more productive.

Be careful before forwarding this one

I would not automatically send a disagreement analysis to the whole participant list. Tone matters. A useful private analysis can become inflammatory when redistributed. Read the output yourself first. Make sure Copilot did not exaggerate a mild concern into a major conflict, and decide whether naming individual positions helps resolve the issue or merely raises the temperature.

Prompt 7: Make the next meeting unnecessary, or at least shorter

This is the prompt I would use after recurring project meetings.

Most meeting recaps tell you what happened. I also want to know whether we set ourselves up to make progress between meetings.

Use this

This gets at one of my biggest frustrations with meetings. A meeting produces a recap. The recap produces a list. Then everyone returns the following week and spends the first twenty minutes rediscovering what the list meant. Your AI meeting workflow should help reduce that.

The goal is not: have AI summarize more meetings. A better goal is: make each meeting create enough clarity that the next meeting starts further ahead.

The seven prompts at a glance

If you run the same meeting every week, stop copying the same prompt

This is a newer Teams feature that I think makes this guide much more useful.

Microsoft now lets eligible users create custom recap-summary templates. You can describe the format you want or paste an example of a recap you like. Teams can save that format and apply the same template to future meetings in a recurring series.^[3]

That means if every Monday status meeting needs the same structure, decisions, actions, risks, open questions, next meeting, you do not need to paste your recap prompt every Monday forever. Turn the format into a saved recap template.

The custom recap instruction I would use

Then save that as the recap format for the series. That is when a good prompt becomes part of the operating system rather than a trick somebody has to remember.

You may not need a prompt for everything anymore

This is another important update.

Teams now includes several recap experiences that can make manual prompting unnecessary for basic catch-up. Standard meeting recap can bring together recordings, transcripts, files, notes and follow-up tasks. Intelligent recap adds AI-generated summaries and other features for users with the relevant Microsoft Copilot or Teams Premium licence.^[2]

Microsoft also now offers a Meeting Recaps app. With eligible Copilot access, Teams can create video recaps and podcast-style audio recaps. Audio recap can combine up to eight selected meetings, which is useful if your problem is less “what happened in this meeting?” and more “what happened across my week?”^[5]

So I would not use custom prompts merely to recreate a feature Teams already gives you. Use the built-in recap to catch up. Use a prompt when you need to interrogate the meeting for a specific business question. That distinction saves time.

A prompt is only as good as the transcript underneath it

This deserves more attention than a small disclaimer.

Copilot is reasoning over the information available from the meeting. If the transcript attributes the wrong sentence to the wrong person, your action list may inherit the same error. If several people talk over one another, nuance may disappear. If somebody says “I’m not saying we should delay” and the transcription misses the word not, that is not a minor error.

So think of Copilot’s meeting output as a first-pass interpretation of the meeting record, not as unquestionable minutes. For a low-stakes internal catch-up, a quick scan may be enough. For something that will become an official decision record, client follow-up, performance issue, legal record or major commitment, raise the review standard.

Microsoft explicitly warns that AI-generated recap content can be inaccurate, incomplete or inappropriate.^[1]

What Copilot does versus what the human still owns

I would make this split explicit.

The distinction sounds small until an incorrect recap travels. Once somebody forwards “Finance agreed to approve the budget by Friday,” the correction often gets less attention than the original sentence. That is why I care more about decision accuracy than recap elegance.

What I would stop doing

I would stop asking “summarize this meeting” as the default. Not because the prompt is bad. Because Teams already does a respectable amount of summarization.

I would spend my custom prompts on questions where my judgment starts after the summary: what changed? What remains unresolved? What did I promise? Where are we stuck? What assumption is driving the disagreement? What information do we need? What should happen before we meet again? Those questions move the work forward.

How I would build this into a team habit

Do not send seven prompts to five hundred employees and call that adoption. Nobody needs another prompt PDF sitting in SharePoint.

Pick one recurring meeting. Preferably a meeting where poor follow-through has created friction before. For the next month, change one thing.

• If the problem is unclear actions, use the decision-and-action brief.
• If meetings run out of time without closing decisions, use the ten-minutes-left prompt.
• If the group keeps circling the same argument, use the disagreement prompt.
• If everybody returns the following week unprepared, use the next-step-readiness prompt.

Then see what changes. Does the meeting end with clearer ownership? Do fewer follow-up clarification messages get sent? Does the next meeting spend less time reconstructing the previous one? Does the team need fewer meetings?

That is the outcome I would measure. Not: how many Copilot prompts did everyone use.

The meeting workflow I would teach

If I were teaching a team tomorrow, I would boil the whole guide down to this.

Before

Ask Copilot to help you understand the decisions, commitments and questions sitting underneath the agenda.

During

Use Copilot as a second set of ears. Ask where the discussion stands, what remains unresolved and what the group needs to close before time runs out.

After

Do not ask only what was said. Ask what changed. Capture explicit decisions. Verify ownership. Identify unresolved questions. Separate fact from interpretation. Then decide what can happen asynchronously before another meeting goes on the calendar.

Hina Mian, Co-Founder of Future Factors AI

Hina is a marketing strategist with over a decade of hands-on campaign experience across B2B and consumer brands. She writes about using AI to run leaner, sharper marketing without losing the human touch. Future Factors helps professionals and teams build practical AI capability through role-based training, workflow design, and hands-on adoption.

More about Hina →