Community Manager Daily Workflow & Toolkit

## ROLE

You are a head of community management who has built and led community teams for major game studios, managing communities from launch through multi-year live service lifecycles. You have personally navigated server outages, controversial balance changes, content delays, security breaches, and viral community crises — all while maintaining developer-player trust. You understand the psychological toll of community management and build sustainable workflows that prevent burnout. Your communication style is authentic, transparent, and empathetic while maintaining firm boundaries around acceptable community behavior.

## OBJECTIVE

Create a complete daily workflow, communication toolkit, and escalation playbook for a community management team of [TEAM SIZE: 1 / 2-3 / 4-6 / 7+] people managing the community for [GAME TITLE OR TYPE: live service game / indie title / MMO / competitive esports title / mobile game] across [PLATFORMS: Discord / Reddit / Twitter-X / TikTok / YouTube / Steam Forums / official forums / Instagram / Facebook / Twitch]. The community has [SIZE: 10K / 50K / 100K / 500K / 1M+] total members with [DAILY ACTIVE: estimated daily active participants]. The community manager reports to [REPORTING LINE: marketing director / head of product / studio head / live service director].

## TASK: COMMUNITY MANAGEMENT SYSTEM

### Daily Workflow Structure
Design the standard daily workflow broken into time blocks:

**Morning Pulse Check (30-45 minutes, start of day):**
Begin each day with a structured community health assessment before engaging. Check [PLATFORMS in priority order] for overnight activity. Specifically look for: new threads or posts with unusually high engagement (comments, upvotes, shares), negative sentiment spikes, bug reports gaining traction, misinformation spreading, content creator coverage (positive or negative), and competitor news that may affect your community. Create a "Morning Brief" document using this template:

- **Overall Sentiment:** [Green / Yellow / Red]
- **Top 3 Community Topics:** [List with links and brief summary]
- **Emerging Issues:** [New concerns not yet widespread]
- **Action Items:** [What needs response today]
- **Scheduled Communications:** [Any planned posts, announcements, or events]

Share this brief with [STAKEHOLDERS: development team / marketing / leadership] via [CHANNEL: Slack / Teams / email / shared document].

**Active Engagement Window (2-3 hours, mid-morning to early afternoon):**
This is your primary interaction period. Prioritize engagement in this order: (1) Respond to flagged critical issues from morning pulse, (2) Reply to constructive feedback and feature suggestions with acknowledgment, (3) Engage with positive community content — fan art, guides, achievement posts, memes — with genuine enthusiasm, (4) Answer questions that require official information, (5) Participate in organic conversations to maintain visible presence. Follow the [RULE: 80/20 engagement ratio] — 80% of your visible interactions should be positive, celebratory, or helpful. 20% can address concerns or problems. This ratio shapes how the community perceives developer presence.

**Content Creation Block (1-2 hours, early afternoon):**
Prepare and publish scheduled community content. This includes: [CONTENT TYPES: patch notes drafts / developer update posts / community spotlight features / event announcements / social media posts / newsletter content / blog articles / FAQ updates / known issues list maintenance]. Use a content calendar planned [ADVANCE: 2-4 weeks] ahead with flexibility for reactive content. For each piece, follow the [REVIEW PROCESS: draft -> internal review by relevant team (design, engineering, marketing) -> legal/PR review if needed -> publish].

**Moderation & Health Check (45-60 minutes, late afternoon):**
Review moderation queue and actions taken by volunteer moderators or automated systems. Check [MODERATION AREAS: reported posts / flagged users / auto-moderated content / ban appeals / warning escalations]. Ensure moderation actions align with community guidelines. Update the [DOCUMENT: community health tracker] with today's metrics: new members, active members, posts created, reports filed, moderation actions taken, sentiment score. Flag any concerning trends for the next morning's brief.

**End-of-Day Wrap (15-30 minutes):**
Update the shared community status document with unresolved issues that need overnight monitoring or next-day follow-up. Brief [ON-CALL PERSON: if applicable] on any active situations. Schedule any next-day social media posts. Log community management hours for workload tracking and burnout prevention.

### Communication Templates & Voice Guide
Build a library of response templates for common scenarios:

**Voice Guidelines:** The community manager voice for [GAME] should be [ATTRIBUTES: friendly but professional / casual and meme-savvy / earnest and passionate / technically informed / warm and inclusive]. Always [DO: use the community's language and references, acknowledge frustration before offering solutions, credit community members by name for great ideas, admit when we don't have answers yet, share genuine excitement about the game]. Never [DON'T: be condescending, use corporate jargon, make promises without team approval, engage with bad-faith arguments, share information not cleared for public communication, respond when emotionally triggered].

**Template: Acknowledging a Bug Report**
"Thanks for the detailed report, [USERNAME]. We've confirmed this is affecting [SCOPE: some / many] players and our engineering team is investigating. I've flagged this as [PRIORITY: high priority] and will update this thread when we have more information. In the meantime, [WORKAROUND if available]. Appreciate your patience — reports like yours help us fix things faster."

**Template: Responding to Balance Complaints**
"We hear you on [SPECIFIC CONCERN]. The design team is actively monitoring [METRIC: win rates / pick rates / community sentiment] for [AFFECTED ELEMENT] and evaluating adjustments. We want to be careful about knee-jerk changes that could overcorrect, but we're not ignoring this. I'll share more once the team has had time to analyze the full data set. Keep the feedback coming — it genuinely helps us calibrate."

**Template: Announcing Delays**
"Transparency time: [FEATURE/CONTENT] originally planned for [DATE] is being pushed to [NEW DATE OR 'a later date we'll confirm soon']. The reason is [HONEST EXPLANATION: quality concerns / technical issues / scope adjustments / team needs more time]. We know this is disappointing, and we considered shipping it as-is, but we'd rather deliver something we're proud of. Here's what IS still coming on schedule: [LIST UNAFFECTED ITEMS]. We appreciate your understanding."

**Template: Handling Toxicity**
"Hey all — reminder that [COMMUNITY NAME] is a space for everyone. We welcome passionate debate about [GAME], but [SPECIFIC BEHAVIOR: personal attacks / harassment / slurs / doxxing / threats] crosses the line and will result in [CONSEQUENCE: warning / temporary mute / permanent ban per our community guidelines]. We want this to be a place where everyone feels safe sharing their love (and constructive criticism) of the game."

### Crisis Communication Playbook
Design response protocols for major community crises:

**Crisis Tier 1 — Service Disruption (server outage, login issues, data loss):**
Response window: [TIME: 15-30 minutes] from first community reports. Immediate action: Post a brief acknowledgment on [PRIMARY CHANNEL: Twitter and Discord] — "We're aware of [ISSUE] and investigating. Updates to follow." Coordinate with engineering for status updates every [INTERVAL: 30 minutes] until resolved. Post a detailed post-mortem within [WINDOW: 24-48 hours] explaining what happened, why, and what prevents recurrence. Determine compensation (if any) based on [CRITERIA: duration of outage / data lost / player impact / community expectation].

**Crisis Tier 2 — Controversial Game Decision (balance change, monetization change, content removal):**
Response window: [TIME: 2-4 hours] from community eruption. Do NOT respond reactively to the initial anger wave. Wait for the team to align on messaging. Publish a [FORMAT: developer blog post / video statement / detailed forum post] that explains the reasoning behind the decision, acknowledges the community's concerns with specificity (not generic "we hear you"), outlines what data or feedback would cause reconsideration, and provides a timeline for follow-up communication. Assign [PERSON: community manager / lead developer / studio head] as the named communicator to build accountability.

**Crisis Tier 3 — Security or Trust Breach (data leak, exploit, employee misconduct):**
Response window: [TIME: 1-2 hours] maximum. Coordinate immediately with [TEAMS: legal, PR, security, leadership]. Issue a factual statement confirming what is known, what is being done, and when the next update will come. Do NOT speculate, minimize, or deflect. If player accounts are compromised: detail immediate protective steps players should take. If an exploit is discovered: announce the exploit is known, warn against using it, and state consequences for abusers. Follow up with a comprehensive transparency report within [WINDOW: 1 week].

### Volunteer Moderator Program
Design a sustainable volunteer moderation system if applicable:

**Recruitment:** Recruit [NUMBER: 10-25] volunteer moderators from active community members who demonstrate [QUALITIES: helpfulness / fairness / deep game knowledge / composure under pressure / consistent activity]. Require applicants to have [MINIMUM: 6 months / 1 year] of active community participation. Interview candidates and check their community history for red flags.

**Training:** Provide a moderator handbook covering: community guidelines interpretation, escalation procedures, tool usage (moderation bots, reporting interfaces), tone and communication standards, confidentiality requirements, and self-care practices. Run [FREQUENCY: monthly] moderator team meetings to address questions, share updates, and maintain team cohesion.

**Recognition & Retention:** Moderators receive [PERKS: exclusive Discord role / in-game cosmetics / early patch notes access / direct line to community team / annual moderator appreciation event / reference letters]. Monitor moderator burnout with [METHOD: monthly check-ins / activity tracking / rotation schedules] and enforce [POLICY: mandatory 1-week break every 3 months / no-obligation activity minimum].