Judge whether it was factually wrong, badly judged, or merely unpopular. Correct facts, apologise for judgement, and leave unpopular alone. Deleting without explanation is the option that escalates.

Three kinds of wrong

The right response depends entirely on which of these it is, and they get conflated in the moment.

Factually wrong: a price, a date, a claim, or a detail that is incorrect.

Badly judged: something insensitive, careless, or capable of being read in a way you did not intend.

Merely unpopular: something correct and considered that some people disagree with.

Those need a correction, an apology, and nothing respectively, and the most common error is treating the third as though it were the second.

Decide within the hour

Because the cost of a bad post rises with how long it stands unaddressed.

A correction posted quickly reads as diligence. The same correction three days later reads as a response to pressure.

That does not mean replying instantly to every comment, which is a different question. It means deciding what you are going to do about the post itself.

Where you genuinely need to think, say so publicly in one line and come back within the day.

Silence while something spreads is the option that costs the most, and it is the one people default to while working out what to say.

Correcting a factual error

The easiest case and the one with a clear procedure.

Edit the post where the platform allows it and note that it has been corrected, or post a correction and link it to the original.

Say what was wrong and what is right, without elaborate explanation of how it happened.

Where the error reached people who acted on it, such as a wrong price or a wrong date, contact them directly rather than relying on them seeing the correction.

Honour the incorrect price if somebody acted on it in good faith, which costs less than the alternative and is remembered.

Apologising properly

The second is the one that turns an apology into a defence. Explaining the intention tells people they misread it, which is the argument rather than the apology.

When to leave it alone

The judgement that requires the most nerve.

A post that is accurate, considered, and simply disliked by some people does not need an apology, and issuing one teaches everybody that complaints work.

That includes a post stating your prices, one declining to do something, or one explaining a policy that some customers dislike.

Answer genuine questions in the comments, correct any factual misunderstanding, and leave the post standing.

Where the reaction is loud but small, which it usually is, it will pass within days.

Removing a defensible post because a few people objected produces a business that cannot say anything, which is a worse position than the original discomfort.

A worked example

A business posted a price increase with a short explanation and received a run of critical comments over an afternoon.

Their instinct was to delete it.

The post was accurate, the explanation was reasonable, and the criticism was from people who did not want prices to rise, which is not the same as the post being wrong.

They left it up, answered three genuine questions about what the increase covered, and ignored the rest.

The comments stopped within two days and two existing customers posted supportively.

Deleting it would have required posting the increase again later, from a weaker position, with everybody knowing the first attempt had been withdrawn.

Deleting is sometimes right

Worth being clear, since the advice against it is usually stated too absolutely.

Delete anything that discloses somebody's private information, anything genuinely offensive, and anything that cannot be corrected because the whole premise was wrong.

When you do, say that you have deleted it and why, in a short post, rather than removing it silently.

Silent deletion is what produces screenshots, because it looks like concealment and people who noticed will say so.

Deleting and acknowledging is a complete response. Deleting and hoping is the one that escalates.

Afterwards

Two things worth doing once it has settled.

Work out how it got published: whether anybody reviewed it, whether it was scheduled and forgotten, or whether it was written quickly while annoyed.

Most bad posts come from those three, and each has an obvious preventative.

Then write down what you decided, briefly, so the next person facing this has something to follow rather than improvising under pressure.

Do not overcorrect into approving every post through a committee, which is how accounts stop posting anything.

Check where else it went

The practical step people forget once they have dealt with the original.

A post that was cross-posted, scheduled to another platform, included in an email, or pushed to a listing exists in several places, and correcting one leaves the rest standing.

Check every channel the post reached, including any scheduler queue where a follow-up may still be waiting to publish.

Where a post went out by email, it cannot be recalled, so a short correction sent to the same list is the equivalent of editing it.

Doing this straight away avoids the situation where a correction is posted and the original continues appearing elsewhere for a week.

The counter-case

Most bad posts matter far less than they feel like they do at the time.

A small business account is seen by a few hundred people, most of whom scroll past, and the sense of exposure is disproportionate to the actual audience.

There is a real risk of a response that is larger than the original, drawing attention to something almost nobody saw.

Before doing anything, look at how many people actually saw the post, which is a number the platform will tell you and which frequently ends the discussion.

Fix facts, apologise for judgement, leave the merely unpopular, and check the reach before assuming it needs handling at all.

What to do

  1. Decide which of the three it actually is.
  2. Check how many people saw it.
  3. Correct facts quickly and directly.
  4. Apologise without explaining what you meant.
  5. Leave the merely unpopular standing.
  6. Never delete silently.
  7. Work out afterwards how it got published.

Step one prevents the most common mistake, which is apologising for a post that was correct and simply unwelcome to some people.

Telling customers about a problem is covered in telling customers something went wrong.


Frequently asked questions

How do I decide what to do?

Work out whether the post was factually wrong, badly judged, or merely unpopular. Those need a correction, an apology, and nothing respectively.

How quickly should I act?

Decide within the hour. A correction posted quickly reads as diligence; the same one three days later reads as a response to pressure.

What makes an apology worse?

Explaining what you meant, which tells people they misread it and turns an apology into a defence. Also blaming a member of staff, and posting it more than once.

When should I leave a post alone?

When it is accurate and considered and simply disliked. Apologising for that teaches everybody that complaints work and produces a business that cannot say anything.

Should I ever delete?

Yes, for private information, genuinely offensive content, or a wrong premise. Say that you have deleted it and why, since silent deletion looks like concealment and produces screenshots.

What should I do before reacting?

Check how many people actually saw it. A small business account reaches a few hundred, and the response is frequently larger than the original problem.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Post landed badly this morning?

Check the reach figure first. It usually ends the discussion about whether anything needs doing.

Start a Conversation