.svg)
Rootly Scribe joins your incident call on its own when the incident gets started, but sometimes after that initial call, your team will need to join again days after the initial conversation ended. Now, the Rootly scribe can be added back so your team's conversations will always be transcribed, and context doesn't get lost on the bridge. Ask @Rootly in the incident channel to add the Scribe back when your team rejoins the call, or summon it yourself with /rootly scribe.
What it captures is sharper too. Scribe now runs on a higher accuracy transcription engine and labels who said what, so the transcript reads like a conversation instead of a wall of text. Every call on the incident is captured as its own session and stitched into one continuous transcript, and the AI summary that follows the call is more legible, with speaker attribution.
Then Rootly holds onto it. The transcript and the summary live on the incident next to your timeline, alerts, and action items, so the call is part of the incident record instead of someone's private notes. Ask @Rootly what was decided on the bridge weeks later, or pull the same context into a retrospective in Rootly when it is time to write things up.
What's included
- Ask the
@Rootlyagent in Slack or run/rootly scribeto add the Scribe back to the call after the initial call ends. - Live transcription streamed back to the incident as the call happens, with speaker labels applied automatically.
- A higher accuracy transcription engine behind every recorded incident call, so nothing gets missed.
- Each call captured as its own session and stitched into a single transcript for the incident.
- A more accurate AI summary after the call, with speaker attribution.
Why it matters
Someone on every incident call ends up as the note taker, and it is usually the person who should be looking at the problem instead. Notes taken that way are thin, and the details that matter get lost between the call ending and the write-up starting.
Letting Scribe hold the record gives that person back to the response. The team talks through the problem, and Rootly keeps what was said, who said it, and what was decided. Later, anyone can ask the Rootly agent what happened on the bridge, or write the retrospective in Rootly with the call already in front of them.
Scribe is set up under your AI & Agent settings. Learn more in the Meeting Scribe documentation.
