Enterprise Incident Ticket Communication Checklist

Role: Customer Success Incident Commander specializing in SaaS high-severity incident communication and enterprise customer retention.

Context

• Disrupted Service: {{affected_cloud_service}}
• Impacted Segment: {{impacted_account_tier}}
• Severity Classification: {{outage_severity_level}}
• Target Cadence Interval: {{incident_cadence_minutes}}
• Active Support Channels: {{stakeholder_notification_channels}}
• Interim Mitigation Status: {{mitigation_status}}

Task

Generate an end-to-end incident ticket communications checklist that guides the support team through acknowledging, updating, and resolving ticket queues affected by an active software outage.

Method

1. Review {{affected_cloud_service}} and {{outage_severity_level}} to determine the baseline communication protocol and template requirements.
2. Cross-reference {{impacted_account_tier}} with contractual notice commitments to set notification priorities.
3. Establish timed checkpoint gates based on {{incident_cadence_minutes}} for broadcasting macro ticket updates.
4. Outline verification steps for public status page consistency across {{stakeholder_notification_channels}}.
5. Define response guardrails for individual enterprise ticket replies while {{mitigation_status}} is developing.
6. Construct verification checks for identifying VIP account tickets requiring bespoke executive summaries.
7. Develop the incident de-escalation checklist for when core functionality is restored.
8. Formulate the post-incident ticket wrap-up checklist, including root cause communication and SLA credit auditing.

Constraints

• MUST specify mandatory time-stamped update milestones tailored to {{incident_cadence_minutes}}.
• MUST NOT include unverified estimated times of recovery (ETAs) in customer-facing checkpoints.
• Customer messaging must remain consistent across all channels listed in {{stakeholder_notification_channels}}.
• Keep all action items directly tied to queue management and customer reassurance.

Output format

1. Incident Phase 1: Ingestion & Mass Acknowledgment Checklist (4-6 items)
2. Incident Phase 2: Active Cadence & Status Synchronization Checklist (4-6 items)
3. Incident Phase 3: Resolution Validation & Queue Closeout Checklist (4-6 items)
4. Risk Mitigation Reminders (3 bullet points highlighting compliance and legal traps) Total length must be between 300 and 500 words.

Self-review

• Are all 6 contextual inputs referenced and applied to operational steps?
• Does the checklist clearly differentiate between active incident tasks and post-resolution tasks?
• Are cadence intervals strictly enforced within the checklist criteria?