Community Management Response Guide

Example output

Response guide — Farrow Kombucha, bloating complaint (40 likes, public comment)

Situation read
This is a public complaint with real visibility — 40 likes means other people are watching how you respond, not just the original commenter. It's also a genuine physical reaction, not just an insult, so the response needs to validate the experience before anything else. The instinct to explain or defend the product first is the wrong order here.

Response framework for this situation
1. Acknowledge the discomfort first, specifically — not a generic "sorry to hear that."
2. Offer a real, honest possible reason if you have one — you do, the higher ginger content — without turning it into a liability-flavored disclaimer.
3. Move the resolution to DM. Public replies should show care; the actual troubleshooting, like a refund or flavor swap, belongs in private.
4. Never argue the point publicly, even gently. Other readers are grading your tone, not just your facts.

Draft reply — option 1 (warm, direct)
"Oh no, that's the opposite of what we want kombucha to feel like! Our ginger-turmeric is our spiciest, ginger-forward brew, and that can hit differently for sensitive stomachs. Sending you a DM — we'd love to make this right."

Draft reply — option 2 (shorter, still warm)
"That's not the reaction we're going for, I'm sorry. Ginger-turmeric runs hotter on ginger than our other flavors, which isn't for everyone. DMing you now."

Draft reply — option 3 (adds a public next step)
"Really sorry to hear it — that flavor is our most ginger-forward, and stomachs react differently to it. Sliding into your DMs so we can sort you out. If a milder flavor sounds better next time, our original is a good place to start."

Tone traps to avoid
- Don't say "everyone reacts differently" as a stand-alone line — it reads as deflection unless paired with a specific, honest reason.
- Don't offer a discount code publicly as the first move; it can read as trying to buy silence rather than address the comment.
- Don't go quiet. An unanswered visible complaint with 40 likes reads worse over time than an imperfect timely reply.
- Avoid any language implying the product is medicinal or reframes bloating as a "detox" — that's both dismissive and a claims risk.

DM follow-up draft
"Hey! So sorry about that — wanted to make it right. Want me to send a replacement in a milder flavor, or would a refund be easier? Also curious which store or size this was so we can flag it if there's a batch issue."

Escalation flag
Low legal risk, moderate care-team follow-through needed. No escalation to legal for this draft language — it makes no health claims and stays descriptive, "higher ginger content," rather than causal. Escalate to a supervisor only if the commenter reports a severe reaction, not just bloating, or if this becomes a pattern across multiple comments on the same batch, which would be a quality signal worth investigating.

Want me to build a short library of go-to responses for the other recurring complaint types you're getting on this flavor?