Who Answers the Silence Alert? A First-Response Plan for Small Radio Teams

A silence alert is only useful if someone reads it and knows what to do next. At a lot of small and community stations, the alert goes to whoever set up the monitoring, often the one technical volunteer, and that person may be asleep, at work or on holiday when the stream goes quiet on a Saturday night. This post is about the human side of monitoring: who gets the alert, what they check in the first few minutes, and how to make sure the whole chain still works a few months from now.

The product details here come from silencealarm.com. The rest is general practice for small radio teams. Adapt it to how your station is actually run.

Decide who the alert is for

Start by writing down one name: the person who is expected to react when the stream goes silent. Then write down the second person, who takes over when the first one can’t. Most stations skip this step because “everyone gets the email” sounds safer. In practice, when five people get the same alert, each of them tends to assume someone else is already on it.

The right person is not always the most technical one. Someone who can open the stream on a phone, call the studio and tell the presenter that nothing is going out solves a surprising number of incidents. The technical volunteer can be the second step for the problems that need a login to the playout or streaming server.

Some questions worth answering as a team:

  • Who covers nights and weekends, when automation is running and nobody is in the studio?
  • Who covers when the usual person is away for a week?
  • How long should the first person have before the second one steps in?
  • Is it fine to wake someone at 3 a.m. for a silent stream, or does your station accept a gap until morning?

There is no correct answer to the last question. A station that streams a live morning show to a big audience will answer it differently from a hobby station playing automated music overnight. The point is to decide it ahead of time instead of during the incident.

Route the alert to where that person will see it

An email to a shared station inbox that nobody opens at the weekend will arrive on time and still be missed. Send the alert to an address the responsible person actually reads on their phone, and check that it doesn’t end up in a spam or promotions folder.

On SilenceAlarm’s Free plan, alerts go by email to one address. If more than one person needs it, one workaround is a mailing list or forwarding address that you manage yourself, so the list of recipients can change without touching the monitor. Pro adds mobile push notifications via ntfy alongside email, which is easier to notice at night than one more email in a busy inbox. Enterprise customers can discuss other channels, such as SMS or webhooks, directly with SilenceAlarm.

Also keep the timing in mind. Alerts follow scheduled checks: every 15 minutes on Free, and every 1 to 60 minutes on Pro. A problem that starts just after a check is found on the next one, and detection and delivery add a little more time on top. Your team should know roughly how late the first message can be, so nobody is surprised that listeners noticed first.

The first five minutes after an alert

When the alert arrives, the goal is to find out quickly whether listeners are really hearing nothing, and roughly where the problem is. A short, fixed routine helps, especially for someone who is half awake.

  1. Listen yourself. Open the public stream in a normal player or app, the same way a listener would. If you hear programme audio, note the time and keep an eye on the next check. If you hear nothing, it is a real incident.
  2. Check whether the stream is there at all. A player that won’t connect points to a different problem than a player that connects and plays silence. The first usually means the stream or the server is down. The second usually means the stream is up but no audio is being sent into it.
  3. Contact the studio or the person on air. If someone is in the studio, a phone call is often the fastest fix. A muted channel on the mixer, a wrong input or a paused playout system can be solved in seconds by the person standing next to it.
  4. Escalate if it isn’t solved quickly. If nobody is in the studio or the simple checks don’t help, hand it to the person who can log in to the playout, encoder or hosting panel. Agree beforehand how quickly that hand-over should happen.

If you want a second opinion on the audio without opening a player, the free 20-second audio check on silencealarm.com works without an account. Paste the public stream URL and it shows whether audio was present at that moment. For a closer look at finding where the audio stops between studio and stream, we wrote a separate guide: Icecast connected but no sound.

Close the incident properly

SilenceAlarm sends a second message when a later check finds audio again. Treat that as the signal that the stream is back, and tell the rest of the team so they stop working on it. A short message in the station’s group chat is enough.

Then write two or three lines down while it’s still fresh: when it started, what the cause was, and what fixed it. After a few incidents, these notes show patterns. Maybe the silence always follows a scheduled restart, or always happens when a particular show hands over to automation. That is the information you need to stop the next one, and it’s easy to lose if nobody writes it down.

Keep a one-page plan

All of the above fits on a single page, and it should. Pin it in the studio and share it in the team chat. A useful plan usually includes:

  • who gets the alert first and who is the backup, with phone numbers
  • the public stream URL to listen to
  • the studio phone number
  • who can log in to the playout and the hosting panel
  • how long to wait before escalating

Keep passwords off this page. Names of the people with access are enough.

Test the chain now and then

Monitoring that hasn’t fired in months can fail without anyone noticing. Email addresses change and volunteers leave. Every few months, check that the alert address still reaches the right person and that the backup still knows they’re the backup. The Free plan also requires a monthly email confirmation, so make sure that email reaches someone too.

A planned test is a good occasion for this. If you have a maintenance window where the stream will be silent anyway, let the team know it’s a test and see whether the alert reaches the people on the list, and how long it took.

FAQ

Can several people receive the same silence alert?

On the Free plan, alerts go to one email address. You can point that address at a mailing list or forward it yourself if several people need it. Pro adds mobile push via ntfy. Enterprise customers can discuss other notification channels with SilenceAlarm.

Why did a listener notice the silence before the alert arrived?

Alerts follow scheduled checks, so silence that starts just after one check is found on the next. Free checks every 15 minutes, Pro every 1 to 60 minutes, and detection and delivery add some time. A shorter check interval on Pro reduces that gap but doesn’t make it zero.

How do I know the stream is back?

SilenceAlarm sends a follow-up message when a later check finds audio again. It’s still worth listening to the stream yourself for a minute before you tell the team it’s fixed.

Do we need someone on call around the clock?

That depends on your station. Some stations want a response at any hour, others accept that overnight silence is handled in the morning. Decide it as a team in advance and write it in your plan.

Leave a Comment

Your email address will not be published. Required fields are marked *