Summary
Let customers subscribe to Help Center articles and receive a notification when that article is updated. Today, once an article is published, there's no built-in way for readers to know when it changes. This forces customers to either re-check articles manually or rely on us to broadcast every update through other channels.
Use case
Our Help Center hosts articles that change as products, firmware, and integrations evolve. Examples include known issue trackers, device compatibility lists, troubleshooting guides, and changelogs. Customers actively rely on these articles to stay current on the state of their deployments.
When we update one of these articles (for example, marking a known issue as resolved, or revising a workaround), the customers who care most about that article have no way to find out. They either keep checking back, or they file a support ticket asking for status, which creates avoidable inbound volume for the support team.
Proposed behavior
- Add a "Subscribe to updates" or "Notify me of changes" option on each Help Center article, visible to logged-in and anonymous readers.
- Anonymous readers enter an email address to subscribe. Logged-in / identified readers can subscribe with one click.
- When an article is meaningfully updated (admin-triggered, not every minor save), subscribers receive an email notification with the article title, a short summary of what changed (optional admin field), and a link back to the article.
- Admins can see subscriber counts per article and choose whether a given save event should trigger notifications.
- Subscribers can unsubscribe from a single article or from all article updates with one click.
Why this matters
- Reduces inbound "any update on this?" tickets
- Keeps customers proactively informed without requiring outbound campaigns from the support or product teams
- Increases the value and stickiness of the Help Center as a source of truth
- Aligns with how other knowledge base platforms (e.g. Zendesk Guide, Notion, GitBook) already handle article subscriptions
Workaround today
We currently have to manually email or message affected customers when a known-issue article changes, or hope they happen to revisit the page. Neither scales. I’ve seen free page-change monitor tools like Visualping, Distill.io, or Wachete that let anyone paste in a URL and get an email/Slack notification when the page content changes, but it seems a bit ridiculous to ask customers to do this, so we will not be doing that.