My team and I recently identified multiple instances where, despite being subscribed to the Zendesk Announcements section, we did not receive notification emails for certain newly published Zendesk announcements. After reporting the issue and working closely with Zendesk Support through multiple investigation cycles, Zendesk confirmed that this is the current system behavior.
According to Zendesk, when an article is moved to the Announcements section, notification emails are sent only to users who have permission to view the article at that specific moment. If the article is initially restricted to Admins and Agents and its visibility is expanded later, the users who did not have access at the time of publication never receive the announcement notification, and the notification is not re-triggered after the visibility change.
We would therefore like to request an enhancement to the Zendesk Announcements notification system.
This creates a significant risk of users missing important product updates, platform changes, security notices, and feature announcements, despite actively subscribing to the Announcements section.
Business Impact:
- Followers can miss critical announcements without any indication that a notification was not delivered.
- The current behavior depends on a temporary publication-state configuration rather than the final visibility of the article.
- Organizations following Zendesk announcements for change management, compliance, release tracking, and operational planning may not be aware of important updates.
- The current behavior can create inconsistent communication across teams, with some followers receiving important announcements while others are unknowingly excluded.
Suggested Improvements:
- Automatically trigger notifications when article visibility is expanded to include new audiences.
- Provide a warning message when moving an article to the Announcements section while visibility is restricted, informing admins (Help Center editors) that users without access will not receive notifications.
- Consider basing notification delivery on the article's final published visibility rather than its visibility at the moment it is moved to Announcements.
- Add reporting or audit capabilities showing which subscribers received announcement notifications.
- Include a notification status indicator that allows administrators to verify whether subscribers have been notified successfully.
Expected Outcome:
Users who follow the Announcements section should reliably receive notifications for all announcements they are eligible to view, regardless of temporary visibility settings used during the publication process. Administrators should also have sufficient visibility and controls to validate, audit, and, if necessary, resend announcement notifications.
Why This Matters:
Subscribers trust the Announcement system to keep them informed about changes that may impact their daily operations, product usage, compliance obligations, and release planning. Notification delivery should be resilient to common administrative publication workflows and should not be permanently lost due to a temporary visibility configuration that is later corrected.
This enhancement would improve reliability, reduce the risk of missed communications, increase transparency for administrators, and align the notification system with customer expectations for a critical communication channel.