Appointment reminder deduplication guard
Zenoti automatically prevents duplicate appointment reminders from being queued when a reminder of the same type is already pending for an appointment. This article explains how the deduplication behavior works and what front desk staff and administrators can expect when reminders are scheduled.
Audience: Administrators and front desk staff who manage appointment notification workflows.
On this page
Before you begin
- Your organization must have appointment notifications enabled. Appointment reminder settings are configured under Configuration > Appointments > Notifications and alerts.
- You need permission to view and manage appointment notification settings.
- Understand that deduplication applies to two specific reminder types:
- First Appointment Reminder β the first scheduled reminder sent before an appointment.
- Second Appointment Reminder β the second scheduled reminder sent before an appointment.
- Deduplication is automatic system behavior. There is no toggle to enable or disable it. No configuration steps are required to activate it.
Note: Appointment reminder timing and channel settings (email, text, or both) are configured separately. See Configure appointment notifications for those settings.
How deduplication works
When Zenoti prepares to queue a First Appointment Reminder or a Second Appointment Reminder, it checks whether a pending reminder of the same type already exists for that appointment group or invoice. A reminder is considered pending if it has not yet been sent via any channel β email, text message, or push notification.
If a matching pending reminder is found, Zenoti skips inserting a new notification record and returns a success result immediately. No duplicate reminder is added to the queue.
This behavior prevents guests from receiving the same reminder more than once when, for example:
- A reminder is triggered by multiple scheduling events in quick succession.
- An appointment is rescheduled after a reminder has already been queued but not yet delivered.
- A batch process attempts to re-queue reminders that are already pending.
Important: Deduplication only applies to reminders that are still pending β that is, reminders that have not yet been sent. If a reminder has already been delivered, a new reminder of the same type can be queued normally for a subsequent trigger.
Steps
Because deduplication is automatic, there are no manual steps required to activate or configure it. The following steps describe how to verify that your appointment reminder settings are correctly configured so that deduplication operates as expected.
Verify appointment reminder settings
- Select the Configuration icon in the main navigation.
- In the search field, type
Appointment notificationsand select the result, or navigate to Appointments > Notifications and alerts. - Under Guest notifications, confirm that Send first reminder for appointment is enabled for the centers where you want reminders to send.
- Confirm that Send second reminder for appointment is enabled if your organization uses a second reminder.
- Review the timing settings:
- When should the first reminder be sent? β Options include Send on the previous day of appointment at, Send on the morning of the day of the appointment at, or Send minutes before the appointment.
- When should the second reminder be sent? β Same options as the first reminder.
- Select Save to preserve any changes.
Note: Deduplication applies regardless of which timing option you select. If a pending reminder already exists for the appointment, a duplicate will not be queued even if the timing window is re-evaluated.
Confirm notification channel settings
- In the same Notifications and alerts section, locate How should the reminder be sent? under the first and second reminder settings.
- Confirm the channel is set to Email, Text, or Email and text as appropriate for your organization.
- Select Save if you make any changes.
Note: Deduplication checks across all channels. A pending reminder is considered a duplicate regardless of whether it was queued for email, text, or push notification delivery.
Review reminder behavior for rescheduled appointments
When an appointment is rescheduled, Zenoti evaluates whether a new reminder should be queued based on the updated appointment time. If a pending reminder of the same type already exists for the appointment, the system skips queuing a new one.
To confirm how reschedule notifications are handled:
- Navigate to Configuration > Appointments > Notifications and alerts.
- Locate Send appointment reschedule notification and review the setting:
- Always β A reschedule notification is always sent.
- Only when service's new start time is changed by at least these many minutes from current start time β A reschedule notification is sent only when the time change meets the threshold.
- Note that reschedule notifications are a separate notification type from reminders. Deduplication for reminders does not suppress reschedule notifications.
Tips
- Check pending notifications before rescheduling in bulk. If you reschedule multiple appointments at once, deduplication ensures guests do not receive duplicate reminders. However, if you want to confirm that reminders are queued correctly after a bulk reschedule, review the guest's notification history on their profile under the Notifications tab.
- Use the second reminder for high no-show risk appointments. Because deduplication prevents duplicate second reminders, you can enable the second reminder for all appointments without concern that guests will receive it more than once per appointment.
- Coordinate reminder timing with your cancellation policy. If your organization charges a cancellation fee, set the first reminder far enough in advance that guests have time to cancel without incurring a fee. Deduplication ensures the reminder is sent once at the scheduled time.
Troubleshooting
A guest reports they did not receive a reminder.
Deduplication only prevents duplicate reminders β it does not suppress the first reminder. If a guest did not receive a reminder, check the following:
- Confirm that the guest's profile has a valid email address or mobile number, depending on the channel configured.
- Confirm that the guest's notification preferences allow transactional messages. On the guest profile, select the Notifications tab and verify that the guest has not opted out of appointment reminders.
- Confirm that the reminder setting is enabled at the center level under Configuration > Appointments > Notifications and alerts.
- Check whether the appointment was booked after the scheduled reminder time. If the appointment was booked within the reminder window, the reminder may not have been queued. Review the Send notification immediately if booking is done after the scheduled reminder time up to setting to confirm whether an immediate notification would have been triggered.
A guest received a reminder but the appointment was already cancelled.
If a reminder was queued before the appointment was cancelled, it may have already been delivered before the cancellation was processed. Deduplication prevents new reminders from being queued for the same appointment, but it does not recall reminders that have already been sent. To reduce this scenario, ensure cancellations are processed promptly so that pending reminders can be cleared before delivery.
Reminders appear to be queued but are not delivering.
Deduplication does not affect delivery β it only prevents duplicate records from being inserted into the notification queue. If reminders are queued but not delivering, the issue is likely with the notification channel configuration or credit balance for text messages. Navigate to Configuration > Notifications to review channel settings and credit usage.