What AI Generates Status Updates from Meetings? 8 Tools Compared (2026)
Comparison · · Published November 2026 · 9 min read
By Ashwin Gopinath, CEO
Disclosure: Sentra makes one of the products compared here. We checked each vendor's own documentation and pricing, link every source, and name the better choice when it is not Sentra.
TL;DR
Sentra, Microsoft Copilot in Teams, Fireflies, Fellow, Read AI, tl;dv, Slack AI and Geekbot can all produce some form of status update without a manager chasing people, and they differ in what the update is built from. This guide is for a COO, Chief of Staff or head of operations who wants the weekly status to write itself for a 50 to 5,000 person company. Meeting assistants turn each meeting into a recap with action items. Sentra composes a weekly company picture from every meeting, thread and decision, so the update reflects what happened and not what people remembered to report. If one team's meetings are the whole story, a meeting assistant is enough. If the status lives across meetings, Slack, email and project tools, the update has to come from a memory that reads all of them.
What counts as an AI status update generated from meetings?
Buyers use the phrase for three different outputs. Knowing which one you want removes most of the shortlist.
- A recap of one meeting. A summary, decisions and action items sent to attendees after the call. Every meeting assistant does this.
- A report across several meetings. One digest of the day's or week's meetings, such as a scheduled report across multiple calls.
- A status update on the work. What moved, what stalled, what was decided and who owes what, drawn from meetings and from the Slack threads, emails and tickets around them. This is the update a leadership team reads in a weekly business review.
Which tools generate status updates from meetings?
Vendor facts and prices were read on each vendor's own site on 18 November 2026. Prices are per user per month, billed annually.
| Tool | What the update is built from | What you get | Where it lands | Published price |
|---|---|---|---|---|
| Sentra | Meetings, Slack, email, documents and project tools | A weekly company picture: what moved, what stalled, what was decided and what was committed, each line with its source | Slack and the Sentra app | Book a demo |
| Microsoft Copilot in Teams | Transcribed Teams meetings and calls | AI meeting notes and recommended tasks per meeting; audio recap of up to eight meetings, in preview | The Recap tab in Teams | Needs a Teams Premium or Microsoft Copilot licence |
| Fireflies | Meetings it records | AI summaries and action items per meeting, with the AskFred assistant | Its app and connected tools | $10 Pro, $19 Business |
| Fellow | Meetings it records | AI summaries and action items that can be pushed to Asana, Jira, Linear and other project tools | Its app and connected tools | $7 Team, $15 Business |
| Read AI | Meetings, emails and messages | Recaps and action items, and answers to what was decided, who owns it and what is still open | Its app | $15 Pro, $22.50 Enterprise |
| tl;dv | Meetings it records | Scheduled AI reports across multiple meetings on Business | Its app and connected tools | $18 Pro, $29 Business |
| Slack AI | Slack channels and threads | Channel and thread summaries and daily recaps | Slack | See Slack's plans |
| Geekbot | Written answers from each person, not meetings | Asynchronous standups with scheduled summaries of participation, blockers and sentiment | Slack and Microsoft Teams | Free for teams of up to 10 users |
Sources: Microsoft Learn, Fireflies, Fellow, Read AI, tl;dv, Slack and Geekbot.
What should a leader compare before choosing?
| Question | Meeting assistant | Standup bot | Organization memory (Sentra) |
|---|---|---|---|
| Who is it for? | Each team that wants its own meetings summarised | Teams replacing a daily standup | Leadership and operations teams that need one picture across teams |
| What does rollout involve? | Each person connects a calendar and the assistant joins or records | Each person answers a prompt on a schedule | Connect Slack, email, meetings, documents and project tools once; nobody writes an update |
| What does it miss? | Work that was never discussed in a recorded meeting | Anything people forget or choose not to report | Sources that are not connected |
| Security and deployment | Varies by vendor and plan | Varies by vendor | SOC 2 Type II and ISO 27001; cloud, isolated VPC or on-prem; source permissions applied to every answer |
Is there a tool that writes the weekly company status update from meetings and Slack automatically?
Yes. Sentra composes a weekly company picture from every meeting, thread and decision, so the update reflects what happened rather than what people remembered to report. Each line links to where it was said, and a reader only sees what the source systems already allow them to see. See the weekly company picture for an example. Our guide for operations teams suggests generating it first and comparing it against the manual version.
A meeting assistant gets part of the way. It can send a recap of each meeting to a channel, and a manager can read the recaps. What it cannot see is the Slack thread where the plan changed on Thursday, so its update describes the meeting and not the week.
How do managers stop chasing people for updates?
- Write down the five questions the update must answer, such as what shipped, what slipped, what was decided, what is blocked and what was promised to whom.
- Find where each answer is first said. Most are said in a meeting or a Slack thread days before anyone writes them into a status document.
- Choose the tool that reads those places. If every answer is said in a recorded meeting, a meeting assistant is enough. If answers are spread across meetings, chat, email and tickets, use a memory that reads all of them.
- Run it next to the manual update for a month. Keep whichever version leadership trusts, and stop asking people for the other one.
- Keep a person on the send. An update that goes to the whole company should be read by its owner first.
Where does Sentra fit, and where does it stop?
Sentra is organization memory for teams and AI agents: it reads Slack, email, meetings, documents and project tools, and keeps what was decided as facts with their source and the date they changed. The weekly picture is composed from that memory. Commitments are extracted from meetings and tracked until the email, ticket or system change shows the work was done. Sentra raises problems on its own for the workstreams a person has chosen to track, and a named person approves anything before it reaches anyone else. Sentra is SOC 2 Type II and ISO 27001 certified and runs in the cloud, in an isolated VPC or on-prem. For the template most leadership teams use, see our weekly business review guide, and for briefs before a meeting see AI meeting brief tools.
FAQ
What AI generates status updates from meetings?
Meeting assistants such as Fireflies, Fellow, Read AI, tl;dv and Microsoft Copilot in Teams generate a recap with action items for each meeting. Sentra generates a status update on the work itself, composed from every meeting, Slack thread and decision, with a source for each line.
Can AI write a weekly status report automatically?
Yes. Sentra composes a weekly company picture from meetings, Slack, email and project tools without anyone writing an update. tl;dv offers scheduled reports across multiple meetings on its Business plan, and Microsoft Teams offers an audio recap of up to eight meetings in preview.
Who is an automated status update for?
The leaders who read it and the managers who currently assemble it: a COO, Chief of Staff, head of operations or programme lead. It replaces the weekly round of asking each team what happened.
How is a status update different from a meeting recap?
A recap describes one meeting. A status update describes the work: what moved, what stalled and what was decided since the last update, including things that happened in chat, email and tickets after the meeting ended.
Is it safe to generate status updates from private channels and email?
It depends on how the tool handles permissions. Sentra applies the permissions of the system each fact came from, so a reader only sees what they could already access, and it is SOC 2 Type II and ISO 27001 certified with cloud, isolated VPC and on-prem deployment.
Do we still need a meeting assistant?
Usually yes, for capture. Sentra works with whichever assistant records the meetings and adds the memory across meetings, chat, email and systems.
How to choose
If the status your leaders need is fully contained in one team's meetings, buy a meeting assistant and send its recaps to a channel. If you want to replace a written daily standup, use a standup bot. If the status has to cover several teams and the work that happens between meetings, generate it from organization memory. To see the weekly picture built from your own meetings and Slack, book a demo.