On-Call & Alerting

Never miss a critical alert again

Smart escalation policies, on-call rotation management, and multi-channel alerting. Reduce your mean time to response and keep your incident response platform running like clockwork.

Escalation Policy: Production Critical
1
Notify on-call engineerACTIVE

Current on-call from "Platform Team" schedule

SMS
Push
Wait 5 minutes
2
Phone call to on-call

Same on-call engineer with voice alert

Phone
Wait 10 minutes
3
Escalate to team lead

Notify engineering manager + team Slack

Phone
Slack
Email
FIRING
INC-2847
CRITICALTriggered 4m ago

API Gateway - HTTP 503

api.example.com returning 503 from US East, EU West regions

ServiceAPI Gateway
Monitorapi-health-check
EscalationStep 1 of 3
Assigned
SK
Sarah K.
Acknowledge
Resolve
Escalation Policies

Route alerts to the right person, every time

Build multi-step escalation policies that ensure no critical alert goes unacknowledged. Define who gets notified first, how long to wait, and who to escalate to if the incident remains unresolved. Your on-call management software should work as hard as your team does.

  • Multi-step escalation with configurable wait times between each level
  • Automatic escalation when alerts are not acknowledged within your SLA
  • Per-severity escalation policies for critical, warning, and info alerts
  • Time-based routing: different policies for business hours vs. off-hours
  • Unlimited escalation steps with any combination of notification channels
Edit Escalation Policy

Policy Name

Production - P1 Critical
Step 1Immediately
SMS + Push
OC
On-call engineer
Step 2After 5 min
Phone Call
OC
On-call engineer
Step 3After 15 min
Phone + Slack
TL
Team Lead
Add Escalation Step
Save Policy
On-Call Schedule - Platform Team
March 2026
Mon
Tue
Wed
Thu
Fri
Sat
Sun
23
Sarah K.
24
Sarah K.
25
Sarah K.
26
Sarah K.
27
Sarah K.
28
Sarah K.
1
Sarah K.
2
Sarah K.
3
Sarah K.
4
Sarah K.
5
Sarah K.
6
Sarah K.
7
Sarah K.
8
Mike R.
9
Mike R.
10
Mike R.
11
Mike R.
12
Mike R.
Alex P.
13
Mike R.
14
Mike R.
15
Alex P.
16
Alex P.
17
Alex P.
18
Alex P.
19
Alex P.
20
Alex P.
21
Alex P.
22
Sarah K.
23
Sarah K.
24
Sarah K.
25
Sarah K.
26
Sarah K.
27
Sarah K.
28
Sarah K.
29
Mike R.
Sarah K.
Mike R.
Alex P.
Override
On-Call Schedules

On-call rotations that respect your team

Create fair, predictable on-call rotation schedules that distribute the load evenly across your team. Support for weekly, daily, and custom rotation patterns with override shifts for vacations and holidays. Your on-call management software should make scheduling effortless, not stressful.

  • Weekly, bi-weekly, and custom rotation intervals
  • Override shifts for vacations, holidays, and planned absences
  • Automatic handoff notifications when rotations change
  • Google Calendar and Outlook calendar integration
  • Fair rotation algorithms that balance on-call load across the team
Multi-Channel

Reach your team on every channel that matters

Different situations call for different alert management approaches. A warning might go to Slack, but a critical production outage needs an SMS and a phone call. Configure notification preferences per team member, per severity level, and per time of day. Our incident response platform delivers alerts with 99.99% reliability.

Email

Rich HTML alerts with full context

SMS

Reply ACK/RES to manage incidents

Phone Call

Automated voice alerts for critical issues

Slack & MS Teams

Interactive messages with action buttons

Push Notifications

Mobile app alerts for iOS and Android

Email Notification
From: alerts@mihari.ioJust now

[CRITICAL] api.example.com is DOWN

HTTP 503 detected from US East, EU West at 14:32 UTC. Escalation policy "Production Critical" activated.

SMS Alert

[Mihari] CRITICAL: api.example.com DOWN. HTTP 503 from 2 regions. Reply ACK to acknowledge. Reply RES to resolve.

Slack Message
M
MihariAPP2:32 PM

Critical Alert - api.example.com

Service is returning HTTP 503 from multiple regions

Acknowledge
View Incident
Phone Call Alert

Calling Sarah K. (+1 ***-***-4829)

Automated voice alert with incident details

Incident Management

Track every incident from detection to resolution

A complete incident response platform with timelines, team collaboration, acknowledgments, and structured postmortems. Reduce your MTTR and learn from every outage.

Incident INC-2847RESOLVED
Duration: 23m 14s
Created14:32
Acknowledged14:34
Investigating14:36
Resolved14:55

Activity Timeline

M
Mihari14:32 UTC

Incident created - api.example.com returning HTTP 503 from US East, EU West

M
Mihari14:32 UTC

Escalation policy "Production Critical" triggered. SMS sent to Sarah K.

SK
Sarah K.14:34 UTC

Acknowledged the incident

SK
Sarah K.14:36 UTC

Changed status to Investigating

Looks like a deployment issue. The latest release is returning 503 on the /health endpoint. Rolling back now.

SK
Sarah K.14:55 UTC

Resolved the incident

Rollback completed. All regions reporting HTTP 200. Root cause: missing env variable in v2.4.1 deployment.

Connects with your existing tools

Integrate Mihari with the communication and incident management tools your team already uses. Send alerts wherever your team works.

Slack

Interactive alerts

MS Teams

Channel notifications

PagerDuty

Bi-directional sync

OpsGenie

Alert forwarding

Email

Rich HTML alerts

SMS

Global delivery

Webhooks

Custom payloads

Phone

Voice alerts

Faster incident response, better outcomes

Teams using Mihari's on-call management software resolve incidents faster and maintain better uptime for their customers.

60%

Faster MTTR on average

24/7

On-call coverage

99.99%

Alert delivery rate

5

Notification channels

Streamline your incident response today

Set up escalation policies, on-call rotations, and multi-channel alerting in minutes. Free for small teams.