Don't Defend. Explain.

Most of the people reading aren’t the one writing.

Replying to negative feedback in public is its own small craft. It looks easy until you’ve done it badly a few times. Most of the people who’ll read your reply aren’t the angry customer. They’re the people watching to see how you behave when you’re cornered. Get that audience right and most of the rest follows.

Stay humble. Don’t take it personally. Accept that not everyone is going to like you, and stop spending energy on the ones who never will. The minute you turn off replies on a post, you’ve already lost. The argument has shifted from “is this person right?” to “this team can’t handle being challenged.” That’s a worse fight to lose.

The voice matters. Don’t use humor or sarcasm when someone’s upset. Don’t use corpospeak. Speak plainly, without jargon, in a register a real person would use over a real coffee. If you don’t know the answer, say so, and tell them what you’re doing to find out. People can spot a stall.

Make them feel heard before you do anything else. Behind nearly every frustrated customer is real, useful feedback that you don’t yet have. Don’t reject it outright. That just gives them something to defend, and the conversation stops being about the issue. Be kind and empathetic even when they don’t deserve it, partly because that’s how people deserve to be treated, partly because the silent audience is keeping score.

When you do reply, explain, don’t defend. The same facts can read as bitter or transparent depending only on how you frame them. Take more responsibility than seems necessary. Take so much ownership that it surprises people. The cost of a little extra ownership is small. The cost of looking defensive in public is not.

Remember that everything you post in public shapes a narrative. Sometimes it’s worth taking longer to write because it’ll be quoted, screenshotted, and read by people who weren’t even part of the original conversation. If you present as bragging or cocky, you’ll find people more interested in knocking you down than in hearing what you have to say. Don’t give them the easy target.

For deeply technical topics, be detailed, calm, factual, and empathetic to the concern underneath. Don’t get caught arguing about implementation details when the underlying complaint is about trust.

And when you do apologize, fully commit. State the problem. Explain the fix. Say what you’re doing to prevent it from happening again. Only apologize if you genuinely mean it; an apology you don’t believe in reads worse than no apology at all.

Sometimes, you just have to post through it. Not everyone is going to like you. That’s fine. The job isn’t to be liked. It’s to be the kind of operator other people want to deal with when something goes wrong.