Visits Guest Pass Shared notification
Type: Transactional Channels: Email, Text, WhatsApp Audience: Host member
What this notification does
Sends an email, text, or WhatsApp message to the host member confirming that a visits guest pass has been shared, with the recipient's pass details and barcode for reference.
When it is sent
When a visits guest pass is shared.
Configure this template
- At the organization level, click the Configuration icon.
- Search for and select Templates for email and text from the Notifications section.
- Expand the Classes template section and locate Visits Guest Pass Shared.
- Click Edit to customize the subject, body, and channels.
- Click Save.
Available macros
Template-specific macros beyond the common surface:
| Macro | Description |
|---|---|
[NameGuestPassSender] |
Sharing host member name. |
[GuestPassInstrumentName] |
Pass instrument name. |
[BarCode] |
Recipient's barcode for reference. |
[CustomMacros1] |
Org-configured custom macro. |
[CustomMacros2] |
Org-configured custom macro. |
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, Text, and WhatsApp only. Push notification, 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.
- Text is appropriate for short, action-oriented messages where the recipient is on the move. Keep the body under 160 characters so the message renders on every device without splitting into multiple segments.
- WhatsApp is appropriate when the organization has the WhatsApp Business API configured and the guest has opted in. WhatsApp templates must be pre-approved by Meta.
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.