ZenotiHelp

Configure alert sounds for visit notifications

ZTZenoti Docs Team Updated August 20, 2026 4 min readHow-to

When a student checks in at a fitness center, the Visits page can play a sound to draw front-desk attention to a check-in event — particularly useful when the front desk also manages a queue, takes phone calls, or supports a busy lobby. Alert sounds can be configured per alert severity (green, yellow, red, grey) and per surface (Visits page, Kiosk).

Audience: Administrators configuring the front-desk check-in experience.


On this page


Before you begin

  • You need administrator access to organization-level Configurations.
  • The browser used at the front desk must allow audio autoplay (some browsers require user interaction before playing audio — verify this before relying on alert sounds at peak hours).
  • The front-desk device must have working speakers and volume set high enough to be heard over ambient gym noise.

Why configure alert sounds

Alert sounds prevent the front desk from missing critical check-in events when their attention is elsewhere. Typical use cases:

  • A red alert (pending payment, expired membership) sounds an attention chime so staff know to follow up before the student leaves the lobby.
  • A yellow alert (membership expiring soon) plays a softer chime, signaling a soft-touch sales conversation opportunity.
  • A green check-in plays a brief confirmation tone, useful in a busy lobby where the front desk wants positive acknowledgment without visual focus.

Open the alert-sound configuration

  1. At the organization level, click the Configuration icon.
  2. Search for Visit alert sounds or open the Fitness > Alerts > Sounds section.
  3. The configuration page shows one row per alert severity.

Configure sounds for each alert severity

For each row (Green, Yellow, Red, Grey):

  1. Toggle the row On to enable a sound for this severity, or Off to disable.
  2. Select the sound from the dropdown — typical options include Chime, Ding, Bell, Buzzer, Custom upload.
  3. Set the volume level (Low, Medium, High).
  4. (Optional) Upload a custom sound file (.wav or .mp3, under 200 KB).

Save the configuration. Sounds apply on the next page refresh of the Visits page or Kiosk on each front-desk device.

Test the sound

After saving:

  1. Click the Test action next to each row.
  2. The selected sound plays through the device's default audio output.
  3. Adjust volume or sound choice based on the test.

If no sound plays during the test, see Troubleshooting.

Apply per-center overrides

Some centers operate in environments where audio cues are not appropriate (for example, a wellness studio where staff prefer silence). To override the organization defaults at a specific center:

  1. At the center level, click the Configuration icon.
  2. Open Fitness > Alerts > Sounds.
  3. Disable specific rows or override the sound choice for this center.
  4. Save the configuration.

The center override supersedes the organization default for this center only.

Configuring a single setting in isolation rarely produces the complete business outcome — Fitness settings typically interact with role permissions, center-level overrides, and related organization toggles.

  • Visits page alert priority — Alert sounds fire based on the alert that surfaces on the Visits row. The alert that surfaces depends on the priority configuration. See Visits — Configure alert priority order.
  • Alert label editing — The label and color you assign per alert influences which severity sound plays. See Visits — Edit alert labels.
  • Browser audio autoplay policy — Modern browsers restrict audio autoplay until the user has interacted with the page at least once. Front-desk staff may need to click anywhere on the Visits page after login before sounds will play.
  • Audit trail — Every change to alert-sound settings is logged in the Configuration audit log.

Impacts and considerations

  • Sound files are cached. Custom sound uploads are cached on each front-desk device; replacements may not take effect until the device refreshes its cache (typically a browser reload).
  • Volume conflicts with system volume. The configured volume scales relative to the device's system volume. If the device is muted at the OS level, no sound plays regardless of the in-app volume.
  • Compliance considerations. Some regions (for example, certain healthcare facilities) prohibit audio cues that could disclose member status to nearby people. Confirm with your compliance team before enabling red-alert sounds in such environments.
  • Default behavior. Out of the box, alert sounds are disabled for all severities. Enable each one explicitly.

Troubleshooting

  • The sound test plays but real check-ins do not trigger sound. The browser may be blocking autoplay. Have the front-desk staff click anywhere on the Visits page after each login session.
  • Custom uploaded sound does not appear in the dropdown. Verify the file is .wav or .mp3 and under 200 KB. Unsupported formats or oversized files are silently rejected during upload.
  • Sound volume is too low even at High. The device's OS volume may be limiting the maximum output. Raise OS volume or use external speakers.
  • Multiple sounds play simultaneously. A student may trigger multiple concurrent alerts (red + yellow). The Visits page plays only the highest-severity sound when multiple alerts surface for the same check-in.
Was this article helpful?
Your feedback helps us improve our documentation.