How to Communicate Website Downtime to Clients

Good client downtime communication matters almost as much as the fix. A site that's down for an hour with a well-informed client is forgotten quickly. One that's down for twenty minutes with no word from you gets remembered for months, and often ends in an awkward conversation about the maintenance retainer.

Here's what to do before, during, and after an outage. No magic templates, just what each message actually needs to contain.

Before anything breaks

The best outage communication is prepared while nothing is wrong.

• Agree on where updates go. Email, WhatsApp, or a status page. What matters is that the client knows where to look instead of guessing.
• Pick one voice. One person or one channel per client. Two people telling different versions creates more doubt than the outage itself.
• Set expectations on response times. Don't promise the impossible, but do say when they can expect to hear from you, during business hours and after.
• Publish a status page before you need it, so the client already knows it exists the day they go looking.

During the outage

The first message matters more than the technical explanation. Sending it fast beats making it perfect.

Every update should answer four questions:

1. What's affected. The whole site, the store, email, or just one part.
2. What we know. No speculation. "We're investigating" is a valid answer while there's no cause yet.
3. What we're doing. One sentence is enough.
4. When the next update comes. Even if there's nothing new. That's what reassures people most.

What to avoid:

• Promising a fix time you don't control. If the cause is your host or registrar, you can't say when it'll be back.
• Blaming a third party in the first message. It may well be the host, but the client cares about their site, not whose fault it is.
• Jargon. "Upstream returning 503" means nothing to a non-technical client. "The site can't serve visitors right now" does.
• Silence. If there's nothing new, say so: "Still working on it, next update in 30 minutes."

After it's resolved

Once everything's back, close the loop properly:

• Confirm it's resolved and since when.
• Explain the cause in plain language, without hiding it or dramatizing it.
• Say what you'll change so it doesn't happen again, if anything needs changing. If it was outside your control, say that too.
• Write it down. A short written summary helps the client, and helps you the next time you review what happened.

How a status page helps

A status page answers "is my site down?" without the client having to email you. In MonitoraWeb, each status page:

• Shows the status of the sites you choose, with an availability bar for the last 90 days.
• Lets you explain incidents in your own words: what happened and how it's going.
• Supports email subscribers with double opt-in, for anyone who'd rather get updates.
• Can be public, private, or password-protected.

On paid plans, it can also carry the client's branding and their own domain with HTTPS. For an agency, that means the client sees a page that's theirs, not a tool's.

What a status page doesn't do is talk for you. Incidents still need explaining, and the client relationship is still yours.

When the client hears about it first

It happens: the client notices before you do. If it does, don't gloss over it. Thank them, confirm you're on it, and say when you'll follow up. Afterward, figure out why you didn't know first. It's almost always an alert channel nobody watches, or a site that wasn't being monitored.

Everything status pages can do is on branded status pages.

Frequently asked questions

When should I tell a client about an outage?

As soon as you've confirmed the outage is real and affects something they care about. You don't need to report every one-minute blip, but you should report anything that drags on or affects sales or email.

What do I say if I don't know the cause yet?

That you're investigating, what's affected, and when the next update will come. That beats speculating.

Should I give an estimated fix time?

Only if you control it. If it depends on your host or registrar, commit to the time of the next update instead.

Does a status page replace notifying the client?

Not entirely. It saves them from asking, but incidents still need explaining and the conversation is still yours.

Can the status page carry the client's branding?

Yes, on paid plans, with their own domain and automatic HTTPS.