The Alchemist's Journal · Playbook

A One Page Plan For The Day A Post Goes Wrong

Who decides, what to say, and when to pause posting, written down before you need it.

A typo gets fixed in two minutes. A wrong price, an unfair comment thread, or a post that lands badly takes longer, and the first ten minutes decide whether it stays small. Write the plan now, while nothing is on fire.

Why a one page plan beats a long policy

Nobody opens a 12 page crisis manual while a complaint is picking up replies. A one page plan works because it answers three questions fast: who decides, what goes out first, and when to stop posting. Everything else, the follow-up statement, the internal review, the apology to a specific customer, can happen once those three are settled.

Keep it to one page on purpose. If it needs a second page, people will skip it.

Who decides

Pick one person as the decision maker for the whole thing, not a channel-by-channel owner. Name them by role, not just by name, so the plan still works when that person is on vacation.

  • Decision maker: the one person who can say "pause posting" or "reply now" without asking anyone else. Usually the founder, marketing lead, or community manager.
  • Backup: a second name for when the first is unavailable. No backup means no plan.
  • Who drafts replies: can be a different person, but they report to the decision maker before anything goes out.
  • Who has the final no: sometimes it is useful to name a second person who can veto a reply before it posts, especially if the first draft is written fast and under pressure.

Write these as roles and backups on the page itself. Don't leave it in someone's memory.

Want this written for your brand?

Fullmedia Alchemist drafts posts from your own website and brand facts, so nothing is made up. Start free, no card.

What to say first

You don't need a perfect statement in the first hour. You need a holding line that buys time without making things worse.

  1. Acknowledge what happened in plain terms. Don't restate the complaint in a way that sounds defensive.
  2. Say you're looking into it. Don't guess at a cause or promise a fix you haven't confirmed yet.
  3. Say when you'll follow up, and actually follow up by then, even if the update is "still checking."
  4. Avoid humor, hashtags, or brand voice flourishes in this first reply. Flat and plain reads as careful. Clever reads as careless.
  5. If it's a factual mistake like a wrong price or date, correct it clearly and say what you're doing about anyone affected.

Write two or three holding-line templates on the one page plan now, so nobody has to compose one from scratch under pressure. Swap in specifics when the moment comes.

One phrase to avoid

"We're sorry if anyone was offended" reads as blame on the reader. Say what happened and what you're doing, not how someone else felt about it.

When to pause posting

Scheduled posts that are unrelated to the issue can look tone deaf next to an active complaint thread. Decide the pause rule in advance so nobody has to debate it live.

  • Pause all scheduled posts if the issue involves safety, a factual error affecting customers, or anything likely to be covered outside your own channels.
  • Pause only the channel in question if it's contained to one platform and one thread, and other channels are unrelated.
  • Keep posting as normal if it's a single critical comment with no pickup elsewhere. Most complaints fall here. Reply, don't freeze the whole calendar.

Write the trigger words that mean "pause everything" on the page: things like a safety concern, a legal threat, or a post getting shared well beyond your usual reach. If you see one of those, the decision maker pauses first and asks questions after.

What goes on the page

SectionWhat to fill in now
Decision maker + backupTwo names or roles, with a way to reach them fast
Who drafts, who approvesOne or two names, so replies aren't posted solo
Holding linesTwo or three short templates for common situations
Pause triggersThe specific signs that mean stop all scheduled posts
Where to log itOne shared doc or channel so the team isn't guessing what happened

After the thread cools down

Once the immediate reply is out and posting is paused or not, do a short review, even if it's just five minutes with whoever drafted the reply. Note what triggered it, what you said, and whether the holding line actually worked. Update the one page plan with anything you'd change. This is the same habit as checking what worked where for regular posts: you're not guessing next time, you're using what actually happened.

If the mistake came from a factual error in a post itself, like a wrong claim or a detail nobody checked, it's worth tightening how posts get written in the first place. A content brief that states facts up front reduces the chance of a post needing a correction later.

Where this fits with Fullmedia Alchemist

Content writes posts from your brand facts and your own pages, so it won't invent a claim you'd later need to walk back. That doesn't replace a response plan, but it does mean fewer of the mistakes start with the caption itself.

Turn your brand into a week of posts.

The Free plan includes 30 credits a month. No card.

Start free