Community managers write constantly — welcome messages, engagement posts, conflict responses, newsletters, event announcements, health reports. The volume is relentless, and burnout is real. These 10 prompts are built for community managers who need to maintain the human touch at scale, without spending half their day staring at a blank text box.
Community Engagement & Content Creation
The backbone of a healthy community is consistent, quality content — the weekly post that gets people talking, the welcome message that makes a new member feel seen, the spotlight that recognizes someone's contribution. These four prompts cover the highest-frequency content tasks you face every week.
1. Weekly community post writer
The Prompt
"You are a community manager for [community name], a [description] community of [size] members. Write a weekly engagement post for [platform: Discord/Slack/Circle/etc.] that sparks conversation. The topic is [topic]. The tone should be [warm/professional/playful]. Include a question at the end that invites members to share their experience. Keep it under 150 words."
Why it works: The platform context matters because Discord posts read differently from Circle posts. The tone instruction prevents the model from defaulting to generic corporate copy. The 150-word ceiling forces a punchy post that actually gets read — and the mandatory closing question is what drives the replies you need to justify the content.
2. New member welcome message
The Prompt
"Write a warm, personal welcome message for a new member named [name] who just joined [community name]. They mentioned they're interested in [interest/role]. Include: a genuine welcome, 2-3 specific resources or channels they should check out first, one question to help them introduce themselves, and a call to action. Keep it conversational, not corporate."
Why it works: The "not corporate" instruction is doing real work here. Welcome messages are the first thing a new member reads — they set the tone for the entire relationship. Filling in the member's interest lets the model personalize the resource suggestions, which is the difference between a message that feels like it was written for them and a mass auto-reply.
3. Member spotlight post
The Prompt
"Write a member spotlight post for [community name] featuring [member name], a [role/title] who [brief achievement or contribution]. The post should: celebrate their win, explain why it matters to the community, tag them (use @[handle] placeholder), and invite others to congratulate them. Tone: warm and genuine. Platform: [Discord/LinkedIn/newsletter]. Keep it under 200 words."
Why it works: Member spotlights are underused because they're surprisingly hard to write well — you want to celebrate without being sycophantic, and make the achievement feel relevant to the whole community, not just the individual. This prompt structures all three moves: celebrate the win, connect it to community value, invite participation. The platform field makes sure the format and tag syntax are right.
4. Re-engagement post for quiet periods
The Prompt
"Our [community name] community has been quiet this week. Write a re-engagement post that: opens with a relatable observation (not 'things have been quiet lately'), asks a specific opinion question about [topic relevant to community], and invites lurkers to share just one word or emoji if they don't want to write a full reply. Tone: [casual/professional]. Keep it under 100 words."
Why it works: The hardest part of re-engagement copy is not sounding desperate. The "not ‘things have been quiet lately’" instruction kills the most common lazy opener. The low-barrier ask (one word or emoji) is the key technique — it removes the friction that keeps lurkers lurking. And keeping it under 100 words ensures it doesn't read like an announcement.
Want 50+ prompts like these?
The Ultimate ChatGPT Prompt Pack covers engagement, moderation, reporting, events, and more — for every situation a community manager faces.
Get the Prompt Pack — $19Conflict Resolution & Moderation
Moderation is the part of community management nobody talks about — and the part that burns people out fastest. Writing a de-escalation DM, a rule violation response, or a community statement under pressure is genuinely hard. These three prompts give you the structure to respond quickly, fairly, and without torching the community's trust.
5. Member conflict de-escalation DM
The Prompt
"A conflict has broken out in [community name] between two members over [topic/issue]. Write a private DM to each member that: acknowledges their perspective without taking sides, reminds them of the community guidelines around [specific rule], explains the impact of the conflict on the community, and gives them a clear path forward. Tone: firm but empathetic. Do not use corporate HR language."
Why it works: “Firm but empathetic” is the exact tonal instruction that prevents this from going wrong in either direction — too soft and nothing changes, too hard and the member disengages permanently. The "no HR language" instruction is critical: conflict DMs that sound like a warning letter from a legal department destroy community trust. This prompt produces something a human would actually say.
6. Rule violation response message
The Prompt
"A member in [community name] has violated the community guideline around [specific rule, e.g. 'self-promotion' or 'respectful discourse']. Write a public (or private — specify which) response that: names the specific guideline that was broken (without being preachy), explains why the rule exists and how it protects the community, states the consequence clearly (warning/temp ban/etc.), and leaves the door open for them to re-engage positively. Tone: direct and fair."
Why it works: Rule violation responses fail when they're either too vague ("please review our guidelines") or too punitive. This prompt builds the four components of an effective response: name the specific rule, explain the why, state the consequence, and leave a door open. The "without being preachy" instruction is what keeps it from sounding like a lecture and losing the room.
7. Crisis/sensitive topic communication
The Prompt
"Our community is dealing with a sensitive situation: [describe situation, e.g. 'a well-known member has publicly called out our company' or 'a controversial topic is dominating discussion']. Write a community manager statement that: acknowledges the situation directly, explains what we are (and are not) doing about it, sets expectations for how discussions on this topic will be moderated going forward, and closes on a unifying note. Tone: transparent, calm, not defensive."
Why it works: Crisis statements in communities fail in two ways: they over-explain (which reads as defensive) or they under-address (which reads as evasive). The structure here forces both sides — acknowledge AND explain what you're not doing. The moderation expectation-setting section is often skipped but it's what prevents the same situation from reigniting in 24 hours.
Reporting, Events & Newsletters
The work that proves the community's value — health reports, event announcements, newsletters — is also the work that gets deprioritized when you're deep in the day-to-day. These three prompts cut the blank-page problem out of the structured documents and content that keep stakeholders informed and members engaged.
8. Monthly community health report
The Prompt
"Write a monthly community health report summary for [community name] to share with [internal stakeholder: leadership/marketing/product]. Data: [X] new members, [Y] total members, [Z] active members, top discussions: [list], notable wins: [list], challenges: [list]. Format: executive summary (3 bullets), key metrics table, highlights section, and 2-3 recommendations for next month. Keep it under 400 words. Audience: non-community-manager executives."
Why it works: The "non-community-manager executives" audience instruction is what changes this from a community ops doc to something leadership actually reads. The four-section structure forces the shape that executives need: a bullet summary they can skim, data they can screenshot, and recommendations that give them something to act on. Paste in your raw data and get a polished report in under a minute.
9. Community event announcement
The Prompt
"Write an announcement for [community name] about an upcoming [event type: AMA / workshop / virtual meetup / challenge] called '[event name]' happening on [date/time] featuring [speaker/host if applicable]. The announcement should: open with a hook about what members will get out of it, explain the format and what to expect, include logistics (date, time, link/location), and close with a clear RSVP or registration CTA. Tone: [excited/professional]. Platform: [Discord/email/Slack]. Keep it under 200 words."
Why it works: Event announcements that lead with logistics ("We're hosting a webinar on [date]") convert poorly. This prompt forces the hook-first structure: start with the member benefit, then cover the format, then the logistics, then the CTA. The platform field matters because a Discord announcement needs different formatting and urgency than a Slack message or email.
10. Community newsletter intro
The Prompt
"Write the opening section of a [weekly/monthly] community newsletter for [community name]. This week's theme: [theme]. Include: a 2-3 sentence editorial opening from the community manager's perspective (personal, not corporate), a brief preview of what's in this issue, and a spotlight question to get members to reply. Tone: like a note from a trusted friend who happens to run the community. Keep the opening under 150 words."
Why it works: The newsletter opening is what determines whether anyone reads the rest. “Like a note from a trusted friend who happens to run the community” is a tone instruction that's specific enough to change the output — it prevents the model from producing generic broadcast copy and pushes toward the conversational editorial voice that gets newsletters opened. The spotlight question at the end turns a one-way broadcast into a two-way conversation.
Community management is one of the highest-volume writing jobs in any organization — and one of the least supported with tools built specifically for it. These prompts won't replace your judgment, your relationships, or your read of the room. They'll replace the blank-page problem so you can spend your energy on the parts of the job that actually require you. Start with whatever's sitting in your queue right now — the welcome message, the conflict DM, the monthly report. The prompt gets you 80% there in under a minute.
Ultimate ChatGPT Prompt Pack
$19
50+ ready-to-use prompts for every situation a community manager faces.
No-Code Automation Starter Kit
$27
Automate your community workflows — from welcome sequences to health reporting — without writing a line of code.