2026-04-05 · Pinger Team
How to Tell a Client Their Site Went Down Without Losing the Account
The right way to communicate a website outage to clients — what to say, when to say it, and how to turn a crisis into a trust-building moment.
A client's site goes down at 3am. By the time you see the alert, it's 6am and they've already gotten three emails from users complaining.
The site comes back up at 7am. Now you need to tell them what happened.
Most freelancers handle this badly. They send a vague email, blame the hosting company, and hope the client doesn't fire them.
Here's the right way to do it.
Why Clients Actually Fire Agencies After an Outage
Before we talk about communication, let's address why clients get upset. It's almost never about the outage itself. Sites go down. It happens.
They're upset because they found out from their users instead of from you. Or because you didn't communicate during the incident. Or because you sent a vague apology that didn't actually explain anything.
The underlying fear: "If this agency can't handle communication during a crisis, how do I know they'll communicate during a normal project?"
Your job during an outage — and the 24 hours after — is to prove the answer is: they'll communicate better than most.
The Outage Communication Template
Use this structure every time:
1. Lead with what you already know (not what you're still investigating)
Wrong: "We're looking into an issue with your site." Right: "Your site went down at 2:47am. We detected it at 6:02am and restored service at 7:11am. Total downtime: 4 hours, 24 minutes."
The second version tells your client you were watching. You found it before they did. You're on top of it.
2. State the cause in plain English
Wrong: "There was a server infrastructure issue." Right: "The hosting provider's database server failed unexpectedly. This caused your site to return errors for all visitors."
If you don't know the cause yet, say: "We're still determining the exact cause and will update you by [specific time]."
3. State what you did about it
Wrong: "We're working to resolve this." Right: "We restarted the database server at 7:08am and the site came back at 7:11am. We've also set up monitoring to alert us within 5 minutes if this happens again."
4. State what you're doing to prevent it
Wrong: "We're taking steps to prevent this from happening again." Right: "We've added automated database monitoring and a 5-minute alert. If the database server fails again, we'll know within 5 minutes instead of 3 hours."
5. Offer something concrete
A free month of hosting. An expedited feature delivery. A 30-minute strategy call to review their infrastructure. Something small that shows you're thinking about their business, not just covering yourself.
The 24-Hour Rule
After an outage, send your first communication within 24 hours — even if you're still investigating.
An email at 8am the next morning is better than silence. Here's a template:
Subject: [URGENT] Your site experienced an outage — resolved
Hi [Client Name],
Your site (www.[domain].com) went down at [time] this morning. We detected the issue at [time] and restored service at [time]. Total downtime was [duration].
The cause was [plain English explanation]. We're [preventive action] to make sure this doesn't happen again.
Your site's current status: [link to their status page]
We're happy to jump on a call today if you'd like to walk through what happened. You can book directly here: [calendly link]
Sorry for the disruption — we take uptime seriously and we're treating this as a priority.
This email does something powerful: it proves you have a status page, you caught it before they did, and you're being proactive about prevention.
How to Set Up Proactive Communication Before an Outage
The best outage communication happens before the outage. Set up your client's status page now, before anything goes wrong.
Send your client their status page URL and say:
"We've set up a monitoring tool that watches your site 24/7. If anything ever goes wrong, your status page at [URL] will update automatically. You can check it any time, or we'll send you an alert."
Now when an outage happens, you send one message:
"We're aware of the issue and actively working on it. Updates at [status page URL]."
You don't have to write a long explanation. They can see the timeline. You're in problem-solving mode, not customer-service mode.
What to Do If You Miss the Outage (And They Tell You First)
This happens to everyone. You missed the alert, the client called you, and they're already upset.
The right move: acknowledge it, apologize specifically, and give them a timeline.
"You're right — we missed this alert and that's on us. We should have caught it within 5 minutes. We've since [what you did to fix the immediate issue]. Here's what we're doing to make sure the next alert reaches us: [specific change]. And here's [compensatory gesture]."
Don't make excuses. Don't blame the tool. Own it and fix it.
How to Turn an Outage Into a Trust-Building Moment
This sounds counterintuitive, but the agencies that have the strongest client relationships are the ones that communicate well during outages.
A client who gets a status page, proactive alerts, and a clear incident timeline — even during a stressful outage — leaves the experience trusting you more than they did before. Because they know you have systems, you communicate clearly, and you don't make excuses.
The agencies that get fired after an outage aren't the ones that caused the outage. They're the ones that went silent, sent vague emails, and made clients feel like they were being managed instead of informed.
The Status Page Checklist (Send This to Every New Client)
When you start working with a new client, set up their status page on day one and send them this:
"Your site is now monitored 24/7. If anything goes wrong, you'll be able to see the status at [status page URL]. We'll also send you an alert if there's an incident.
Bookmark this page — it's where you'll always find the most current information about your site's status."
This is the foundation of good outage communication. You never have to explain the status page during a crisis because they've already seen it.
The Bottom Line
Clients don't fire agencies because sites go down. They fire agencies because sites go down and nobody communicates.
The investment is minimal: set up monitoring, create a status page, send one onboarding email, and write one clear incident report when something breaks.
Do this consistently and you'll find that clients trust you more after an outage than they did before — because they know you have systems, you communicate clearly, and you've thought about their experience.