Crisis Communication Basics: What to Say (and Not Say) When Your Business Is in the News for the Wrong Reasons

05 September 2026·5 min read

Quick answer: When your business is suddenly in the spotlight for the wrong reasons, speed matters more than polish — a short, honest holding statement within hours beats a perfect statement three days later. Say what you know, what you're doing about it, and when you'll update people next. Don't guess at facts you don't have yet, don't get defensive, and don't let it go straight to a lawyer with no one speaking plainly on your behalf. 🚀

Every business thinks a reputation crisis is something that happens to someone else, right up until a bad experience goes viral on local Facebook groups or a mistake ends up screenshotted and shared a thousand times. The businesses that come out the other side intact aren't the ones with the best legal team — they're the ones who said something true, said it fast, and didn't disappear. Silence reads as guilt even when there's none 💖, and that's the trap most small businesses fall straight into, simply because nobody had a plan before they needed one.

What most businesses get wrong

The most common mistake is going quiet while "getting the facts straight," which can take days — and during those days, the story gets written entirely by other people. A short acknowledgement that you're aware and looking into it costs you nothing and buys real time. The second mistake is the opposite extreme: reacting fast but sloppily, speculating about causes or blame before anyone actually knows, which then has to be walked back publicly and looks worse than the original issue. The third, and most avoidable, mistake is letting the first public words be written entirely by a lawyer — legally safe language that reads as cold, defensive, and evasive tends to escalate a crisis rather than contain it.

The holding statement template — fill this in and you have something publishable within the hour, before all the facts are confirmed:

"We're aware of [brief, factual description of the situation — no blame, no speculation]. We take this seriously and are looking into it now. [One sentence on the immediate action being taken, if any exists yet — e.g. "we've paused X while we confirm what happened."] We'll share an update by [specific time or date — always give one, even a rough one]. If you've been affected, please [contact method]."

Before it goes out, check:

Has one person been named as the only spokesperson? (Avoid multiple staff replying differently in comments.)
Does it avoid blaming a customer, a staff member, or a third party before anything is confirmed?
Does it give an actual next update time — not "soon," an actual time or date?
Has anyone who might be legally exposed reviewed it for accuracy, without being allowed to rewrite it into legal jargon?

A booking-based business where a scheduling mistake went viral: a double-booking error left a customer stranded and they posted about it with photos. The business replied within two hours with a holding statement acknowledging the mix-up, confirmed a fix was already being offered to that customer, and posted an update the next morning with what changed in their booking process. The post stopped trending locally within a day, not because the mistake didn't matter, but because the business visibly owned it fast.

A B2B firm facing a service outage affecting several clients: instead of waiting for a root-cause analysis before saying anything (which would have taken two days), the firm sent affected clients a holding email within three hours: aware, investigating, an update by end of day. That single email meant zero clients escalated publicly while the technical team finished the actual fix.

A local seasonal business hit by a false accusation online: a post falsely claimed the business had done something it hadn't. The instinct was to fire back defensively in the comments. Instead, one calm public reply stating the facts, an invitation to discuss it directly, and no further engagement in the comment thread let the situation cool instead of escalating into a pile-on.

The first-24-hours process

Hour 0–1: confirm one spokesperson, pull together what's actually known (not assumed), and get the holding statement out.
Hour 1–6: monitor where it's spreading (reviews, socials, direct enquiries) and reply consistently everywhere with the same core message — don't improvise different versions per platform.
Hour 6–24: confirm the facts properly, decide on any concrete action, and publish the promised update on schedule, even if the update is "still investigating, next update by [time]."
After 24 hours: once resolved, a short, honest close-out post (what happened, what changed) tends to land better than pretending it never occurred.

💡 This covers reputational and PR-type incidents, not genuine emergencies. If anyone's safety is at risk, that's a job for emergency services and your actual safety protocols first — communications come after, not instead of.

Mistakes to avoid

Going silent while you "figure out the full picture" — a short acknowledgement costs nothing and buys time.
Letting multiple staff respond differently across comments and DMs.
Speculating about cause or blame before it's actually confirmed.
Letting a lawyer's first draft become the public-facing statement without a plain-language pass.
Promising a resolution timeframe you're not actually confident you can hit.

Frequently asked questions

Should we delete negative comments or posts about the incident?

Generally no — deleting comments (as opposed to genuinely abusive or false ones) tends to look like you're hiding something and can reignite the story. Responding openly usually serves you better than removing the evidence you responded at all.

Do we need a lawyer involved at all?

For anything with real legal exposure, yes, get advice — but keep the lawyer reviewing for accuracy and risk, not writing the public voice. The best outcomes come from legal sign-off on a human-sounding statement, not a legal statement with a human gloss.

What if the story is genuinely our fault?

Own it plainly. Vague non-apologies ("we regret that some customers felt...") are usually spotted immediately and do more damage than a direct "this was our mistake, here's what we're doing about it."

Does this apply to a genuine emergency, not just a PR problem?

No, and that's an important limit — this framework is for reputational incidents. A safety emergency needs your actual emergency protocols and the relevant authorities first; communications support that, they don't replace it.