Picture this: Your service goes down at 2 PM on a Tuesday. Within minutes, your support inbox explodes. Twitter mentions spike. Customers are frustrated, confused, and some are genuinely panicked about their own business operations.
Here's the thing - most of this chaos is preventable. Not the outage itself (those happen to everyone), but the customer frustration that follows. After analyzing thousands of incident responses and customer feedback, we've discovered what customers actually want during outages. Spoiler alert: it's simpler than you think.
The Three Things Customers Crave Most
1. Acknowledgment That Something Is Wrong
The worst customer experience during an outage? Wondering if the problem is on their end.
Customers will spend 10-15 minutes clearing their cache, restarting their router, or asking colleagues "Is it just me?" before they even think to check your status page. Every minute they waste troubleshooting increases their frustration exponentially.
What customers want: Immediate confirmation that yes, there's a problem, and no, it's not their fault.
How to deliver: Update your status page within 5 minutes of detecting an issue. Even a simple "We're investigating reports of issues" is better than silence. This single action can reduce support tickets by 40-60% during an incident.
2. A Realistic Timeline (Even If It's Bad News)
Here's a hard truth: customers handle bad news better than no news.
When asked, 78% of customers said they'd rather hear "This will take 4 hours to fix" than see repeated "We're still working on it" updates every 30 minutes. Why? Because they can plan around a 4-hour outage. They can't plan around uncertainty.
What customers want: An honest estimate of when service will be restored, even if that estimate might change.
How to deliver: After your initial investigation (usually 15-30 minutes), provide a timeline estimate. Use ranges if needed: "We expect service to be restored within 2-3 hours." If you genuinely don't know, explain what needs to happen: "We need to complete a database restoration, which typically takes 2-4 hours."
3. Plain English Explanations
Your customers don't care about your Kubernetes cluster or your Redis cache invalidation issues. They care about whether they can process payments, send emails, or access their data.
What customers want: Simple explanations of what's broken and how it affects them.
How to deliver: Translate technical issues into business impact:
- Instead of: "DNS propagation failure in US-EAST-1"
Say: "Customers in the Eastern US may have trouble accessing the platform"
Instead of: "Database connection pool exhausted"
Say: "The service is running slowly and some features may timeout"
The Information Hierarchy That Actually Works
During an outage, customers scan for information in this order:
- Is it broken? (Yes/No)
- When will it be fixed? (Timeline)
- What exactly is broken? (Scope)
- What should I do? (Workarounds)
- Why did this happen? (Root cause)
Most companies get this backwards, leading with technical explanations when customers just want to know if they should wait or implement their backup plan.
The Psychology of Update Frequency
Here's what our data shows about update frequency:
- First 30 minutes: Customers check every 2-3 minutes
- 30-60 minutes: Checks drop to every 10-15 minutes
- After 1 hour: Most customers want updates every 30 minutes
This means front-loading your communication is crucial. Those first few updates set the tone for the entire incident.
Real Examples: Good vs. Bad Communication
Bad Example:
"We are aware of issues affecting some users. Our team is investigating."
(Vague, no timeline, no scope)
Good Example:
"Login services are currently down for all users. We've identified the issue and expect service to be restored by 3:30 PM EST. In the meantime, any active sessions will continue to work normally."
(Clear scope, timeline, and workaround)
The Mobile Reality Check
Over 65% of your customers will check your status page on their phone during an outage. This means:
- Keep updates short (under 280 characters when possible)
- Use bullet points for multiple pieces of information
- Make sure your status page loads quickly on mobile
- Consider that they might be checking while in a meeting or on the go
Building Trust Through Consistency
Customers remember how you handle outages. They'll forgive technical issues, but they won't forget poor communication. Here's how to build trust over time:
- Standardize your language: Use consistent terms for severity levels
- Keep promises: If you say hourly updates, deliver hourly updates
- Close the loop: Always post a final "resolved" update
- Follow up: Send a post-incident email within 24 hours
Your Action Plan
Ready to improve your incident communication? Here's your checklist:
- [ ] Create templates for common incident types
- [ ] Set up monitoring to detect issues within 2 minutes
- [ ] Train your team on the information hierarchy
- [ ] Practice translating technical issues into customer impact
- [ ] Review your status page on mobile
- [ ] Set up automated alerts for customers
- [ ] Plan your post-incident communication process
The Bottom Line
Your customers aren't asking for perfection. They're asking for respect - respect for their time, their business, and their intelligence. When you communicate clearly during outages, you're not just reducing support tickets. You're building the kind of trust that turns frustrated users into loyal advocates.
Remember: every outage is an opportunity to show your customers who you really are. Make sure you're showing them a company that has their back, even when things go wrong.
🚀 Keep Your Users Informed with StatusRay
Looking for a powerful status page solution? StatusRay helps you:
- Create beautiful, customizable status pages
- Monitor your services automatically with uptime, SSL, and keyword monitoring
- Keep users informed across multiple regions Create your free status page today - No credit card required!
Top comments (0)