Once you have configured PagerDuty Advance, you can use the following features:

• PagerDuty Advance Assistant
  • PagerDuty Advance for Post-Incident Reviews
  • PagerDuty Advance Slack Side Panel
• PagerDuty AI Agents
• PagerDuty Advance Integration for Amazon Q
• PagerDuty Advance for Status Updates
• Periodic Incident Progress
• PagerDuty Advance for Automation Digest
• PagerDuty Advance Analytics

PagerDuty Advance Assistant

📘

Availability

PagerDuty Advance Assistant is available in US and EU service regions.

🚧

Required User Permissions

You can interact with the PagerDuty Advance Assistant in Slack.

1. Navigate to the channel that is linked to the incident for questions directly related to a PagerDuty incident. For non-incident questions, navigate to any channel.
2. Mention the PagerDuty bot and enter your question to interact with the PagerDuty Advance Assistant within the channel.
   1. In a Slack channel: @PagerDuty
   2. In a Microsoft Teams channel: @PagerDuty advance

Prompt Examples

To meet these requirements, the bot requires the ability to join the channel, send messages, and send URLs within the channel.

PagerDuty Advance for Post-Incident Reviews

📘

Availability

• Generally available to Professional, Business, and Enterprise Incident Management accounts using Jeli and PagerDuty Advance (one-time AI Actions, trial, or add-on).
• This feature is only available in the US service region.

🚧

Requirements

• If you have the role of Observer, Limited User, User, Admin, or Account Owner (or their respective advanced permission base roles), you can generate post-incident reviews.
• You must have a dedicated incident channel or have at least one Slack channel connection to a PagerDuty service.
• To create a post-incident review in Jeli, your account must first be integrated with Jeli.

1. Mention @PagerDuty and ask it, “what happened” once you resolve an incident in Slack or Microsoft Teams.
2. PagerDuty Advance reviews the entire chat history and presents you with an executive summary, including what happened, actions, decisions, and the incident resolution. A call to action to create a post-incident review displays if your account has an integration with Jeli.
3. Click Create a Post-Incident Review to import the PagerDuty Advance summary into Jeli as a new post-incident review. You can edit the post-incident review within Jeli.
4. Jeli displays an indicator to show that the post-incident review is AI-generated.

Direct Messages using the PagerDuty Advance Slack Side Panel

PagerDuty Advance in the Slack side panel automatically understands which channel you are currently viewing and can access relevant information about any associated incidents. When you use the split view to examine an incident, the PagerDuty Advance Assistant intelligently references that specific incident in its responses to your questions, ensuring more accurate and relevant assistance. This contextual understanding allows the PagerDuty Advance Assistant to provide more targeted and helpful responses without requiring you to provide additional background information.

To begin a conversation with the PagerDuty Advance Assistant in the Slack side panel:

1. Click the PagerDuty Advance Slack side panel logo on the top right corner of your Slack workspace.
2. Enter your question or request.

PagerDuty AI Agents

PagerDuty AI agents are purpose-built to help operations teams drive productivity and efficiency through every stage of the operations lifecycle.

Visit these resources to learn about each agent's capabilities:

• Insights Agent
• Shift Agent
• Scribe Agent
• SRE Agent

PagerDuty Advance Integration for Amazon Q

🚧

Requirements

To begin using the integration, you must first link your PagerDuty and chat app user accounts. See our Slack User Guide or Microsoft Teams Integration Guide for more information on linking user accounts.

📘

View Integration Summary

From the PagerDuty Advance incident context card, click the Use Amazon Q button to view a summary of the integration and its usage instructions.

1. You can use Amazon Q by typing the amazonq command and entering your question.
   1. In a Slack channel: /pd amazonq
   2. In a Microsoft Teams channel: @PagerDuty amazonq
2. If you have not authenticated with Amazon Q or your AWS session has expired, you receive a message prompting you to log into your company Identity Provider for AWS (for example, AWS IAM Identity Center, Okta, Entra, or Auth0).
   1. Click Link Accounts to log into your Identity Provider. Note: If you are unable to log in, reach out to your AWS account administrator and ensure your AWS user account can access the Amazon Q Business app and the PagerDuty Advance data accessor.
   2. Once authenticated, type the amazonq command and re-enter your question for Amazon Q.
3. You can ask questions such as:
   • What is our rollback process?
   • Who can I talk to about feature X?
   • Why do we use encryption for feature Y?
   • What kinds of questions can you answer?
4. PagerDuty Advance searches your connected Amazon Q Business data sources to find and show you relevant information. It presents key information, including a link to the source documents. PagerDuty Advance only reads data – it does not modify any source content or run any actions, even if PagerDuty Advance is integrated with Amazon Q Business as a plugin. Note: Information availability and recency vary based on the Amazon Q Business configuration in your AWS account.

PagerDuty Advance for Status Updates

📘

Availability

PagerDuty Advance for internal status updates is available in US and EU service regions. PagerDuty Advance for the external status page is not available at this time.

🚧

Required User Permissions

• If you are not a Limited Stakeholder or Full Stakeholder, you can generate status updates for incidents assigned to you.
• Only Responders, Managers, Global Admins, and Account Owners can generate status updates for incidents that are not assigned to them.

📘

Slack and Microsoft Teams Sources

Status updates generate from the following chat app sources:

Slack

1. The incident-associated channel, when present.
2. The service-associated channel.

Microsoft Teams

1. The incident-associated chat or meeting, when present.
2. The service-associated channel.

In PagerDuty

1. In the web app, click the title of your preferred incident, navigate to the Status Updates tab, and click New Update.
2. Click Generate to the right of the Message field. A status update automatically generates. You can make edits to the draft according to your preferences.
3. Click Send Update.

In Slack and Microsoft Teams

1. On the incident card, click New Status Update.
2. Select the tone that you want to use when generating the status update.
3. Review and edit the status update.
4. Click Send Update.

Alternatively, you can chat directly with the PagerDuty app and give it a prompt, such as “write a status update”. After the draft generates, you can choose Send Status Update to send the update, Review Status Update to make additional changes, or change the tone.

Periodic Incident Progress (PIP)

🚧

Required Permissions

Account Owners and Global Admins can create and edit all incident workflows. You can create and edit workflows and triggers for services where they have Manager access.

Overview

The PagerDuty Advance - Periodic Incident Progress incident workflow action automatically posts progress updates in Slack or Microsoft Teams on active incidents, keeping responders and stakeholders informed of what changed since the last update. By default, updates are sent every 15 minutes, but you can adjust the cadence to fit your team needs. It is designed for teams that want regular, low-toil status pings without manual check-ins.

Each update shows only what changed since the last check—such as priority, assignee, responders, notes, or severity—rather than repeating the full incident state. Updates post to your configured Slack or Microsoft Teams dedicated incident channels. If no changes occur during an interval, the update may be skipped depending on your settings.

📘

Meeting Summaries

Periodic Incident Progress posts metadata changes (status, priority, assignments, responders, severity, notes) at your configured cadence. When the Scribe Agent is enabled, Periodic Incident Progress also includes AI-based meeting summaries generated by the agent in its periodic updates.

When Thread updates in Dedicated Channels is enabled in Slack, progress updates post as a thread under a pinned card. This card is then automatically updated with the latest summary.

🚧

Important

Periodic Incident Progress updates are only posted to dedicated incident channels created for specific incidents.

Use cases

• Automated status updates: Keep incident channels in Slack or Microsoft Teams up to date without manual typing.
• Change tracking: Provide clear details of what changed (assignee, priority, notes, responders, severity, and other fields) since the last update.
• Cross-team visibility: Improve cross-team awareness during longer-running incidents.

Configuration

See Add Periodic Incident Progress workflow instructions.

PagerDuty Advance for Automation Digest

See our Automation Actions article for more information on generating an automation digest.

PagerDuty Advance Analytics

See our PagerDuty Advance Analytics article for more information on viewing PagerDuty Advance Analytics data.