Configure alert rules
Alerts track business conditions β low inventory, high no-show rates, missed register closures β not guest actions like bookings or cancellations. When a business metric crosses a defined threshold, Zenoti sends an alert to the configured recipients. This article explains how to configure alert rules and lists every available alert.
Important: Alerts are processed a few hours after the center closes for the day, not in real time. Do not expect immediate delivery after configuring an alert. The one exception is the service request not responded alert, which runs hourly.
Before you begin
The setting Enable alerts must be turned on at the organization level for the Alerts section to appear. Navigate to Configuration > Notifications and confirm the Alerts row is visible. If it is not visible, contact your Zenoti administrator to enable the alerts feature and the alerts license.
Permission: Edit under Organizations in the Administrator section of the security role (Configuration > Security > Security roles) is required for alert configuration.
Navigation
- For organization-level rules, switch to the organization view; for a center's rules, switch to that center.
- Navigate to Configuration > Notifications > Alerts.
- Rules are grouped under the headers Appointment Book & POS, Employee, Inventory, Guest Loyalty, and Operational Issues. Each rule has an ON/OFF switch and an Edit link.
Configure organization-level alert rules
Organization-level alerts define defaults that apply to all centers unless overridden at the center level.
- In the organization view, navigate to Configuration > Notifications > Alerts.
- Find the rule under its group header (for example, Inventory).
- For each rule:
- Switch the rule ON or OFF.
- Select Edit to open the Edit Alert Rule dialog. For threshold-based rules, set the threshold value that triggers the alert (for example, stock quantity below 10 units).
- Under Recipients, choose the Delivery Mode and set Recipient Type to Username (specific employees) or Role.
- Select Save.
Enable or disable alerts for centers
Center-level alerts let you override organization defaults for a specific location.
- Switch to the center you want to configure.
- Navigate to Configuration > Notifications > Alerts.
- For each rule you want to override, switch the rule ON or OFF and, through Edit, adjust the threshold value, Recipients, or Delivery Mode as needed.
- Select Save.
Center-level alert settings take priority over organization-level settings for that center only. Any alert type that is not overridden at the center level uses the organization-level configuration.
Alert processing
Alerts are processed by scheduled jobs, not in real time.
- Daily alerts β 47 of 50 alert rules run daily after the center closes for the day. The system evaluates each rule against the day's data and sends alerts for any conditions that meet the configured thresholds.
- Hourly alerts β 1 alert rule (service request not responded) runs every hour to check for mobile appointment requests that have not been responded to within the configured time.
- External event alerts β 3 alert rules (webhook failure, recovery, and subscription freeze) are triggered by external system events rather than scheduled processing.
Alert delivery channels
Alert notifications can be delivered through the following channels:
- Email β detailed alert with full context and data
- SMS β brief alert message for time-sensitive conditions
- In-app notification β displayed within the Zenoti application
In the Edit Alert Rule dialog, the Delivery Mode list offers Email and SMS (Text Message).
Note: The available channels depend on the master Activate email and Activate SMS toggles in notification settings. If these toggles are disabled, alert delivery through those channels is also suppressed.
Complete alert reference
Appointment Book & POS
| Alert | Description | Rule syntax | Level |
|---|---|---|---|
| Too few appointments were created | Send an alert when the number of appointments booked is less than the threshold | "had [TotalAppointments] appointments booked" β threshold: less than N | Center |
| Too many appointments were deleted | Send an alert when the number of appointments deleted exceeds the threshold | "deleted [TotalAppointments] appointments" β threshold: greater than N | Center |
| Too few invoices were created | Send an alert when the number of invoices created is less than the threshold | "had [TotalInvoices] invoices" β threshold: less than N | Center |
| Too many invoices were deleted | Send an alert when the number of invoices deleted exceeds the threshold | "deleted [TotalInvoices] invoices" β threshold: greater than N | Center |
| Too many open appointment requests | Send an alert when the number of open invoices exceeds the threshold | "had [TotalInvoices] open invoices" β threshold: greater than N | Center |
| Register was not closed (center) | Send an alert when the register was not closed at a center | Unconditional β triggers when register is not closed by end of day | Center |
| Register was not closed (organization) | Send an alert listing all centers that did not close the register | Unconditional β triggers when any center did not close | Organization |
| Too many OTP overrides | Send an alert when the OTP override code is used more than the threshold | "OTP override code used [Count] time(s)" β threshold: greater than N | Center |
| Cash adjustment exceeds limit | Send an alert when cash adjustment in register closures exceeds the threshold | "cash adjustment is more than [Value]" β threshold: greater than N | Center |
Employee
| Alert | Description | Rule syntax | Level |
|---|---|---|---|
| Employee has been absent | Send an alert when an employee has not checked in for more than the threshold number of days | "did not check in more than [rule] days" β threshold: greater than N days | Center |
| Employee utilization is low | Send an alert when employee utilization falls below the threshold | "utilization did not meet the criteria" β threshold: less than N% | Center |
| Missed check-outs (organization) | Send an alert listing employees who checked in but did not check out | Unconditional β lists all employees with missed check-outs | Organization |
| Missed check-outs (center) | Send an alert listing employees at a center who checked in but did not check out | Unconditional β lists employees with missed check-outs at the center | Center |
| Pending self check-ins (center) | Send an alert listing employees with pending self check-in requests | Unconditional β lists pending requests | Center |
Guest Loyalty
| Alert | Description | Rule syntax | Level |
|---|---|---|---|
| Guest outstanding balance is too high | Send an alert listing guests with an outstanding balance above the threshold | "outstanding balance more than [ConditionValue]" β threshold: greater than N | Center |
| Service request not responded | Send an alert when mobile appointment requests exceed the threshold wait time (runs hourly) | "[ExceededThreshold] requests received more than [ThresholdValue] mins ago" β threshold: greater than N minutes | Center |
| Guest is not on target for package goal | Send an alert listing package guests who are not on target | Unconditional β lists guests not meeting package targets | Center |
| Guest has been irregular on package visits | Send an alert listing package guests who are irregular on visits | Unconditional β lists irregular guests | Center |
| Member has not accepted T&C | Send an alert listing guests who have not accepted membership terms and conditions | Unconditional β lists non-compliant guests | Center |
| Guests did not receive products purchased | Send an alert listing guests who did not receive products purchased online | "did not receive products purchased" β threshold: less than N days | Center |
Inventory
Feature prerequisite: The Near expiry alert and Real time expiry alert are available only for organizations that have the Batch Management and Expiry feature enabled in their license. Without this feature, both alert rules are inert even if configured. Contact your Zenoti account manager to enable the feature.
| Alert | Description | Rule syntax | Level |
|---|---|---|---|
| Product level is running low | Send an alert when product quantity falls below the alert level | "quantity less than the alert level specified" β uses product-level alert threshold | Center |
| Product order level has been reached | Send an alert when product quantity falls below the order level | "quantity less than the order level specified" β uses product-level order threshold | Center |
| Product level is negative (retail) | Send an alert when retail floor quantity is below zero | "retail floor quantity less than 0" β unconditional | Center |
| Product level is negative (consumable) | Send an alert when consumable floor quantity is below zero | "consumable floor quantity less than 0" β unconditional | Center |
| Appointments missing consumption entry | Send an alert listing appointments without consumable data | "does not have the Consumable data entered" β unconditional | Center |
| Reconciles pending for approval (organization) | Send an alert listing centers with pending reconciliation approvals | "reconciliations pending approval" β threshold: greater than N | Organization |
| Reconciles pending for approval (center) | Send an alert listing pending reconciliation approvals at a center | "reconciliations pending approval" β unconditional | Center |
| Near expiry alert | Send an alert for products expiring within the threshold number of days | "expiring in the next [AlertData] days" β threshold: equals N days | Center |
| Expired products alert | Send an alert for products identified as expired | "identified as EXPIRED" β unconditional | Center |
| Inventory daily digest | Send a daily summary of products below reorder point with stockout and below-reorder counts | "[StockoutCount] stockouts, [BelowReorderCount] below reorder point" β unconditional | Center |
Operational Issues
| Alert | Description | Rule syntax | Level |
|---|---|---|---|
| Text message (SMS) balance is low (center) | Send an alert when center SMS credits fall below the threshold | "[BalanceInfo] credits remain" β threshold: less than N | Center |
| Email balance is low (center) | Send an alert when center email credits fall below the threshold | "[BalanceInfo] credits remain" β threshold: less than N | Center |
| Text message (SMS) balance is low (organization) | Send an alert when organization SMS credits fall below the threshold | "[BalanceInfo] credits remain" β threshold: less than N | Organization |
| Email balance is low (organization) | Send an alert when organization email credits fall below the threshold | "[BalanceInfo] credits remain" β threshold: less than N | Organization |
| Voice balance is low (center) | Send an alert when center voice credits fall below the threshold | "[BalanceInfo] credits remain" β threshold: less than N | Center |
| Voice balance is low (organization) | Send an alert when organization voice credits fall below the threshold | "[BalanceInfo] credits remain" β threshold: less than N | Organization |
| Always on balance is low (center) | Send an alert when center Always On credits fall below the threshold | "[BalanceInfo] credits remain" β threshold: less than N | Center |
| Always on balance is low (organization) | Send an alert when organization Always On credits fall below the threshold | "[BalanceInfo] credits remain" β threshold: less than N | Organization |
| Opportunities missed follow-up | Send an alert listing opportunities that missed follow-up | "opportunities missed follow-up" β threshold: greater than N | Center |
| Room utilization is low | Send an alert when room utilization falls below the threshold | "rooms utilization did not meet the criteria" β threshold: less than N% | Center |
| Issues open for too many days | Send an alert listing issues open longer than the threshold | "issues are open more than [Value] day(s)" β threshold: greater than N days | Center |
| Payment dispute reminder | Send a reminder about disputed charges that need attention | "disputed charges that need your attention" β threshold: equals N | Center |
| SSL certificate will expire soon | Send an alert when an SSL certificate is nearing expiry | Unconditional β manual SSL management only | Organization |
| API key expiry | Send an alert when API keys are about to expire | "API Keys are going to expire soon" β threshold: less than N days | Organization |
| Email domain verified | Send a notification when domain verification succeeds | Unconditional β informational | Organization |
| Email domain verification failed | Send a notification when domain verification fails | Unconditional β action required | Organization |
| Webhook endpoint delivery failure | Send an alert when a webhook endpoint fails repeatedly | Triggered by external event β threshold: greater than N retries | Organization |
| Webhook delivery recovered | Send a notification when a failing webhook endpoint recovers | Triggered by external event β informational | Organization |
| Webhook subscription frozen | Send a notification when a webhook subscription is frozen due to continuous failure | Triggered by external event β action required | Organization |
Tips
- Start with organization-level alert rules to set baseline thresholds for all centers. Only create center-level overrides when a specific location has different operational needs.
- For inventory alerts, set threshold values based on each product's reorder lead time. A product that takes two weeks to restock should have a higher minimum stock threshold than one that can be restocked overnight.
- Assign alert recipients by role rather than by individual employee when possible. This ensures that alerts continue to reach the right people even when staff changes occur.
- Review and update alert thresholds periodically as your business volume changes.