What Meetings Can Do

Meetings is the part of Sarudo that turns a recording into a structured outcome. You send your AI employee an audio or video file (or a link to one), and it comes back with a time-stamped transcript, a short summary, a list of action items with assignees and deadlines where it can infer them, a list of decisions the group made, and a list of attendees linked into your CRM. From there you can triage the action items — mark them in-progress or done, add notes, and move on. Everything runs on your dedicated server, so the recording itself never leaves your infrastructure.

Voice Calls is about phone conversations that Sarudo places on your behalf in real time — outbound calls through Twilio with a Vapi-powered AI voice. Meetings is about recordings that already exist — a Zoom call you recorded, a Google Meet you saved, a Microsoft Teams export, a YouTube video, an MP3 someone sent you. The Voice Calls pipeline generates the recording; the Meetings pipeline consumes one. If your AI employee made a phone call for you, the transcript already lives in the call record (see Voice Calls > How Transcription Works). You only need the Meetings category for recordings that came from somewhere else.

Every meeting you process yields six outputs. A full time-stamped transcript with speaker labels (Speaker 1, Speaker 2, up to eight speakers — heuristic-based, not biometric). A short summary of the discussion. A list of action items, each with the assignee and deadline when those are inferable from the text. A list of decisions the group explicitly made. A list of key topics ranked by how often they were discussed. And if you provided CRM contact IDs for the attendees, every contact gets a logged meeting activity so the meeting shows up in their CRM history.