Community Management Rules
Rules for managing a brand's social community day to day: response time and tone, handling public criticism, when to move a conversation to DM, moderation lines, rewarding contributors, and never arguing with trolls.
0 downloads · Used by 0 stacks
Every public reply is read by far more people than the one it's addressed to — community management is a performance with an audience, not a private customer service exchange that happens to be visible, and every response should be written with that silent audience in mind.
Response time and tone
- Set an explicit response-time target per channel (e.g. under 1 hour for direct mentions during business hours, under 24 for lower-urgency comments) and hold it — an inconsistent response time trains the audience not to expect a reply, which suppresses engagement more than a merely-okay response time does.
- Match tone to the brand voice, but let a real person's voice come through — a reply that reads as copy-pasted corporate boilerplate gets noticed and mocked more than it reassures; specificity and a human register both build more trust than caution does.
- Reply to positive engagement too, not only problems — a like or a one-line acknowledgment on a genuinely good comment costs almost nothing and is a large part of what makes a community feel like a two-way conversation instead of a broadcast channel.
Public criticism handling
- Acknowledge the substance of a public complaint before doing anything else — restate what went wrong in your own words to show it was actually read, not just triaged. A generic "sorry for the inconvenience, DM us" with no acknowledgment reads as dismissive even when it isn't meant to be.
- Answer what can be answered publicly, in public — a simple factual question or a quick fix doesn't need to move to DM; resolving it in the open lets other people with the same question see the answer and also shows the brand handles problems well.
- Move to DM only when the conversation needs account-specific detail (order numbers, personal information, a drawn-out back-and-forth) — say explicitly in the public reply that you're moving it there ("sent you a DM to sort out the order details") so the public thread still shows resolution was pursued, not dropped.
Moderation lines
- Write down explicit, specific rules for what gets removed (harassment, hate speech, spam, doxxing) versus what stays even if it's harsh (a legitimate negative opinion, sharp but non-abusive criticism) — a moderation team without written lines makes inconsistent calls that themselves become a complaint.
- Never delete or hide a comment just because it's critical or unflattering — deleting legitimate criticism is far more damaging when it's noticed (and it usually is, via screenshot) than leaving the original criticism up ever was.
- Apply the same moderation lines to everyone, including people with large followings or close relationships to the brand — a visibly inconsistent standard is what actually erodes community trust, more than any single moderation decision does on its own.
Rewarding contributors
- Notice and publicly acknowledge people who consistently add value to the community (helpful answers, quality user-generated content, thoughtful feedback) — a public shoutout, a repost, or early access costs little and turns a passive follower into an invested contributor.
- Make the reward specific to what the person actually did ("your thread on X helped a lot of people") rather than a generic thank-you — specific recognition is what makes someone want to keep contributing.
- Build a lightweight, repeatable habit for this (a weekly highlight, a running list) rather than an occasional one-off gesture — consistency is what turns recognition into an incentive structure the community can rely on.
Never argue with trolls
- Don't respond in kind to bad-faith engagement (insults, deliberate misreadings, obvious rage-bait) — a public back-and-forth with a troll produces a permanent record that reflects worse on the brand than the original comment ever would have on its own.
- Give a bad-faith comment at most one calm, factual reply if a public correction is genuinely needed for onlookers' sake, then disengage — don't chase the last word; the audience reading the thread, not the troll, is who the reply is actually for.
- Use mute/block/hide tools freely on genuine trolling and harassment — these tools exist because not every interaction deserves a considered reply, and treating every comment as worthy of engagement is itself a moderation failure.
Related modules
- API Documentation RulesAPI & Backend
Rules for writing API reference documentation developers can actually use: runnable examples per endpoint, realistic request/response pairs, a full error catalog, auth explained first, breaking-change changelogs, a five-minute quickstart, and generating docs from source of truth.
No ratings yet - Auth FundamentalsAuth
Core authentication rules every login system needs: password hashing, session revocation, verification, and the line between authentication and authorization.
No ratings yet - Performance Review RulesBusiness Docs
Rules for writing performance reviews that are fair and useful: evidence-based specifics, behavior over personality framing, the SBI structure, balanced but honest assessment, forward-looking goals, and the no-surprises rule.
No ratings yet - Job Description RulesBusiness Docs
Rules for writing job descriptions that attract the right candidates: real responsibilities over buzzwords, must-have versus nice-to-have separation, salary transparency, inclusive language, and cutting requirement inflation.
No ratings yet
Badge
Link back to this module from your own README.
[](https://markdowners.com/m/markdowners/community-management-rules)Discussions about this module
No discussions about this module yet.
Start a discussion
Comments (0)
Sign in to comment. Sign in
No comments yet. Be the first to add one.