# Status page subscribers and announcements > Let visitors subscribe to your status page for updates, and post announcements to keep everyone informed. Source: https://infranest.io/docs/status-page-subscribers Last updated: 2026-10-26 --- Status pages can collect email subscribers, connect chat channels, and carry announcements, so the people who rely on your service always know what's going on. This is for anyone running a **Status Pages** entry who wants visitors kept in the loop automatically. ## Overview - Visitors can subscribe by email and get notified automatically when there's an incident or update. - You can also connect a Slack, Microsoft Teams or Discord channel so updates post there directly. - You can post a one-off **Announcement** — for maintenance, an incident summary, or a general message — without opening a formal incident. ![Status page subscribers and announcements](/media/34836ca5-9bc4-4285-9700-038c6f327b08) ## Turn on email subscriptions 1. Open your status page and go to the **Subscribers** tab. 2. Find the switch that enables **Subscribe to updates** and turn it **On**. 3. With it on, visitors see a subscribe box on your public page and are emailed automatically whenever there's an incident or an update. With it **Off**, the subscribe box disappears and nobody new can sign up. 4. Set a **Reply-to address** so replies to your outage emails go somewhere you'll see them. Outage emails are always sent from InfraNest's address for reliable delivery, but replies go to the address you set here. Leave it blank and replies will bounce. > [!NOTE] > Subscriber addresses are only ever used to send status updates for this page — it isn't a marketing list. The subscribe form and confirmation email both say so, and there's no download or bulk-import option. ## Manage your subscriber list 1. In the **Subscribers** tab, review how many people have subscribed, how many are **Awaiting confirmation**, and a chart of list growth over time. 2. Use **Search by address…** to find a specific subscriber. 3. Remove one person with the × on their row — this does exactly what their own unsubscribe link does. 4. Use **Remove all** from the same tab to clear the whole list. 5. Check the **Status** column for problem addresses: **Address does not exist** or **Blocked by their provider** explains why someone says they never got your email, while **Not confirmed yet** means they simply haven't confirmed their subscription. > [!TIP] > The subscriber chart counts people subscribed today, so it answers "is this growing" rather than "how many did I have in June" — anyone who's unsubscribed won't appear in it. ## Connect a Slack, Teams or Discord channel 1. On your public page, below the email subscribe box, open **Post to Slack, Teams or Discord**. 2. Paste the channel's webhook URL and **Connect** it — updates start arriving immediately, with no confirmation email needed, since creating the webhook already proves you administer that channel. 3. To get a webhook URL **in Slack**: go to Apps → Incoming Webhooks → **Add to Slack**, pick the channel, then copy the address (it looks like `https://hooks.slack.com/services/…`). 4. To get a webhook URL **in Discord**: open channel settings → Integrations → **Webhooks** → New Webhook, pick the channel, then copy the address (it looks like `https://discord.com/api/webhooks/…`). 5. To get a webhook URL **in Teams**: open the channel → **⋯ → Workflows**, create a flow from the **Post to a channel when a webhook request is received** template, and copy the URL shown when you save it. 6. InfraNest detects which of the three services the URL belongs to, and confirms which one was connected. > [!WARNING] > The old Teams Incoming Webhook connector was switched off on 22 May 2026. A `webhook.office.com` address will be refused — use the **Workflows** method instead. ## Manage connected channels 1. In the **Subscribers** tab, connected channels show as **Slack**, **Microsoft Teams** or **Discord** with a short code rather than the webhook URL, since the URL itself could post to your channel. 2. Each connected channel also appears as its own tile, so you can see at a glance where your updates are going. 3. If a channel stops working it's marked, the same way a dead email address is: **Webhook no longer exists** usually means the app, webhook or workflow was removed or turned off on the other end — create a new webhook and connect it again. **Could not be reached** usually clears itself once an update gets through; it only appears after more than one failure, so a single bad minute won't flag it. 4. To disconnect a channel, remove its row from the **Subscribers** tab. ## Post an announcement 1. Go to your status page's announcement area and select **New announcement**. 2. Type your message — a maintenance notice, an incident summary, or a general update. 3. Select text and use the formatting buttons above the message box: **Bold** or *italic* to emphasize a word, **Link** to point visitors somewhere (paste the address over the highlighted `https://`), or a bulleted list to turn lines into a list. 4. Paste a web address on its own, starting with `https://` or `http://`, and it becomes a clickable link automatically; long addresses are shortened to just the site name so they don't stretch the notice. 5. Check **How it should read** at the bottom of the form — it shows the notice exactly as visitors will see it. Anything you type outside the supported formatting, such as headings or images, will show as plain text. 6. Save or publish the announcement to make it live on the page. > [!TIP] > You can also use **Schedule one** to set an announcement to appear and end at specific times, rather than posting it immediately. ## Troubleshooting - **A subscriber says they never got an email:** check their row in the **Subscribers** tab — if it reads **Address does not exist** or **Blocked by their provider**, the address itself is the problem, not your notification. - **A Slack/Teams/Discord channel stopped receiving updates:** look for **Webhook no longer exists** (something was removed or disabled on the other end — reconnect with a fresh webhook) versus **Could not be reached** (usually temporary and clears on its own). - **Someone tried to subscribe but can't:** confirm the **Subscribers** tab switch is still **On** — when it's off, the subscribe box doesn't appear on the public page.