Use case · Microsoft Teams + Planner
AI meeting notes that file action items in Teams
OMNA-01 listens for the Teams meeting to end, writes the recap, extracts action items, files them as Planner tasks, and pings the owners — the chain that Otter and Fireflies stop short of.
The problem
Meeting transcripts get captured. Then nothing happens. The action items live in someone's notebook or a Slack message that scrolls away. Owners never get pinged. The next meeting starts with the same items unaddressed. The notes are not the problem; the chain after the notes is the problem.
Who this is for
Engineering, product, and operations leaders running recurring team meetings in Microsoft Teams. Especially useful for teams that already use Planner or Microsoft To Do for task tracking and want the gap between recap and action closed.
What it does weekly
- · Reads the Teams meeting transcript as soon as the meeting ends
- · Writes a one-page recap with decisions, open questions, and a list of action items with owners
- · Files each action item as a Planner task in the team's bucket, dated and assigned
- · Pings the owner with a short Teams DM linking the task to the source quote
- · Posts the recap in the meeting's channel so the people who missed get caught up
- · Tracks which action items get done and surfaces stale ones at the next meeting
First useful output
A one-page recap in the channel and a Planner board with this week's action items assigned and dated.
Time to first output
Same day
How it works
| Trigger | Action | Outcome |
|---|---|---|
| Teams meeting ends with a transcript recorded | OMNA-01 reads the transcript, writes a recap with decisions, open questions, and action items | Recap posted in the channel within a few minutes; everyone who missed catches up in two scrolls |
| Action items extracted from the transcript | OMNA-01 files each one as a Planner task in the team's bucket with a owner and a date | Owner gets a Teams DM linking the task to the source quote in the recap |
| Action item still open at the next meeting | OMNA-01 surfaces it in the pre-meeting brief with the owner's last activity timestamp | Lead facilitates from facts: who is blocked, who needs scope reduced, what got dropped |
| Action item gets done in Planner | OMNA-01 closes the loop in the original meeting thread with a brief confirmation | The team sees the rhythm: meeting decision → task → done — captured in one searchable thread |
What gets wired
Wire Teams channels and chats
How the agent listens for @-mentions, posts threaded replies, and uses adaptive cards. Base wiring every other use case depends on.
Wire Planner and Microsoft To Do
How the agent files action items into Planner buckets and personal To Do lists after meetings, threads, and customer escalations.
Recommended agent
OMNA-01
AI Operations Orchestrator
Multi-agent ops coordinator for teams running 3+ agents
What it costs
OMNA-01 costs a small fraction of what a mid-market operations associate or chief-of-staff costs. We don't price the agent against a salary; we price it against the part of the role that scales — the recap, the task filing, the owner pings, the stale-item tracking.
A full-time operations associate runs roughly $8–12K/month fully loaded, and that money buys things OMNA can't replace: the judgment to spot the unspoken disagreement in a meeting, the political read on which action items are real and which are theater. OMNA does the part that scales. See the math on /pricing.
Edges of this connection
OMNA-01 in Teams currently does not:
- Replace the meeting facilitator's judgment. The agent extracts action items from the transcript; humans decide which ones are real.
- Read meetings the host has not enabled transcription for. If transcription is off, the agent has nothing to summarize.
- Edit Planner tasks the agent did not create. Human-created tasks stay under their owner's control.
Where to next
- → Back to Microsoft Teams — the full cluster
- → See the Roster — agents you can hire
- → All integrations