What to Post When Your Website or Booking System Goes Down

05 October 2026·5 min read

Quick answer: The moment your site or booking system goes down, post something — fast, honest, and specific — because silence is what actually damages trust, not the outage itself. A short status update within the first 15-30 minutes, a follow-up if it runs long, and a clear "we're back" post once it's fixed covers almost every outage scenario. Customers forgive downtime; they don't forgive finding out from a failed payment with zero explanation. 📱

Every outage feels like an emergency in the moment, but the actual damage rarely comes from the system being down — it comes from the forty-five minutes of silence while someone tries to fix it quietly before anyone notices 💖. Someone always notices. Post first, fix second.

What most businesses get wrong during an outage

They say nothing and hope it resolves before anyone notices, which it rarely does.
They post once, then go quiet for hours while the issue drags on, leaving people assuming it's still broken even after it's fixed.
They get technical and defensive instead of plain and reassuring.
They only post to one channel and forget email entirely, missing anyone who doesn't follow the socials.
They don't say when to expect an update, so people keep refreshing and getting more frustrated by the minute.

Three Outage Templates, by Length

Short outage (under 1 hour) — post within 15-30 min:
"Quick heads up — [website/booking system] is currently down and we're on it. If you were trying to [book/pay/log in], please hold off for now, nothing's been lost on our end. We'll update here the moment it's back. Thanks for your patience 🤍"

Longer outage (1-4+ hours) — follow-up post:
"Update: [system] is still down — we're working directly with [provider/our dev team] and don't yet have a fixed time, but wanted to keep you posted rather than go quiet. If you need to reach us in the meantime, [phone/DM/email] still works and we're actually at our desks. Next update by [specific time]."

Resolved — we're back:
"We're back! [System] is up and running normally again as of [time]. If you tried to [book/pay/submit] during the outage and aren't sure whether it went through, flick us a message and we'll check manually — better safe than sorry. Thanks for bearing with us 💖"

Email version: same three messages, shorter subject lines ("Quick update on [system]", "Still working on it", "We're back — here's what to check"), sent specifically to anyone with an active booking or order in the affected window, not a full list blast.

A booking-based business: had their payment processor go down on a Saturday — their busiest booking window of the week. Rather than waiting to see if it resolved itself, they posted the short-outage template within twenty minutes, specifically naming that bookings could still be made and paid for by phone. People who saw the post before trying to book switched to calling instead of hitting a broken checkout and giving up entirely — a saved booking is worth a lot more than a silently broken page.

A B2B firm: had their client portal go down for several hours while multiple clients had document deadlines looming. Instead of one social post most of their clients never saw anyway, they sent the email version directly to everyone with an active matter in the portal, naming the issue plainly and giving a specific next-update time. Clients who'd normally have escalated a "why can't I log in" complaint to their main contact instead just waited, because they'd been told exactly when to expect the next word.

A seasonal business: had their site crash under traffic during their single busiest week of the year, right as a time-sensitive promotion was live. They posted immediately, were upfront that the crash came from demand ("you broke our website, in the best possible way"), and gave a realistic timeframe rather than an optimistic guess. Framing the outage honestly, with a touch of humour about the cause, turned a potentially embarrassing moment into something people found charming rather than frustrating.

How to actually run outage comms

Assign one person as the comms owner for the duration of any outage, so messaging doesn't come from three people saying three slightly different things. Post to the channel your specific audience actually uses — email for clients with an ongoing relationship, social for consumer-facing bookings, both if you're not sure. Always include a next-update time, even if that update is just "still working on it." Don't guess a fix time you're not confident in — underpromise rather than having to walk it back. And keep whatever post is pinned or at the top of your feed current, so an old "we're down" message doesn't sit there looking live long after you're actually back up.

💡 Write your three templates now, while nothing's broken. The worst time to compose a calm, clear status update is mid-outage, stressed, with customers already messaging you. Save the three templates above as drafts in your notes app or social scheduler right now — swap in the specifics when you actually need them, and you'll post in minutes instead of panicking for twenty.

Mistakes to avoid

Going completely silent and hoping the outage resolves unnoticed.
Over-promising a fix time you can't actually guarantee.
Posting once and never following up, leaving the last update looking stale.
Blaming your hosting provider or payment processor publicly in a way that reads as finger-pointing rather than information.
Forgetting to post the "we're back" update, so people stay cautious long after it's fixed.

Frequently asked questions

Should we apologise in the outage post, or just explain?

A brief, genuine "sorry for the disruption" is enough — you don't need an extended apology for something outside your control, like a third-party processor failing. Save the fuller apology tone for mistakes that were actually yours.

What if we don't know what caused the outage yet?

Say that. "We're still working out what caused it" is a perfectly fine thing to post — it's more honest and more reassuring than staying silent until you have the full technical answer.

Do we need to post on every single social platform?

No — post where affected customers actually look for updates, and where you can keep updating quickly. One well-maintained channel beats five neglected ones during a live outage.

Will good outage comms actually stop people from being annoyed?

Not entirely, and that's worth being realistic about — some people will still be frustrated, especially if the outage cost them a booking or a deadline. What good comms does is stop that frustration turning into distrust. People forgive downtime; they remember silence.

Keep reading 🤍

Written by

Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦