powering productive workplaces
latest
Front page
FeatureUC&C15m · 13:31 GMT · 8 min read

Nine Years After WannaCry, Have We Forgotten the Batphone?

Nine years after WannaCry exposed how little healthcare had planned for losing its usual systems, November's Microsoft 365 outage raised the same question again. Tom Boyle of Sheffield Teaching Hospitals argues that voice is the backup plan too many organizations have neglected.

A black vintage rotary telephone on a wooden counter

In June 2017, following the WannaCry cyberattack that disrupted hospitals and healthcare services across England's NHS, Dr. Joe McDonald wrote an article for Digital Health asking a fairly simple question: where was our Bat Signal?

Joe's point wasn't just about the technology that had failed. It was about how healthcare organizations communicated when the systems they relied upon suddenly weren't available. Who did we contact, how did we reach one another, and did we actually have a plan that worked when our usual communications didn't?

Almost a decade later, the Microsoft 365 outage that began on Thursday, November 12, and ran into Friday, November 13, 2026, brought those questions back into focus.

I happened to be at a healthcare digital leadership conference on the Friday, surrounded by senior digital leaders from across Yorkshire, the Humber and the North of England. As the disruption unfolded, it was interesting to see how quickly conversations shifted. Suddenly, there was a rather noticeable increase in interest in what I do for a living.

Discussions that might ordinarily have centered on AI, digital transformation or the latest technology developments turned toward something more fundamental: how do we communicate when the platforms we've become so dependent upon aren't working?

I spent much of the day discussing what alternatives existed, what could continue operating independently and the role that established voice infrastructure still plays. Later that Friday evening, I found myself having a similar conversation with Paul Ginn, Senior Director, Product & Solutions Marketing at Mitel. We were approaching the issue from different perspectives, mine from the operational realities of healthcare and Paul's from the wider communications industry, but kept returning to the same point. We've made enormous progress in how we connect people, but have we given enough thought to what happens when those connections aren't available?

When everything is connected, everything can be affected

Over the past decade, we've understandably worked toward bringing more of our communications together. Email, instant messaging, meetings, telephony and collaboration increasingly sit within common platforms. It's convenient, familiar and, for the most part, works incredibly well.

But the more we consolidate, the more we potentially concentrate our dependencies. When several critical communications capabilities rely on the same underlying platform, identity service or infrastructure, a single failure can have consequences well beyond the original technology.

An email outage, for example, isn't necessarily just an email outage. In healthcare, many organizations rely on Microsoft 365 services within wider operational workflows, including automated notifications, patient appointment communications and integrations with other systems.

For some, this extends to email and SMS appointment reminders, where the process responsible for generating or delivering a message depends on Microsoft-hosted services or gateways. The SMS provider itself might be working perfectly well, but if the system responsible for passing the message to it has failed, the outcome is much the same. The patient doesn't receive the information they were expecting.

The same dependencies can affect incident coordination, internal alerts and communication between organizations. Even where individual applications remain operational, the processes connecting them may not.

We spend considerable time discussing the resilience of clinical systems, and rightly so. But the communications surrounding those systems deserve just as much attention.

Voice never stopped being critical

There's something revealing about what happens when modern digital communications become unavailable. People reach for the telephone.

For all the progress we've made, voice remains one of the most immediate and familiar ways of reaching someone. Within hospitals, it continues to underpin an extraordinary amount of everyday activity, from patient inquiries and clinical escalation to operational coordination and emergency response.

During a major incident, the ability to establish a telephone conference, contact clinical areas or initiate an emergency communications cascade becomes particularly important. These aren't especially glamorous capabilities, but they're essential to keeping organizations functioning when other systems are unavailable.

This is where on-premises and hybrid voice environments can offer something valuable. Where designed appropriately, core calling and conferencing capabilities can continue operating independently of cloud collaboration platforms experiencing disruption.

That's not to suggest on-premises technology is automatically more reliable than cloud, or that traditional telephone systems never fail. Both approaches have vulnerabilities, and both can be designed with considerable resilience. A telephone system dependent on a single network connection, power supply or external service is still vulnerable, regardless of where its core infrastructure sits.

The important distinction is understanding what depends on what, and making deliberate decisions about where those dependencies should exist. Resilience isn't necessarily about where something is hosted. It's about what continues working when something else doesn't.

Have we confused modernization with resilience?

We talk a great deal about digital transformation in healthcare. Cloud adoption, AI, automation and integrated platforms all have an important role to play. But I sometimes wonder whether, in our enthusiasm to modernize, we've become a little too quick to regard certain technologies as yesterday's problem.

Telephony is a good example. It's often treated as something to maintain until the next transformation program replaces it, rather than recognized as a strategic capability in its own right.

Yet the importance of a technology shouldn't be measured by how new it is or whether it features prominently in the latest digital strategy. It should be measured by what happens to the organization when it isn't there.

This was a common thread in my conversation with Paul. The communications industry has often framed the debate around cloud versus on-premises, as though one must inevitably replace the other. But the more useful discussion is about architectural choice, understanding dependencies and deciding how much risk an organization is comfortable concentrating within a single platform.

Hybrid communications can play an important role in that approach. Modern collaboration platforms have transformed how people work, but retaining independent voice capabilities alongside them can provide an additional layer of resilience. For sectors such as healthcare, public safety and critical infrastructure, that independence can be a deliberate strategic decision rather than a reluctance to modernize.

The communications industry has a responsibility here too. For years, we've encouraged consolidation, simplification and integration, all for understandable reasons. But we should be equally enthusiastic about explaining the dependencies these decisions introduce and helping organizations understand what happens when something fails.

A successful communications strategy shouldn't simply be measured by how well everything works on a normal working day. It should also consider what remains available when it doesn't.

Knowing your Batphone number

Which brings me back to Joe McDonald's article from 2017. Perhaps the most important lesson isn't technological at all. It's organizational.

We can have resilient infrastructure, but it's of limited use if nobody knows how to access it when the usual systems aren't working. An operational telephone system offers little reassurance if the emergency contact directory is sitting in an unavailable cloud service, conference details are buried in someone's inbox or escalation procedures rely on sending an email.

Within healthcare, emergency preparedness and business continuity are familiar territory. We regularly plan for major incidents, infrastructure failures and disruption to clinical services. But how often do we genuinely test our communications arrangements on the assumption that our usual digital tools simply aren't available?

Could we alert clinical and operational teams quickly, establish an incident management conference or coordinate with neighboring organizations experiencing the same disruption? More importantly, would the people expected to do those things know how?

This is where the distinction between the Bat Signal and the Batphone becomes particularly useful. The Bat Signal is how we alert people that something is wrong. The Batphone is how we communicate and coordinate what happens next.

They're different capabilities, and we need both. Neither should depend entirely on the very systems whose failure might require us to use them.

A strategic conversation worth revisiting

I don't think the lesson from November 2026 is that we should abandon cloud technology, reverse digital transformation or start preserving every piece of legacy infrastructure we've ever owned.

Quite the opposite. We should continue modernizing, but with a more deliberate understanding of the resilience implications of the decisions we make. That means recognizing critical dependencies, considering where independent communications capabilities are necessary and ensuring business continuity arrangements reflect how organizations actually operate.

It also means recognizing voice as more than simply another feature within a collaboration platform. For many organizations, particularly those delivering essential public services, it remains a critical operational capability deserving strategic attention, appropriate investment and regular testing.

Nine years ago, Joe McDonald challenged healthcare to consider how it would communicate when the unexpected happened. Nearly a decade later, despite everything that's changed, we're still wrestling with much the same question.

We've become very good at connecting people when everything is working. Perhaps the next phase of digital transformation should place just as much emphasis on how we communicate when it isn't.

Because when the next major disruption arrives, the most important question might not be which platform has failed. It might simply be whether anyone still knows the Batphone number.

Tom Boyle is NHS Digital Communications Leader at Sheffield Teaching Hospitals NHS Foundation Trust.

rate this story
helps rank stories across uc today
Join the conversation

Does this reflect your experience?

opening the room…