This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how PagerDuty Advance Scribe Agent updates (Generally Available) build towards this vision.

When a major operational issue hits, there’s always someone drawing the short straw to take on the most thankless job in incident response: scribing the call. Chances are you were already that someone. Instead of investigating the issue, you’re struggling to type and keep up with what everyone’s saying and deciding, in real time.

When the incident is resolved, half the context is gone. Critical decisions disappear when the meeting ends or get lost in endless chat threads. The post-incident review becomes the team’s best reconstruction of what actually happened. A week later, when a similar incident hits, teams start from scratch.

And it costs you every time. According to our State of AI-First Operations report, an hour of downtime can cost organizations over $300K—much of it from repeat incidents that could have been avoided with a documented resolution path.

But it doesn’t need to work like this anymore.

Scribe Agent captures what you’d otherwise forget

PagerDuty’s Scribe Agent joins your incident meetings automatically to capture audio and chat. It works alongside SRE Agent to give you a complete picture of an active incident: while SRE Agent investigates, triages, and recommends the best course of action, Scribe captures every critical detail and decision, while making it easier to share that knowledge across the team.

Here’s what Scribe Agent can handle for you:

• Transcribes conference bridges (Zoom, Microsoft Teams, Google Meet), including audio and chat, so side conversations don’t disappear. 
• Enriches status updates and post-incident reviews with a comprehensive summary of what happened, so teams have an actionable start to extract learnings from the incident. Try our new Post-Incident Reviews in PagerDuty UI available in Early Access.
• Feeds operational intelligence into SRE Agent’s memory, helping accelerate future incident response.

New Incident Workflow actions enriched by Scribe Agent

Two new Incident Workflow actions further automate stakeholder communication and bridge scheduling. Paired with Scribe Agent, they unlock even richer context:

• Periodic Incident Progress: Automatically posts progress updates in Slack or Microsoft Teams at a custom cadence, keeping stakeholders informed without manual check-ins on responders. With Scribe Agent enabled, updates can include rich context such as meeting transcripts, chat history, and additional incident data. Learn more.

  

• Google Meet: Schedules a Google Meet bridge for incidents. It also supports adding Scribe Agent to capture audio and chat, enriching incident context and post-incident reviews. Learn more.

These capabilities eliminate manual status update toil and ensure complete incident documentation—feeding operational intelligence back into the platform to help teams resolve incidents faster and prevent repeat issues.

Get started with Scribe Agent

Scribe Agent paves a path to Autonomous Operations by making sure critical context is captured automatically, not lost. Every transcript becomes institutional knowledge inside the PagerDuty platform, feeding directly into how teams respond to the next incident.

Responders stay focused on resolution. Stakeholders stay informed without interrupting them. And the learnings that used to disappear with every resolved incident start compounding into intelligence that prevents the next one.

Scribe Agent is generally available for PagerDuty Advance customers using Slack or Microsoft Teams for chat collaboration, Zoom and Google Meet for incident-related meetings. Watch the demo and learn more.