How to Use Slack Notification Sounds to Improve Team Morale in Remote Work
Ten questions I get asked about notification sounds and how they land on a remote team, answered without the padding.
Can a notification sound really affect how a team feels?
Not on its own. What it affects is how often people get yanked out of something they were concentrating on. Do that thirty times a day and by Thursday afternoon people are short with each other in threads and nobody can say why. The sound is not the morale problem. It is the delivery mechanism for the morale problem.
What is the first sign that notification noise is wearing people down?
People start muting things without telling anyone. Watch for the moment someone writes "sorry, I have that channel muted" in a thread. That is the visible edge of a much larger set of channels they never mentioned. The second sign is that everything moves to DMs, because a DM is the only alert people still trust to be relevant.
Isn't the obvious answer just to turn notifications off?
It is the fastest answer and it usually fails within a fortnight. All-off means the person becomes unreachable, so someone has to text them for anything genuinely urgent, which is worse for everyone. The people who successfully go all-off are usually the ones with a colleague quietly absorbing the interruptions on their behalf.
Does a distinct sound for good news actually help?
More than I expected. If your wins channel or your CI success messages get their own short, warm sound, people stop bracing every time the laptop makes a noise. Most teams currently have exactly one sound for "someone deployed to prod at 2am" and "someone shipped the feature they have been stuck on for three weeks." Those should not be the same noise.
Won't a celebration sound get annoying?
Yes, if it is long or musical. Keep it under half a second. Anything with a melody becomes unbearable around the fortieth hearing, and you will hear it forty times in a month. Short and low outlasts cheerful and long.
Should the whole team use identical sounds?
No, and trying to enforce it wastes a meeting. What is worth agreeing on is the categories: which kinds of message deserve to interrupt someone, which deserve a quiet marker, which deserve nothing at all. Once that is settled, let people pick whatever they like inside each category. Someone will use a bird call for DMs and it will be fine.
What about people who work with speakers on, in a shared room?
Per-rule volume covers most of it. Turn the urgent tier down to something polite and set the routine tier to silent for those hours. The alternative people reach for instead is muting the whole app, which puts them back at the start.
Where does Chirpy fit, and does it need access to Slack?
No Slack access, which surprises people. Chirpy is a native macOS menu bar app that reads notifications through the macOS Accessibility API, locally on your own machine. There is no workspace to authorize and no admin approval to chase. You install it, grant the Accessibility permission, set Slack's own notification sound to None so you do not hear two at once, then write rules that match on app, channel, person, or keyword.
What is the smallest useful change I could make today?
Give direct messages from your two or three closest collaborators one sound, and give everything else in Slack a much quieter one. That single split does most of the work. You can spend an afternoon building a fifteen-rule setup later if you want to, but you do not need to.
What if people try it and hate it?
Then they turn it off and you have learned something cheap. There is a three-day trial with no card required, it is $19.99 once rather than a subscription, and there is a 30-day money-back guarantee. The download is 7.8 MB and it needs macOS 13 or later.
If the noise on your team has stopped being useful, see what Chirpy does about it.