Create Accountor Login
Docs

Sounds

Part of the MountDev Ops Workspace documentation. Updated November 17, 2026

MountDev Ops Workspace documentation | Updated November 17, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 6,565 automated checks before it ships, and every screen change is walked through before release.

One Place for Sounds

Every sound in the workspace is made and played in one place. An app or a screen asks for a sound by its name, and nothing else in the workspace makes a tone. Sounds are made on your device in the browser, so no sound file is downloaded and nothing about a sound is sent anywhere or counted.

Keypad Tones

Pressing a digit, *, or # on the dial pad plays its tone, the standard tones a touch-tone phone makes. This works on the dial pad at any time, not only during a call. On a live call the digit is also sent to the other side, where the phone provider supports it.

Incoming Calls

An incoming call rings on each device that is set to ring for it, with a repeating ring until the call is answered or declined. Answering or declining stops the ring at once. A call that connects plays a short rising tone, and a call that ends plays a short falling tone. Call waiting plays one soft tone.

Calls are never silenced by quiet hours or by Mute for One Hour. A call's sounds play only in one tab of a device (see One Tab Plays).

Notice Sounds Planned

A notice sound for each kind below is planned. The kinds and their starting settings are already in the workspace:

KindStarts
New chat messageOff
New ticket or replyOff
MentionOn
Approval waitingOn
Meeting startingOn
ReminderOff

A person can change any kind, and can turn all sounds off with one switch. The notice sounds will be set in each person's own notification settings, with a volume and a Test button.

Quiet Rules

A notice sound stays silent when the person is on a call, during their Mute for One Hour, and during their quiet hours. A call's sounds are not silenced by any of these.

One Tab Plays

On each device, one tab of the workspace plays sounds: the one the person used last and can see. Other tabs and windows stay quiet, so two open windows never sound at once. Keypad tones are the exception: the tab where the person pressed the key plays them.

Browser Rules

Browsers allow sound only after a person has tapped or clicked on the page. The first tap, key press, or click in the workspace is that tap. On an iPhone or iPad with the silent switch on, the browser plays no web audio, so every sound also has a visible signal: the call card shows the incoming call, and the bell shows the notice.

Vibration Planned

On Android browsers, an incoming call can also vibrate when the person turns on Vibrate for Calls. This is planned with the settings.

Settings Planned

The person's sound settings, and this device's (sounds on or off, volume, keypad tones), are planned for the Sounds card in the person's notification settings and This Device. The settings are kept in the account. Until then, the workspace keeps this device's sound settings in the browser, with the defaults above.

Accessibility

Every sound has something a person can see or read, so no information comes by sound alone. A flash or pulse stays within three flashes a second, and is steady when reduced motion is on.

Out of Scope

  • Sounds a person or an account uploads (planned for a later part).
  • The operating system's own notification sound when the workspace is closed.
  • Music, background sound, or a sound for each caller.

Ask Us Anything

We’d love to hear from you!