Sistava

Meeting Summary

When a meeting your employee attended ends, it writes a summary and drops it in chat automatically: what got decided, who owns what, and the action items. No need to ask for a recap, it is already waiting when you check in.

After every meeting an AI employee attends, a structured summary is generated automatically: the decisions that were made, the action items that were assigned, and who was in the room. It is ready moments after the call ends.

A transcript tells you everything that was said. The summary tells you what mattered. It is built from the actual transcript, so decisions are stated plainly, owners are attached to action items, and the noise of small talk and tangents is filtered out.

The difference from a note-taking app is that the summary lands on the same private thread you already chat with the employee on, not a separate notes tool. It writes the recap into its own memory too, so asking "what did we decide on the launch date" three weeks later still works, the same way it would with a colleague who was actually in the room.

What Should a Meeting Summary Actually Contain?

Most meeting notes fail because they transcribe activity instead of extracting outcomes. The automatic summary is organized around the three things people actually look for afterward: what was decided, what was assigned, and who was there.

Each summary keeps the link back to its source. If a decision looks surprising, the full transcript is right there in Drive, so trust never depends on the summary alone.

When It Fires, and When It Does Not

The summary is not on a timer. It fires the moment the call provider reports the transcript is finished processing after everyone hangs up, and it fires exactly once per meeting, a dedup guard skips any retried webhook so you never get the same recap twice.

A genuinely silent meeting, nobody spoke, produces no summary at all. The employee does not spend a turn writing up silence. If the call drops the employee's connection mid-meeting, there is no automatic reconnect, so the summary covers only what was captured up to that point, a partial recap rather than a failure.

From Forty Minutes to Two

The summary turns meeting attendance from mandatory to optional for anyone who only needs the outcome. Skip the call, read the summary, and you know what changed and what is expected of you.

Across a week of standups, reviews, and client calls, that compounds into hours returned to every person on the team, while the level of shared awareness goes up rather than down.

Action Items That Become Action

An action item trapped in a notes doc is a wish. Because the summary is produced by an AI employee inside your workspace, assigned work can move onto the task board on request, ask it to "create tasks from the action items" and they land on the kanban board, with the employee itself picking up anything delegated to it.

It does not push items to the board on its own the moment the summary is written. That step stays a request, so the board only fills with tasks you actually meant to track.

Meeting Summary vs. the Live Transcript vs. Meeting Notes

Meeting Summary and the live transcript are two different outputs of the same call: the transcript is the verbatim, speaker-tagged record saved to Drive under /documents/meetings/, the summary is the curated read of that record, decisions, action items, attendees, with the small talk stripped out.

Meeting Notes is a separate, on-demand skill for a call the employee was never on, hand it a recording or rough notes after the fact and it produces the same kind of write-up. Because that version is often meant to go out to people beyond you, it stops and waits for your go-ahead before naming anyone's action items or deadlines. The automatic summary skips that gate, it stays inside your own private chat with the employee, nobody else sees it unless you share it.

How It Works

From transcript to decisions, action items, and attendees, automatically.

When a meeting ends, the employee processes the full transcript and produces a structured summary: the decisions made, the action items with owners, and who attended. It lands in Drive next to the transcript moments after the call.

Because the summary is produced by a working agent rather than a note-taking app, it connects to action: items delegated to the employee go onto its board, and the summary becomes part of team knowledge that any teammate or employee can query later.

Use Cases

Executives skim a week of meetings in minutes

Five summaries replace five hours of recordings when catching up after travel.

Teams stop re-litigating decisions

What was decided is written, dated, and linked to the transcript that proves it.

Project leads track commitments

Action items with owners are extracted automatically, so nothing depends on memory.

Skipped meetings stop being information gaps

Anyone who misses a call reads the outcome in two minutes.

Comparison

BeforeAfter
Outcomes depend on someone writing good notes.Every meeting yields the same structured summary.
Action items scatter across notes and chat.Items are extracted with owners and become tasks.
Catching up means watching a recording.Catching up is a two-minute read.
Summaries live in a separate notes app.Summaries live with your workforce and feed its memory.

FAQ

What does the AI include in a meeting summary?

Decisions made, action items with their owners, and the attendee list, extracted from the full transcript of the meeting.

How soon after the meeting is the summary ready?

Moments after the meeting ends, once the platform finishes processing the transcript. The summary is generated automatically with no manual step, and only once per meeting.

What happens if nobody spoke, or the employee got disconnected mid-call?

A silent meeting produces no summary at all, there is nothing to write up. A dropped connection produces a partial summary covering only what was captured before the disconnect, there is no automatic reconnect.

Can action items from the summary become tasks?

Yes, on request. Ask the employee to create tasks from the action items and they land on the kanban board; it does not file them there automatically the moment the summary is written.

Where are meeting summaries stored?

The recap is written into the employee's own memory on your private chat thread, so it can answer questions about the meeting later. The full transcript it was built from lives separately in the employee's Drive, under /documents/meetings/.

How is this different from asking for meeting notes on a call the employee did not attend?

Meeting Summary only covers calls the employee actually joined, and it is automatic and private to your own chat. The separate Meeting Notes skill can turn a recording or rough notes from any call into the same kind of write-up, but because that version is usually meant to circulate, it holds for your sign-off before it names anyone's action items or deadlines.

Where Meeting Summary fits

Meeting Summary is part of Things they can do out of the box.

Every AI employee ships with built-in abilities that work out of the box. Search the live web for real-time information, scrape and crawl any website for structured data, and generate images directly in conversation. No plugins to install, no APIs to configure.

Read the guide

More in Capabilities

Explore