Exactly one audible path per alert

Visible tab gets the in-page chime; hidden tab with a desktop notification lets the OS carry the alert; hidden tab without one still chimes, so nothing is silent by accident.

What it is

A single decision function returning chime, os or none. Info events, events with sound turned off, and muted sessions return none — the desktop notification may still appear, silently, because mute governs audio rather than visibility.

Also called: double notification · it dings and pops up at the same time · I hear nothing in another tab

See it
Exactly one audible path per alert
Area
Operations
Group
Notifications
System
Notifications
Solves
2 named problems
01decideAudiblePath takes severity, the event's sound channel, whether the document is hidden, and whether an OS notification will actually show.
02The fallback chime plays in hidden tabs, which browsers permit once audio is unlocked.
A four-cell decision table: visible/hidden × OS-will-show/won't. notificationSound.ts decideAudiblePath. Sample data — no customer information appears here.
How it works
  1. 1decideAudiblePath takes severity, the event's sound channel, whether the document is hidden, and whether an OS notification will actually show.
  2. 2The fallback chime plays in hidden tabs, which browsers permit once audio is unlocked.
Why we built it

The comment names the hole the fallback closes: 'Without this fallback a user who dismissed the permission card gets NOTHING audible — the exact missed-event hole this feature fixes.' The matrix also guarantees the alert is never doubled.

The problem
  • Double-alerting
  • Silence for users who declined desktop notifications
Sound familiar?
What you get
One alert per event no matter where you are looking
Declining desktop alerts does not make you deaf

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →