July 10, 2025
Scribe - our note-taking agent that automatically joins calls, transcribes conversations and shares key updates back to the incident channel, is one of our most loved features, and rightly so!
However, sometimes you want to temporarily remove Scribe from the call - while you take a break, or have a sensitive conversation - then add it back later to ensure detailed notes for the remainder of the incident.
Equally, sometimes Scribe gets removed or turned away by someone accidentally, and you want to manually intervene and bring it back, to ensure no context is lost.
From today, you can easily add or remove Scribe from all calls, at any time, via the Web Dashboard, Slack, and Microsoft Teams.
We’ve also made it much easier to see understand Scribe's current status, so it's clear if it’s actively taking notes, in the waiting room to be admitted, or hit a snag like a permissions error, preventing it taking notes.
When configuring escalation paths, you can now send Slack notifications to private channels. Just like in workflows and alert routes, you'll need to ensure @incident
is in the channel (using /invite @incident
) in order to be able to send messages to it.
We've shipped a new alert source for Sentry metric alerts.
Our previous Sentry alert source only supported "issue" alerts (e.g. "alert me as soon as an error happens"). With metric alerts you get alerted based on changes to a metric (e.g. "tell me when error volume goes up by 10%").
As long as you have the Sentry integration installed, you can now add the "Sentry Metrics" alert source in your configuration!
incident.io
sender name, improving our delivery rates in these regions/inc relate
or in the dashboard.Ready for modern incident management? Book a call with one our of our experts today.