How to Use Slack Notification Sounds to Improve Team Adaptability in Remote Work
The notification setup that works for three people is actively harmful at fifty, and the setup for fifty is pointless overhead at three. Most teams pick one configuration early and then wonder why Slack feels louder every quarter. It is the same rules meeting ten times the message volume.
Here is what to run at each stage and what specifically to change when you cross into the next one.
Three people
At this size everything is urgent and nothing is routine. You are in a shared context all day. You do not need a taxonomy.
The setup
One rule. A single sound for direct messages and @mentions, everything else silent. That's it.
Resist the urge to give each of your two colleagues their own sound. It feels charming and you will delete it within a month, because at three people you already know who is messaging you from the content of the message and the time of day. The sound is not carrying information the context lacks.
What tells you to move on
You start missing things in a channel because you were not looking at Slack. That is the first real signal. Until then, one rule.
Fifteen people
This is where it breaks. Message volume roughly squares, channels multiply, and you no longer read everything. You also stop knowing what every notification is about before you open it, which is exactly when sound starts earning its place.
The setup
Three rules, organised by channel rather than by person:
- Mentions and direct messages. Short, high, slightly louder than the rest.
#prod-* or whatever your incident channel prefix is, on a lower two-note sound. Use the wildcard, not individual channel names. New incident channels get created during incidents, and nobody edits notification rules at 2am.#support-* or your equivalent customer-facing prefix, on a third sound at lower volume.
Everything else silent.
The change that actually matters
Switching from person-matching to channel-matching. At three people, "who" was the useful axis. At fifteen, "what kind of thing" is. A message from your CTO about lunch and a message from your CTO about a customer outage should not sound identical, and only a channel or keyword rule can tell them apart.
Set priority ordering explicitly here. With three rules, overlaps become common: a mention inside #prod-api matches two rules, and you want the mention sound to win.
Fifty people
Fifty people generate more notifications than any sound scheme can encode. The instinct at this size is to add rules. The correct move is to delete them.
The setup
A hard ceiling of four sounds, and an audit.
Sit down with your current rule list and, for each one, answer whether you have physically changed what you were doing in response to it in the last two weeks. If not, delete the rule and let that traffic go silent. Most people find they are down to three real sounds and four decorative ones.
Then add exactly one thing that only matters at this scale: a keyword rule. At fifty people, the messages you must not miss are frequently not in a channel you own and do not mention you by name. Something like a keyword match on your service name, ANDed with a channel prefix so it does not fire on every casual reference.
Per-rule volume becomes load-bearing
At three people, everything at the same volume is fine. At fifty, volume is your second axis. Keep the incident sound audible from another room and drop everything else to something you only notice when the room is quiet. Two sounds can share a tone and still be distinguishable if one is clearly quieter.
The audit is the whole practice
Growing teams add rules and never remove them, which is how you end up with a setup nobody can explain. Whatever size you are, treat the rule list as something with a maintenance cost. Two rules you react to beat six you have tuned out.
Running any of these
Chirpy handles all three configurations. It is a native macOS menu bar app that reads notifications through the Accessibility API locally, so there is no Slack account to connect and nothing leaves your machine. Install it, grant Accessibility permission, set Slack's own notification sound to None, then write your rules. Matching works on app, channel, person, or keyword, with AND/OR, wildcards, priority ordering, and per-rule volume.
Set it up for the size you are now, and put a reminder in your calendar to re-read your rules the next time the team doubles. The guides have the syntax.