ZenotiHelp

Configure alerts for expiring memberships

ZTZenoti Docs Team Updated September 17, 2026 4 min readHow-to

The Visits page surfaces a yellow alert when a member with an expiring membership checks in, signaling the front desk to start a renewal conversation. This article walks through configuring the lead-time thresholds, the alert text, the membership types in scope, and the per-center overrides.

Audience: Administrators configuring membership-lifecycle alerts at the front desk.


On this page


Before you begin

  • You need administrator access to organization-level Configurations.
  • The Visits page alert system must be enabled for your organization.
  • You should know your standard renewal lead time (typically 14 or 30 days before expiry).

How the expiring-membership alert works

When a student checks in via the Kiosk, Visits page, or Roster sign-in:

  1. The system retrieves the student's active memberships.
  2. For each membership, it calculates days-until-expiry.
  3. If any membership falls within the configured lead-time threshold, the system fires the "Membership Expiring Soon" yellow alert.
  4. The alert surfaces on the Visits row, on the student's profile, and (if configured) on the Kiosk welcome message.

The alert is informational — it does not block check-in. It exists to give the front desk a renewal conversation cue.

Configure the lead-time threshold

  1. Navigate to Configuration > Fitness > General setup > Expiring Membership/Package Alert.
  2. Turn on the Enable alert for expiring membership toggle.
  3. In the Number of days from expiration field, enter the number of days before expiry that the alert should start showing (for example, 3 or 7).
  4. Click Save.

The alert fires for any check-in where a member's membership is within the lead-time window.

Configure alert text

The default alert text is "Membership expiring in N days." To customize:

  1. From the same configuration page, click the Alert text field.
  2. Enter the new text. The placeholder {days} substitutes the actual days-until-expiry at render time.
  3. To localize, click Translate and enter the translation for each enabled locale.
  4. Save.

Limit the alert to specific membership types

By default, the alert fires for every active membership. To limit it to specific types (for example, only month-to-month memberships, not annual contracts):

  1. From the configuration page, open Membership types in scope.
  2. Select the membership templates the alert should fire for.
  3. Save.

Membership types not in scope do not fire the alert even if they are within the lead-time window.

Apply per-center overrides

Different centers may have different renewal cadences. To override the org default at a specific center:

  1. At the center level, click the Configuration icon.
  2. Open Fitness > Alerts > Expiring Memberships.
  3. Configure a center-specific lead time, alert text, or membership-type list.
  4. Save.

The center override takes precedence over the organization default for this center.

  • Notification templates. Pair the expiring-membership alert with the Membership Expiry Reminder notification template (Email + Text) so members hear from you before they arrive. See Notification template reference.
  • Renewal incentives. Combine alerts with a one-time renewal offer (see One-time offers for memberships and packages). The front desk has the cue and the carrot in the same interaction.
  • Auto-renewal. For recurring memberships configured to auto-renew, the alert still fires — but renewal is automatic. Some organizations suppress the alert for auto-renewing memberships; configure this at the membership-type level.
  • Audit trail. Every change to expiring-membership alerts is logged in the Configuration audit log.

Impacts and considerations

  • Front-desk workload. A 60-day lead time produces more frequent alerts than 14 days. Tune the threshold to match your renewal-cycle conversion practices.
  • Member experience. The alert text is visible to the member if your alert configuration surfaces it on the Kiosk welcome page. Use member-facing language ("Renew your membership for uninterrupted access") rather than internal language ("Member due for renewal"). Edge case: recently expired memberships. A member whose membership has already expired triggers a different alert — Membership Expired (red, blocks check-in) — not Expiring Soon. The expiring alert covers only future expiry within the lead-time window.

Troubleshooting

  • The alert is not firing for an expiring membership. Verify the membership template is in scope (see Limit the alert to specific membership types). Verify the lead-time threshold is greater than the member's days-until-expiry.
  • The alert fires too late. Increase the lead-time threshold. A 30-day lead is common; 60 days is a soft signal start.
  • The alert fires for a member who already renewed. The system fires based on the latest membership expiry date. If the renewal extends the same membership record, the alert clears immediately; if the renewal creates a new membership record, the old one may still be in scope until you cancel it.
  • The custom alert text shows {days} instead of a number. The placeholder syntax is case-sensitive: use exactly {days} in lowercase with the curly braces.
Was this article helpful?
Your feedback helps us improve our documentation.