Loyalty notification settings
Zenoti sends several loyalty-related notifications to guests, including points earned, points redeemed, tier changes, and expiry reminders. All loyalty notifications are classified as Transactional (not Marketing). This article provides an overview of notification types and where to configure them.
On this page
- Before you begin
- Notification types
- Configure notification templates
- Language selection
- SMS character limits
- Email Cc/Bcc support
- Test notification behavior
- Related articles
Before you begin
- You need organization-level access to configure notification templates.
- Notification templates are configured at the organization level. Centers can override organization templates when the Override org notification settings option is enabled for that center.
Notification types
The following loyalty notifications are available. All are classified as Transactional.
| Notification | Trigger | Delivery |
|---|---|---|
| Points Added | Manual point addition or invoice close | Immediate |
| Points Redeemed | Guest redeems loyalty points as payment | Immediate |
| Welcome / Enrollment | Guest enrolls in tiered loyalty | Immediate |
| Tier Upgrade | Guest qualifies for a higher tier (during nightly processing) | Immediate (within nightly processing) |
| Tier Downgrade | Guest is downgraded to a lower tier (during nightly processing) | Immediate (within nightly processing) |
| Expiry Reminder | Scheduled daily job identifies guests with points expiring within the configured reminder window | Batch (daily) |
| Balance Statement | Scheduled daily job sends periodic loyalty point statements | Batch (daily) |
Important: The Expiry Reminder notification is sent before points expire — based on the configurable number of days set in your organization's loyalty settings — not on the expiry date itself.
Note: Tier Upgrade and Tier Downgrade notifications are sent as part of the nightly processing batch. Tier changes are not processed in real time.
Configure notification templates
Notification templates are configured at the organization level. Centers may override organization templates only when the Override org notification settings option is enabled for the center.
Steps
- At the organization level, click the Configuration icon (gear icon).
- Navigate to Notifications > Templates for email and text.
- Locate the loyalty notification you want to configure.
- Edit the template content for the applicable channels. For each email template, you can configure:
- Subject — the email subject line
- Body — the message body for email and SMS
- Cc and Bcc recipients — additional recipients for email notifications only
- Per-language template content (see Language selection below)
- Use macros to insert dynamic guest and points data into the template body. For the full list of available macros for each notification type, see the program-specific template articles linked below.
- Select Save to apply your changes.
For full macro tables and program-specific template details:
- Regular programs: See Configure regular loyalty notification templates
- Tiered programs: See Configure tiered loyalty notification templates
Language selection
Notification templates support per-language configuration. The system resolves the language for each notification using the following priority order:
- Guest language preference
- Center language
- Organization language
In tiered programs, tier names in notifications are localized when translations are configured.
SMS character limits
SMS notifications respect center-level character limits configured in center settings. These limits are not hardcoded — they are configurable per center, with separate limits for standard messages and Unicode messages.
Email Cc/Bcc support
Email notifications support Cc and Bcc recipient lists. You can configure additional recipients for each notification type, allowing managers or administrative staff to receive copies of guest notifications.
Test notification behavior
When you send a test notification, macros do not expand with live guest data. Test messages display the macro placeholder names (for example, [FirstName]) rather than actual values. This is expected behavior and does not indicate a problem with your template.