How to Use Slack Notification Sounds to Improve Team Communication in Remote Work
Most teams that try to fix their notification sounds do it twice. The first attempt makes things noisier, and the second attempt is usually a retreat back into total silence, which is how you end up missing the deploy that broke checkout.
The failure is almost never the idea. It is the setup. Here are six ways it goes wrong, why each one looks reasonable while you are building it, and what to do instead.
1. Giving every channel its own sound
You are in thirty channels, so you assign thirty sounds. It feels like maximum information per alert.
It is not. You can reliably tell apart four or five short sounds without thinking about it. Past that you are back to looking at the screen to find out what happened, which is the thing you were trying to avoid. Map sounds to what you will do, not to where the message came from. Three is usually enough: drop everything, look soon, look later.
2. Choosing sounds because they are pleasant
Pleasant sounds tend to be soft, rounded, and similar to each other. That is exactly what makes them useless as signals. Two mellow marimba tones are indistinguishable when you are mid-sentence in a code review.
Audition candidate sounds in pairs, back to back, while you are actually typing. If you cannot name which one played without looking, one of them has to go. A sound can be unremarkable and still be distinct.
3. Rolling it out as a team-wide standard
A shared sound vocabulary sounds like a good idea. "Everyone uses the chime for #incidents" seems like it builds a common reflex.
In practice the standard collapses within a month, because your teammates have different roles, different focus hours, and different tolerance for interruption. The person on support wants the support channel loud; the person shipping a migration wants it muted until Thursday. Agree on the tiers as a team and let each person pick the actual audio. What matters is that everyone has the same idea of what counts as urgent.
4. Treating volume as the only priority signal
Louder equals more important is intuitive, so people set the urgent alerts to full and everything else to a whisper. Then the whisper alerts become inaudible in a cafe and the loud ones become unbearable in headphones, and the whole scheme falls apart the first time you change rooms.
Use two dimensions instead. Let timbre carry identity, so you know what it is, and let volume carry urgency, so you know how much it wants from you. Chirpy sets volume per rule, so the same sound can be a nudge in one context and a demand in another.
5. Leaving Slack's own sound switched on
This one is a silent killer, and by silent I mean the opposite. You configure custom rules, everything works, and every notification now plays twice: once from Slack, once from your rule. The double-chime is annoying enough that people blame the new setup and turn it off.
Slack's own sound has to go to None before anything else will feel right. In Slack, open Preferences, then Notifications, then set the notification sound to None. Chirpy reads macOS notifications through the Accessibility API rather than talking to Slack, so it has no way to suppress Slack's audio for you. You have to mute it at the source.
6. Setting it up once and never touching it again
Configuration feels like a thing you finish. But the rule you wrote for #prod-alerts in March made sense when that channel fired twice a week. By September it fires forty times a day and you have stopped hearing it entirely.
Put fifteen minutes in the calendar every quarter. Look at which rules actually fired and ask whether each one still earned the interruption. Demote the ones that became routine. Delete the ones for channels you left. A sound scheme that never shrinks is a sound scheme that will eventually be muted wholesale.
Fixing it without the guesswork
Chirpy is a native macOS menu bar app that gives you the pieces these fixes need: rules that match on app, channel, person, or keyword, priority ordering so the first match wins, per-rule volume, and 72+ built-in sounds plus your own .mp3, .wav, or .caf files. It reads notifications locally through the Accessibility API and never connects to your Slack account. Try it free for three days, no card required.