PagerDuty’s Scribe Agent ingests video conference transcripts and chat messages in real-time, ensuring comprehensive and consistent record keeping, while eliminating manual information gathering.

It enhances Incident Summarization features like "catch me up" and "wrap me up" prompts, as well as status updates, by including transcripts from both active and finished meetings. To support continuous improvement, the Scribe Agent enriches Post-Incident Reviews by capturing critical context and timeline details.

Supported Platforms

Chat Apps

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

Video Conferencing Platforms

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

Requirements

In order for the Scribe Agent to transcribe and deliver meeting summaries, you need:

• PagerDuty Advance AI Actions: Your account must have available PagerDuty Advance AI Actions or the add-on enabled. Without credits, the Scribe Agent cannot be used.
• A configured chat surface: Either Slack or Microsoft Teams must be connected to PagerDuty Advance so you can receive the meeting transcripts and summaries.
• A supported meeting platform: A valid meeting must be initiated in Zoom, Microsoft Teams, or Google Meet for Scribe Agent to join. If using automated mechanisms, a valid meeting must be linked to the PagerDuty incident in question for Scribe Agent to join without human intervention.

Role Requirements

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 — Any user can then add the Scribe Agent to their 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, click Settings and select the 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.

📘

Note

Zoom Admins can also enable these settings for a group of users, or for all users in your account. Please visit these Zoom resources for more information:

• Enabling automated captions
• Configuring authentication settings and profiles
• Allowing only authenticated users in meetings

6. 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, you can 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, you can skip this step.
2. Optional: By default, the Scribe Agent will wait 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 Microsoft's 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, you can skip this step.

Step 2 - PagerDuty Configuration

Follow these steps to complete the PagerDuty setup:

1. Connect a Chat Integration:
   • Connect PagerDuty Advance to Slack, or
   • Connect PagerDuty Advance to Microsoft Teams
2. Enable the Scribe Agent: Navigate to AI Settings and enable the Scribe Agent.
3. Optional: Configure Auto Launch to automatically add the Scribe Agent to every incident meeting:
   1. Click Configure next to the Scribe Agent.
   2. Click the Automatically launch Scribe Agent toggle to enable it.
   3. Click Save.

🚧

Known Limitation

Enabling Slack and Microsoft Teams simultaneously may cause auto-join mechanisms to fail or behave unexpectedly.

Add the Scribe Agent to a Meeting

Once an Admin has completed the initial configuration, any user with a linked chat account can add the Scribe Agent to their incident meetings.

📘

Scribe Agent Limit

Only one Scribe Agent can join and transcribe each incident meeting. When the Scribe Agent is removed 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.

Channel Linking

Channels are automatically linked to incidents through your chat integration's channel connections:

• Slack channel connections
• Microsoft Teams channel connections

To manually link a channel to an incident, ask@PagerDuty to add or change an incident in the channel.

Add the Scribe Agent

Once your Admin has configured and enabled the Scribe Agent, you can add it to your meetings. You can add the Scribe Agent using:

• Automatically
  • Auto Launch Feature
  • Incident Workflows
• Manually
  • Slack or Microsoft Teams

Using the Auto Launch Feature

🚧

Requirements

To add the Scribe Agent to your incidents using the Auto Launch feature, you will need to have a valid meeting linked to the incident and a dedicated incident channel (or service mapping) in your preferred chat surface.

With the Automatically launch Scribe Agent toggle enabled:

• Someone must join the incident meeting within 15 minutes of setting the incident’s Conference Bridge meeting URL for the Scribe Agent to automatically join.
• If no one joins the incident meeting within 15 minutes, the Scribe Agent will 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

🚧

Requirements

To add the Scribe Agent using Incident Workflows, you will need to have a valid meeting linked to the incident and a dedicated incident channel (or service mapping) in your preferred chat surface.

When using Incident Workflows it is recommended to have the steps to create the incident conference bridge, dedicated channel and add Scribe Agent in the same workflow to ensure all requirements are covered.

You can add the Scribe Agent to incident meetings via Incident Workflows, which give you precise control over when the agent is added based on your trigger conditions (e.g. incident creation, priority changed to P1, trigger only for major incidents). To avoid redundancy, disable the Automatically launch Scribe Agent toggle.

For detailed instructions about adding the Scribe Agent via Incident Workflows, please read our Add PagerDuty Advance Scribe Agent workflow action article.

When the Add PagerDuty Advance Scribe Agent workflow action runs:

• Someone must join the incident meeting within 15 minutes of setting the incident’s Conference Bridge meeting URL for the Scribe Agent to automatically join.
• If no one joins the incident meeting within 15 minutes, the Scribe Agent will 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

🚧

Requirements

To add the Scribe Agent, you must first link your PagerDuty and chat app user accounts.
Please 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 that is linked to an incident.
2. Either:
   • Type the scribecommand:
     • Slack: /pd scribe
     • Microsoft Teams: @PagerDuty advance scribe
   • Or click Add Scribe Agent to meeting. This button appears when the linked incident has a Conference Bridge meeting URL.
     • Note: When you click Add Scribe Agent to meeting for a specific incident, all transcripts and meeting summaries from the Scribe Agent will be linked to that incident only.
3. On the Add Scribe Agent modal, the incident’s meeting URL is automatically filled in. You can modify the URL, if needed.
4. Ensure that the meeting URL includes the meeting’s passcode.
5. Click Add.

Next Steps

With Scribe Agent properly configured, it will now be ready to join your incident meetings.

During the Meeting

The Scribe Agent sends live transcripts directly to your channel's meeting thread unless disabled by a PagerDuty Administrator. Meeting hosts can change the transcript language through the video conferencing tool’s caption settings.

The agent also monitors meeting participation by sending messages when users join or leave. It keeps 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 will post a comprehensive meeting summary to the channel. 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 may take extra time to generate.

📘

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, find the initial message from the Scribe Agent that says “A meeting transcript has started for <your incident>.”
2. Click Remove Scribe Agent.

Hide Transcripts in Chat Platform

By default, Scribe Agent sends the meeting conference to Slack and/or Microsoft Teams, but you may choose not to receive it if it doesn’t offer any added value. In the AI Agents Console, find Scribe Agent configuration and disable the 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

How do I get more compliance, legal, privacy or security information about the Scribe Agent?

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

I've added the Scribe Agent to my Zoom meeting. Why isn’t it able to join the meeting?

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

The Scribe Agent has joined my Zoom meeting. Why isn’t it sending transcripts to my channel?

The meeting host must configure the required Zoom settings before the Scribe Agent can start transcribing. If Zoom settings are already configured, check if Scribe Agent is configured to send transcripts to the chat platform at all.

🚧

Known Limitation

Enabling Slack and Microsoft Teams simultaneously may cause auto-join mechanisms to fail or behave unexpectedly.

Why does the Scribe Agent show as “Unverified” in my Microsoft Teams? meeting?

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 doesn't affect the agent's functionality -- it will still transcribe and summarize your meeting normally.

Can the Scribe Agent help with status updates and Post-Incident Reviews?

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.

What happens if I don't have PagerDuty Advance AI Actions?

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