Configure notification types and triggers
Zenoti supports over 190 notification types organized across multiple domains. Each notification type is linked to a specific trigger event, such as an appointment confirmation or a membership renewal, and can be delivered through one or more channels. This article lists the most commonly used notification types, the events that trigger them, the channels they support, and when each notification is sent.
Before you begin
- You need administrator access at the organization level.
- Confirm that your organization has active communication credits for the channels you plan to use (SMS, email, WhatsApp, or others).
Permission: Edit under Organizations in the Administrator section of the security role (Configuration > Security > Security roles).
Navigation
To view and configure notification types:
- Navigate to Configuration > Notifications.
- Open the Notification center section.
- Select a notification category to view its types and configure delivery channels.
Note: The Notification center section specifically requires the Notification Center feature to be enabled for your organization. See How to confirm Notification Center is enabled for confirmation steps. Standard email and SMS template configuration (covered in Configure notification template customization) does not require this feature β older organizations without Notification Center can still configure templates through the classic Templates for email and text area.
On this page
- Notification channels
- Notification categories
- Appointment notifications
- Membership notifications
- Package notifications
- Gift card notifications
- Loyalty point notifications
- Invoice and payment notifications
- Employee notifications
- Daily and lifecycle notifications
- How notification timing works
- Appointment reminder timing
- SMS character limits and delivery
- Pre-care and post-care instructions in notifications
- Thank-you message scope
Notification channels
Zenoti delivers notifications through the following four channels. Each notification type can be enabled for one or more channels depending on your configuration, and individual channel availability depends on your organization's provisioning.
| Channel | Description |
|---|---|
| Delivered through configured email providers. Supports rich HTML content and branding. | |
| Text (SMS) | Text messages delivered through SMS providers. Subject to character limits (160 characters per segment for standard encoding; 70 characters per segment for Unicode). |
| Messages delivered through Twilio. Requires pre-approved templates before messages can be sent. See Configure WhatsApp notification templates. | |
| Push | Mobile push notifications for iOS and Android devices through the Zenoti guest app and employee app. Push notifications do not consume email or SMS credits. See Configure push notifications. |
Channel availability depends on your organization's provisioning and on the master Activate email and Activate SMS toggles in notification settings.
Notification categories
Every notification falls into one of three categories that determine its priority and opt-in behavior:
- Transactional β appointment confirmations, invoice receipts, password resets, and other business-critical notifications. Sent regardless of marketing opt-in status.
- Marketing β promotions, campaigns, and birthday messages. Sent only to guests who have opted in.
- OTP β one-time passwords for authentication. Delivered at the highest priority.
Appointment notifications
Appointment notifications are triggered by scheduling events and are the most commonly used notification type.
| Notification | Trigger | When sent | Description |
|---|---|---|---|
| Confirmation (time) | Appointment time is set | Immediately after booking | Sends the confirmed appointment time to the guest |
| Confirmation (standard) | Appointment is booked | Immediately after booking | General appointment confirmation with service and provider details |
| Confirmation (online booking) | Guest books online | Immediately after booking | Confirmation specific to online booking with booking reference |
| Group confirmation (online) | Group booking online | Immediately after booking | Confirmation for group appointments booked through online booking |
| Group confirmation | Group appointment created | Immediately after creation | Confirmation for group appointments created in Zenoti |
| Cancellation | Appointment is cancelled | Immediately after cancellation | Notifies the guest that their appointment has been cancelled |
| No-show | Appointment marked as no-show | Immediately after marking | Notifies the guest when their appointment is marked as a no-show |
| First reminder | Scheduled before appointment | At the configured interval before the appointment | First reminder sent at the configured interval before the appointment |
| Second reminder | Scheduled before appointment | At the configured interval before the appointment | Second reminder sent at a shorter interval before the appointment. Your organization can choose to skip it for guests who have already confirmed β see Configure appointment notifications. |
| Thank you | Invoice is closed | Immediately after the invoice is closed | Thank-you message sent after the appointment is completed and paid |
| Check-in | Guest is checked in | Immediately after check-in | Confirms the guest's check-in and may include estimated wait time |
| Completion | Appointment service completed | Immediately after service completion | Notifies the guest that their service is complete |
Important: Both the reminder schedule and the template content are captured at the time the appointment is booked. If you edit a template after an appointment is already booked, the change applies only to appointments booked after the edit. Guests with existing bookings will receive the version of the template that was active when their appointment was created. This is why editing a template and seeing no change in tomorrow's reminders is expected behavior, not a broken edit.
Membership notifications
Membership notifications are triggered by membership lifecycle events and scheduled batch jobs.
Which template sends the membership signup email?
The template that sends the membership purchase confirmation email is called Signup in the notification configuration. On screen, this template is labeled Membership Purchase Confirmation. If you are searching for the template that confirms a new membership sale β whether you know it as "Signup" or as "Membership Purchase Confirmation" β both names refer to the same template row.
| Notification | Trigger | When sent | Description |
|---|---|---|---|
| Signup (also shown as: Membership Purchase Confirmation) | New membership purchase | Immediately after purchase | Confirms the membership purchase with plan name, fee, start date, expiry date, and benefits |
| Renewal | Membership renewal | Immediately after renewal | Confirms the renewed membership with updated dates |
| Upgrade | Membership upgrade | Immediately after upgrade | Confirms the upgrade with the new plan name and effective date |
| Downgrade | Membership downgrade | Immediately after downgrade | Confirms the downgrade with the new plan name and effective date |
| Transfer | Membership transfer | Immediately after transfer | Confirms the transfer to a different center |
| Cancellation | Cancellation request submitted | Immediately after cancellation | Confirms the cancellation with the effective date, fee, and reason |
| Freeze | Membership freeze | Immediately after freeze | Confirms the freeze with start date, end date, fee, and reason |
| Expiry reminder | Scheduled batch job | Daily batch job, at the configured number of days before or after expiry | Reminds the guest before their membership expires |
| Anniversary | Scheduled batch job | Daily batch job, on the membership anniversary date | Celebrates the membership anniversary with the number of years |
| Recurring collection reminder | Scheduled batch job | Daily batch job, at the configured number of days before the collection date | Reminds the guest of an upcoming recurring payment collection date and amount |
| Recurring collection failed | Scheduled batch job | Daily batch job, after a recurring payment fails | Alerts the guest about a failed recurring payment and prompts them to update their payment method |
Package notifications
| Notification | Trigger | When sent | Description |
|---|---|---|---|
| Purchase | Package purchase | Immediately after purchase | Confirms the package purchase with name, price, expiry date, and redeemable services |
| Redemption | Package service redeemed | Immediately after redemption | Confirms the redemption and shows remaining package benefits |
| Expiry reminder | Scheduled batch job | Daily batch job, at the configured number of days before or after expiry | Reminds the guest before their package expires |
Gift card notifications
| Notification | Trigger | When sent | Description |
|---|---|---|---|
| Purchase | Gift card purchase | Immediately after purchase | Confirms the purchase with gift card number, value, expiry date, and barcode |
| Redemption | Gift card used | Immediately after redemption | Confirms the usage amount and shows the remaining balance |
Loyalty point notifications
| Notification | Trigger | When sent | Description |
|---|---|---|---|
| Points accrual | Invoice close | Immediately after invoice close | Notifies the guest of points earned and their updated balance |
| Points redemption | Points redeemed against an invoice | Immediately after redemption | Confirms points redeemed and the guest's updated balance |
| Points expiry reminder | Scheduled batch job | Daily batch job, at the configured number of days before expiry | Warns the guest about points that are about to expire |
| Balance statement | Scheduled batch job | Daily batch job, on a periodic schedule | Sends a summary of accrued, redeemed, and current balance |
| Tier enrollment | Tier enrollment event | Immediately after enrollment | Notifies the guest when they are enrolled in a loyalty tier |
| Tier upgrade | Tier upgrade event | Immediately after upgrade | Notifies the guest when they move up to a higher loyalty tier |
| Tier downgrade | Tier downgrade event | Immediately after downgrade | Notifies the guest when they move down to a lower loyalty tier (for example, after falling below the minimum points threshold for their current tier) |
Invoice and payment notifications
| Notification | Trigger | When sent | Description |
|---|---|---|---|
| Invoice receipt | Invoice closed | Immediately after invoice close | Sends the invoice details including total, amount paid, and items |
| Payment link | Payment link created | Immediately after creation | Sends a payment link for an outstanding balance |
| Payment made | Payment recorded | Immediately after payment | Confirms the payment amount and method |
| Auto-pay success | Auto-pay processed | Immediately after processing | Confirms a successful auto-pay transaction |
| Auto-pay failure | Auto-pay failed | Immediately after failure | Alerts the guest about a failed auto-pay attempt and prompts them to update their payment method |
Employee notifications
| Notification | Trigger | When sent | Description |
|---|---|---|---|
| Initial credentials | Employee account created | Immediately after creation | Sends initial login credentials (username and temporary password) |
| Reset password | Password reset requested | Immediately after request | Sends a password reset link |
| Password changed | Password successfully changed | Immediately after change | Confirms the password change |
Daily and lifecycle notifications
| Notification | Trigger | When sent | Description |
|---|---|---|---|
| Birthday | Scheduled daily job | Daily batch job, at approximately 10:00 AM center local time on the guest's birthday | Sends a birthday greeting. This is a marketing notification and is sent only to guests who have opted in. |
| Anniversary | Scheduled daily job | Daily batch job, at approximately 10:00 AM center local time on the guest relationship anniversary | Sends an anniversary message. This is a marketing notification. |
| Check-in alert | Check-in event | Immediately after check-in | Alerts staff via push notification when a guest checks in at the center |
How notification timing works
Zenoti uses three delivery mechanisms. The mechanism used depends on the notification type and the timing configuration.
Event-triggered (immediate) delivery
Most notifications are triggered by a specific event and delivered immediately. When an event occurs β such as booking an appointment, closing an invoice, or purchasing a membership β the system processes the notification within minutes.
Scheduled delivery
Some notifications are scheduled for a specific future time. For example, appointment reminders are scheduled for a configured interval before the appointment. If the scheduled time is more than 20 minutes in the future, the notification is queued for later delivery.
If all configured reminders have already lapsed when an appointment is booked (for example, when a guest books less than 2 hours before the start time), Zenoti can still send a reminder within 10 minutes of booking if the Send reminder immediately option is enabled for your organization.
Daily batch jobs
Certain notifications run as daily batch jobs, once per day per center. These include:
- Birthday and anniversary greetings β processed at approximately 10:00 AM in the center's local time zone
- Membership expiry reminders β processed daily; sent when the number of days until (or since) expiry matches the configured value
- Package expiry reminders β processed daily; sent when the number of days until (or since) expiry matches the configured value
- Loyalty points expiry reminders β processed daily at the configured interval before points expire
- Loyalty balance statements β processed daily on a periodic schedule
- Recurring collection reminders β processed daily at the configured number of days before the collection date
- Membership anniversary reminders β processed daily on the membership anniversary date
Appointment reminder timing
Appointment reminders support three timing modes. The mode is controlled by a configuration setting at the organization or center level.
| Mode | How timing works | Example |
|---|---|---|
| Day before appointment | The reminder is sent at a specified hour on the day before the appointment. | If the setting is 18 (hours) and the appointment is on March 15, the reminder is sent at 6:00 PM on March 14. |
| Day of appointment | The reminder is sent at a specified hour on the same day as the appointment. | If the setting is 8 (hours) and the appointment is on March 15, the reminder is sent at 8:00 AM on March 15. |
| Minutes before appointment | The reminder is sent a specified number of minutes before the appointment start time. | If the setting is 120 (minutes) and the appointment starts at 2:00 PM, the reminder is sent at 12:00 PM. |
You can configure both a first reminder and a second reminder, each with its own timing mode and channel (email, SMS, or both). For example, you might send a first reminder by email 24 hours before and a second reminder by SMS 2 hours before.
Centers can override the organization-level reminder settings if the center is configured to override organization notification settings.
SMS character limits and delivery
SMS messages are billed and transmitted in segments. The number of segments a message uses depends on the characters it contains:
- Standard characters (GSM-7 encoding): Up to 160 characters per segment. Messages longer than 160 characters are split into multiple segments, each billed as one SMS credit.
- Unicode characters (non-GSM characters, emoji, accented letters outside the basic set): Up to 70 characters per segment. A single Unicode character anywhere in the message reduces the entire message to 70-character segments.
Important: A message that exceeds the carrier's maximum part limit may be reported as accepted by Zenoti while failing to arrive at the guest's device. The interface shows a "sent" status, but the message is not delivered. This distinction matters especially for bulk sends β a campaign can report full success while almost nothing lands. Keep SMS templates short and avoid Unicode characters unless your audience requires them.
To check credit consumption, navigate to Configuration > Notifications > Credit Usage Dashboard.
Pre-care and post-care instructions in notifications
Pre-care instructions are delivered with the appointment confirmation notification. Post-care instructions are delivered with the invoice-close thank-you message (the Thank you notification type in the appointment notifications table above).
Both types of instructions are authored on the service record, not inside the notification template itself. To add or update instructions:
- Navigate to Configuration > Services (or the equivalent services catalog path for your organization).
- Open the service record.
- Enter pre-care instructions in the Pre-care field and post-care instructions in the Post-care field.
The notification templates for appointment confirmation and thank-you automatically include the instructions when they are present on the service record. If you update the instructions on the service record, the change applies to all future notifications that include that service β you do not need to edit the notification template separately.
Thank-you message scope
The Thank you notification (sent when an invoice is closed) suppresses the entire notification for the invoice when it is turned off. It is not possible to remove only the feedback link from the thank-you message, and it is not possible to suppress the thank-you for specific invoice types while keeping it active for others.
Important: The toggle that controls the thank-you message suppresses the complete notification β subject line, body, feedback link, and all. Removing only the feedback link, or suppressing the thank-you for non-service purchases while keeping it for service invoices, is not supported.
To suppress the thank-you message for non-service purchases (such as product-only or gift card invoices), enable the organization setting Do not send Thank You message for non-service purchases. This setting applies to all centers in the organization and cannot be scoped to individual invoice types beyond the service/non-service distinction.
Tips
- Enable the master Activate email and Activate SMS toggles in notification settings before configuring individual notification types. If these toggles are off, notifications of that type are not sent.
- For scheduled notifications like expiry reminders, configure the reminder interval (in days) to give guests enough time to take action.
- Monitor credit usage regularly to ensure you have sufficient SMS and WhatsApp credits for your notification volume.
- Use the notification center to enable or disable specific channels per notification type, so you can send appointment confirmations by email and SMS but membership renewals by email only.
Used in CMA
The following notification triggers are configured in this article and drive guest-facing behavior in the Customer Mobile App (CMA):
- Appointment reminders, confirmations, and cancellations β see Manage your appointments (guest-side) and Configure customer mobile app settings (admin-side push notification setup for CMA).
- Self-pay completion β the "Guest - Self-Pay Completion" trigger (one of the auto-pay related notifications) feeds the CMA Zenoti Go flow; see Set up Zenoti Go for the guest-side experience.
- Referral Thank You (Email / SMS / Push) β see Set up a referral program for the end-to-end referral setup that this trigger is part of.