Microsoft Teams Copilot for meetings: what it does and doesn't do

What Teams Copilot actually is

Teams Copilot is a meeting assistant that works off the live transcript. It is part of Microsoft 365 Copilot, so it sits inside the same surface where your team already does email, docs, and chat. During a call you can open the Copilot side panel and ask it questions; after the call it produces a recap.

That framing matters because everything Copilot can do flows from one fact: it reads the transcript. It is very good at turning spoken words into structured text. It is not built to bring new information into the room. Once you internalize that, the strengths and the limits both make sense.

What it does well

Teams Copilot is genuinely useful for three jobs, and it is worth being clear-eyed about them.

Catch-up summaries

If you join a meeting fifteen minutes late, Copilot will tell you what you missed. This is the feature people love most, because it removes the awkward "can someone catch me up" tax. It reads the transcript so far and gives you the gist, the decisions made, and the open questions. For back-to-back schedules, that alone earns its keep.

Recaps and action items

After the call, Copilot generates a recap: a summary, a list of notes, and suggested action items pulled from what people said they would do. The quality depends on how clearly people spoke their commitments out loud. When someone says "I'll send the deck by Friday," Copilot usually catches it. When the commitment was implied, it often misses.

Follow-up drafting

You can ask Copilot to draft the recap email, rewrite a summary for an executive audience, or pull every quote where a specific person spoke. Because it lives inside Outlook and Teams, that draft lands one click from sending. For teams already deep in Microsoft 365, the integration is the real value.

Where it stops

Teams Copilot answers questions about the meeting. It does not answer the questions the meeting raised. That one distinction explains almost every limit.

Here is what that looks like in practice.

It can't research live

When your team hits a question mid-call, the sales lead asks for a competitor's pricing, the PM wants last sprint's velocity, the founder needs the Q3 retention cohort, Copilot stays quiet. It only knows what is in the transcript. The answer sits in a doc, a dashboard, or a website that Copilot will not reach into during the conversation. So the team does what it always did: someone writes it down to "look up later," and the momentum leaks away.

It waits to be asked

Copilot is a prompt tool wearing a meeting badge. You open the panel, you type a question, you read the answer. Nobody talks to a teammate that way. A real participant notices the gap and fills it without being addressed. Copilot needs an explicit prompt for every output, which means in a fast meeting it mostly goes untouched until the recap fires automatically at the end.

It stays inside Microsoft

If your stack is Outlook, Teams, Word, and SharePoint, the integration is seamless. The moment your decisions need to land in Linear, your notes in Notion, or a heads-up in a non-Teams Slack workspace, you are back to copy and paste. Plenty of teams run Microsoft for calls and something else for work tracking, and that seam is exactly where Copilot's reach ends.

The transcript ceiling

Every transcript-based meeting tool shares the same ceiling, and Copilot is no exception. A transcript is a record of what was said. It is not a record of what the meeting needed.

Think about a typical product review. The team debates a feature, someone references a competitor, someone else half-remembers a metric, and a decision gets made on incomplete information because pulling the real numbers would have stalled the call. The transcript captures all of that faithfully, including the wrong assumptions. A recap built on it inherits the gaps.

The fix is not a better recap. It is a participant that closes the gaps while they are still open. That is a different category of tool, and it is worth naming the difference clearly before you decide what your team actually needs.

Recap tool vs live teammate

The cleanest way to think about meeting AI is on a single axis: does it work after the conversation, or during it?

After: the recap tool

Teams Copilot, Zoom AI Companion, Otter, and most notetakers live here. They watch quietly, then hand you a clean artifact when the call ends. The value is documentation and follow-up speed. The limit is that the meeting that needed help already happened.

During: the live teammate

A live teammate joins the call, listens for the moment the room needs something, and acts in real time. It pulls the competitor's pricing while the sales lead is still talking. It logs the decision the instant it is made, with the owner and the date. It drafts the follow-up before anyone asks. The value is continuity: the room never stops to look something up, and the work is done by the time the meeting ends.

Neither is wrong. They solve different problems. The mistake is assuming a recap tool will give you a teammate's behavior, then being disappointed when it waits to be prompted.

How to decide what you need

Ask your team two questions.

1. What slows our meetings down? If the answer is "writing the notes" or "remembering who agreed to what," a recap tool like Copilot fixes it. If the answer is "we keep stalling to look things up" or "decisions evaporate by the next standup," you need a live teammate.
2. Where does the work need to land? If it all lives in Microsoft 365, Copilot's integration is hard to beat. If your work tracking spans Linear, Notion, Slack, and Gmail, you want a tool that routes output across all of them, not one bound to a single stack.

Most teams discover they want both: Copilot for the polished Microsoft-native recap, and a live teammate for the in-meeting research and decision capture Copilot was never built to do.

Where relly fits

relly is the live teammate, not another recap tool. It joins your meeting over Zoom, Google Meet, or Microsoft Teams, listens for the moment the room needs something, and acts while you keep talking. It pulls the research, captures the decision with an owner and a date, and routes the follow-up to Slack, Notion, Linear, or Gmail, wherever your team actually works.

If you already lean on Teams Copilot for recaps, relly fills the half it can't reach: the live half. (See why Zoom's AI Companion runs into the same ceiling for the broader pattern.)

If you're evaluating AI for live meetings, early access gets you in before public launch, with 50% off for your first 12 months. No card needed until launch.