← Back to blog

How to Write a 'We Made a Mistake' Post Before Someone Else Writes It For You

17 September 2026·3 min read
Quick answer: Own it in one clear sentence, explain what you're doing about it in one more, and stop — don't over-explain or get defensive. A short, direct acknowledgement almost always lands better than a long justification, and it's far better delivered by you, proactively, than pulled out of you after a complaint goes public. ✨

Here's a moment most businesses avoid until they're forced into it 💖: publicly owning a mistake. It feels risky, so the instinct is to stay quiet and hope it blows over. But a mistake that's already visible to customers — a delay, an error, a bad batch — doesn't go away by staying silent. It just means someone else gets to tell that story first.

What Most Businesses Get Wrong

The common mistake is over-explaining — a long, defensive post that reads as justification rather than accountability. The second is waiting too long, so the acknowledgement arrives only after a complaint has already gained its own momentum online, which makes it look reactive rather than proactive.

The Formula

[What happened, plainly] + [what we're doing about it] + [how to reach us if you're affected].

Example: "We got an order wrong for a number of customers this week due to a system error on our end. We've fixed the issue and are reaching out individually to anyone affected. If you think this affected you and haven't heard from us, please reply here or email [address]."

No excuses, no lengthy technical explanation — just the facts and the fix.

A booking-based business that double-booked a busy week due to a system glitch: posts a short acknowledgement within hours, naming the issue and the fix, rather than waiting to see if anyone actually complains publicly — the proactive tone earns visible goodwill in the comments.
A local service business that missed a promised delivery window during a busy season: pairs the acknowledgement post with a direct, individual follow-up to every affected customer, so the public post and the private resolution reinforce each other.

The Mechanics: Timing and Tone

Post as soon as you have the facts straight — speed matters more than polish here. Keep the tone plain and steady, avoiding both over-apology (which can read as performative) and defensiveness (which reads as avoidance).

💡 Short and early beats long and late: a brief, prompt acknowledgement almost always outperforms a longer, more polished statement that arrives after the story's already spread without you.

Mistakes to Avoid

  • Waiting to post until a complaint has already gained public momentum
  • Over-explaining in a way that reads as justification rather than accountability
  • Making promises about the fix that aren't genuinely deliverable
  • Posting once and never following up with affected customers individually

Frequently asked questions

Should every mistake get a public post, even small ones?

No — reserve this for mistakes that are already visible to a meaningful number of customers. Small, isolated issues are usually better resolved individually and privately.

What if the mistake wasn't really your fault (a supplier error, for instance)?

You can note the cause factually, but avoid making it sound like blame-shifting — customers care most about the fix and how they're being treated, not who's technically at fault.

Is it better to delete negative comments while this is happening?

Generally no, unless they breach clear platform guidelines — visible, honest engagement with concerns tends to build more trust than a scrubbed comment section.

How do you know if a mistake is big enough to warrant a public post?

If more than a handful of customers are likely to notice or be affected, or if it's already being discussed publicly, it's worth addressing proactively rather than case by case.


Keep reading 🤍

Share
Written by
Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦