Skip to content
Sarudo

What Meetings Can Do

An overview of Sarudo's meeting pipeline — transcribe recordings, extract action items and decisions, and track follow-ups.

meetingsoverviewtranscriptionaction itemsdecisionsrecordings

What This Category Covers

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.

Nothing to set up and nothing extra to pay. Transcription runs on-device on your own server — there is no external transcription service to sign up for, no per-minute transcription bill, and no audio ever sent to a third party.

How This Is Different from Voice Calls

Voice Calls is about phone conversations that Sarudo places on your behalf in real time — outbound calls through Twilio with an AI-powered 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.

Short form: Voice Calls = outbound phone conversations Sarudo makes. Meetings = pre-existing recordings you send Sarudo to process.

What You Get Back

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.

Summary of a processed meeting

What a completed meeting looks like.

You say:
What did I agree to in today's kickoff with ClientCo?
Sarudo responds:
Kickoff with ClientCo (42 min, 4 speakers). Summary: scope covers the Q3 rebuild, with shared access to the staging environment and a soft launch target of June 15. Action items: (1) You send the revised SOW by Friday — assigned to you, due 2026-04-25. (2) Mark provides Figma credentials — assigned to Mark. (3) Schedule weekly standup — no assignee, no deadline. Decisions: (1) Phase 1 will use the existing component library. (2) Analytics will ship in Phase 2, not Phase 1. Key topics: SOW revision, staging access, component library, soft launch. I logged the meeting to the ClientCo contact and two team-member contacts in your CRM.