Major incidents are not the time to figure out comms. Freshservice has Major Incident Management features designed for this. Configured ahead of time, they save your reputation. Configured during the outage, they make it worse.
Pre-stage the major incident template
Create a Major Incident template in Admin → Templates with required fields: business impact, stakeholder list, comms cadence, status page link. The on-call engineer should declare with three clicks, not three minutes of typing.
Stakeholder broadcasts
Use the Stakeholder Update feature to send templated updates to a saved distribution list. Pre-write three templates: Initial, Update, Resolved. Variables populate from the incident record.
Subject: [INCIDENT-{{id}}] Update {{update_number}}
Body:
Status: {{status}}
Impact: {{impact_summary}}
Next update: {{next_update_at}}War room integration
Wire the Major Incident workflow to auto-create a Slack or Teams channel via the native integration. Channel name pattern incident-{id}-{short_subject} makes them findable later.
// Workflow Automator action
{
"trigger": "major_incident_declared",
"action": "slack_create_channel",
"name_template": "incident-${id}-${subject_slug}"
}Status page sync
Statuspage.io and Freshservice integrate via Marketplace. Major incidents auto-create public status entries. Confirm the visibility default is “private” — public posting on declare is rarely what you want.
On-call paging
Connect PagerDuty or Opsgenie. Major incident declaration triggers the right rotation, not a generic “ops” alias. Test this monthly with a synthetic declaration in sandbox.
Post-incident review hand-off
On resolution, auto-create the PIR ticket with the incident timeline pre-populated. The PIR is due in 5 business days. A workflow enforces the SLA.
What to do this week
Pre-stage the Major Incident template, write the three stakeholder broadcast variants, wire the Slack/Teams channel auto-create, and run a sandbox synthetic declaration to validate paging.
