Enhancement Idea: Shared Services for Incidents and Status Page

An enhancement that would significantly improve incident communication is the ability to use a shared service model across Incidents, Major Incidents, and the Status Page. We’re looking for a way to better align how services are defined and used across Incidents, Major Incidents, and the Status Page in Freshservice. Today, services defined for incident impact and major incident workflows are not linkable to Status Page services, requiring teams to manually recreate and maintain separate service lists. This prevents incident impact (e.g., a critical platform like Kubernetes going down) from automatically triggering major incidents and updating the Status Page with the correct impacted services. Enhancing this feature to support a shared service model would improve ITSM workflows by enabling automated incident impact communications, reducing manual maintenance, and ensuring consistent service visibility across incident management and customer-facing status updates.