ZenotiHelp

Check-in alerts

ZTZenoti Docs Team Updated September 2, 2026 4 min readGuide

The Visits page displays color-coded alerts for each guest when they sign in, giving front desk staff an immediate visual summary of the guest's membership, payment, and guest-pass state. You can customize alert labels, severity levels, and sounds to match your organization's workflow.

Audience: Fitness administrators who configure center-level visit tracking settings.


On this page


Before you begin

  • Visits must be enabled for your center. Navigate to the center level, click the Fitness icon, and confirm that Visits appears in the menu.

  • You need the following permissions to configure alert settings:

    Permission: You need edit access to fitness configuration settings to modify alert labels and configurations.

  • The Allow editing of alert labels and configurations toggle must be enabled at Configuration > Fitness > Essentials before alert customization options appear.

How check-in alerts work

When a guest signs in on the Visits page, Zenoti evaluates the guest's current membership, payment, and guest-pass state and displays a color-coded alert. Each alert has a severity level that determines its color and, optionally, a sound that plays when the alert triggers.

Alerts give front desk staff an at-a-glance view of each guest's status without opening the guest's full profile. For example, a guest with an overdue payment balance displays a different alert color than a guest with an active membership in good standing.

The following attributes are configurable per alert:

Attribute Description
Display Order Controls the order in which alerts appear when multiple alerts apply to a guest.
Alert Message The text displayed to front desk staff when the alert triggers.
Severity Visual priority of the alert. Options are Critical, Moderate, and Normal.
Alert Sound An optional audio cue that plays when the alert triggers.
Active Whether the alert is currently enabled. Inactive alerts are not displayed on the Visits page.

Note: Alert colors are determined by the Severity setting. Critical alerts display in red, Moderate alerts display in amber, and Normal alerts display in a neutral color. Color values are fixed by severity level and are not individually configurable.

Enable alert label editing

Before you can edit individual alert labels or configurations, you must enable the editing toggle at the organization level.

  1. At the organization level, navigate to Configuration > Fitness > Essentials.
  2. Locate the Allow editing of alert labels and configurations toggle and turn it on.
  3. Select Save.

Once enabled, the alert configuration table becomes editable for your organization.

Configure individual alerts

After enabling alert label editing, you can update the message text, severity, sound, display order, and active state for each alert.

  1. At the organization level, navigate to Configuration > Fitness > Essentials.

  2. Scroll to the check-in alerts section.

  3. For each alert you want to modify, select Edit.

  4. Update the following fields as needed:

    • Alert Message — Enter the text that front desk staff will see when this alert triggers. Keep messages concise and actionable.
    • Severity — Select Critical, Moderate, or Normal to set the alert's color and visual priority.
    • Alert Sound — Select a sound to play when the alert triggers, or leave blank for no sound.
    • Display Order — Enter a number to control the order in which this alert appears relative to other alerts.
    • Active — Select this option to enable the alert. Clear it to disable the alert without deleting its configuration.
  5. Select Save.

Tip: Use Critical severity for alerts that require immediate action, such as a guest with a suspended membership or an outstanding balance that blocks sign-in. Use Normal severity for informational alerts, such as a guest using a guest pass.

Note: Alert labels support translation. Select Translate next to an alert to provide translated text for centers operating in multiple languages.

Columns

Each alert occupies one row. The row shows the following columns.

Column Description
Display Order Row number with a drag handle. Determines which alert surfaces first.
Alert Message The staff-facing text. May contain runtime placeholders that resolve when the alert fires.
Edit Pencil icon. Rewrites the alert text; available only when alert label editing is enabled.
Translate Per-alert localization across your enabled locales.
Info Explains the condition that causes the alert to fire.
Severity Colour swatch with a dropdown, configurable per alert.
Alert Sound Dropdown with a play-to-preview control. Shows N/A where sound is not supported for that alert.
Active Toggle that enables the alert.

Worked example

Your organization wants front desk staff to immediately notice when a guest's membership payment has failed. You configure the payment-failure alert as follows:

  • Alert Message — "Payment overdue — collect before class"
  • Severity — Critical
  • Alert Sound — Select an audible chime
  • Display Order — 1
  • Active — Selected

When a guest with a failed payment signs in, the Visits page displays the message in red at the top of the alert list and plays the chime, prompting the front desk to address the balance before the guest proceeds.

Unsuccessful sign-in recording

When a guest sign-in attempt fails, Zenoti records the failure with a visible status and the reason for the failure. Unsuccessful sign-ins appear in the All check-ins section of the Visits page with:

  • A Status indicating the sign-in was not completed.
  • A failure reason describing why the sign-in was blocked or unsuccessful.

Front desk staff can review the All check-ins list to identify patterns in sign-in failures and follow up with affected guests. The same failure reasons are surfaced in Zenoti Mobile App (ZMA) and on the kiosk with equivalent user-facing messages, so guests receive consistent information regardless of the sign-in channel.

Important: Unsuccessful sign-in records are retained for audit purposes. Historical sign-in data is preserved even after the guest's status changes.

Was this article helpful?
Your feedback helps us improve our documentation.