At a glance
Dots in Microsoft Teams: Meetings, Decisions, and Follow-Ups
Use a dot in Microsoft Teams to turn meeting notes and project conversations into reviewable work: a preparation brief, a decision summary, or a follow-up draft. The strongest workflow keeps the source beside each conclusion and leaves uncertain owners, dates, and decisions visible. For the related guide, see Use Dots in Microsoft Teams.
This guide focuses on what to do after the contact method is available. For setup, account availability, and the difference between messaging and connected data, start with Use Dots in Microsoft Teams. OpenAI’s current documentation says that connected channels reach the same dot, while messages remain in their respective conversations.
Guide
Workflow 1: prepare a meeting brief from named sources
Before a meeting, tell the dot which conversation, files, or notes are in scope, what the meeting must decide, and who will review the brief. Ask for a short agenda, recent changes, conflicting information, and unanswered questions. A source that cannot be accessed should appear in a “missing source” note, not be silently replaced by a guess.
Review checkpoint: open the cited messages and files. Confirm that each “confirmed decision” was actually accepted, and that the brief does not expose information from a private conversation to a wider meeting audience.
Guide
Workflow 2: create a decision summary that separates facts from proposals
During a project, a suggestion can be repeated until it sounds final. Ask the dot to separate what the team decided from what people proposed. Make the source and date part of each row, and leave the status “unresolved” when the discussion does not show agreement.
| Topic | Confirmed decision | Proposal or open question | Evidence | Reviewer |
|---|---|---|---|---|
| Release timing | Not stated until a participant explicitly confirms it | Move the date after QA | Link to the dated message or meeting note | Project lead |
| Mobile QA | No owner recorded in the source | Assign a tester | Link to the open action or note | Team lead to confirm |
The table is a format example, not a claim about a real team decision. The task should preserve the words “not stated” or “unresolved” when that is what the evidence supports. The project lead confirms the final summary before it becomes a tracker entry or announcement.
Guide
Workflow 3: draft follow-ups with explicit ownership
After a meeting, provide the approved notes and the intended recipients. Ask for a draft grouped by action, owner, due date, dependency, and evidence. If the source mentions a person without showing that they accepted the task, write “owner to confirm.” If a deadline is absent, leave it blank or mark it “not stated.”
Compare the draft with the original notes before sharing. A polished message still needs a person to approve the recipient list, wording, commitments, and destination.
Guide
Handle missing or conflicting information
- Ask the dot to show both versions with their dates and sources when two notes disagree.
- Do not resolve a conflict by treating the newest message as approved unless the team’s process says that it is authoritative.
- Mark inaccessible files and missing transcript sections explicitly.
- Do not infer an owner from who spoke most often or a deadline from a calendar date mentioned nearby.
- Ask a named reviewer to decide when the sources do not settle the question.
These checks matter most when a summary will update a project board, change a commitment, or be sent to people who were not part of the original discussion. See the app permissions checklist when the task also uses connected data.
Questions
Frequently asked questions
Can a dot prepare a meeting agenda from Teams messages?
It can prepare a draft from the messages and files available through its permitted sources. Name the conversation and documents, ask for links, and verify that the draft reflects the intended meeting.
Can it decide which proposal the team accepted?
It can identify evidence of agreement and show the source. If the source is ambiguous, keep the item unresolved and ask the meeting owner to confirm.
Should the dot send the follow-up itself?
Start with a draft and a human review of the exact text, recipients, and channel. Expand permissions only after the team has defined an approval process for that action.
What if a Teams meeting transcript or file is missing?
Ask the dot to list the unavailable source and continue only with the material it can actually access. Supply the missing approved file or have a participant confirm the relevant fact.
Where do I find connection steps?
Use the Microsoft Teams integration guide for setup and workspace access. This article covers meeting, decision, and follow-up workflows.
For the official channel behavior and current availability, read OpenAI’s Message your dot guide. The page explains how Slack and Teams conversations work across the same dot.