---
title: "Discord announcement templates for servers and communities"
description: "Annotated Discord announcement templates: season launch, maintenance, incident, event, promo and rule change, plus the structure that gets read to the end."
url: "https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template"
type: "page"
language: "en-US"
---

Discord Bots · 10 min · Beginner

Published on Aug 26, 2026 · Updated on Aug 26, 2026

# How to write a Discord announcement that people actually read

Most server announcements die on the first line. This guide breaks down the anatomy of a notice that works, when to mention everyone without burning your audience, and gives you six ready-made templates for the cases that keep coming back.

By [Equipe StreetHosting](https://streethosting.com.br/en/autores#equipe-streethosting) · StreetHosting infrastructure and support team

[Community and game modes](https://streethosting.com.br/en/guides/topics/community)

Summarize with:

[](https://chat.openai.com/?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fdiscord-bots%2Fdiscord-announcement-template.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "ChatGPT") [](https://claude.ai/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fdiscord-bots%2Fdiscord-announcement-template.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Claude") [](https://www.google.com/search?udm=50&aep=11&q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fdiscord-bots%2Fdiscord-announcement-template.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Google AI Mode") [](https://x.com/i/grok?text=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fdiscord-bots%2Fdiscord-announcement-template.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Grok") [](https://www.perplexity.ai/search/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fdiscord-bots%2Fdiscord-announcement-template.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Perplexity")

Share:

[](https://x.com/intent/tweet?text=Discord%20announcement%20templates%3A%20how%20to%20write%20one%20people%20read&url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fdiscord-bots%2Fdiscord-announcement-template "Share on X") [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fdiscord-bots%2Fdiscord-announcement-template "Share on Facebook") [](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fdiscord-bots%2Fdiscord-announcement-template "Share on LinkedIn") [](https://wa.me/?text=Discord%20announcement%20templates%3A%20how%20to%20write%20one%20people%20read%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fdiscord-bots%2Fdiscord-announcement-template "Share on WhatsApp")

For agents: Copy as Markdown [.md](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template.md)

In this guide 7 sections

* [Anatomy of an announcement that gets read](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#anatomia)
* [When to use everyone without burning your audience](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#everyone)
* [Announcement channel and chat channel](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#canal-de-anuncio)
* [Embeds: what they solve and where they trip you up](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#embed)
* [Six annotated templates](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#templates)
* [What to avoid](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#o-que-evitar)
* [Turning this into a routine](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#rotina)

Quick answer

A Discord announcement that works states in the **first line** what happened, then **what changes** for the reader, **when** it applies and **what to do now**. Greetings, thank-yous and emoji come after that, if there is room left. If you would rather have the text ready than write from scratch, the [writecord](https://writecord.streethosting.com.br/?utm%5Fsource=streethosting&utm%5Fmedium=site&utm%5Fcampaign=tools&utm%5Fcontent=guia%3Atemplate-anuncio-discord-servidor) generates the announcement from the topic and the tone, with a short version for the embed.

## Anatomy of an announcement that gets read[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#anatomia)

An announcement on Discord does not compete with other announcements. It competes with chat, memes, notifications from fifteen other servers and the person's life outside the app. The notification preview shows very little text, and that is where the decision to open or ignore happens.

That is why the writing order matters more than the content. Four blocks, always in this sequence.

1. **The fact.** What happened or is about to happen, in one sentence. The server is going offline. A new season opens Saturday. The IP changed.
2. **The impact.** What changes for the person reading. Your progress carries over. You need to update the saved address. Registration closes earlier.
3. **The when.** Date, time, duration and time zone. Without it, the announcement produces a queue of questions in the chat channel.
4. **The action.** What the person does now. Update the IP, confirm attendance, read the new rule, do nothing and just wait. Saying explicitly that nothing needs to be done is also an action.

The most common mistake is opening with "Hey everyone, how's it going?". That line takes up exactly the space the notification preview shows, and it says nothing. The person reads the greeting, does not get the subject and does not open it.

## When to use everyone without burning your audience[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#everyone)

Mentioning everybody is the most powerful and most misused feature on Discord. It fires a notification at people on their phone, at work and asleep. And it has a cost nobody measures in the moment: every unnecessary mention pushes a slice of the community to mute the channel, and whoever mutes rarely comes back.

| Situation               | Right mention  | Why                                                              |
| ----------------------- | -------------- | ---------------------------------------------------------------- |
| Server just went down   | everyone       | Affects everybody and the information loses value within minutes |
| IP or address changed   | everyone       | Without it nobody can get in                                     |
| Season opening          | everyone       | It is the event the whole community was waiting for              |
| Scheduled maintenance   | here or a role | Already announced earlier, this is just a reminder               |
| Event for one game mode | Specific role  | Only matters to the people who play it                           |
| Store promotion         | No mention     | A commercial post that pings everybody burns trust fast          |
| Rule change             | None or here   | Needs to be on record, does not need to wake anyone up           |

A homemade metric that works: if you mentioned everyone more than once a week in a normal month, with no incident at all, you are spending the resource. Interest roles solve almost all of these cases, and the guide on [reaction roles](https://streethosting.com.br/en/guides/discord-bots/discord-auto-role-reaction-roles) shows how to let people choose for themselves what they want to receive.

## Announcement channel and chat channel[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#canal-de-anuncio)

An announcement channel has a job beyond communicating: being searchable. Three months from now someone will want to know when the season opened, what changed in the building rule or when the last maintenance was. That only works if the channel is a clean timeline.

* Announcement channel set to read-only for everyone
* Reactions enabled, because they measure reach without cluttering
* Threads allowed when a specific announcement is going to spark debate
* Chat channel linked at the end of every important announcement
* No loose chatter, memes or corrections posted as a new message without editing the original

On corrections: when an announcement goes out with a mistake, edit the original message and add a short erratum line at the end. Posting a second message to correct the first leaves both versions circulating, and there will always be someone who only reads the wrong one.

If your Discord follows a game server, it is worth having a status-only channel fed by a webhook, separate from the editorial announcements. The guide on [webhook alerts](https://streethosting.com.br/en/guides/discord-bots/discord-webhook-server-alerts) covers that automated part.

## Embeds: what they solve and where they trip you up[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#embed)

The embed is the block with the colored bar down the side. It exists to organize information and to give a visual signal before reading. Used well, the person already knows the type of notice from the color, before reading the first word.

### Color as a code[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#cor-como-codigo)

* **Green:** opening, back to normal, good news.
* **Yellow:** scheduled maintenance, notice with a deadline, rule change.
* **Red:** ongoing incident, outage, something that needs attention right now.
* **Brand color:** event, promotion, editorial content with no urgency.

Pick the four and keep them forever. A color code only becomes a code once the community learns it, and it only learns through repetition.

### Limits you will run into[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#limites-do-embed)

| Field              | Limit           | Practical use                            |
| ------------------ | --------------- | ---------------------------------------- |
| Title              | 256 characters  | One short sentence with the fact         |
| Description        | 4096 characters | The body of the announcement             |
| Fields             | 25 per embed    | Date, duration, what changes, what to do |
| Field name         | 256 characters  | Short label, like When                   |
| Field value        | 1024 characters | The content under that label             |
| Footer             | 2048 characters | Team signature and time                  |
| Embed total        | 6000 characters | Sum of everything above                  |
| Embeds per message | 10              | Rarely worth using more than one         |

A mention inside an embed notifies nobody. If you need to ping a role, the mention has to be in the message text, outside the embed. It is the gotcha that lets a lot of important announcements slip by unnoticed.

For the occasional embed, a webhook is enough. A bot starts to pay off when you want to schedule posts, repeat the same format every week or update an incident notice without posting a new message. In that case the guide on [scheduling messages](https://streethosting.com.br/en/guides/discord-bots/discord-bot-schedule-messages) shows the way, and a bot that has to be up at announcement time calls for [24-hour bot hosting](https://streethosting.com.br/en/bots).

## Six annotated templates[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#templates)

The cases below cover most of what a server community needs to announce in a year. Adapt the text to your tone, but keep the order of the blocks.

### 1\. Season opening[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#template-temporada)

Mention: everyone. Color: green. It is the announcement that most deserves interrupting everybody, and the only one where excitement in the text helps instead of getting in the way.

* **Title:** Season 4 opens Saturday at 8 PM
* **Impact:** new world, progress from the previous season is archived and stays accessible in read-only mode
* **When:** Saturday the 12th, at 8 PM Brasília time. The IP goes live at the same time.
* **Action:** join with the indicated version and check the updated rules before building
* **Extra that works:** artwork with the characters of well-known community players, which is covered in the guide on [3D skin avatars](https://streethosting.com.br/en/guides/minecraft/minecraft-3d-skin-avatar)

### 2\. Scheduled maintenance[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#template-manutencao)

Mention: here or a role, with a heads-up days in advance. Color: yellow. What annoys the community is never the maintenance, it is the surprise.

* **Title:** Maintenance on Thursday, 3 AM to 5 AM
* **Impact:** the server is offline during the window. Nothing is lost, the backup runs beforehand.
* **When:** Thursday the 17th, 3 AM to 5 AM Brasília time. Expected duration of two hours.
* **Action:** leave the server before 3 AM to avoid losing whatever was loading
* **Mandatory wrap-up:** a message confirming it is back. Maintenance without a back-online confirmation generates a queue of questions.

### 3\. Ongoing incident[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#template-incidente)

Mention: everyone. Color: red. Here speed is worth more than wording. Owning the problem in five minutes with little information beats a flawless statement an hour later.

1. **First message:** confirm the problem exists, say what is affected and promise the next update within a specific interval, for example thirty minutes.
2. **Updates:** edit the same message or reply in the thread, always within the promised interval. Saying it is still being investigated is a valid update.
3. **Closing:** announce it is back, say in one sentence what caused it and what was done to keep it from happening again. Going quiet after the incident is what really erodes trust.

Never promise a recovery time that depends on third parties. Promise an update time, which depends only on you. One is a guess, the other is a commitment you can keep.

### 4\. Event[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#template-evento)

Mention: interest role. Color: brand color. An event lives on advance notice and on clarity about what the person gets out of it.

* **Title:** PvP tournament on Sunday at 7 PM
* **Impact:** limited spots, prizes in VIP role and server currency
* **When:** Sunday the 20th, at 7 PM. Sign-ups until Saturday night.
* **Action:** react with the sword to sign up or open the form in the indicated channel
* **Reminder:** post a second short notice two hours before. That is the one that actually brings people in.

### 5\. Store promotion[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#template-loja)

Mention: none. Color: brand color. A commercial post that pings everybody is the fastest way to teach the community to ignore the announcement channel.

* **Title:** VIP 30% off until Sunday
* **Impact:** say what VIP gives, in three concrete items, not adjectives
* **When:** until Sunday the 20th, at 11:59 PM
* **Action:** direct link to the store, no middle steps
* **Frequency:** at most one promotion per month. A permanent discount stops being a discount and becomes the price.

### 6\. Rule change[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#template-regra)

Mention: none or here. Color: yellow. The goal is a record, so the text has to survive being read months from now by someone who was not there.

* **Title:** New rule on building near spawn
* **What changes:** the old rule and the new one, side by side. Without that nobody understands what actually changed.
* **Why:** one sentence of context drastically reduces the arguing in the chat channel
* **When it takes effect:** a specific date, and what happens to what was already built
* **Action:** where to complain or ask questions, with the right channel linked

## What to avoid[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#o-que-evitar)

* **Wall of text.** A ten-line block with no breathing room does not get read even by the team that wrote it. Break it into embed fields or short items.
* **An emoji on every word.** One or two marking a section help. A whole line of emoji turns into noise and also gets in the way of screen reader users.
* **Announcement with no date.** Soon, in the coming days and later today are not information. If you do not know the date, say you do not know yet and promise when you will.
* **A deadline you do not control.** Promising it will be back in an hour when the cause sits with another provider creates a second crisis on top of the first.
* **Incident with no ending.** The missing message is almost always the last one: the one that says it is over and what was done.
* **The whole sentence in caps.** It does not increase urgency, only fatigue, and it disappears among other announcements in all caps.

## Turning this into a routine[](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#rotina)

A well-informed community is not the result of writing talent, it is the result of repetition. The same six formats, the same four colors, the same place. After two months the community reads the announcement by color and format before reading the text.

When writing from scratch every time starts to weigh on you, the [writecord](https://writecord.streethosting.com.br/?utm%5Fsource=streethosting&utm%5Fmedium=site&utm%5Fcampaign=tools&utm%5Fcontent=guia%3Atemplate-anuncio-discord-servidor) handles the draft: you give it the topic and the tone, it hands back the message ready to paste into the channel, with a short version for the embed. It is one of the [free tools](https://streethosting.com.br/en/ferramentas) from StreetHosting.

And it is worth remembering the obvious: a quality announcement does not make up for an unstable server. If your bot needs to be awake at posting time, it calls for [dedicated bot hosting](https://streethosting.com.br/en/bots) instead of running on your computer. And if the community follows a game server, that server's stability is what makes the season announcement worth anything, whether on [Minecraft hosting](https://streethosting.com.br/en/minecraft) or on a [VPS](https://streethosting.com.br/en/vps) of your own.

In this guide

* [Anatomy of an announcement that gets read](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#anatomia)
* [When to use everyone without burning your audience](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#everyone)
* [Announcement channel and chat channel](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#canal-de-anuncio)
* [Embeds: what they solve and where they trip you up](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#embed)
* [Six annotated templates](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#templates)
* [What to avoid](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#o-que-evitar)
* [Turning this into a routine](https://streethosting.com.br/en/guides/discord-bots/discord-announcement-template#rotina)

## Frequently asked questions

How do you write an announcement for a Discord server?

Start with the fact, not the greeting. The structure that works has four parts: what happened or is about to happen, what changes for the reader, when it applies and what the person should do now. Date, time and time zone are mandatory in any notice with a deadline.

When should I mention everyone in an announcement?

Only when the information affects everybody and is urgent: the server went down, the IP changed, a season is opening, a registration deadline is closing. For everything else, use a specific role or mention nobody. Every unnecessary everyone makes more people mute the channel for good.

What is the character limit of a Discord embed?

Title up to 256 characters, description up to 4096, up to 25 fields with a 256-character name and a 1024-character value, footer up to 2048 and author up to 256. Everything in the same embed combined cannot exceed 6000 characters, and a message accepts at most 10 embeds.

Do I need a bot to post a good-looking announcement?

For a simple, occasional embed a webhook does the job. A bot is worth it when you want to schedule posts, repeat the same format every week, update an incident notice in real time or mirror the game server status in the channel.

How do I announce maintenance without annoying the community?

Give advance notice, state the exact window with the time zone, say what goes offline and what keeps working, and promise a confirmation at the end. What annoys people is not the maintenance, it is finding out on the spot that the server is down and getting no information.

Should an incident announcement go out before there is a fix?

Yes. Owning the problem within a few minutes is worth more than a perfect statement an hour later. Post what you know, say how long until the next update and keep that interval, even if the update is just saying you are still investigating.

Next step

See bot plans

24/7 Discord bots with fast activation and support in Portuguese.

[See bot plans](https://streethosting.com.br/en/bots)

[Minecraft plans Compare Minecraft hosting options in Brazil.](https://streethosting.com.br/en/minecraft) [See VPS plans Root VPS in Brazil with NVMe and Anti-DDoS.](https://streethosting.com.br/en/vps)

## Related guides

[Discord bots Intermediate How to schedule automatic Discord messages with a bot Scheduled messages are great for event announcements, voting reminders and recurring notices. See how to implement them with node-schedule in a Node.js bot, plus scheduling best practices. 3 min Read guide](https://streethosting.com.br/en/guides/discord-bots/discord-bot-schedule-messages) [Discord bots Beginner How to set up an automatic welcome message on Discord with a bot A welcome message sets the first impression of your server. See how to set it up with your own Node.js bot or with ready-made bots, and what to include to keep new members around. 3 min Read guide](https://streethosting.com.br/en/guides/discord-bots/discord-welcome-message-bot) [Discord bots Beginner How to use a Discord webhook for server alerts A Discord webhook is a quick way to notify your team about incidents, deploys and outages without relying on manual monitoring. 2 min Read guide](https://streethosting.com.br/en/guides/discord-bots/discord-webhook-server-alerts)

[← Back to the Guide Center](https://streethosting.com.br/en/guides)
