Table of Contents
Starting a writing Discord can feel like walking into a crowded café with no map. You want to be friendly, but you also don’t want to spend the first month yelling into the void. What I’ve noticed (both running servers and joining a bunch of them) is that growth usually comes down to one thing: making your community easy to find, easy to understand, and genuinely fun to participate in. Do that, and people stick.
In this post, I’m going to walk through the exact setup I’d use to grow a writing Discord—how I structure channels, what I write in the welcome flow, which bots I actually recommend, and how I run events with a schedule members can count on. No fluff. If you copy these pieces, you’ll have something you can test immediately.
Key Takeaways
- Name + keywords matter: use a clear server title like “Fantasy Writers & Critique” and match it with the same keywords in your Discord server description (not just vibes).
- Write a real description: 2–3 short paragraphs + bullet list of what happens weekly (prompts, critique, workshops).
- Onboarding flow: set up a dedicated #introductions channel and a bot-based “read-me-first” checklist (rules + how to pick roles + where to post).
- Rules that people follow: keep it short (5 rules), pin them, and repeat the “how to critique” expectations in a separate channel.
- Event cadence that works: run weekly prompts + a monthly contest + a rotating “workshop night” so members always have something to do.
- Interaction prompts: ask one question per day in #writer-chat (example: “What’s your current WIP goal for this week?”).
- Member spotlight: pick one “Win of the Week” post format and reuse it every week to build momentum.
- Collaboration hooks: create #pairing and #group-projects channels and run a “buddy feedback” sprint every 2–4 weeks.
- Promotion with receipts: post the same 3 content types on social (prompt teaser, member highlight, event reminder) and link to your Discord invite.
- Use bots you can configure: MEE6 (levels/moderation), Carl-bot (welcome + auto roles), Dyno (logging), and a poll bot (prompt votes).
- Exclusive perks: give members a reason to stay—prompt packs, a public critique queue, or early access to events.
- Track what matters: check 7-day retention, event attendance, “new members who post in #introductions,” and churn reasons.
- Channel layout that reduces friction: genre channels + critique channels + a single “Start Here” hub so newcomers don’t wander.
- Workshops that feel real: do 30–45 minute sessions with a repeatable agenda (lesson → example → practice → Q&A).
- Inclusive tone is a system: model behavior, moderate early, and handle conflicts privately so the server stays safe.

Here’s what I recommend doing first: build your Discord like a small website. People decide in minutes whether they “get it.” If your server is hard to navigate, they leave. If it feels welcoming and structured, they stay.
1) Make your server easy to find (title, description, and keywords)
When someone searches “writing discord” or browses Discord listings, your server has to sound like the exact place they want. I’d do this:
- Server name: keep it specific. Example: “Sci-Fi Writers + Critique” beats “Writers United.”
- Description keywords: include the topics you actually cover: “writing prompts,” “critique,” “workshops,” “fiction,” “poetry,” “novel drafting.”
- Category + tags: if your listing supports tags, use the same words people use when they search.
- Invite settings: avoid “temporary” invites if possible—fresh links help, but broken links kill momentum.
Also, don’t just say “we’re friendly.” Say what happens. “Weekly prompts + monthly contests + critique channels” is instantly scannable.
2) Write a description that answers: “What do I do here?”
My favorite server descriptions are short, clear, and a little specific. Here’s a template you can steal:
Example server description (copy/paste):
“Welcome to Fantasy Writers & Critique—a supportive Discord for writers of all levels. We run weekly writing prompts, monthly short story contests, and rotating workshop nights (character, plot, revision, and more).
What you can do:
• Join a genre channel (Fantasy / Sci-Fi / Romance / Poetry)
• Post drafts in critique (with our feedback guidelines)
• Vote on next week’s prompt
• Join buddy feedback pairs”
3) Set up onboarding that doesn’t rely on you being online 24/7
When new members join, they want two things: (1) where to start and (2) what’s expected. If you don’t give that, they’ll lurk for a week and then drift away.
What I’ve used that works well:
- #start-here (pinned message with the “first 10 minutes”)
- #rules (short + readable)
- #introductions (required post)
- #pick-your-roles (choose genres so they only see what they care about)
- #writer-chat (general conversation)
Example welcome message text (the one I’d pin):
“Hey! Welcome to the server 🎉 If you’re new, please do these in order:
1) Read #rules
2) Post in #introductions (2–3 sentences + what you’re writing)
3) Pick your roles in #pick-your-roles (Fantasy / Sci-Fi / Poetry / Critique)
4) Check #weekly-prompts and vote on next week’s prompt
If you’re stuck, message @Mod and we’ll point you in the right direction.”
4) Keep rules simple—but make critique expectations crystal clear
Rules should be short enough that people read them. Here are 5 rules I like because they’re enforceable:
- Be respectful (no harassment, no dunking on beginners).
- No spam (including repeated promo links).
- Give critique, not insults (focus on craft, not character).
- Credit sources (especially if you share excerpts from published work).
- Use the right channels (drafts go in critique; prompts go in prompts).
Then add a pinned “How to critique” mini-guide in your critique channel. Example:
- Start with one thing that worked.
- Then one suggestion with an example.
- End with one question (“What was your goal with this scene?”).
5) Host events with a schedule members can plan around
“Post prompts sometimes” doesn’t build habits. “Every week on Tuesday at 7pm” does.
Here’s a concrete example schedule I’d run for 3 months:
- Weekly (Tuesdays): #weekly-prompts
Theme: “Character goal + obstacle”
Format: members have 24–48 hours to post 300–800 words.
Voting: members vote by reacting to 3 prompt options (use a poll bot). - Weekly (Thursdays): #writer-chat question of the day
Example questions:
• “What’s the hardest scene to write in your current draft?”
• “What’s a trope you love (and why)?” - Monthly (First Saturday): Short story contest
Length: 1,000–2,000 words
Submission: post in #contest-submissions with a title + 1-sentence premise
Judging: 50% craft (clarity, pacing, voice), 30% creativity, 20% engagement (peer votes)
Winner selection: 1 mod + 2 volunteer judges, then announce + spotlight feedback highlights. - Monthly (Third Wednesday): Workshop night (45 minutes)
Agenda: 10 min teaching → 15 min example breakdown → 15 min practice prompt → 5 min Q&A.
If you want a seasonal example, you can absolutely run something like a winter writing prompt series, but I’d still tie it to a recurring cadence so people learn when to show up.
6) Encourage real interaction (not empty “how’s it going?” replies)
Interaction grows when you give members a reason to respond. Instead of “Say hi,” try prompts that are easy to answer:
- “What line are you stuck on this week?”
- “Drop a 1-sentence logline for your WIP.”
- “What’s one piece of advice you wish you got sooner?”
- “Who’s your favorite writer and what do you steal from them (honestly)?”
Also, celebrate progress. One simple post format works wonders:
Win of the Week template:
“Win of the Week (Week #1): @username finished a chapter draft!
What they did: (1 sentence)
What they learned: (1 sentence)
Want to join next week? Post your goal in #weekly-goals.”
7) Add bots/tools that actually reduce your workload
I’m not a fan of “add 12 bots and hope.” But a small set of well-configured bots can make your server feel alive and easier to manage. Here’s what I’d use:
- MEE6: moderation + (optional) levels/engagement.
Use it for: auto-mod basics, welcome/leave messages, and simple leveling to reward participation. Tip: don’t overdo leveling—too many gamified systems can make people spam. - Carl-bot: welcome messages + auto roles + reaction roles.
Use it for: “Pick your roles” and onboarding reminders. Tip: set roles based on genre so members self-sort immediately. - Dyno: moderation logs and useful configuration.
Use it for: logging mod actions, leveling backups, and keeping your server history clean when you need to review issues. - ProBot (or similar): advanced moderation helpers.
Use it for: spam control and anti-raid tools if your server grows quickly.
If you don’t want to rely on bots for everything, you can still automate the essentials with Discord features like Scheduled Events for workshops and contests, and channel permissions for critique queues.
8) Give members exclusive reasons to stay
People join for the idea. They stay for the routine and the perks. Examples that work in writing servers:
- Critique queue: a “request a spot” channel where members can sign up weekly.
- Prompt packs: members get a monthly downloadable prompt list or a curated set of examples.
- Early access: voting on next month’s contest theme before everyone else.
- Member spotlight: winners get feedback breakdowns, not just a trophy emoji.
9) Partner up to reach writers who already want what you offer
Don’t just “promote.” Collaborate. Look for other writing servers, forums, or Facebook groups with similar audiences. Then do something tangible:
- joint prompt swaps (each server runs a prompt and shares the best entries)
- co-hosted workshops (one topic, two communities)
- cross-posted contest themes
When you do this, your invite link isn’t just an ad. It’s a direct path into an event they already care about.
10) Promote consistently (and make it easy to click)
Social media promotion works best when you repeat a few content types. I’d rotate:
- Prompt teaser (short excerpt + link to join)
- Member highlight (with permission) + “come critique with us”
- Event reminder (date/time + what people should post)
For example, if you’re posting on Instagram or Reddit, include the same info every time: theme, deadline, and channel where people submit.

13. Empower Active Members with Roles and Responsibilities
One of the fastest ways to stop feeling like you’re doing everything is to give your most active members real roles. Not just “Member” and “Mod.” Think: Prompt Curator, Event Organizer, Beta Reader, and Workshop Host.
In my experience, people contribute more when they feel trusted. And honestly, they usually do a better job than you’d expect because they’re closer to what members want.
Here’s how I’d set it up:
- Prompt Curator: picks 3 prompt options every week; posts them in #weekly-prompts; runs a vote.
- Event Organizer: schedules contests/workshops and drafts the announcement message.
- Beta Reader: maintains a queue (example: “Drop your draft request by Friday”); assigns volunteers.
Important: set expectations in writing. A role without a checklist turns into “extra work” (and people burn out). Give them a simple template like:
Prompt Curator checklist (weekly):
1) Post 3 prompt options by Tuesday 6:30pm
2) Start the vote in #prompt-voting
3) Announce the winning prompt by Tuesday 7:00pm
4) Post a “how to participate” reminder in #writer-chat
14. Use Data and Feedback to Improve Your Community
I used to rely on vibes. “Seems like people like it.” That’s not enough. If you want growth that sticks, you need a feedback loop.
Track a few simple metrics weekly:
- 7-day retention: how many new members are still active after a week?
- #introductions participation rate: what % of new members post an intro?
- Event attendance: average unique attendees per workshop/contest announcement.
- Message rate in key channels: #writer-chat, #weekly-prompts, and critique channels.
- Churn reasons: ask departing members (or do a quick anonymous form) why they left.
Then run small tests. For example:
- Test A: prompt posted Tuesday vs. Thursday.
- Test B: contest theme announced 7 days ahead vs. 3 days ahead.
- Test C: critique posts allowed for 48 hours vs. 72 hours.
Keep what works for 4–6 weeks before changing again. If you constantly flip the server, people won’t build habits.
15. Facilitate Collaboration Through Pairing or Group Projects
Collaboration is where writing communities start to feel like communities instead of chat rooms.
Set up dedicated spaces like:
- #pairing (buddy feedback requests)
- #group-projects (anthology, shared worldbuilding, co-writing)
- #collab-updates (only for progress, not random chat)
Then run a repeatable collaboration event. Example:
- “Buddy Feedback Sprint” (every 2 weeks)
- Members sign up by posting: genre + word count range + what they want feedback on
- Pairing happens via reactions or a simple spreadsheet
- Feedback deadline: 72 hours
- Wrap-up: members post “what I changed” in #collab-updates
It’s not just about output. It builds accountability. People show up for their buddy.
16. Promote Consistency with a Content Calendar
If your server is random, your members will be random too. A content calendar removes guesswork and helps people plan around their real lives.
I like calendars that are simple enough to remember:
- Weekly: prompts + a “question of the day”
- Monthly: contest + workshop night
- Quarterly: bigger challenge (community anthology, revision month, genre spotlight)
Use Discord’s Scheduled Events for workshops/contests so reminders land automatically. If you prefer an outside tool, Google Calendar works fine—just make sure you post the dates in #announcements with the same wording every time.
One thing I learned the hard way: don’t overstuff the calendar. If you announce 5 things in a week, people miss all of them and stop trusting the schedule.
17. Leverage Popular Trends and Challenges to Attract New Members
Trends can help you get discovered—just don’t copy them blindly. Adapt the format to writing.
Here are trend-friendly challenge ideas that actually fit a writing Discord:
- Spring-themed Writing Challenge: “Write a scene where the weather changes the character’s decision.”
- Meme-to-Microfiction: members translate a meme caption into 300–600 words.
- Story Hook Roulette: members spin a prompt (character, setting, goal) and write for 20 minutes.
If you want a seasonal tie-in, you can use something like winter writing prompts and then turn it into a Discord-friendly series (weekly posts + one monthly “best of” thread).
The key is making it feel native. A trend that looks forced usually gets ignored.
18. Utilize Creative Channels and Topic-Specific Spaces
Channel clutter is real. New members don’t want to scroll for 10 minutes just to find where drafts go.
I recommend a clean layout:
- #start-here (pinned onboarding steps)
- #announcements (events, contests, workshop schedules)
- #weekly-prompts (prompt posts + submission threads)
- #critique (drafts + feedback guidelines)
- #writer-chat (general talk)
- Genre channels: #fantasy, #sci-fi, #romance, #poetry, #nonfiction
Also add one small resource channel like #writing-tips or #craft-breakdowns. When members have a place to share useful stuff, the server starts generating value even when you’re not posting.
19. Host Informative Workshops and Skill-Backsessions
Workshops are where you can build authority and keep people coming back. But only if they’re structured.
Instead of “we’ll talk about character development,” run a repeatable format:
- 10 minutes: teach one concept (example: “showing vs. telling”)
- 15 minutes: break down an example (a short excerpt or your own sample)
- 15 minutes: practice prompt (write 300–500 words)
- 5 minutes: Q&A + optional sharing
Use voice channels for live Q&A if you can, but don’t force it. Text-based workshops also work—especially for international communities.
Promote workshops ahead of time with a clear “what to bring” message. Example: “Bring one paragraph from your WIP and we’ll rewrite it together.” That boosts attendance a lot.
20. Build a Welcoming and Inclusive Atmosphere
Kindness isn’t a poster on the wall. It’s how you moderate and how you respond when things go sideways.
Here’s what works in practice:
- Model the behavior: when someone shares work, respond with specifics (“I loved the sensory detail in paragraph 2”).
- Correct critique tone early: if someone insults a writer, handle it fast and publicly (then remind them privately too).
- Make room for different skill levels: encourage beginners to post “practice drafts” and advanced writers to share “revision notes.”
- Address conflicts privately: don’t turn drama into a group event.
If your server feels safe, people come back. And when it feels safe, members invite friends without hesitation.
FAQs
Start with your server name + description. Use the same words people search: “writing prompts,” “critique,” “fiction writing,” “poetry,” etc. Then list your server on Discord listing sites and link directories, and make sure your invite link is always working. I also recommend posting your invite in a few targeted places (Reddit writing communities, genre-specific forums) with a short explanation of your weekly schedule—don’t just drop the link.
Include three things: (1) who it’s for, (2) what you do weekly, and (3) how newcomers join right away. For example: “For fantasy writers who want critique,” then list “weekly prompts (Tue), critique channel (daily), monthly contest (1st Sat), workshop night (3rd Wed).” Finally, add a quick call to action like “Post your intro in #introductions and pick your genre role in #pick-your-roles.” That last part reduces confusion instantly.
Give people prompts that are easy to answer and tie interaction to events. A simple setup is: #writer-chat has one question/day, #weekly-prompts posts the prompt with a word-count target, and #critique has a clear “how to critique” rule. If you want it to feel active, schedule one member spotlight post per week using the same format so people know what to expect.
Keep a consistent cadence (weekly prompt + monthly contest + workshop) and make sure newcomers can participate within their first 10 minutes. Track which events get replies and which ones get “views but no posts.” When something underperforms, don’t just scrap it—change one variable (time of day, prompt format, or submission length) and test again next month.






