Skip to main content

💫 Early Access for ‘Service Reassignment
(aka Changing an Incident’s Service)
’ will begin in December! 💫
💚 Open to all Incident Management customers. 💚
Please sign up here!

 

Feature Details: 
Reporters and Responders, rely on PagerDuty’s detection and mobilization routing to ensure the incident’s remediation can begin quickly. When an incident is created on the wrong service, PagerDuty will unblock mitigation by allowing incident responders: 

  1. To change the incident's service to the correct service, 
  2. To determine what information (i.e. Incident Users, Tasks, Incident Roles, Custom Fields, etc.) is relevant to an incident.
  3. Lastly, PagerDuty will automatically loop in the new service's on-call response team. 

Furthermore, CSOps and ITSM integrations (i.e. Service Now, Sales Force) that work better with PagerDuty, will use service reassignment to ensure ticket details are properly aligned with Incident resolution and documentation.

Customer Value: 
This ensures the right data is captured and incident triaging is accelerated. Thus reducing the risk and cost of operational failures, and enabling deeper data insights.

Next Steps:

To join the program - Please sign up here! As a participant, we ask that you actively use the feature and provide feedback via surveys or virtual interviews.

We will follow up with next steps and program details on December 2nd. 

Looking forward to your participation.
PagerDuty Service Team

Be the first to reply!