Skip to main content

​
Overview

The bridge call is where incidents actually get solved, and the first place that context is lost. Meeting Scribe joins the bridge automatically and preserves the call as a live, searchable, speaker-labeled record attached to the incident. Late responders catch up from the live transcript instead of interrupting the call. Transcripts flow straight into AI Summaries and retrospectives. Supported platforms: Zoom, Google Meet, Microsoft Teams, Webex, and GoToMeeting.

​
What You Get

During the call, the scribe joins as Rootly Scribe in the participant list, announces itself, then provides:
  • Live transcription, streamed back to Rootly in real time with speaker identification
  • Audio recording, and video where the platform supports it
  • Slack notifications in the incident channel when recording starts and when the transcript is ready
  • Live context for catchup, so /rootly catchup already knows what the bridge discussed
After the call, the incident’s Scribe tab holds the full speaker-labeled transcript, a Rootly AI meeting summary of the key points and decisions, and the optional video recording. Every transcript is PII-redacted before storage across 36 categories, from credentials to personal identifiers. See Data Privacy for AI Summaries & Meeting Scribe for the full list.
The incident Scribe tab with the Rootly AI meeting summary and the speaker-labeled transcript

​
Setup

Meeting Scribe rides on your existing meeting-platform integration: connect the platform, then enable the scribe toggle.
Prefer the Rootly-generated meeting URL. When an incident starts, Rootly creates the meeting room and pins the link in the incident’s Slack channel; the scribe is created automatically for that meeting. You can also attach a different meeting URL to the incident and the scribe will target it, but the Rootly-generated link works with zero extra steps.
1

Install the Zoom integration

Follow Zoom → Installation to connect your Zoom account via OAuth.
2

Enable transcript and summary

Go to Integrations → Zoom, then toggle on Meeting transcript and summary.
3

Turn on Auto-join bot (recommended)

In the same settings pane, enable Auto-join bot. The scribe then joins without waiting for a host to admit it, so it never sits in a waiting room while the call starts without it.
Zoom-specific issues live at Zoom Meeting Scribe Troubleshooting.

​
Limits and Scribe Behavior

​
Recording Sessions

Sessions appear chronologically in the Scribe tab, each with its own transcript, summary, and optional video.
  • Pause and resume mid-call without ending the session. Resuming picks up in the same session.
  • Reinvite the scribe if it leaves or is removed, either from the Scribe tab or by mentioning @Rootly in the incident channel and asking it to re-add the meeting scribe. Reinviting starts a new session and preserves everything already captured.
The @Rootly route needs Rootly AI in Slack enabled for your workspace, and it runs in the incident channel only. It is capped at your own Rootly permissions like every other Rootly AI action.
Rootly AI confirms the platform and the new session number in its reply, so you can see the rejoin landed and how much of that platform’s 10-session limit for this incident has been used.
A responder asks @Rootly to hop back into the bridge, and Rootly AI replies that the meeting bot was re-added to the Google Meet call as session 6 and is joining shortly

​
Multilingual Support

The scribe transcribes 20+ languages, auto-detecting the language spoken and producing the transcript in it. Your Rootly account team enables it for your workspace.

​
Privacy and Security

The short version: The full dossier, covering subprocessors, the data flow, every redaction category, and retention per storage location, lives at Data Privacy for AI Summaries & Meeting Scribe.

​
Troubleshooting

For platform-specific issues, start with the dedicated pages:

Zoom Troubleshooting

Auto-join, waiting rooms, host controls, and Zoom-specific failure modes.

Google Meet Troubleshooting

Service account setup, admin console settings, and admission failures.
Check in order: the meeting URL is attached to the incident (the pinned Rootly-generated link works out of the box; a manually added URL must be attached to the incident); Meeting transcript and summary is toggled on under Integrations → [platform]; and the scribe is being admitted. Zoom without Auto-join needs a human to admit it, and Google Meet Host management can hold it in the waiting room even with a service account.
One of the two timeouts fired. Either no one admitted the scribe within 10 minutes, or it got in and no responders joined within 5. Reinvite from the Scribe tab or by asking @Rootly in the incident channel, and enable Zoom Auto-join to prevent the first case.
Post-meeting processing takes a few minutes. Check the Scribe tab and refresh. Past 10 minutes with nothing, confirm the scribe actually recorded: there should be a Recording started event in the incident timeline.
The incident is probably carrying a personal meeting room or a manually generated link. The scribe is scoped to the meeting attached to the incident. Start a fresh meeting from the incident’s Slack channel and reinvite the scribe.
Your team exceeded its monthly recording cap. Ask your Rootly admin to review usage or raise the limit.

Data Privacy for AI Summaries & Meeting Scribe

Subprocessors, redaction categories, and retention.

AI Summaries

Where transcripts turn into summaries and catchups.

AI in Retrospectives

Bridge transcripts as retrospective source material.