On Thursday 12 November a business with its email at Microsoft could not send a message, and for most of them that also meant it could not tell anyone it could not send a message. We wrote up what happened. This is the list we would hand a client the week after one.
Five of the six need no new software. They are a matter of deciding, on a quiet day, where small things live. The times below are our estimates.
The rule: nothing you need on the bad day lives in the thing that failed
Many businesses keep their mail, their calendar, their chat and their address book with one supplier. That is sensible and we would not tell anyone to split it up. The risk is keeping the fallback there too, which is easy to do: the customer phone numbers in Outlook contacts, the staff rota in a shared mailbox, the “how to reach us” page that says only “email us”.
What fails together, and what does not
Four things most businesses keep with their email provider, and four worth keeping outside it.
The left column fails together, because it is one service. The right column is cheap, and none of it depends on the left.
The National Cyber Security Centre says the same thing in its guidance for organisations whose systems have been disrupted: set up “alternative mechanisms for communicating with staff, stakeholders and customers”. It wrote that for cyber attacks. It applies just as well when the supplier has broken itself.
The six things
What you are allowed to send customers
Owners hold back from texting or emailing customers from a second address because they worry about marketing rules. The Information Commissioner’s Office draws the line clearly. A message sent “for administrative or customer services purposes” is a service message, not marketing. By our reading, “Our email is down, your order is unaffected, ring this number” is one: it tells people how to reach you about a problem and sells nothing.
The line is crossed the moment you add a promotion. The guidance is blunt that a message with any marketing in it counts as marketing as a whole, even if that was not its main purpose. So no “while you are here, 10% off”. Say what has happened and how to reach you, and stop.
One caution of our own, which is not from that guidance: send only to customers who would expect to hear from you. An outage is not a reason to message everyone who ever filled in a form.
What you do not need to buy
You do not need a second email system on standby to catch incoming mail. The standard email runs on advises the sender’s server to keep trying, waiting at least 30 minutes between attempts, for at least four to five days, and Microsoft said service was back for the last customers on the Saturday, the third day. Most mail sent to you should arrive late, not never. What you cannot recover is the days in which nobody could reach you and you could not say why.
So spend the effort on the outgoing half: the notice, the list, the form. A notice only helps if customers can find the site it sits on. When we checked 5,599 UK business homepages against Google’s own advice, only 27% passed six basic checks together.
What we do about it for our own clients
Two of the six are things we build, so here is how, plainly.
The quote form on zxn.uk saves each request to our own record first and gives that save four seconds. Then it sends the email, then a short alert to us. The visitor sees “sent” if the email or the alert got through, and a failed save never stops either. The enquiry form on a client site we look after works the same way round: the enquiry is written to the site’s own record before any email is sent. So when a mailbox is down, the enquiry is still on record.
The sites themselves are served from Cloudflare, so an outage at Microsoft does not take a site or its form down. If the client’s mailbox is at the provider that failed, the notification email waits, and the saved enquiry is still there. The honest other half: if Cloudflare has a bad day, the site and the form are down together, and we have written about that risk too.
What we do not sell today is a standby service that takes over a company’s customer messages when its provider fails. This week made the case for one, and we are working out what it would have to do to be worth trusting. We will write that up when there is something real to show.



