Configure package notification templates
Zenoti sends automatic notifications to guests when package events occur — purchase confirmation, benefit redemption, and expiry reminders. You can customize the message templates for each notification type and control which channels are used (email, SMS, WhatsApp, or push notification).
Audience: Administrators who configure guest communication settings.
On this page
- Before you begin
- Notification types
- Notification channels
- Available macros
- Macro availability by notification type
- Package expiry communication
- Scheduled notification job
- Package webhook events
- Related articles
Before you begin
Permission: Edit (under Notifications) — Required to modify notification templates.
- Navigate to Configuration > Notifications at the organization level.
- Notification templates are configured at the organization level. Centers can override organization templates when the Override org notification settings option is enabled for the center.
Notification types
Zenoti supports three package-related notification types. Each type has a specific trigger and delivers relevant information to the guest.
| Notification | Trigger | Recipient | Description |
|---|---|---|---|
| Package purchase | Package sale | Guest who purchased | Sent when a guest purchases a package. Confirms the package name, price, expiry date, and list of redeemable services. |
| Package redemption | Service redemption | Guest who redeemed | Sent when a guest redeems a service from their package. Confirms the package name and remaining benefits. |
| Expiry reminder | Scheduled daily | Guests with packages expiring soon | Sent as a reminder before package expiry. Runs as a daily scheduled job and checks each guest's package expiry dates based on the configured reminder days. |
Additionally, the following transactional templates are available:
| Template | Trigger | Description |
|---|---|---|
| Package agreement | Package purchase | Sends the package agreement document to the guest after purchase. |
| Sale confirmation | Package sale | Sends a sale confirmation email summarizing the package details. |
Notification channels
Each notification type can be sent through one or more channels:
- Email — Full-format notifications with HTML templates. Supports all macros and rich formatting.
- SMS — Short text messages with key details and macros.
- WhatsApp — Messaging via WhatsApp when the guest has provided consent.
- Push notification — Mobile app notifications when the guest app is enabled.
To enable or disable channels, configure the Send email and Send SMS toggles at the organization level. Centers can override these settings when center-level notification overrides are enabled.
Available macros
Use these macros in your notification templates to insert dynamic package data. Type the macro name including the square brackets.
| Macro | Description | Example value |
|---|---|---|
| [PackName] | Package name | Spa Day Package |
| [PackRemBenefits] | Remaining package benefits | 3 massages, 2 facials |
| [Price] | Package price | 299.00 |
| [ExpiryDate] | Package expiry date | 2025-12-31 |
| [ListOfRedeemableServices] | List of services included in the package | Deep Tissue Massage, Classic Facial, Manicure |
In addition to package-specific macros, all standard guest and center macros are available (for example, [FirstName], [LastName], [CenterName], [CenterPhone]).
Macro availability by notification type
Not all macros apply to every notification type. Use the following guide to select the right macros for each template.
| Macro | Package purchase | Package redemption | Expiry reminder |
|---|---|---|---|
| [PackName] | Yes | Yes | Yes |
| [Price] | Yes | — | — |
| [ExpiryDate] | Yes | — | Yes |
| [ListOfRedeemableServices] | Yes | — | — |
| [PackRemBenefits] | — | Yes | Yes |
Package expiry communication
Two separate settings control expiry communication. Navigate to Configuration icon > Packages to configure them.
| Setting | Purpose |
|---|---|
| Send an email/text to guests when the package expires | Sends an automated email or text to the guest when their package expires or is about to expire. |
| Create an opportunity to follow up | Creates a sales opportunity for the opportunity owner to follow up with the guest. Distinct from the guest-facing email/text — this notifies internal staff. |
Timing configuration
After enabling either setting, configure when the notification is sent:
| Field | Description |
|---|---|
| Send before/after the package expires? | Choose the direction: Before (reminder before expiry) or After (follow-up after expiry). |
| When to send the email/text message (in days)? | Enter the number of days before or after the expiry date to send the notification. |
Worked example: Select Before + 4 days → the guest receives a reminder four days before the package expiry date.
Scheduled notification job
The package expiry reminder runs on a daily schedule rather than being triggered by an immediate action.
| Job | Runs | Configuration |
|---|---|---|
| Expiry reminder | Daily per center | Configure using the "Send an email/text to guests when the package expires" and "Create an opportunity to follow up" settings (see Package expiry communication above). Set the number of days and timing direction (before/after). |
Package webhook events
When package events occur, the system can fire webhook events to external integrations. These are configured separately from notification templates. Webhook events are triggered only when the Event Management System (EMS) is enabled for the organization.
For webhook configuration and event details, refer to the Zenoti APIs documentation.