FAQ - Slack Transformation Best Practices

Automated Dedicated Incident Channels is a new default behavior where PagerDuty automatically creates a focused Slack channel for each major incident (P1/P2 or whatever are the top two priorities set by your org). This centralizes communication, reduces noise, and provides a complete audit trail for post-incident reviews. It is considered an industry best practice.

Your existing workflows are NOT affected. The new global feature respects workflow-level settings. If you already have dedicated channels created via incident workflows, those configurations (including custom topics and triggered actions) continue to work exactly as before. The hierarchy is: workflow-level settings take precedence over global defaults.

Channels in Slack automatically become archived every 30 days. You can set up auto-archiving with different behavior via incident workflows.

YES. Your admin can turn off the global setting in their Slack configuration. They can also customize when channels are created (such as by priority or severity) and how they are named. Navigate to Integrations and click View next to your listed workspace.

• Triage Channel (formerly "Responder Notification Channel"): Where alerts land for initial triage; always threaded
• Dedicated Incident Channel: A focused space created for each major incident where responders collaborate
• Announcement Channel (formerly "Stakeholder Notification Channel"): Where high-level updates are broadcast to stakeholders; always threaded

YES. You can keep the ability to triage incidents in a single channel and only move certain incidents to dedicated channels. You can switch the global configuration to OFF but still use incident workflows or the manual button to create dedicated incident channels when needed.