ZenotiHelp

Appointment Notification Deduplication β€” Wait Time Threshold Reminders

ZTZenoti Docs Team Updated September 12, 2026 3 min readGuide

Zenoti prevents duplicate wait-time threshold notifications from reaching guests by checking whether a pending notification of the same type already exists before adding a new one to the queue. This article explains how the deduplication guard works for First Threshold and Second Threshold notifications and what administrators need to know about its scope.

Note: For conceptual background on the guest kiosk and queue integration, see Front Desk Kiosk Overview.


On this page


Before you begin

  • Your organization must have the guest kiosk enabled at both the organization and center level before wait-time notifications are active.
  • Wait-time notifications require the Enable wait time notifications for guests center setting to be turned on. This setting also governs next-in-line notification behavior β€” there is no separate next-in-line toggle.
  • The deduplication behavior described in this article is automatic and requires no additional configuration. It cannot be disabled per center.

Permission: Reviewing or modifying kiosk and notification settings requires the Edit permission on the Organizations security object. Admin path: Configuration at the organization level


How wait-time threshold deduplication works

When Zenoti is about to enqueue a wait-time threshold notification for a guest, it first checks whether a pending notification of the same type already exists for the same appointment group or invoice. If a matching pending notification is found, the new notification is skipped β€” it is not added to the queue a second time.

The check evaluates all of the following conditions simultaneously:

  • The reference identifier matches β€” the system uses the appointment group ID if one exists, or the invoice ID if no group ID is present.
  • The notification type matches β€” either First Threshold or Second Threshold.
  • The existing notification has not been voided.
  • At least one delivery channel (email, SMS, or push) on the existing notification has not yet been sent (status equals pending).

Only when all four conditions are met does the system treat the existing record as a duplicate and skip enqueueing the new notification. If any condition is not met β€” for example, if all channels on the existing notification have already been sent β€” the new notification proceeds to the queue normally.

This behavior prevents guests from receiving the same threshold alert more than once for the same appointment or group booking.


Notification types covered by deduplication

The deduplication guard applies exclusively to the following two notification types:

Notification Description
First Threshold Sent when a guest's wait time reaches the first configured threshold.
Second Threshold Sent when a guest's wait time reaches the second configured threshold.

Both notification types are subject to the same deduplication logic. The guard runs each time either type is about to be enqueued, regardless of which delivery channel (email, SMS, or push) is in use.


Notification types not covered by deduplication

The deduplication check described in this article applies only to First Threshold and Second Threshold notifications. All other notification types β€” including appointment confirmations, reminders, cancellations, and any other system-generated messages β€” are not subject to this guard and follow their standard enqueueing behavior.

If you observe duplicate notifications for a type other than the two threshold types, that behavior is unrelated to this deduplication mechanism. Review the notification settings for that specific type under Configuration at the center level.


Output parameter for enqueued notifications

When a threshold notification is successfully added to the queue (that is, no duplicate was found), the enqueueing process returns a notifications queue reference to the calling process. This reference is available to any internal process that triggers threshold notifications, allowing downstream steps to confirm that the notification was enqueued and to track its queue entry.

This output is produced automatically when a notification is enqueued. No configuration is required to enable it, and it is not visible in the Zenoti administration interface. It is relevant only when integrating with or troubleshooting notification delivery pipelines.

Note: If the deduplication check determines that a duplicate exists, no notification is enqueued and no queue reference is returned for that attempt.


Was this article helpful?
Your feedback helps us improve our documentation.