|docs
Start Trial

AI & Automation

Scribe Agent

Transcribe incident meetings in real time to enhance incident summaries and post-incident reviews

PagerDuty Scribe Agent ingests video conference transcripts and chat messages in real time to ensure comprehensive and consistent record keeping and eliminate manual information gathering.

The agent enhances incident summarization features like "catch me up" and "wrap me up" prompts, and status updates, by including transcripts from both active and completed meetings. To support continuous improvement, the Scribe Agent enriches post-incident reviews) by capturing critical context and timeline details.

Availability

Agents are a PagerDuty Advance feature. PagerDuty Advance is available through one-time credits or as an add-on with the following pricing plans:

  • Professional
  • Business
  • Enterprise for Incident Management

Please contact our Sales Team if you would like to upgrade to a plan featuring PagerDuty Advance.

Supported Platforms

Chat Apps

The Scribe Agent can send meeting transcripts to the following chat apps:

PlatformTranscription Delivery Support
Slack✓ Supported
Microsoft Teams✓ Supported

Video Conferencing Platforms

The Scribe Agent can join and transcribe meetings on the following video conferencing platforms:

PlatformTranscription SupportLimitations
Zoom✓ SupportedNone
Microsoft Teams✓ SupportedThe Scribe Agent cannot join meetings and webinars that require registration or CAPTCHA verification.
Google Meet✓ SupportedNone

Requirements

To ensure the Scribe Agent transcribes and delivers meeting summaries, you require:

  • PagerDuty Advance AI Actions: Your account must have available PagerDuty Advance AI Actions or the add-on enabled. Without credits, you cannot use the Scribe Agent.
  • A supported meeting platform: You must initiate a valid meeting in Zoom, Microsoft Teams, or Google Meet for the Scribe Agent to join. If you use automated mechanisms, you must link a valid meeting to the PagerDuty incident for the Scribe Agent to join without human intervention.

Note

Chat surface configuration requirement

As of July 23, 2026, Scribe Agent no longer requires a chat surface to join incident conference bridges. This means meeting transcripts are now collected and used automatically for summary generation, SRE Agent analysis, and Post-Incident Review — even without a configured chat surface.

Note: Scribe Agent transcripts and summaries are not displayed anywhere by default. To make them visible to your team, configure a chat surface (Slack or Microsoft Teams)) and a notification or dedicated incident channel.

Role Requirements

ActionRequired Role
Enable Scribe Agent and connect integrationsPagerDuty Admin, or Account Owner
Add Scribe Agent to meetingsAny user with a linked PagerDuty ↔ chat app account

See our Slack User Guide or Microsoft Teams Integration Guide) for instructions on linking accounts.

Initial Configuration

Scribe Agent configuration is a two-step process:

Admin setup — An admin enables the Scribe Agent and configures the required integrations.
User setup — You can then add the Scribe Agent to your meetings.

Step 1 - Video Conferencing Platform Setup

Zoom and Microsoft Teams require initial configuration, while Google Meet meetings work without additional setup steps.

Zoom Configuration

  1. Sign in to the Zoom web portal.
  2. In the navigation menu, navigate to Settings Meeting tab.
  3. Under In Meeting (Advanced), click the Automated captions toggle to enable it.
  4. On the verification prompt, click Enable.
  5. Under Security, ensure that the Only authenticated users can join meetings… toggle is disabled.
Automated captions toggle for Zoom meetings
Automated captions toggle for Zoom meetings

Authentication toggle to allow users to join Zoom meetings
Authentication toggle to allow users to join Zoom meetings

Note

Configuration Note

Zoom administrators can also enable these settings for a group of users or for all users in your account. Visit these Zoom resources for more information:

  1. To automatically add the Scribe Agent using incident workflows or the auto launch feature, install the Zoom | PagerDuty integration. If you plan to add the Scribe Agent manually using Slack or Microsoft Teams, skip this step.

Microsoft Teams Configuration

  1. To automatically add the Scribe Agent using incident workflows or the auto launch feature, install the Microsoft Teams | PagerDuty) integration. If you plan to add the Scribe Agent manually, skip this step.
  2. Optional: By default, the Scribe Agent waits in the meeting lobby for manual admission. To allow the Scribe Agent to bypass the lobby and join meetings automatically, configure your Microsoft Teams organization settings. For more information, visit the Microsoft resource on Using the lobby in Microsoft Teams meetings.

Google Meet Configuration

  1. To automatically add the Scribe Agent using incident workflows or the auto launch feature, set up a workspace connection to your Google Workspace. If you plan to add the Scribe Agent manually, skip this step.

Step 2 - PagerDuty Configuration

Follow these steps to complete the PagerDuty setup:

  1. Connect a Chat Integration:
  1. Enable the Scribe Agent: Navigate to AI Settings and enable the Scribe Agent.

    Note

    EU Data Region

    In the EU data region, the Scribe Agent is enabled by default. In the US data region, you must enable it manually using this step.

  2. Optional: Disable auto launch. When the Scribe Agent is enabled, auto launch is on by default, so the agent is added automatically to every incident meeting. To stop the Scribe Agent from joining every incident meeting automatically:

    1. Click Configure next to the Scribe Agent.
    2. Click the Automatically launch Scribe Agent toggle to disable it.
    3. Click Save.
Scribe Agent card in AI Settings
Scribe Agent card in AI Settings

Automatically launch Scribe Agent with a PagerDuty incident toggle
Automatically launch Scribe Agent with a PagerDuty incident toggle

Add the Scribe Agent to a Meeting

Once an administrator completes the initial configuration you can add the Scribe Agent to your incident meetings.

Note

Scribe Agent Limit

Only one Scribe Agent can join and transcribe each incident meeting. When you remove the Scribe Agent from a meeting, you can add it back to that same meeting if needed.

You can have up to 10 Scribe Agents simultaneously transcribing across different meetings.

Add the Scribe Agent

Once Scribe Agent is enabled you can add it to your meetings using these methods:

Using the Auto Launch Feature

Warning

Requirements

To add the Scribe Agent to your incidents using the auto launch feature, you require a valid meeting linked to the incident.

We also recommend setting up a dedicated incident channel (or service mapping) in your preferred chat surface so your team can see the live transcript and meeting summary.

With the Automatically launch Scribe Agent toggle enabled:

  • A participant must join the incident meeting within 15 minutes of setting the incident conference bridge meeting URL for the Scribe Agent to automatically join.
  • If no one joins the incident meeting within 15 minutes, the Scribe Agent does not join automatically. You can still add the Scribe Agent to the meeting using Slack or Microsoft Teams or by manually running an incident workflow.

Using Incident Workflows

Warning

Requirements

To add the Scribe Agent to your incidents using the auto launch feature, you require a valid meeting linked to the incident.

We also recommend setting up a dedicated incident channel (or service mapping) in your preferred chat surface so your team can see the live transcript and meeting summary.

When using incident workflows, including the steps to create the incident conference bridge, dedicated channel, and add Scribe Agent within the same workflow is recommended to ensure you satisfy all requirements.

You can add the Scribe Agent to incident meetings via incident workflows, which provide precise control over when the agent is added based on your trigger conditions (for example, incident creation, priority changed to P1, or triggering only for major incidents). Because auto launch is enabled by default, disable the Automatically launch Scribe Agent toggle to avoid redundancy.

For detailed instructions about adding the Scribe Agent via incident workflows, read our Add PagerDuty Advance Scribe Agent workflow action article.

When the Add PagerDuty Advance Scribe Agent workflow action runs:

  • A participant must join the incident meeting within 15 minutes of setting the incident conference bridge meeting URL for the Scribe Agent to automatically join.
  • If no one joins the incident meeting within 15 minutes, the Scribe Agent does not join automatically. You can still add the Scribe Agent to the meeting using Slack or Microsoft Teams or by manually running an incident workflow.

Using Slack or Microsoft Teams

Warning

Requirements

To add the Scribe Agent, you must first link your PagerDuty and chat app user accounts. See our Slack User Guide and Microsoft Teams Integration Guide) for more information on linking user accounts.

  1. In your chat app, navigate to a channel linked to an incident.
  2. Complete one of the following actions:
    • Type the scribe command:

      • Slack: /pd scribe
      • Microsoft Teams: @PagerDuty advance scribe
    • Click Add Scribe Agent to meeting. This button appears when the linked incident has a conference bridge meeting URL.

      Note

      Transcript Association

      When you click Add Scribe Agent to meeting for a specific incident, all transcripts and meeting summaries from the Scribe Agent link to that incident only.

  3. On the Add Scribe Agent modal, the incident meeting URL populates automatically. You can modify the URL if needed.
  4. Ensure that the meeting URL includes the passcode for the meeting.
  5. Click Add.

Next Steps

With the Scribe Agent properly configured, the agent is ready to join your incident meetings.

During the Meeting

The Scribe Agent sends live transcripts directly to your channel meeting thread unless a PagerDuty administrator disables this preference or you don't have a channel mapped to the incident. Meeting hosts can change the transcript language through the caption settings of the video conferencing tool.

The agent also monitors meeting participation by sending messages when participants join or leave. It maintains an updated participant list on the initial "A meeting transcript has started for <your incident>" message.

After the Meeting

When the meeting ends or the host removes the Scribe Agent from the meeting, the Scribe Agent posts a comprehensive meeting summary to the mapped channel (if one exists). This includes key discussion points, action items, next steps, and a complete list of all participants who attended the meeting. For longer meetings, the summary can take extra time to generate.

Note

Operational Note

While transcripts sent during the meeting are audio-only, the final meeting summary captures both audio and chat content.

Remove the Scribe Agent from a Meeting

You can remove the Scribe Agent from a meeting at any time.

As the Meeting Host

Zoom

  1. In Zoom, hover over the Scribe Agent and click the overflow menu.
  2. Click Remove.

Microsoft Teams

  1. In Microsoft Teams, click the People icon to view the meeting participants.
  2. Click the overflow menu next to the Scribe Agent.
  3. Click Remove from meeting.

Google Meet

  1. In Google Meet, click the People icon to view the meeting participants.
  2. Click the overflow menu next to the Scribe Agent.
  3. Click Remove from the call.

If You Are Not the Meeting Host

  1. In your chat app, locate the initial message from the Scribe Agent that reads "A meeting transcript has started for <your incident>."
  2. Click Remove Scribe Agent.

Hide Transcripts in Chat Platform

By default, the Scribe Agent sends the meeting conference details to Slack or Microsoft Teams, but you can choose not to receive this data if it does not offer added value. In the AI Agents Console, locate the Scribe Agent configuration and disable the Send transcripts to chat surface toggle.

Send transcripts to chat surface toggle
Send transcripts to chat surface toggle

Disable Scribe Agent

Disable the Scribe Agent by toggling its switch to the off position on the AI Settings page.

FAQ

You can read the PagerDuty Advance AI Disclosure to learn more about how PagerDuty designed, built, and assessed PagerDuty Advance with mission-critical work in mind.

The meeting host must configure the required Zoom settings before the Scribe Agent can join the host's meetings.

The meeting host must configure the required Zoom settings before the Scribe Agent can start transcribing. If Zoom settings are already configured, check if the Scribe Agent is configured to send transcripts to the chat platform at all and/or if there is a chat surface configured with a channel properly mapped to the incident.

The Scribe Agent appears as "Unverified" in Microsoft Teams due to Microsoft's February 2024 update, which automatically labels participants based on their relationship to the meeting organizer's organization. Since the Scribe Agent is a bot without an established trust relationship with your organization, Microsoft Teams assigns it the "unverified" label by default. This labeling is purely cosmetic and does not affect the agent's functionality — it still transcribes and summarizes your meeting normally.

Yes, the Scribe Agent can assist with both:

  • Status updates: The Scribe Agent's meeting transcripts are used as context to generate status updates.
  • Post-Incident Reviews: The Scribe Agent's meeting transcripts provide context for "wrap me up" prompts, and these summaries can be used to create post-incident reviews.

Without available AI Actions or the PagerDuty Advance add-on, you cannot use the Scribe Agent. Contact your account administrator or PagerDuty sales to add AI Actions to your account.