📘
New Ebook: SharePoint alone, or SharePoint + Jint? Find out.
Learn more
📘
New Ebook: SharePoint alone, or SharePoint + Jint? Find out.
Learn more
📘
New Ebook:  SharePoint alone, or SharePoint + Jint?.
Learn more
📘
New Ebook: SharePoint alone, or SharePoint + Jint?
Learn more

Cyberattack: reaching staff without email

Florian Bouron
Florian Bouron
October 5, 2026
Cyberattack: reaching staff without email
Cyberattack: reaching staff without email
Cyberattack: reaching staff without email

Table of content

If email went down tomorrow at 8 a.m., how would your staff know what to do by 10 a.m.?

In March 2024, city systems and phone lines in Hamilton, Ontario, were hit for weeks (Canadian Centre for Cyber Security, 2024). In La Rochelle, France, an attack forced four weeks of work "with pen and paper", with 53 of 150 servers infected (French Senate, 2021). On the first morning, the problem is not the message, but the channel.

Recovery often takes several weeks, sometimes several months (ANSSI and CDSE, 2021). This guide helps chief executives, internal communications leads, IT directors and CISOs prepare a fallback channel that holds over time, and a protocol tested every year.

What's inside this guide:

  • The day nobody gets the email: why a council under attack first loses touch with its staff, based on the cases of Hamilton, La Rochelle and Villers-Saint-Paul.
  • Three outages, three sets of channels: three questions to assess the outage with IT within the first hour, and a matrix of the likely state of each channel in each situation.
  • The channel before the message: five criteria for choosing the alert channel, then a fallback channel for each audience, from office staff and field crews to care homes and elected officials.
  • The five-step protocol: from the alert to the debrief, each step with an owner, a deadline and an exit criterion, along with roles, deputies and the incident log.
  • Ready in thirty days, tested every year: a four-week plan, the emergency contact list and its personal data rules, three Microsoft 365 settings and the annual tabletop exercise.
  • Where a mobile channel fits: what an app connected to the intranet brings in situations 1 and 2, and why it does not replace the alert outside Microsoft 365 in situation 3.
  • Two printable tools: the 8 message templates, from the initial alert to the return to normal, and a 12-point continuity checklist.

Why download it:

A protocol ready for your continuity plan. The five steps, the roles and the incident log add a chapter on internal communications to your business continuity plan.

Messages written before the crisis. The eight templates follow the FACET method of ANSSI, the French cybersecurity agency, and field staff can review them now, so that nobody has to write them on the morning of the outage.

A realistic view of each channel. The guide shows which channels remain usable in each situation, and why only a channel outside Microsoft 365 holds when that environment is compromised.

Criteria to test the setup. The tabletop exercise sets three success criteria: the situation assessed within one hour, the first message sent within two hours and 90% of managers reached within three hours.

3

outages that leave different channels available

5

protocol steps, each with an owner, a deadline and an exit criterion

8

message templates ready to send, from first alert to back to normal