Skip to main content
Ready to enable Scribe? Jump to this section.
Video calls bring responders together allowing rapid coordination across teams and countries but it brings a number of issues. If you join an incident call in progress it can be hard to quickly build up an understanding of what’s happening without interrupting. The same applies when it comes after the incident has been resolved: without the context and detail of the call it can be hard to build up a clear picture of how an incident progressed from declaration to resolution. You may have someone keeping notes or even responders regularly updating the incident channel with information but this all takes time and distracts from the issue at hand. How do you easily ensure you don’t miss any context, important information, decisions or next steps? By using Scribe of course!

What is Scribe

Scribe is our friendly AI powered note taker - with Scribe enabled our bot will join your incident calls automatically and take detailed notes as well as providing summaries, key moments, and the current topic into your incident channel.

Feature: Integrated transcripts

By joining the call it has access to the video and audio from that call. It uses this data, in conjunction with streamed captions from the meeting, to deduce who has said what. It is this transcription we use to power the other Scribe features such as summaries, key moments and current topic. The transcript can be accessed in the incident details page, by clicking ‘View notes’.

Feature: Detailed summaries

One of the hardest things when joining an in progress incident is knowing what everyone is talking about, or how best you can help. Scribe is continually building a picture of what is happening on the call. Scribe is continuously building a detailed summary of the whole call. It pulls out important information and next steps, along with providing a general summary of the incident call from start to finish. These summaries are created in real-time, and are viewable within the incident channel and the dashboard.

Feature: Current topic

Along with frequent call summaries, the current topic is shown in both the incident channel and the dashboard to help give other users an “at a glance” idea of what’s being discussed and how things are going, potentially highlighting that they might want to join the call.

Feature: Proactive key moments

Scribe also looks to actively pull key moments from the call transcript into the incident channel. Key moments are a combination of important decisions, agreements, or when key information was discovered on a call. Some examples of key moments are decisions to update a status page, or when a roll-back was triggered, or potentially new information came to light that might help in solving the issue. Key moments also help new responders get up to speed, as well as streamlining the post-incident process when it comes to building a timeline of what happened.

Enabling Scribe

Scribe is available to Pro and Enterprise customers. By default it is disabled but once you have a call provider set-up (Zoom, Microsoft Teams calls, Google Meet, or Webex) you can go to Settings > AI and enable Scribe there. Once enabled, Scribe will request to join all Google Meet, Zoom, and Webex incident calls. From here, someone on the incident call can choose to allow or deny entry to Scribe. If you disable auto-joining in Settings → AI, Scribe can be added manually from the call in the dashboard.
Note: We highly recommend turning on auto-call creation which automatically attaches a new call to each incident.

Set a transcription language

Scribe detects the language spoken on each call automatically. In some cases, background noise or some words or phrases can be detected as words in the wrong language. It normally only affects a few words, and doesn’t change the summaries or key moments Scribe posts to your incident. To transcribe every call in the same language instead, go to Settings → AI, open Scribe, and set Transcription language. More than 90 languages are available. Leave it on Auto-detect to keep detecting the language call by call.

FAQs

We use Recall.ai for raw transcription data, who are a third-party sub-processor that provide call transcription services. In order to transcribe the call, Recall.ai store a temporary recording which is deleted when the last human leaves the call. Recall.ai do not retain any data after this point.Transcription is provided by ElevenLabs, a second sub-processor, which receives the call audio through Recall.ai and returns the transcript. We don’t ask ElevenLabs to retain that audio, and it isn’t used to train models.We only store the call transcript, which we use to power Scribe features mentioned in this article. We do not store any audio or video from the call.If you’d rather we didn’t send call audio to ElevenLabs, contact us at help@incident.io. Scribe then transcribes from your meeting provider’s captions instead. Webex doesn’t offer closed captions, so Webex calls fall back to English-only transcription.For more information on how we use AI, you can read the AI data handling article.
We require new permissions for Zoom and Google Meet to enable call transcription. If you previously had those integrations setup it might be that you are using an older version of our permissions.Please make sure to update to the latest by re-authenticating the integration to ensure you have the right permissions.If you’re still seeing issues with Zoom, please check your settings in the Zoom app to ensure that recording has been allowed.If you are using Webex, please ensure that you have the incident.io Scribe service app installed.If you are still seeing issues - please reach out to support.
We rely on Zoom meeting captions to generate the transcript of your call. If the bot joined your call but you’re not seeing a transcript after a few minutes, it could be because you have meeting captions disabled.To enable meeting captions, navigate to Host Caption Control Settings while in a Zoom meeting, then enable the setting called Allow Closed Captioning for this meeting.fee4d8c-CleanShot_2024-05-17_at_12.07.54.pngIf you don’t see the option to enable meeting captions in your Zoom client, you likely have the setting turned off globally.To resolve this, simply go to Zoom settings and flip the toggle for Automated captions.If this is the first time you’ve installed Zoom, we recommend to ensure you’ve ticked the option to allow shared access permissions at the bottom referenced here.Should you continue to experience issues, please reach out to support.
Yes. Scribe transcribes calls in more than 90 languages, detecting the language spoken on each call automatically. To transcribe every call in the same language instead, see Set a transcription language.The transcript is in the language spoken on the call. The summaries, key moments, and current topic that Scribe posts to your incident channel are written in English, whatever language the call was held in.
Scribe doesn’t capture messages sent in the meeting’s built-in chat. For now, the best approach is to encourage responders to share key information in the incident channel itself rather than the bridge call chat, so that everything is captured in the incident timeline. That way, Scribe handles the verbal discussion and the channel captures any written updates.