Telegram alertsAvailable
Telegram is the primary controlled alert-delivery channel when the workspace integration is configured.
Product
Alerts and reporting built around operational metadata, not noise.
PingNodes is designed to route meaningful operational messages and summaries without pretending every channel is active or every delivery path is guaranteed.
Alert delivery
Alert delivery depends on the configured integrations and workspace preferences. Public copy should explain those dependencies clearly.
Alert channels
Telegram and email remain the public delivery story today. Browser Web Push is intentionally labeled unavailable.
Email alertsAvailable
Email remains available for supported alert and summary delivery paths.
Notification preferencesAvailable
Workspace-level preferences help control which channels should receive specific categories of operational messages.
Browser Web PushUnavailable
Web Push remains unavailable while its delivery infrastructure is under maintenance and should not be presented as active.
Reports and evidence
Reporting stays tied to operational metadata. PingNodes should never imply unnecessary customer payload storage just to produce summaries.
Reporting surfaces
Evidence, daily digest, and weekly reporting help teams confirm what PingNodes observed and what still needs follow-up.
Monitoring evidenceAvailable
Evidence should reflect what PingNodes has actually observed rather than inventing proof before setup is complete.
Recent activityAvailable
Operational events help explain what PingNodes detected and when those signals appeared.
Daily digestAvailable
A daily operational summary helps reduce manual checking across monitored workspaces.
Weekly reportAvailable
Weekly reporting helps summarize broader operational patterns and follow-up needs.
Important boundaries
These points should stay visible anywhere PingNodes describes notifications publicly.
Web Push is unavailable
Browser Web Push remains unavailable while its delivery infrastructure is under maintenance.
Delivery depends on setup
PingNodes should not claim guaranteed delivery or real-time guarantees when a workspace integration is still missing or not configured.
Next step
Use setup help to connect the channels you actually want to rely on.
The public site should explain the alerting model clearly, then hand off to protected setup and preference flows when a real workspace is ready.