How To Communicate During An Outage

Your system went down at 2pm. It's now 2:45pm. Nobody has heard from you.

Customers are posting on social media. Your sales team is calling the office. Three employees are texting the owner. Two are texting the IT person. One is already on the phone with a competitor.

This is the cost of not communicating during an outage.

What this solves

Reduces customer churn. 65% of customers say they'd leave after a poor outage communication experience. You don't want to be that business.

Prevents internal chaos. Employees stop bugging the IT person every five minutes if they know what's happening.

Manages expectations. People can plan around a 30-minute outage. They can't plan around uncertainty.

Protects your reputation. How you handle a crisis matters as much as whether you have one.

What can go wrong

Radio silence. Customers assume the worst. Social media fills with speculation. Competitors get calls.

Saying "we're working on it" without updates. That's not communication. That's a placeholder.

Over-promising on resolution time. "It'll be fixed in 15 minutes" when you don't know creates worse problems when 15 minutes pass.

Blaming vendors or partners publicly. Venting is fine. Putting it in writing to customers is not.

Inconsistent messages. Owner says 30 minutes. IT says an hour. Customer support says they're not sure. Pick one message and one voice.

What it costs (honest ranges)

Status page tools (Statuspage, Cachet): $30-$100/month for small business plans. Lets customers self-service their questions about status.

Mass notification platforms (Everbridge, AlertMedia): $500-$2,000/month for comprehensive alerting to customers and employees.

Social media monitoring: $0-$200/month for tools like Mention or Hootsuite to track what customers are saying.

PR/communications consultant: $1,000-$5,000 for a single crisis engagement if things get bad enough.

Customer churn from poor communication: Harder to quantify, but studies suggest 15-30% of customers leave after a bad outage experience.

Minimum viable implementation

1. Draft a status update template before you need it. Something like: "[System] is currently experiencing [issue]. We identified the cause at [time] and are [action being taken]. Next update at [time]."

2. Send first update within 15 minutes of confirming an outage. Even if you don't know the cause. Even if you're still investigating. Say you're aware and investigating.

3. Update every 30 minutes until resolved. Same format. Same channel. Consistent and predictable.

4. Resolve the message matches the update. If you say 30 minutes, deliver in 30 minutes. If you can't, send an update explaining the delay.

5. Send a resolution message. Tell people when it's fixed. Briefly explain what happened if known. Thank them for patience.

Vendor questions (copy/paste)

Ask your IT vendor or MSP:

• Do you have a status page for our services?
• Who is authorized to send customer-facing communications during an outage?
• Do you have pre-approved templates we can use?
• Can we integrate your monitoring with our customer communication channels?

Ask your team:

• Who sends external communications? Who approves?
• What channels do we use? Website? Email? Social media?
• What's our escalation path for communications?

When to hire help

You're trending on social media. Beyond your local market. That's when you need communications help.

Multiple stakeholder groups need different messages. Employees, customers, investors, press — each needs a tailored message.

You're not sure what to say. Most SMB owners have never done this. Get a template and some coaching before you need it.

The outage involves a security incident or data breach. This requires specific legal and communications handling. Get specialized help.

---

Customers don't expect perfection. They expect honesty and speed. Tell them what you know, when you know it, and what you're doing about it. That's it.