Who this is for
For community managers, moderators, game developers, club organizers, and creators posting event invitations, maintenance notices, rule changes, or server updates.
Write for members scanning the announcements channel
Members may see your post between conversations or as a notification preview. Lead with the actual news: registration is open, a channel is moving, or the game server will be unavailable. Skip introductions such as “We are delighted to inform our valued community.” They delay the useful part and rarely sound like a moderator speaking.
Build the announcement around three questions: What is changing? Who needs to act? What should they do next? Use short paragraphs and a small list when there are several requirements. A heading can make the topic clear, but bolding every sentence makes priorities harder to distinguish. Keep essential instructions in text even when you attach a graphic.
Make it casual, not careless
Casual mode should relax the language, not weaken the message. Replace “participants are requested to indicate their attendance” with “React with ✅ if you’re coming.” Use contractions and familiar words, but don’t force memes, slang, or enthusiasm that your moderators would never use. A quiet study server and a lively gaming community need different voices.
Match warmth to the situation. An event invitation can be playful; a moderation-policy change needs clear boundaries. For outages, acknowledge the disruption without inventing a cause, promising an unconfirmed fix, or turning frustration into a joke. Preserve the difference between “we expect service to return” and “service will return.” Those statements create different expectations.
Revise in Humanizely, then check the Discord-specific details
Paste your draft into Humanizely and choose Casual mode. Include instructions such as: “Keep the date, UTC time, channel names, and eligibility unchanged. Don’t add a ping or promise.” The free allowance is 500 words per request. For longer announcements, revise coherent sections and review the combined version for repetition or contradictory instructions.
Treat the rewrite as an editable draft. Compare names, numbers, links, and deadlines against the original source. Preserve any citations or source links beside the claims they support. Confirm that linked channels are visible to the intended roles and that registration links work. If you use Discord timestamp markup, verify the underlying instant and its displayed time. Review mentions before sending: a rewrite should never silently escalate a role notification into @everyone.
