Troubleshoot notification delivery
When guests or employees report missing notifications, use this guide to diagnose and resolve common delivery issues across email, SMS, WhatsApp, and push channels.
Audience: Administrators and front desk staff who manage guest and employee notifications.
On this page
- Before you begin
- General checks
- Platform incidents β multiple unrelated notifications failing at once
- Credit exhaustion and queue drain
- SMS delivery issues
- Email delivery issues
- Hard bounce suppression β when email is never attempted
- WhatsApp delivery issues
- Appointment reminder issues
- Late reminders β separating a Zenoti delay from a carrier delay
- Notification shows as sent but the guest never received it
- OTP delivery issues
- One-time passcode failing at one center only
- Confirmation link reports failure
- Guest blocked by the messaging provider
- Text messages failing at one center while other centers succeed
- Single staff member stops receiving notifications
- SMS opt-out β guest no longer receives any text messages
- Common scenarios
- Additional diagnostic procedures
- Related articles
Before you begin
- You need administrator access at the organization level.
- Access to the notification settings and credit usage dashboard is required for most troubleshooting steps.
Permission: Edit under Organizations in the Administrator section of the security role (Configuration > Security > Security roles) is required to modify notification settings during troubleshooting.
General checks
Before investigating channel-specific issues, verify these common causes:
- Verify master toggles are enabled β Navigate to Configuration > Notifications and confirm that the Activate email and Activate SMS master toggles are enabled. When either toggle is off, all notifications of that channel are suppressed organization-wide.
- Verify the notification type is enabled β In the notification center, confirm that the specific notification type (for example, Appointment Confirmation) is toggled on for the expected channel.
- Check communication credits β Navigate to Configuration > Business details > Credit balance. If credits for a channel are exhausted, notifications for that channel stop being delivered. See Monitor notification credit usage.
- Verify guest contact information β Open the guest profile and confirm that the mobile number (including country code) and email address are correct and up to date.
- Check whether the appointment is a surprise visit β For an appointment booked as a surprise visit, Zenoti does not send the appointment confirmation, change, cancellation, reminder, payment-added, or new-guest registration notifications. This is expected behavior, not a delivery failure. See Mark a surprise visit.
- Check opt-out status β The guest may have unsubscribed from notifications. Check the guest profile for opt-out flags, especially for marketing notifications.
Platform incidents β multiple unrelated notifications failing at once
When several unrelated notification types fail at the same moment β for example, appointment confirmations, loyalty point accrual notices, and invoice receipts all stop sending simultaneously β this pattern is the signature of a platform incident rather than a configuration fault.
Check for a platform incident first. Before investigating individual templates, channels, or credit balances, verify whether Zenoti has reported a service disruption. If an incident is confirmed:
- No configuration change on your end will restore delivery until the incident is resolved.
- Notifications missed during a platform incident are not sent retroactively once the incident is resolved. The system does not replay queued messages after recovery. If a time-sensitive notification (such as an appointment reminder) was missed, you may need to contact affected guests directly.
If no incident is reported and multiple notification types are still failing, proceed to the general checks above.
Credit exhaustion and queue drain
When your organization's communication credits run out, outgoing messages accumulate in a sending queue, and topping up does not always resume delivery straight away.
Usually this is the queue. The backlog must flush before new messages resume delivery, so if you purchase credits and notifications do not arrive immediately, sending normally resumes on its own once the backlog clears. This is expected, not a sign that the top-up failed.
To check current credit status and usage trends:
- Navigate to Configuration > Business details > Credit balance.
- Review the credit balances listed for Text messages, Whatsapp messages, Email, Voice, Always on, and RCS Messages to confirm credits have been restored for the relevant channel.
- Monitor delivery over the next several minutes as the queue drains.
If delivery has not resumed once the queue has had time to drain, do not keep waiting. First confirm the balance was actually restored for the affected channel and at the level that center draws on β channel balances are separate, and so are organization and center balances. If the balance is healthy and messages still are not going out, contact Zenoti Support, and tell them which center and which channel are affected. Delivery can be blocked for one channel at one center while everything else sends normally, so "text messages are not sending at one center while email works there" is the detail that gets the right check made first.
Why a center can still be out of credits after a purchase
Running out of credits is not a single condition, so a purchase that restores one balance does not always restore the one that was blocking delivery. When one center stops sending on a channel while other centers keep sending β including right after a credit purchase β that center's own balance is exhausted and it could not draw more from the organization. There is more than one reason for that:
- The purchase went to other centers. Credits were added where they were not needed, and the balance at the failing center is unchanged.
- The organization has fewer than one block (50 credits) left for the channel. A center tops itself up from the organization pool one block at a time, so an organization balance below a full block cannot replenish the center even though the pool is not empty.
- The center does not draw on organization credits. The center holds its own balance for that channel and has to be topped up directly.
Compare Configuration > Business details > Credit balance in the organization view and in that center's view to tell these apart. See Organization and center balances in Monitor notification credit usage. If the organization balance is healthy and the center still cannot send, contact Zenoti Support naming the center and channel.
SMS delivery issues
Guest not receiving SMS notifications
- Verify the guest's mobile number β Open the guest profile and confirm the mobile number is correct, including the country code.
- Check SMS credits β Navigate to Configuration > Business details > Credit balance. Ensure your organization has sufficient SMS credits.
- Verify the notification type is enabled for SMS β In the notification center, confirm the specific notification type is toggled on for the SMS channel.
- Check opt-out status β The guest may have texted a STOP keyword to opt out of SMS notifications. When a guest replies with an opt-out keyword, they are opted out of all text messages, not only marketing messages.
DLT registration (India)
For organizations operating in India, SMS messages must be registered with the DLT (Distributed Ledger Technology) platform as required by TRAI regulations.
- Template registration β All SMS templates must be registered with the DLT platform before they can be sent.
- Sender ID β Your organization's Sender ID must be registered with your DLT operator and approved before it can be used. This is not a setting in Zenoti's notification settings: you request the Sender ID in your DLT operator's portal, and an approved Sender ID is then linked to your organization. For the registration checklist, the documents required and how to get an approved Sender ID linked, see India DLT and KYC compliance.
- Content matching β SMS content must match the registered template exactly. Dynamic fields (macros) are allowed only in designated variable positions.
Note: If SMS notifications are not being delivered in India, verify that the notification template is DLT-registered and the content matches the approved template. For other regions, registration and sender identity requirements are handled outside Zenoti β see Configure SMS compliance.
SMS credit exhaustion
If SMS credits are depleted:
- Check the credit balance at Configuration > Business details > Credit balance.
- Purchase additional credits via the Marketplace.
- Consider enabling email as a fallback channel for critical notifications.
Email delivery issues
Emails going to spam or not delivered
- Verify DNS configuration β Ensure SPF, DKIM, and DMARC records are properly configured. Navigate to Configuration > Business details > Customize outgoing email addresses to review and verify your DNS records using the in-app wizard. See Configure DNS for email delivery.
- Check the sender email address β Ensure the From address matches your organization's domain and is not using a generic or free email provider.
- Review email content β Avoid spam trigger words in notification templates. Excessive use of capital letters, exclamation marks, or promotional language can trigger spam filters.
- Check bounce logs β Emails may bounce if the guest's email address is invalid or the recipient's mailbox is full.
Email bounces
Common bounce reasons:
- Hard bounce β Invalid email address (permanent). Update the guest's email address. See Hard bounce suppression below for how Zenoti handles hard bounces automatically.
- Soft bounce β Mailbox full or temporarily unavailable (retried automatically).
- Blocked β Recipient's email server is blocking your domain. Check DNS records.
Hard bounce suppression β when email is never attempted
Hard bounces are handled differently from other delivery failures in Zenoti, and the distinction matters for troubleshooting.
How Zenoti suppresses bounced addresses
When an email address experiences a hard bounce, Zenoti marks that address as bounced in the guest's profile. Once an address is marked as bounced:
- The system assigns a failure status to any queued message destined for that address β it does not attempt delivery. As a result, these notifications do not appear with a Sent status. They are never handed to the email provider in the first place.
- A note is recorded against each affected guest's profile, making the suppression discoverable. You can see this note when you open the guest's record.
- The suppression applies to every guest profile that shares the same email address string. If a shared mailbox address receives a hard bounce, email delivery is suppressed for all profiles using that address β not only the one that originally bounced.
This suppression is organization-wide and applies to all email notification types, including appointment confirmations, loyalty points-expiry reminders, balance statements, membership expiry reminders, and package expiry reminders, in addition to register-closure reports.
How to distinguish a suppressed address from a sent-but-undelivered message
These two cases must not be treated as the same problem:
| Situation | Interface status | What happened | Action |
|---|---|---|---|
| Hard bounce suppression | No Sent status β message was never attempted | Zenoti blocked delivery because the address is marked as bounced | Correct or re-confirm the email address, then reactivate it (see below) |
| Sent but undelivered at carrier | Shows Sent | Zenoti handed the message to the provider; carrier could not deliver | No Zenoti change needed; ask guest to verify device/inbox settings |
How to reactivate a bounced email address
Correcting or re-confirming a bounced address is required before email delivery resumes. Updating the email field is not sufficient β the bounced state must also be cleared.
Permission: The To Allow Email Activate permission must be enabled for the role before the Activate button is visible on the guest profile. To grant it: navigate to Configuration > Security > Security roles, select the role (for example, Manager), open the Permissions tab, locate Guests under the Guest Manager section, and select To Allow Email Activate.
To reactivate a bounced address:
- Open the guest profile.
- Correct the email address if it was invalid, or confirm it is accurate if the bounce was erroneous.
- Select Activate to clear the bounced state.
Once the address is reactivated, future email notifications will be delivered normally.
If a shared mailbox is involved: Because suppression applies to every profile sharing the same address, you must reactivate the address on all affected profiles, not the one you are currently viewing.
WhatsApp delivery issues
WhatsApp messages not delivered
- Verify template approval β WhatsApp templates must be approved by Twilio and Meta before they can be used. The approval process typically takes up to 48 hours. Check the template status in the notification center. See Configure WhatsApp notification templates.
- Check WhatsApp credits β Verify that your organization has sufficient WhatsApp credits at Configuration > Business details > Credit balance.
- Verify guest's WhatsApp number β The guest must have an active WhatsApp account registered to the phone number on their profile.
- Check consent status β WhatsApp messages require guest consent. Verify the guest has opted in.
Appointment reminder issues
Reminders not being sent
- Check reminder timing configuration β Verify that the reminder timing is correctly configured at the organization or center level. See Configure notification types and triggers for details on reminder timing modes.
- Verify the appointment was booked in time β If a guest books an appointment after the configured reminder time has already passed, the reminder is not sent unless the Send reminder immediately option is enabled.
- Check center-level overrides β If the center has overridden organization notification settings, verify that the center's reminder configuration is correct.
- Check whether the second reminder is set to skip confirmed guests β If the first reminder arrived and only the second is missing, and the guest had already confirmed the appointment, this is configured behavior rather than a delivery failure. The setting is Don't send reminder if confirmed at the organization level and Do not send reminder if confirmed at the center level; each offers Send only when guest has not confirmed booking or always send second reminder. It appears only when the second reminder is enabled, and it is not turned on by default. See Configure appointment notifications.
- Check whether the appointment is a surprise visit β Zenoti sends no reminders for an appointment booked as a surprise visit. See Mark a surprise visit.
Late reminders β separating a Zenoti delay from a carrier delay
A reminder that arrives late can have one of two causes: a delay before the message left Zenoti, or a delay introduced by the carrier after Zenoti handed it off. The procedure below separates them.
- Find the scheduled send time β In the guest profile, open the Notifications tab and locate the reminder. Note the time Zenoti scheduled the message for delivery.
- Find the actual delivery time β Check the time the guest received the message on their device.
- Compare the two times:
- If the delivery time is close to the scheduled time, the delay occurred at the carrier. Carrier delays are outside Zenoti's control and typically resolve on their own. There is nothing to change in Zenoti for a carrier-side delay.
- If the delivery time is significantly later than the scheduled time, the delay occurred before the message left Zenoti. In this case, check credit balance, queue status, and master toggle settings as described in General checks.
Notification shows as sent but the guest never received it
When a notification shows a Sent status in Zenoti but the guest reports never receiving it, the issue is carrier-side rather than a Zenoti configuration problem.
What "Sent" means: The Sent status confirms that Zenoti successfully handed the message to the messaging provider. It does not guarantee that the message reached the guest's device. Delivery receipts from the carrier can be delayed, and an unreachable handset (for example, a phone that is off, out of coverage, or has a full message inbox) can cause the carrier to hold or drop the message without returning an immediate failure.
What to do: There is nothing to change in Zenoti for this case. The message left Zenoti successfully. If the guest consistently fails to receive messages that show as Sent, ask the guest to verify their device settings (SMS blocking, spam filters, or storage limits) and confirm their number is active and receiving messages from other senders.
Note: This Sent-but-undelivered case is distinct from hard bounce suppression, where email delivery is never attempted and no Sent status appears. See Hard bounce suppression for the procedure that applies when an address is bounced.
OTP delivery issues
Guest not receiving OTP codes
- Verify contact information β The guest must have a valid mobile number (for SMS OTP) or email address (for email OTP) on their profile.
- Check the OTP delivery channel β Navigate to Configuration > POS > Invoices > Basic invoice actions and verify which channel (SMS or email) is configured under Enforce one-time-password (OTP) for redemptions - SMS and Enforce one-time-password (OTP) for redemptions - Email.
- Verify master toggles β The Activate SMS or Activate email master toggle must be enabled for the configured OTP channel.
- Check credits β OTP messages consume credits from the configured channel.
One-time passcode failing at one center only
When a one-time passcode (OTP) fails at a single center while sibling centers succeed, the issue is specific to that center's configuration. Check the following in order β the first item is self-serve; the second requires Zenoti Support:
- Center's own message credits β Navigate to Configuration > Business details > Credit balance and review the balance for the affected center. Confirm the center has sufficient credits for the OTP channel. A center with depleted credits will fail to send OTPs even if the organization-level balance appears healthy.
- Center's messaging provisioning β If credits are available but OTPs still fail at that center only, the center's messaging channel may not be fully provisioned. Contact Zenoti Support to verify and restore provisioning for the affected center.
- Guest's preferred-center scoping β OTP generation is scoped to the guest's preferred center. If the guest's preferred center is set to a different center than the one where the redemption is being attempted, the OTP may not be generated for that center. Verify the guest's preferred center in their profile and confirm it matches the center where the OTP is needed.
Confirmation link reports failure
A confirmation link in a notification allows a guest to confirm their appointment. If one guest reports a failure, the most likely cause is the appointment's current state.
A confirmation link cannot confirm an appointment that is already confirmed. The link is expected to fail β and will report an error β when the appointment is in any of the following states at the time the guest clicks:
- Already confirmed
- Cancelled
- No-show
- Completed
- Deleted
If the guest clicks the link and the appointment is still in a New or Pending state, and the link still fails, verify that the link has not expired and that the guest is using the most recent confirmation notification (not an older one from a previous reminder).
If several guests report the same failure at once, stop checking appointment states. When many guests fail on the same notification type at the same time, the cause is the template the link was sent from, not any one appointment. Open each template that carries the confirmation link under Configuration > Notifications > Templates for email and text:
- Appointment Confirmation
- Appointment Confirmation - Online Booking
- First Appointment Reminder
- Second Appointment Reminder
- Appointment Rescheduled
- The group confirmation templates, where group bookings are used
In each of these templates, check how the link is inserted β a confirmation link breaks for everyone when the macro is removed, when it is placed in a template type that does not support it, or when it is entered as a link address with a fixed protocol such as https:// in front of it, which sends every guest to an error page. Note that the template saves without an error in each case. See Configure notification template macros.
This is a different pattern from several unrelated notification types failing at the same moment, which points at a platform incident β see the "Platform incidents" section above.
Note: When you reproduce this with a test booking, book the appointment far enough ahead. Your organization sets a minimum lead time under Send appointment confirmation notification if an appointment is booked (in minutes) before the appointment β appointments booked closer than that do not trigger a confirmation at all, so a test booked a few minutes out produces no notification to click. See Configure appointment notifications.
Guest blocked by the messaging provider
In some cases, a guest's number or email address is flagged and blocked by the messaging provider. When this happens:
- The notification shows as Sent in Zenoti's interface, because Zenoti successfully handed the message to the provider.
- The provider records the message as undelivered on their side.
This mismatch β Sent in Zenoti, undelivered at the provider β means the guest never receives the message even though the interface shows no error.
Removing a provider-side block is performed by Zenoti Support, not by an administrator. If you suspect a guest is blocked at the provider level (for example, the guest consistently shows Sent but never receives messages, and their contact details are confirmed correct), raise a support ticket with the guest's details and the affected notification types. Zenoti Support will work with the provider to investigate and remove the block.
Text messages failing at one center while other centers succeed
When SMS notifications fail at a single center but succeed at other centers in the same organization, the most likely cause is the phone number stored for that center.
SMS numbers must be in full international format. A number saved without the country code causes intermittent SMS failures for that center alone, while other centers with correctly formatted numbers continue to send successfully.
To resolve this:
- Navigate to the affected center's settings.
- Locate the center's outgoing SMS number.
- Verify the number includes the full international dialing code (for example,
+1for the United States,+44for the United Kingdom). - Update the number to full international format if it is missing the country code.
- Test by sending a notification from that center.
Single staff member stops receiving notifications
When one staff member stops receiving email or text notifications while other employees at the same center continue to receive them, the cause is not a center-wide credit or configuration failure β it is a per-recipient condition on that employee's profile.
Work through the following checks in order:
- Transactional email or text consent β Open the employee's profile and confirm that the transactional email and text consent settings are enabled. If the employee has opted out of transactional notifications, delivery is suppressed regardless of center or organization settings.
- Non-null email address and mobile number β Verify the employee's profile contains a valid, non-empty email address (for email notifications) and a valid mobile number in full international format (for text notifications).
- Email address is in a deliverable state β Check whether the employee's email address has experienced a hard bounce. If it has, the address is marked as bounced and email delivery is suppressed. To reactivate it, follow the procedure in Hard bounce suppression. If the employee's email address is shared with other profiles (for example, a shared team inbox), correcting the bounce state must cover all profiles using that address.
- Last working date β Confirm that the employee's last working date has not passed. Employees whose last working date is in the past are excluded from notification delivery.
If all four conditions are met and the employee still does not receive notifications, verify that the notification type is enabled for the employee's role and that center-level credits are available, then raise a support ticket if the issue persists.
SMS opt-out β guest no longer receives any text messages
When a guest replies to an SMS with an opt-out keyword (such as STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT), they are opted out of all text messages from your organization β not only marketing messages. Transactional notifications such as appointment confirmations and reminders are also suppressed until the guest opts back in.
To re-subscribe a guest:
- Open the guest profile and check the SMS opt-out status on the General tab.
- Confirm with the guest that they want to receive text messages again.
- Have the guest reply to a previous SMS from your organization with the opt-in keyword configured for your organization (commonly START or YES), or send the guest an opt-in re-subscription message.
- Once the guest replies with the opt-in keyword, their SMS opt-out flag is cleared and they will begin receiving text messages again.
Note: The opt-in keyword is configured in Configuration > Guests > Marketing > Keywords to subscribe to marketing messages. Avoid reusing the transactional keywords
aptandunsubscribefor marketing opt-in keywords.
Common scenarios
The table below lists the most common notification delivery symptoms, their likely causes, and the recommended resolution. For symptoms that require more detailed investigation, refer to the dedicated sections above.
| Symptom | Likely cause | Solution |
|---|---|---|
| No notifications sent at all | Master Activate email or Activate SMS toggle is disabled | Enable the master toggle in Configuration > Notifications > Email / Text |
| SMS sent but not received | Invalid mobile number or missing country code | Verify guest's mobile number with country code |
| Email sent but landing in spam | Missing SPF, DKIM, or DMARC records | Configure DNS records via Configuration > Business details > Customize outgoing email addresses |
| Notifications delayed | Credit exhaustion or processing backlog | Check Configuration > Business details > Credit balance; if credits were recently topped up, wait for the queue to drain |
| OTP not received | Guest contact info is outdated | Update mobile number or email in guest profile |
| Appointment reminders not sent | Reminder timing misconfigured | Check reminder timing settings (day-before vs. minutes-before) |
| WhatsApp messages not sent | Template not approved by Twilio/Meta | Check template approval status in notification center |
| Center notifications differ from organization | Center-level overrides are active | Review center notification settings for overrides |
| Multiple unrelated notification types failing simultaneously | Platform incident | Check for a Zenoti service disruption; note that messages missed during an incident are not sent retroactively |
| Notification shows as Sent but guest never received it | Carrier-side issue; unreachable handset or delayed receipt | No Zenoti change needed; ask guest to verify device settings and confirm number is active |
| Reminder arrived late | Delay before message left Zenoti, or carrier delay | Compare scheduled send time to delivery time to identify which side introduced the delay |
| OTP failing at one center only | Credits depleted at that center, or center not provisioned, or guest's preferred center does not match the redemption center | Check center-level credit balance at Configuration > Business details > Credit balance; verify guest's preferred center in their profile; contact Zenoti Support for provisioning issues |
| One center stops sending on a channel while other centers keep sending, including immediately after a credit purchase | That center's own balance is exhausted and it could not draw more from the organization: the purchase went to other centers, the organization has fewer than one block (50 credits) left for the channel, or the center does not draw on organization credits | Compare Configuration > Business details > Credit balance in the organization view and in that center's view. See Organization and center balances in Monitor notification credit usage. If the organization balance is healthy, contact Zenoti Support naming the center and channel. |
| Confirmation link fails when guest clicks it | One guest: the appointment is already confirmed, cancelled, no-show, completed, or deleted. Several guests at once: the template the link was sent from. | For one guest, explain that the link only works when the appointment is in a New or Pending state. For several at once, check how the confirmation link macro is inserted in the template. |
| Notification shows Sent but provider records it as undelivered | Guest is blocked at the messaging provider | Contact Zenoti Support to investigate and remove the provider-side block |
| SMS failing at one center, other centers succeed | Center's number is not in full international format | Update the center's SMS number to include the country code |
| Guest opted out and is wondering why no SMS arrives | Guest replied STOP (or equivalent) to a previous SMS, triggering opt-out. The guest is now flagged as opted out of all text messages, not only marketing. | 1. Open the guest profile and check the SMS opt-out status. 2. If the status is opted out, confirm the guest now wants to receive SMS again. 3. Send an opt-in re-subscription message OR have the guest reply with the opt-in keyword (commonly START or YES). The guest is re-subscribed once they opt back in. |
| Email notifications show no Sent status for a guest or employee | Email address has experienced a hard bounce and delivery is suppressed | Correct the email address if invalid, then reactivate it using the Activate button on the profile (requires To Allow Email Activate permission). If a shared mailbox is involved, reactivate all profiles using that address. |
| Single staff member stops receiving notifications while others succeed | Per-recipient condition: consent disabled, missing contact info, bounced email address, or last working date has passed | Work through the service-provider delivery checklist: verify transactional consent is on, confirm email and mobile are populated, check for a bounced email state, and confirm the last working date has not passed |
Additional diagnostic procedures
Check delivery status from the guest profile (Sent / Pending / Failed)
Navigate to the guest's profile and click the Notifications tab to review the status of sent notifications. A notification can have a Sent, Pending, or Failed status. Use this per-guest view to confirm whether a specific notification was delivered.
Note: A Sent status means Zenoti handed the message to the provider β it does not confirm delivery to the guest's device. A message that was suppressed due to a hard-bounced email address does not appear with a Sent status; it is never attempted.
Per-employee confirmation suppression
If guest confirmations are missing for appointments booked under a specific employee, check that employee's confirmation setting:
- Go to Employees > Employees and select the employee profile.
- Open the General tab.
- Confirm Send confirmation email/text to guests for appointments scheduled for this employee is selected.
When this option is cleared, Zenoti suppresses guest confirmations for that employee's bookings.
Reactivate a bounced email address
When an email address bounces, Zenoti deactivates it. To reactivate it, the To Allow Email Activate permission must be enabled for the role:
- Navigate to Configuration > Security > Security roles, select the role (for example, Manager), and open the Permissions tab.
- In the Guest Manager section, under Guests, select To Allow Email Activate.
- With the permission enabled, reactivate the bounced email address from the guest profile.
If the address is a shared mailbox: Because Zenoti matches suppression on the email address string across all profiles, reactivating the address on one profile does not automatically clear the suppression on other profiles that share the same address. Reactivate the address on every affected profile.
Therapist request-type confirmation
If confirmations are not sent for appointments of a particular therapist request type, enable confirmation for that therapist request type.
Service-provider delivery checklist
When a single staff member stops receiving email or text notifications while others succeed, use this checklist before raising a support ticket. Each condition can silently block delivery independently of center-level credit and configuration checks:
- Transactional consent is enabled β Verify the employee's profile has transactional email or text consent switched on.
- Email address is populated and valid β Confirm the profile contains a non-empty email address.
- Email address is in a deliverable state β Check that the email address has not been marked as bounced. If it has, follow the Reactivate a bounced email address procedure above. If the address is shared with other profiles, the fix must cover all profiles using that address.
- Last working date has not passed β Confirm the employee's last working date is either unset or in the future. Employees whose last working date has passed are excluded from notification delivery.
If all four conditions are met and the issue persists, verify that the notification type is enabled for the employee's role and that center-level credits are available, then raise a support ticket with the affected employee's name, the notification type, and the timestamp.