Instant Alerts in Telegram, Slack & Email
Availability monitoring with second-level precision. Get notified the moment an incident occurs, configure custom escalation paths, and keep your on-call team aligned.
Supported Notification Channels
Pulsely routes incidents through four primary delivery paths. Each channel supports rich formatting, priority tagging, and automatic retry logic for failed deliveries.
Telegram Bot
Connect via BotFather token or webhook URL. Supports inline reply buttons for acknowledge/resolve, MarkdownV2 formatting, and channel/topic routing. Average delivery latency: 180ms.
Slack Webhooks & App
Post to dedicated alert channels or direct messages. Includes interactive blocks for status updates, fallback to email on webhook timeout, and automatic thread management for recurring incidents.
Email & SMS
SMTP and SendGrid integration for structured HTML/plain-text alerts. SMS fallback via Twilio for critical severities. Includes DKIM verification and bounce handling with automatic recipient rotation.
Custom Alert Templates
Replace generic pings with actionable, context-rich messages. Pulsely uses Handlebars-style templating to inject runtime metrics, endpoint details, and runbook links directly into notifications.
Critical Outage
[CRITICAL] api.pulsely.io (52.14.88.21) is down. Status: 502 Bad Gateway. Last success: 14:02:11 UTC. Runbook: https://wiki.internal/runbooks/api-502. Acknowledge: /ack 8f3a1c
Degraded Performance
[WARNING] cdn-assets.pulsely.io latency spike. P95: 1,240ms (threshold: 800ms). Region: eu-west-1. Affected endpoints: /static, /img. Dashboard: https://app.pulsely.io/d/4x9k2
Service Restored
[RESOLVED] db-primary.pulsely.io is back online. Downtime: 4m 12s. Root cause: connection pool exhaustion. Auto-remediation triggered at 14:06:44 UTC. Ticket: INC-2024-0891
Smart Escalation Policies
Don’t let silent incidents drain your SLOs. Pulsely automatically routes unacknowledged alerts through predefined escalation ladders, adjusting frequency and channel based on severity and response time.
Initial Notification
Sent immediately to primary on-call via Telegram. Includes incident ID, affected service, and direct acknowledge link. Retries every 30 seconds for 3 attempts if delivery fails.
Tier 2 Escalation
Triggers after 5 minutes of no acknowledgment. Routes to Slack #incidents channel and emails the engineering manager. Message frequency increases to every 2 minutes until resolved.
Executive Alert
Activates after 15 minutes for P1 outages. Sends SMS to VP of Engineering and posts to #exec-updates. Includes MTTR projection, customer impact estimate, and automatic status page sync.