25 AI Prompts for Community Management

TL;DR: These 25 community management prompts are grouped by the moment they solve: welcoming a new member, keeping a slow week talking, drafting a moderation response, winning back someone who's gone quiet, and reporting on all of it. None of them post anything automatically. Every draft, especially anything about a warning or a ban, gets read and edited by a human moderator before it reaches a member.

Running a community, whether it's a Discord server, a subreddit, a Slack workspace, or a Circle space, is mostly the same handful of writing tasks repeated at different volumes: welcome the new person, say something worth replying to on a quiet Tuesday, and answer the message that just made a thread go sideways. Good community management prompts don't automate any of that away. They just mean you're not starting from a blank message box for the fortieth time this month.

What Counts as a "Community Management Prompt"?

A community management prompt is a reusable template that turns a specific, recurring situation, a new join, a quiet week, a rule violation, into a first draft you still have to read before anyone else does. That distinction matters more here than in almost any other prompt category on this site, because the output is aimed at a real person who didn't ask an AI to talk to them.

Three moments account for most of the writing a community manager actually does: onboarding someone new, keeping the space active when nothing's happening on its own, and responding when something goes wrong. The table below maps all 25 prompts to those moments, plus reporting and the cross-platform differences that trip people up when the same community lives in more than one place.

Most small teams draft these the same rough way today: a running ChatGPT tab, or a shared doc of canned replies someone half-remembers to update. Both work, until the tab gets closed or the doc gets a fourth outdated version. Here's the honest comparison.

None of that changes what a moderator's judgment is for. It just means the twentieth welcome message takes the same ten seconds as the first one.

How Do You Draft a Welcome Message a New Member Actually Reads?

The first ten minutes after someone joins decide whether they post once or never again. These five prompts cover that window: the DM itself, translating a rule into something that doesn't read like a terms-of-service page, a public spotlight, an onboarding FAQ built from real questions, and the different note a returning member needs.

1. First-DM welcome

New member: [name]. They said in their intro: [paste their intro message,
or "no intro yet" if they skipped it].
Write a 60-word welcome DM. Reference something specific from their intro
if they gave one. Point them to exactly one channel or thread relevant to
what they said, not a list of five. No exclamation points in every sentence.

2. Rules-in-plain-language explainer

Community rule, as written: [paste the formal rule text].
This new member seems interested in: [what their intro or first post suggests].
Rewrite the rule as a 40-word explanation in plain language, framed around
why it exists rather than just what's forbidden. No legal or ToS-style phrasing.

3. New-member spotlight post

New member: [name]. What they shared: [paste their intro, hobbies, or
what brought them here].
Write a 50-word public "welcome" post for the community's general channel
that introduces them using only what they actually shared. Ask one open
question the community can reply to.

4. Onboarding FAQ from real questions

Here are the questions new members have actually asked in the last month:
[paste 8-15 real questions, unedited].
Group them into the 5 most common underlying questions and write a short,
direct answer for each, 30-40 words per answer. Use our actual answers
where I've given them below: [paste any existing answers you have].

A pinned post built this way answers the questions people are actually asking, not the ones a generic community-FAQ template assumes they'll ask.

5. Re-onboarding a returning member

Member: [name]. They left [timeframe] ago and just rejoined.
What's changed since they left: [list new channels, rules, or events].
Write a 45-word note welcoming them back, naming one or two specific
changes they'd want to know about. Don't ask why they left.

What Keeps a Community Talking on a Slow Week?

A community engagement prompt earns its place the week nothing is happening on its own. These six cover a daily discussion starter, a themed poll, a weekly recap, a member-spotlight interview, an event announcement, and a thread that turns your own audience's habit of trading prompts into content.

6. Daily discussion-prompt generator

Community topic/niche: [what your community is actually about].
Recent conversation themes: [list 2-3 things members have been discussing].
Write 5 discussion-starter questions for the week, each one specific enough
that a one-word answer wouldn't make sense. Avoid generic "what's your
favorite X" framing.

7. Themed poll question

Day/ritual: [e.g. "Feedback Friday", "Show-and-tell Wednesday"].
This week's context: [any relevant news, launch, or theme].
Write a poll question with 4 answer options, phrased so that picking any
option reveals something real about how the person works, not just a
preference.

8. Weekly highlights digest

Here are this week's most-replied threads, pasted with reply counts:
[paste thread titles and top comments or a summary of each].
Write a 100-word "this week in [community name]" recap highlighting 3 of
these threads, with one line each on why it's worth a look, and one
open question to carry into next week.

9. Member-spotlight interview questions

Member being spotlighted: [name, what they do, how long they've been here].
Write 5 short interview questions for a member spotlight, mixing one
practical question, one opinion question, and one that invites them to
recommend something to the rest of the community.

10. Event or AMA announcement

Event: [type, e.g. AMA, workshop], guest/host: [name and one line on why
they're relevant], date/time: [details], what attendees get: [one sentence].
Write a 70-word announcement and a 20-word one-line reminder to post the
day before. No countdown clichés.

11. "Share your best prompt" thread starter

Community focus: [what your members build or work on with AI].
Write a 50-word thread starter inviting members to share one prompt
they're proud of and what it's for, plus 3 example replies in different
voices to seed the thread before real members reply.

Who Decides When a Warning Becomes a Ban?

This is where moderation AI gets misunderstood fastest, so the rule up front is the whole point of this section.

12. De-escalation reply for a heated thread

Thread context: [paste the last 5-10 messages, or a summary of the conflict].
Write a 60-word moderator reply that names what's happening without
taking a side, redirects to the actual rule at issue, and asks both
parties to continue by DM if it isn't resolved. No passive-aggressive
phrasing ("as previously stated").

13. First-warning message

Member: [name]. Rule violated: [paste the specific rule]. What happened:
[factual description, no editorializing].
Write a 50-word first-warning DM stating the specific behavior, the rule
it breaks, and what happens on a repeat, in a firm but non-hostile tone.
I will edit before sending.

14. Mediation summary between two members

Member A's side: [paste or summarize]. Member B's side: [paste or summarize].
Write a neutral 80-word internal summary of the dispute for my own
reference before I respond to either party, noting where their accounts
agree and where they conflict. This is not member-facing.

15. Suspension or removal notice

Member: [name]. Violation history: [list prior warnings, dates, if any].
Current violation: [factual description]. Our appeal process: [paste it,
or note there isn't one].
Write a 70-word removal notice stating the reason, referencing prior
warnings if any exist, and including exactly how to appeal if we offer
that. I will review every line before this goes out.

16. Gray-area report triage

Report received: [paste the report as submitted]. Relevant rule, if any:
[paste it, or note none clearly applies].
Instead of a verdict, write a 40-word reply to the reporter asking one
clarifying question that would change how I'd handle this, and a
separate 30-word note to myself on what I still need to know before deciding.

17. Post-incident mod-team recap

Incident: [what happened, dates, members involved, action taken].
Write an internal 100-word recap for the mod team: what happened, what
we did, and one specific thing to watch for if it happens again. Internal
only, not member-facing.

Pasting two or three of your own past warnings as examples before you draft a new one is a form of few-shot conditioning: the draft matches your community's actual register instead of a generic, corporate-sounding one. If your community has more than one moderator, the real risk isn't a bad draft, it's five moderators drafting in five different voices; our guide to building a brand-voice context covers writing that voice down once so every draft, warning or otherwise, starts from the same block.

How Do You Win Back a Member Who's Gone Quiet?

Someone who's stopped posting hasn't necessarily left, and a generic "we miss you" message is exactly the kind of AI-slop reach-out that gets ignored. These three are specific to what actually happened.

18. Win-back DM for a quiet member

Member: [name]. Last active: [date]. What they used to engage with:
[topics, threads, or channels they were active in].
Write a 45-word DM referencing what they specifically used to engage
with, not a generic "we miss you." Ask one low-pressure question, not
"come back!"

19. Follow-up after someone leaves

Member who left: [name, if you can DM them, or note if they're just gone].
Reason given, if any: [paste it, or note none was given].
Write a 40-word message thanking them for the time they were here and
leaving the door open, with no guilt and no discount-style incentive
to return.

20. Reviving a stalled thread

Stalled thread: [paste the original post and last reply, plus how long
it's been quiet].
Write a 35-word reply that adds a genuinely new angle or question to the
original topic, not a generic "bump" or "anyone still discussing this?"

What Should a Mod Team Actually Report on Each Week?

Reporting is the part of community management that gets skipped until someone senior asks what's actually happening in there. These three turn raw activity into something worth reading.

21. Weekly mod-team status update

This week's numbers: [new members, active threads, reports handled,
anything notable]. Incidents, if any: [brief description].
Write a 100-word internal status update for the mod team covering
volume, any incidents and how they were handled, and one thing to
watch next week.

22. Public-message theme summary

Here are [N] public messages/threads from this week, pasted in full:
[paste only messages posted publicly, never private DMs].
Summarize the 3 most common themes members raised, in 30 words each,
without naming individual members. This is for internal planning, not
for quoting anyone directly.

23. Monthly stakeholder report

This month's numbers: [growth, engagement, notable events, incidents].
Last month's numbers, for comparison: [paste if available].
Write a 150-word monthly report for [founder/team/stakeholders] covering
growth, engagement trend versus last month, and one specific
recommendation for next month.

If more than one person is pulling these together, the same shared-library problem that hits marketing and support teams shows up here too: our guide to AI prompt management for business teams covers keeping one editable version instead of three slightly different ones in three different DMs.

Does the Same Prompt Work on Discord, Reddit, Slack, and Circle?

Mostly, with the format tweaked. But it's worth being precise about what these prompts are for versus what each platform already builds in, because the two get confused constantly.

Discord's own AutoMod already blocks messages automatically, before a human ever sees them. Discord's help center describes it plainly: "AutoMod is a system of multiple content filters designed to make content moderation easier and less work for moderators." It also caps a custom keyword rule at 1,000 terms of up to 60 characters each, with mention-spam limits topping out at 50 mentions per message (support.discord.com, AutoMod FAQ, edited June 15, 2026, accessed September 4, 2026). Reddit's AutoModerator works the same way one level down. Reddit's own moderator help center says: "AutoModerator is a site-wide moderation tool that you can set up and customize in any subreddit to assist you in moderating that community." It can remove, filter, flair, or auto-reply to posts the instant they're submitted, with no human in the loop at that moment (mods.reddithelp.com, AutoModerator, last edited May 17, 2023, accessed September 4, 2026). Both are for the messages you never want a human to have to deal with at all.

Slack has no equivalent built for community use specifically, and cleanup there is manual. Slack's own help center makes two separate points worth knowing before you rely on it: "Owners and admins can also delete members’ messages in public channels, private channels, and group direct messages (DMs) they’re part of." And separately: "It's not possible to bulk delete messages." (slack.com/help, Edit or delete messages, accessed September 4, 2026). One message at a time, which is a real argument for getting the welcome and moderation drafts right the first time rather than cleaning up after.

Everything in this post, on any of those platforms or on Circle, is for the messages that do land, that a human still has to answer, warn about, or explain. That's a different job from what AutoMod or AutoModerator do, and it's why none of the 25 prompts above should go out to a member without your own read first.

24. Adapting one draft to a platform's format

Original message: [paste your draft, written for one platform].
Target platform: [Discord embed / Reddit stickied comment / Slack canvas
or pinned message / Circle post].
Rewrite this for the target platform's actual format and length norms,
keeping the same core message and tone, adjusting only structure and length.

25. Locking your house voice into every prompt

Our community's voice, in our own words: [3-5 sentences on tone, what
we never say, and what makes us sound like us].
Turn this into a 40-word instruction block I can paste at the start of
any community prompt, so every draft, welcome message or warning,
sounds like the same person wrote it.

Turning your community's actual voice into a reusable instruction block like this is a form of persona prompting, and our guide to persona prompting covers the mechanics if you want to go further than one paragraph. Treat the callout in the conflict section above as the real guardrail here, not this prompt: the block only controls how something sounds, never whether it should be sent.

Start with the Three Moments Every Community Already Has

You don't need all 25 of these on day one. Almost every community, ours included, hits the same three moments regardless of size: someone new shows up and needs ten minutes of real attention, a Tuesday goes quiet and needs one good question, and a thread gets heated and needs a human, not a bot, to answer it carefully. We run a small Discord ourselves for Advanced and Team customers, and it isn't exempt from any of that; a welcome message and a de-escalation draft get used there the same way they'd get used anywhere else.

Start with prompts 1 and 12: the welcome message and the de-escalation draft cover the two moments that do the most damage when they're handled badly. Once you're running these daily rather than occasionally, save the ones that work instead of retyping them; our guide to organizing a large prompt library covers keeping 25 prompts searchable once they turn into 100. And if community management is one of several hats you wear, the overlap with customer support prompt work is closer than it looks: both jobs are mostly writing a specific, correct reply to one person, fast, in a voice that's consistently yours.