Question 1

How does SentryDock decide what to alert me about?

Accepted Answer

Each monitor has a topic, a set of sources and a schedule. When a source produces new material, SentryDock extracts the available content and compares it with the instructions saved on that monitor. Items that appear relevant can be summarized, translated and analysed. Duplicate or substantially similar items may be grouped so the same event does not create a stream of identical alerts. The exact analysis available depends on the monitor and plan. What affects relevance The subject, entities, locations and events named in your monitoring instruction. Any exclusions or materiality criteria you added. The content that was available from the original source at check time. The relevance threshold and analysis settings used by the monitor. How to reduce noisy alerts Make the instruction more specific about what should trigger an alert and what should not. Add trusted, narrowly focused sources and remove broad sources that repeatedly produce irrelevant results. If the topic is not time-sensitive, use an hourly or daily schedule. AI filtering can make mistakes. Open the original item before acting on a material alert, and use repeated false positives as evidence that the monitor instruction or source list needs adjustment. If an expected alert is missing Confirm that the original source was public and reachable. Check that the event clearly matched the saved monitoring instruction. Review the monitor schedule and the enabled delivery destination. Contact support with the monitor name and original URL if the source should have matched.

Question 2

Where can I receive alerts?

Accepted Answer

SentryDock can deliver alerts to personal and team channels. Available destinations can include email, SMS, browser notifications, Slack, Microsoft Teams, Discord, Discourse and X. The options shown in Settings depend on your workspace, subscription and enabled integrations. Choose destinations based on urgency. Email or a team channel is usually suitable for normal monitoring, while SMS or browser notifications are better reserved for the small number of monitors that genuinely require immediate attention. Configure a destination Sign in and open the alert or integration settings for your workspace. Connect or verify the destination and grant only the permissions requested by that integration. Select the destination on the relevant monitor or workspace rule. Send a test notification when available, then confirm it arrived in the expected channel. Troubleshoot missing delivery First confirm that the monitor produced a result. Then check the destination is still connected, the recipient or channel has not changed, and email or browser notifications are not being blocked locally. For team integrations, an administrator may need to reconnect an expired app or choose a replacement channel. For email, check spam and allow-list SentryDock. Contact support with the monitor name, approximate alert time and destination, but do not send passwords or private access tokens. Use the fewest useful channels Sending every monitor to every destination creates alert fatigue. Route routine updates to a digest or shared channel, and reserve interruptive channels for narrow, high-priority monitors.

Alerts & delivery

Alerts & delivery guides

How does SentryDock decide what to alert me about?

Where can I receive alerts?