Recording a meeting

Reverbic does not send a bot to join your calls. You capture audio from a device you already control, which means it works on any platform — Zoom, Meet, Teams, Slack Huddles, or a conversation in a room.

Browser

Meetings → Record captures from your microphone. Good for in-person conversations and for calls where you are comfortable capturing your own mic only. You can switch microphones mid-recording, and a persistent recording bar lets you move around the app without stopping.

Desktop app

The desktop app captures system audio on macOS and Windows, so you get everyone on the call rather than just your own microphone. This is the recommended route for remote meetings.

iPhone and Apple Watch

The mobile app records from your phone, and the watch app can start and stop a recording from your wrist. Recordings transfer to your phone and upload when the app has connectivity.

Slack Huddles

With the desktop app running and Slack connected, you can start a Huddle recording with a slash command. The summary is posted back to the channel when processing completes. See the Slack integration doc for setup.

If a recording is interrupted

Audio is written continuously while you record, so a crash, a closed tab, or an accidental navigation does not lose the recording. When you return, Reverbic offers to recover it. The raw file uploads even if later processing fails, so the audio is never stranded on your machine.

What happens after you stop

1. 01The file is analyzed and split into chunks small enough to transcribe reliably.
2. 02Each chunk is transcribed, primed with vocabulary from the meeting's Context Pack.
3. 03The transcript is summarized into a title, summary, key points, action items, and decisions.

Long meetings are chunked at fifteen-minute boundaries and transient failures are retried automatically. If you close the tab mid-run, a recovery job picks the pipeline back up.

Something unclear or missing? Tell us and we'll fix the page.