ZenotiHelp

Substitute Request Expiry Reminder for Instructor notification

ZTZenoti Docs Team Updated September 17, 2026 3 min readGuide

Type: Scheduled Channels: Email, Push Audience: Instructor (requester)

What this notification does

Sends an email or push reminder to the requesting instructor before their substitution request expires without being accepted, prompting them to take action.

When it is sent

Before an instructor substitution request expires, at the configured reminder offset.

Configure this template

  1. At the organization level, click the Configuration icon.
  2. Search for and select Templates for email and text from the Notifications section.
  3. Expand the Classes template section and locate Substitute Request Expiry Reminder for Instructor.
  4. Click Edit to customize the subject, body, and channels.
  5. Click Save.

Available macros

Template-specific macros beyond the common surface:

Macro Description
[ExpiryDate] Date on which the request will expire.
[ExpiryTime] Time at which the request will expire.
[NewInstructor] Substitute instructor name, if one has been proposed.

See the Fitness notifications umbrella for the full common-macro table.

Common macros used in this notification

Every Fitness notification draws from a shared macro surface. The macros most often used in this template are listed below; the complete list for Fitness notifications is documented in the Fitness notifications umbrella.

Macro Resolves to
[FirstName] Recipient's first name from their Zenoti profile.
[Name] Recipient's full name (first + last).
[PreferredName] Recipient's preferred name, if configured; resolves to an empty string otherwise.
[ClassName] Class name as configured in the class master.
[SessionName] Session name within the class, if the session is named.
[ClassDate] / [DayOfClass] Class date and the day of the week in the center's time zone.
[StartTime] / [EndTime] Scheduled start and end time in the center's time zone.
[Instructor] Instructor assigned to lead the session.
[CenterName] / [OrgName] Center and organization display names.
[CenterPhone] / [CenterE-mail] Center contact information configured on the center profile.
[GuestReferralCode] Recipient's referral code, for campaigns or referral tracking.
[MailUnsubscribeLink] Unsubscribe link included in marketing-channel emails.

Channel selection guidance

This template supports Email and Push notification only. Text, WhatsApp, Voice call, and RCS are not available for this template.

  • Email is appropriate when the message includes rich text, links, longer explanations, or calendar attachments. Use email when the recipient checks email regularly and the message benefits from formatting.
  • Push notification is appropriate when the recipient has the Zenoti Customer Mobile App or Zenoti Mobile App installed and you want the message to appear on their device lock screen. Push bodies should be brief; deeper detail belongs in the email that accompanies the push.

Configure the active channels for this template on the Templates for email and text page under Configuration > Notifications. When you disable a channel, the template does not fire on that channel even if the organization has a provider configured.

Tips

  • Preview the template after any edit using the Preview action to confirm that macros resolve to expected values before enabling the template for a center.

  • Keep email subject lines under 60 characters so they render cleanly on mobile devices. Place the call to action or the key information in the first line of the body — many email clients preview only the first few lines.

  • Use the Override at center toggle on the template page when specific centers need a branded or localized variant. This preserves the organization default as the fallback for centers that do not override.

Troubleshooting

  • The notification did not send. Verify that the template is enabled for the recipient's center (in the center's notification settings) and that the recipient's profile has a valid email address or phone number for the configured channels. For Text or WhatsApp, confirm that the organization has a provider configured and that the recipient has opted in.
  • A macro renders as blank or as the literal macro text. The macro failed to resolve against the triggering entity — typically because the underlying field is empty on the profile, class master, or center profile. Populate the missing field; the next occurrence of the notification will render correctly.
  • Recipients report receiving duplicates. The organization may have two overlapping templates enabled for the same trigger. Review the templates under Configuration > Notifications > Templates for email and text and confirm only one is active for the trigger. If both are required for different audiences, check the audience filter on each template.
Was this article helpful?
Your feedback helps us improve our documentation.