A senior leader has five meetings on Tuesday afternoon. Three are informational syncs. She sends a bot to those three. It captures what happened, generates a five-minute highlight reel for each, and she reviews all three in fifteen minutes.
This is no longer hypothetical. Recently, both the Klarna CEO and Zoom CEO Eric Yuan used AI avatars on their quarterly earnings calls. Yuan’s avatar, deployed via Zoom Clips, opened with: “I am proud to be among the first CEOs to use an avatar in an earnings call.” The CEO of Otter is reportedly training his own avatar to share the workload.
The productivity math is obvious. The instinct is right. But most of the conversation stops there — at whether to send the bot, not which meetings can actually survive the swap.
Two types of meetings. One type of bot.
The AI meeting tools on the market right now — Otter, Fireflies, Teams Facilitator, Fellow — are information processors. They record, compress, retrieve, and route. That’s genuinely useful. But every single one of them does only that.
None of them do coordination work. They don’t challenge an assumption mid-discussion. They don’t synthesize competing perspectives into something a group can act on. They don’t read tension in the room. They don’t force commitment. And they cannot bind their human to a decision.
That distinction is the whole ballgame.
At Growth Wise, we classify meetings into types we call Arenas. For example, a Status Sync exists to move information from the people who have it to the people who need it. No stress-testing, no mental model to align, no decision to close. For that Arena, a bot is a structural improvement — because everything that matters in a Status Sync is information, and the bot captures information well.
An earnings call where a CEO delivers prepared remarks to investors? That’s a Status Sync. The avatar is fine.
A decision forum where a cross-functional team has to commit to a roadmap date, stress-test assumptions, and actually close? That’s a different Arena entirely.
Where the bot breaks
When a bot replaces a human in a meeting that requires coordination, three things break.
First, alignment becomes fragile. The absent person receives a summary — a compression of what happened, not participation in it. The result is divergent interpretations that look like agreement until they don’t.
Second, the meeting drifts. Meetings shift Arenas mid-conversation. A Status Sync becomes a Decision Forum when someone raises a real issue. A human pivots with it. A bot continues in information-processing mode. The coordination function just goes missing.
Third, the decision doesn’t close. A bot cannot bind its human to anything. The group believes they decided; the absent person reviews a summary and quietly retains veto power. The decision reopens on Thursday.
When bots start acting, not just attending
Yuan has said Zoom aims to create digital twins of users — avatars that eventually do more than deliver scripted remarks. That next version is bots that don’t just observe meetings but act in them: approving budgets, committing to roadmap dates. When that happens, governance matters in ways the current conversation hasn’t caught up to.
The industry answer is “Governance as Code” — an immutable audit trail proving a decision was recorded. Necessary, but not sufficient. An audit trail tells you what happened. It doesn’t tell you whether the decision was structurally valid.
The Growth Wise model addresses this through Arena adherence. A bot approving a budget during a Decision Forum where that function was invited is doing legitimate work. A bot forcing a roadmap commitment during an Ideation Session — an Arena whose rules suppress convergence — is structurally invalid. Same action, different Arena, different legitimacy.
There’s a second distinction worth making: whether the bot is exercising judgment or transmitting a decision already made. “Budget approved per policy X” is enforcement, not judgment. The governance question for each is different, and conflating them produces frameworks that are either too restrictive or too permissive to be useful.
And then there’s the alignment gap. A bot can achieve action closure perfectly — log the decision, assign the owner, record the timestamp. It cannot achieve aligned closure. It cannot verify that the humans in the room understood the trade-offs. Any governance framework that doesn’t flag that distinction is measuring the wrong thing.
The question that actually needs answering
Yuan’s avatar opened an earnings call. Klarna’s CEO addressed investors through a digital proxy. These are Status Syncs — prepared remarks, one-directional, no coordination required. The bot belongs there.
Organizations that understand that distinction will delegate the right meetings, protect the right meetings, and build governance that knows the difference between an Arena-valid bot action and one that broke the coordination contract. Their decisions will stick.
Organizations that treat all meetings as interchangeable will send bots into Decision Forums and spend Thursday re-litigating what the avatar attended on Tuesday.
The question was never “should we send bots to meetings?” Yuan and Klarna already answered that. The question is which meetings are structurally safe for delegation — and when bots do act, whether they respected the Arena they were operating in.