Emergency Words: What to Write to Your Clients When You Don't Yet Know a Thing

It's 8:12 on a Tuesday morning in Portici. The air is that thick, heavy kind — salt-laden and damp, rising up from the harbour, a veil that wraps itself around the buildings and makes everything feel slightly out of focus. I'm sitting at my usual table outside the bar beneath the office, the one with the slightly chipped marble top that smells of strong coffee and freshly baked cornetti. The ritual never changes: the clink of a teaspoon against porcelain, the first bitter sip, the morning light catching the windscreens of passing cars.

I pull out my phone for the usual distracted glance at my emails, but this time the screen doesn't give me back the reassuring list of unread newsletters and inconsequential social notifications.

The screen shows eleven messages. Eleven WhatsApp notifications, all arrived in the last twenty minutes. And they all have the same collective sender, even if the names are different: the anxiety of my clients. The question is just one, expressed across various shades of urgency: "Umberto, why is the site down?", "I can't send emails, what's going on?", "The management system's crashed, we've got customers queuing, help us." I feel my stomach tighten into a cold knot — a physical sensation, almost electric, starting in the pit of my stomach and rising up to my throat.

My brain goes into overload. I'm trying to run three calculations at once while staring at the screen: how bad is the damage? Who else already knows? What on earth am I about to write to these people? In that moment, you're completely exposed — naked in front of your own professionalism. It doesn't matter how many successful campaigns you've signed off on or how many awards are gathering dust on your shelf; at that precise instant, you're just a person holding a phone with a crisis hammering at the door. And the most frightening thing isn't the technical fault — that, somehow, gets sorted — it's the void. That radio silence between discovering the problem and finding the solution, a suspended stretch of time during which a company's reputation can burn faster than a match dropped in a haystack.

This article isn't about managing a complex business crisis over the long term. It's not a PR manual for multinationals with legal departments the size of football stadiums. It's about what to write in those first, wretched hours, when the crisis is still an unopened box that nobody's had time to look inside. When your technical team is entirely occupied trying to work out whether the server's blown up or someone's simply unplugged something, and you — the owner, the manager, the consultant — still have to respond to those messages. Right now. Before the eleven messages become twelve, then twenty, then a public thread on Google or a scathing review on Facebook.

Silence, in that moment, feels like the safest choice — a way to avoid committing yourself until you have some certainty. But let me say this plainly, as someone who's been there: silence is a short fuse. In the absence of your words, the client will use their own. And theirs will almost certainly be worse than reality.

The most dangerous moment isn't when the crisis hits. It's right after.

There is a precise instant when a technical hitch transforms into a reputational disaster. Not the moment of the breakdown, but the moment of perception. In my experience — both here in Italy with Campanian SMEs and in more structured contexts in Manchester or London — I've noticed that the actual severity of the problem takes a back seat to how the initial communication is handled. The client can forgive a server going down; what they can't forgive is the feeling of having been abandoned in the dark whilst their business takes a hit.

The critical window of the first hour

In my experience — and in that of anyone who's ever managed a crisis, from the owner of a bespoke tailoring shop in Santa Maria Capua Vetere to a creative agency in Hackney — there's a window of time that opens immediately after the fault occurs. I call it "the critical window." It's the span of time during which the client is still willing to give you the benefit of the doubt, to think that "these things happen." In practice, this window lasts between twenty and forty minutes from the first report. I've seen it hold with almost geometric precision across dozens of different situations. It's not a rule written up in an academic paper — it's a field observation, repeated enough times to deserve respect.

Once this limit passes without any official communication from you — even a minimal one — the consumer psychology shifts dramatically. The client stops being an understanding partner and becomes a frightened detective. The mechanisms of what cognitive psychology researchers call narrative vacuum start to take hold: in the absence of reliable information, human beings tend to fill the gap by constructing their own version of events. And because we're wired for survival, our brains fill that void with the most catastrophic scenarios imaginable. If your site is offline and you say nothing, the client doesn't think there's an update running — they think you've gone bust, done a runner with their data, or that a cyberattack has wiped your entire database. The self-generated narrative is almost invariably worse than reality, and once it takes root, eradicating it takes ten times the energy that would have been needed to prevent it with a simple "we're on it."

The specific problem facing SMEs

In a large company, a crisis follows pre-established tracks. There's a press office, a social media manager who knows exactly what to post, a customer care team with holding messages already prepared. In our SMEs — whether they're in Caserta, Santa Maria Capua Vetere, among the industrial units of the Agro Aversano, or in the creative districts of Hackney and Salford — the reality is brutal and solitary. In that moment of crisis, the business owner is a tightrope walker on a very thin wire: trying to ring the technician, managing suppliers to work out who's responsible, trying to calm the partners, and simultaneously trying not to completely lose it.

In this scenario, communication with the client is often demoted to "something to do once we've sorted it." That's a fatal mistake. Communication isn't the last piece of the puzzle — it's the glue holding the puzzle together whilst you're still trying to assemble it.

Two opposite mistakes, same result

When managing a crisis, SMEs tend to oscillate between two equally damaging extremes. On one side, active silence: the choice not to respond until you have all the answers. On the other, the improvised response: a post dashed off in haste, with the wrong tone, or — gravest of all — a reckless promise: "We'll be back online in ten minutes," when the technician has just told you it'll take hours.

The point isn't to choose between staying quiet and making things up. There's a third way: the honest communicator who knows how to define the boundary between what can be said now and what will be said in an hour's time. It's the art of managing uncertainty without passing the panic on.

I watched a company lose 60% of its clients in three days. Here's what really happened.

I want to tell you a story that left a mark on me and changed the way I think about copywriting for emergencies. A few years back, I was working closely with a web hosting company from Friuli. It was a solid outfit, built from the passion of a man I'd describe as "prickly by nature" but technically a giant. One of those Friulani who don't say much but work sixteen hours a day — someone I'd built a genuine friendship with, founded on mutual respect. His infrastructure hosted hundreds of websites, e-commerce databases, and email services for clients all over Italy.

The relationship was excellent. There was trust, a history of prompt interventions and shared technical successes. Then the moment zero arrived.

The fault wasn't his. It was everything that came after.

A team of council workers, carrying out roadworks kilometres away from the site, cleanly severed the main fibre optic cables serving the entire district. In an instant, hundreds of companies were plunged into digital darkness. It wasn't my friend's fault. It was an external, unforeseeable event. In itself, the fault was manageable: you just had to wait for the cables to be repaired or activate the backup lines. What happened next, though, was not manageable.

The sequence of errors: minute by minute

The scene looked like something out of a thriller, where the tension builds not from what happens, but from what doesn't. While the telecom engineers worked in the street, total silence descended on the hosting company. Sites offline, emails blocked, phones ringing out. My clients started ringing me. "Umberto, what's going on?" I was trying to ring him, but he wasn't picking up. He was dealing with the emergency, yes — but he was making the active silence mistake.

While he said nothing, the vacuum filled. On national technical forums, the first posts started appearing. With no official communication, people began constructing their own narratives. "The company's gone under," someone wrote. "There's been a hack and they've lost all the data," added another. But the detail that stung most was the direct cannibalism. On the company's official Facebook page, left unattended, competitors without a shred of scruples started leaving comments: "Your sites are offline? That's down to this unreliable company. Come to us — we'll migrate everything in 24 hours and give you a discount." All of this was playing out in front of the frightened clients, beneath posts that celebrated — the irony — the "maximum reliability of our servers."

When he finally responded, he did so in the worst possible way. Exhausted and stung by the criticism, he wrote an aggressive, combative post. "This isn't our fault — it's the council workers. Instead of moaning, have a bit of patience." He used complicated technical jargon to explain why the backup systems hadn't kicked in, but his own engineers, in separate parallel threads, were giving slightly different versions. Every response fuelled new questions; every denial opened a new front.

There was also a technical detail that made everything worse — one we only discovered in that chaotic phase. A backup line existed, with a different provider. It seemed like salvation. Except that this line also ran through the same conduit whose cables had been severed during the roadworks. The backup was redundant on paper, not in the physical reality of the cables under the tarmac.

The solution identified in the chaos was to find a wireless connectivity provider — satellite or WiMax — sign an emergency contract, and activate a line completely independent of the damaged physical infrastructure. The decision was the right one. But it was precisely that attempt to bring the hosting company back online that brought the other problem to the surface — one that had been lurking for years.

The hosting company, over the years, had become more complicated than NASA. Every engineer who'd ever passed through had added their own line, their own diagram, their own piece of logic. Double redundancies, triple redundancies, cables starting in one place and ending somewhere else with nobody quite sure why. When they tried to connect the new wireless line, nobody could work out where certain circuits started, where they went, or what they were feeding. A labyrinth without a map. In the end, faced with the impossibility of making sense of it all, the most painful decision was taken: recable the entire thing from scratch. Bit by bit, with further expenditure of time and energy, while he was still there — surrounded by cables strewn across the floor — simultaneously responding and arguing on the phone, in chats, on social media, on forums.

How we stopped the bleeding

That's when he rang me. He was a broken man. "Umberto, I'm losing everything." At that point we took communication in hand. We stopped looking for excuses or someone to blame, and started publishing clear updates every hour, with the exact status of the work. Not "we're resolving the issue," but "the repair team is on site — 40 out of 100 cables have been spliced." Honest estimates, even when they were grim: "We won't be back online before tomorrow morning." A firm tone, never defensive.

We couldn't save everyone. Many clients had already migrated elsewhere, terrified by the uncertainty of the first two days. But we stopped the bleeding. And we isolated those trying to poach the client base with targeted legal responses — a decisive tone, never aggressive — turning the attacks into proof of the resilience of someone who, despite the disaster, was still standing there and putting their face on the line.

The number that says it all

The final tally was brutal: 60% of clients lost in three days. Not because of the technical fault — which was resolved within 48 hours — but because of the communication. The clients who had decided to migrate all told me the same thing: "We would have stayed if only you'd told us straight away what was happening." Those three days of silence and wrong responses had been perceived as a betrayal of trust. The words he hadn't written cost more than the severed fibre optic cables.

The 4 phrases that pour petrol on the fire — and why we say them anyway

When we're under pressure, our language regresses. We take refuge in formulas we've heard a thousand times, convinced that a certain "corporate tone" will protect us. In reality, those are precisely the phrases that fan the flames.

Phrase 1: "This isn't our fault"

A natural defence mechanism. And it's true — often it really isn't your fault. But the client doesn't care one bit about fault. When they read "this isn't our fault," what they hear is: "I don't care about you — I'm just trying to save my own reputation." You and the client are on opposite sides: they have a problem, and you're distancing yourself from it.

The correct version: explain the event objectively, without assigning blame. Focus on what you're doing to remedy the situation, regardless of who was initially responsible.

Phrase 2: "We're working to resolve this as soon as possible"

The most overused and most useless phrase in the history of crisis communication. A shield-phrase containing absolutely no real information. What does "as soon as possible" actually mean? Five minutes? Three days? To the client, it sounds like a statement drafted by a legal department to buy time.

The correct version: be specific, even when the news is vague. "Our engineers have been on site since 9:30 and are currently testing the backup line" is infinitely better than "we're working on it." Specificity creates the perception of control, and control reduces anxiety.

Phrase 3: "The problem is almost resolved"

We say it because we're desperate to give some good news. But if the "almost" then stretches into another three hours of waiting, you've destroyed your credibility. The second disappointment is always far more damaging than the first, because it adds to the anger the feeling of having been taken for a ride.

The correct version: estimates with an explicit margin of error. "We estimate we'll be resolved by 6pm, but to be on the safe side please allow for the possibility it may extend into the evening. We'll update you at 5pm regardless."

Phrase 4: "We apologise for any inconvenience caused"

The problem isn't the apology. The problem is delivering it with this bureaucratic, sterile formula. "Inconvenience" is a word that minimises. If an e-commerce site loses ten thousand pounds in sales because it's been down, that's not an "inconvenience" — it's a financial loss. If a solicitor can't file a document because their email isn't working, that's not an "inconvenience" — it's a professional risk.

The correct version: name the specific thing. "We apologise for the hours during which your services were unreachable" is real and honest. It acknowledges the seriousness of what happened instead of hiding it behind the kind of adjective you'd expect from a train delay announcement.

The 3-phase language protocol: Acknowledge – Reassure – Resolve

To avoid falling into the trap of tired phrases, you need a method. At Insight ADV we use a protocol we call ARR. It's not about creativity — it's about the architecture of communication. It exists to give the client what they need, in the order in which they need it.

Phase 1: ACKNOWLEDGE

This is the most important phase and the one almost everyone skips. Before explaining what you're doing, you need to show the client that you understand what they're going through. Name the problem explicitly, without minimising it. If you write "we're experiencing a minor technical hitch" when nothing is working, the client will think you're either incompetent or haven't grasped the gravity of the situation.

Language ingredients: concrete verbs such as "we know," "we can see," "we've received your reports." A specific reference to the problem: "We know that since approximately 8am this morning your sites have been unreachable." A precise timestamp. This tells the client: I'm looking at exactly the same thing you are.

Phase 2: REASSURE

Once you've acknowledged the problem, you need to demonstrate that action is under way. The client needs to "see" the action happening. It doesn't matter if it's a small action — what matters is that it's real and verifiable. You don't need to promise the final solution if you don't have it yet; you need to promise a process.

Language ingredients: concrete subjects ("our engineers," "I personally"), specific actions, and — crucially — a declared update schedule. "We'll update you every two hours, even if there's no significant news." This removes the anxiety of passive waiting from the client. If they know you'll post something in two hours, they stop obsessively refreshing the page every thirty seconds.

Phase 3: RESOLVE (or begin to resolve)

The final phase indicates the next step. It doesn't have to be "the problem is resolved" — it just needs to be "here's what happens next." It could be the next update, the next point of contact, or a specific action the client needs to take.

Language ingredients: a precise time reference, the channel for subsequent updates, and — where possible — a direct contact for cases of absolute urgency. Knowing there's a number to ring "if it's genuinely urgent" dramatically reduces the number of people who ring for non-urgent reasons.

Brand case studies: when it worked and when it didn't

To understand the power of words in an emergency, we need to look at those who have played this game on a global scale. The principles are identical whether you're a multinational or a cake shop in Caserta.

NEGATIVE CASE 1: United Airlines, 2017

You'll remember the video of the passenger being forcibly dragged off an overbooked flight. A global disaster. The first response from CEO Oscar Muñoz was an internal letter to staff in which he described the victim as "disruptive and belligerent." Muñoz assumed the internal communication would stay internal. In 2017, nothing stays internal. The letter always gets out. The next day's headlines were written before the papers even went to print, and United's share value took a severe knock within 24 hours before the slow recovery began.

The lesson: the tone of internal communications always leaks out. In a crisis, write every email and every message as if it could end up on the front page. Because it can.

NEGATIVE CASE 2: Samsung Galaxy Note 7, 2016

When the phones started exploding, the initial reaction was denial, followed by a partial admission, then a limited recall, and finally a total withdrawal of the product from the global market. Every step arrived days behind public perception.

The lesson: minimising a real problem doesn't reduce it — it amplifies it. When the truth eventually surfaces — and it always does — it's magnified by the contrast with your initial reticence.

POSITIVE CASE 1: KFC UK, 2018 – FCK

In 2018, KFC ran out of chicken in almost all its restaurants across the UK due to a logistics problem with its new supplier. A farcical disaster for a chain that sells, well, fried chicken. The response was masterful: a full-page spread in the major British newspapers featuring the iconic KFC bucket with the letters of the logo rearranged to spell "FCK."

The detail that makes this story even more useful for SMEs: the campaign was developed by the agency Mother London and approved by management in a matter of hours. It wasn't a lucky improvisation — it was a fast strategic decision, made by people who knew exactly what they were doing. The result? Positive global coverage and articles hailing it as the "best crisis response" in years.

The lesson: an authentic tone — one capable of acknowledging failure, even with a wry smile — builds more trust than any formal press release. And the speed of the decision is itself part of the response.

POSITIVE CASE 2: Johnson & Johnson, Tylenol 1982

The absolute gold standard of global crisis communication. Seven people died in Chicago after ingesting cyanide-laced Tylenol capsules. J&J didn't wait to establish whether the fault lay in production or in external sabotage. They recalled 31 million units from the market. They acted before anyone had asked them to — and they did so by publicly declaring that consumer safety came before any commercial consideration. The sabotage was subsequently confirmed — the contamination had occurred after the product had left the factory — but the culprit was never identified.

The lesson: radical transparency, even when it's painfully costly, is the investment with the best reputational return over the long term. Decades on, J&J remains the benchmark that every crisis management manual references.

Berto and Bobby compared

Over the years I've learnt that geography matters. When my client Berto from Caserta suffers a service disruption, his first reaction is emotional. He wants to hear my voice — he wants to know I'm there. If he senses an authentic human connection, he's prepared to forgive almost anything. He'll tell me: "Umberto, I know you're doing everything you can — just keep me posted."

Bobby — my counterpart in Hackney or Salford — reacts quite differently. He wants to see the process. He wants a structured email with an incident report, steps to resolution, and an estimated time of recovery. Bobby doesn't want me to be his mate; he wants me to be a professional with a clear methodology.

Two different cultures, one shared root: both want to feel they're being treated as intelligent human beings, not as a support ticket number in an endless queue.

Ready-to-use templates: what to write on each channel

These templates are not magic formulas to copy and paste without thinking. They're frameworks you need to dress with your own voice. In an emergency, though, having a structure ready prevents you from making the mistakes we've discussed.

The difference between apologising and making excuses

In a crisis, words are like scalpels. The difference between an apology that heals a relationship and a justification that infects it is subtle but vital. A genuine apology looks towards the client; a justification looks towards oneself. Read also ⟶ Don't let "sorry" be the hardest word in your business

The structure of a genuine apology

An apology that actually works must contain three distinct elements:

1. Acknowledgement of the specific event: "X happened."
2. Acknowledgement of the impact on the client: "I know this prevented you from doing Y."
3. A concrete commitment: "Here's what I'll do to make sure it doesn't happen again."

If any of these elements is missing, it's not an apology — it's an empty pleasantry.

The justification dressed as an apology

The most common case: "We apologise for any inconvenience caused by circumstances beyond our control." Let's analyse it word by word. "Circumstances beyond our control" is a way of saying: it's not my fault, so you can't hold it against me. But the client doesn't care whether it was in your control or not — they're paying you precisely because you're meant to manage those variables on their behalf.

The Friuli case: before and after

The starkest comparison I can show you comes directly from the story of the Friuli hosting company. In the first few days, the owner's self-managed communication sounded like this:

 Same technical incident. Same facts. Completely opposite perception. That is the power of words chosen with precision under pressure.

The follow-up after resolution: closing the loop

The last great mistake SMEs make is going quiet the moment the problem is resolved. Once the light turns green and the site is back online, silence descends. The business owner breathes a sigh of relief and returns to their daily routine. But the client is still there, with a bitter taste in their mouth from the hours of anxiety they've just been through.

The closing communication is what transforms a service disruption into an opportunity to build loyalty. It needs to serve three functions:

• Informative: confirm that everything is resolved and explain, in plain terms, what was done.
• Relational: acknowledge the experience the client has just been through. Saying "sorry for the inconvenience" isn't enough — you need to say "thank you for staying with us through such a difficult day."
• Prospective: indicate what has been put in place to ensure that specific problem doesn't happen again.

The difference between a formal close and a human close

The 48-hour follow-up: small gesture, big impact

One technical distinction that many overlook: the 48-hour follow-up should go out on a personal channel — WhatsApp or a direct email — never as a broadcast. A mass message saying "all sorted" is bureaucratic; the same message sent individually is a human gesture. The difference between the two is felt immediately.

The craft of words under pressure

My mind goes back to that morning in Portici — eleven messages on my phone and a coffee going cold on a chipped marble table.

These days, when a crisis hits, the phone still makes me anxious. But I read those eleven messages differently. I don't see eleven problems. I see eleven people who chose to write to me rather than go looking for someone else. Eleven clients who, in that moment, were still placing a bet on me. That's the real stake in the first hours of an emergency: not the technical fault, but the bet the client has placed on you — one you can choose to honour or to squander.

Emergency writing isn't the finest work you'll do in your professional life. It's not the piece you'll put in your portfolio to win awards. But it's the writing that decides whether those clients will still be yours next week. It's pure craft — worked in millimetres, in weights and counterweights, in chosen silences and words measured against the scales of truth.

And like all craft, you learn it by getting it wrong. You learn it by feeling the weight of responsibility on your shoulders. But you can also learn by watching those who've already walked that tightrope and come out the other side in one piece. Or those who, unfortunately, fell — and left behind a lesson worth having.

In the end, those severed cables in Friuli taught me more than any manual ever could. My friend paid an enormous price for that lesson. I've tried my best not to waste it.