How to Use Teams AI Facilitator

Teams AI Facilitator is a feature of Microsoft Copilot in Teams that helps structure meetings in real time: tracking the agenda, suggesting when to move to the next topic, and capturing notes and action items as the conversation unfolds. Like any AI meeting assistant, it captures what was said — not what was confirmed. Reviewing the Facilitator's output and recording the accepted decisions where your whole team can see them is the step that makes those decisions actionable. Tools like fenbs keep that confirmed record outside the meeting tool, available to every AI assistant and team member before the next session starts.

This guide covers how to prepare for a Facilitator session, how to review what it produces, and how to route the confirmed outputs into a project record that does not live inside Teams.

What Teams AI Facilitator does during a meeting

Facilitator, available as part of Copilot in Teams, tracks the meeting agenda and shows participants where they are in the discussion. It captures notes in real time and flags action items as they are mentioned. After the meeting, it produces a structured summary with the agreed items and next steps.

The Facilitator feature requires Copilot to be active in the meeting and participants to have been notified. For current setup steps and plan requirements, see Microsoft's Teams documentation directly, since features and licensing conditions change with product releases. The steps below describe the review and recording workflow that follows, whichever AI feature you use to take meeting notes.

How to prepare for a Facilitator-assisted meeting

Facilitator works better when the meeting has a clear agenda. Before the call, share the agenda with participants and load it into the Facilitator if your Teams workspace supports that. An agenda gives the AI context for when a topic is being discussed and when the conversation has moved on, which improves the quality of the notes it produces.

Also prepare the decision you need the meeting to make. If the meeting is a review, write down the possible outcomes before it starts. If the meeting is for planning, write down the open questions that need answers. That preparation helps you review the Facilitator's output quickly afterward — you know what the meeting was trying to decide, so you can check whether it actually did.

Review the Facilitator output before you record anything

The Facilitator summary shows the notes it captured and the action items it identified. Read the action items first. Check: does each one have a specific owner? Is the deadline stated or implied? Is the action something the owner actually agreed to, or something that was suggested and not accepted?

For anything that is unclear, check the meeting transcript. The Facilitator's summary is a condensed version of what the transcript records. If a commitment looks ambiguous in the summary, the transcript shows the exact words used — and whether they sounded like a firm agreement or a general direction.

Compare the decisions list against your agenda. Every agenda item should have an outcome: decided, deferred, or further discussion needed. If an agenda item does not appear in the Facilitator summary's decisions, it either was not discussed or the discussion did not reach a conclusion. Either way, record the state explicitly rather than leaving it blank. The Claude Teams integration article covers how to connect AI tools to your Teams workspace for follow-on work.

Record accepted decisions and task ownership

Once you have reviewed the Facilitator output and corrected any errors, record the accepted decisions in a project record. This means: what was decided, who will act on it, and by when. A decision without an owner tends not to happen. A task with a stated deadline gets more attention than one with a vague "soon."

Store decisions separately from tasks. A decision is something the team agreed on; a task is something one person will do as a result. Mixing them in one list makes it harder to track which decisions have been implemented and which tasks are still blocked on a person. Keep them in separate places in your project record.

How to use Teams AI Facilitator with fenbs

1. Create a free account and add a project for the work your team is meeting about. Write down the open questions the next meeting needs to answer.
2. Before the meeting, prepare a clear agenda with the decision or outcome needed from each item. Share it with participants.
3. After the meeting, review the Facilitator summary. Check each action item for a clear owner and deadline, and compare decisions to the agenda.
4. Add accepted decisions to Decisions and rules and follow-up tasks to the project board with owners and due dates.
5. Connect your AI assistants to fenbs from Integrations. The next session reads the confirmed decisions and open tasks, so the work picks up from the right place.

What Facilitator does not decide for you

Facilitator identifies what was discussed and what sounded like a commitment. It cannot tell you whether the team actually reached consensus, whether the person who volunteered for a task has the capacity to do it, or whether the decision is consistent with earlier choices the project already made. Those judgments still belong to the people in the room.

The value of recording decisions in a shared project record — beyond what Facilitator captures — is that it provides context the AI cannot read from the meeting alone: the prior decisions that constrain this one, the rules that apply to the whole project, and the team's history with similar problems. A meeting note tells you what happened today; a project record tells you how today fits into everything that came before.