When Crisis Hits
A major outage, security breach, or product failure can generate 10-50x your normal ticket volume in hours. How your support team responds in the first 60 minutes defines your brand reputation for months to come.
The Crisis Communication Framework
1. Acknowledge Immediately
Within 15 minutes of identifying a crisis, post a status update on your status page, social media, and in-app. Acknowledge the issue even if you do not have full details yet. Silence breeds speculation.
2. Centralize Communication
Designate a single source of truth for updates. All agents should reference the same talking points. Update these talking points every 30-60 minutes as new information becomes available.
3. Triage Aggressively
During a crisis, not every ticket needs a detailed response. Use auto-replies with status links for tickets about the known issue. Focus human effort on customers with unique problems or high-value accounts.
4. Over-Communicate
Post updates even when there is no new information. Saying we are still investigating and will update you by 3pm is better than going dark for 2 hours.
5. Post-Mortem and Follow-Up
After the crisis is resolved, send a detailed post-mortem to affected customers. Explain what happened, why, and what you are doing to prevent recurrence. Transparency builds trust.
Preparing Before Crisis Hits
- Create pre-written templates for common crisis scenarios
- Define escalation paths and decision authority during crises
- Set up a dedicated crisis Slack channel with auto-alerts
- Practice crisis drills quarterly
- Configure Helpzen auto-replies and SLA overrides for crisis mode
