Skip to content
IncidentBot

On-call app with push, SMS and voice paging for engineering teams

IncidentBot is an on-call app that tells each engineer when they are on call, wakes them with a push, an SMS or a voice call when a service breaks, and escalates to the next person if nobody acknowledges. It installs on the phone home screen with push notifications, and SMS and voice paging work without the app open. Plans start at 24 USD per user per month billed annually.

What the on-call engineer sees when a page arrives

TimeEventChannel
02:14:03Alert fires on checkout-api, severity SEV2Monitoring webhook
02:14:04Primary on-call, Payments, pagedPush
02:15:04No acknowledgement, personal rule firesSMS
02:17:04Still no acknowledgementVoice call
02:17:41Acknowledged by keypress, escalation stopsVoice
02:18:00Incident channel opens in Slack with the alert attachedSlack
The timeline is an example of a policy with a 1 minute and a 3 minute personal rule. Every step is recorded with a timestamp, which feeds time to acknowledge reporting on Team and above.

What an on-call app has to get right at 3 a.m.

Most on-call apps look alike on a feature list. They differ in what happens when the first notification is missed. A phone on silent, a dead battery or a notification setting that Android quietly changed after an update are the usual reasons an alert goes unseen, so the app has to keep trying through other channels.

  • Push to the phone, with acknowledge and escalate buttons in the notification.
  • SMS and voice call as the next steps, with acknowledgement by reply or keypress.
  • Personal notification rules per engineer, for example push at once, SMS after one minute, voice call after three.
  • An escalation policy behind it: if the primary does not acknowledge, the secondary is paged, then the team lead.
  • A clear view of who is on call now, next and after that, on the phone and in Slack.

How the mobile side works

Open IncidentBot in the phone browser and add it to the home screen. It then opens full screen like an app and receives push notifications. We do not ship a native iOS or Android app, and we say so plainly because it matters for one case: if your policy depends on a phone tree with live call routing, look at a tool built around that first. For everything else, paging by push, SMS and voice call covers a phone that is locked, on silent mode for apps, or out of data coverage while still reachable by cell signal.

  • Acknowledge, escalate, reassign or snooze from the notification or the alert page.
  • Override a shift or swap with a colleague from the phone.
  • See the schedule as a calendar and sync it to your own calendar.
  • SMS and voice paging do not need the app, so a new hire is reachable the minute they are added to a rota.

On-call schedules behind the app

The app is only as good as the rota behind it. Schedules support daily and weekly rotations, follow-the-sun handoffs between regions, overrides, holiday cover and layered primary and secondary shifts. See on-call scheduling software for the calendar side, and on-call management for tiers and timeouts.

  • Recurring rotations with a handoff summary to the incoming engineer.
  • Overrides and swaps that apply immediately, including from the phone.
  • Time zones per person, so the schedule reads correctly for a distributed team.

Who gets the most out of it

Teams of 5 to 50 engineers who need a reliable pager and also want the incident run in Slack, a status page and a postmortem draft in the same bill. Support, sales and leadership follow incidents as read-only viewers, which are included and not billed, so only the people who carry the pager take a seat.

A team of 10 engineers on Starter pays 240 USD a month on annual billing, and 490 USD on Team with unlimited schedules and no IncidentBot limit on SMS and voice paging through your own Twilio account. The full list is on the pricing page. If you are leaving Opsgenie before it shuts down on April 5, 2027, schedules and escalation policies import, see the Opsgenie shutdown plan.

On-call app options at a glance

NeedIncidentBotTypical native-app pager
Push notificationsYes, installed web appYes, native iOS and Android app
SMS and voice pagingYes, through your own Twilio account (100 per user a month on Starter, no limit on Team and above)Yes, often limited or sold as an add-on
Live call routingNoOffered on higher plans by some vendors
Slack incident channel with rolesYesOften a separate product
Status pageIncludedOften a separate product
Read-only viewersFreeUsually billed as users

For a side by side with named vendors see the best incident management software roundup and the PagerDuty alternative page.

Questions

What is the best on-call app for a small engineering team?

The best on-call app for a small team pages reliably through more than one channel, escalates on its own and does not charge for people who only watch. IncidentBot offers push, SMS and voice paging, escalation policies and free read-only viewers from 24 USD per user a month billed annually, with a status page included.

Does IncidentBot have a mobile app for iOS and Android?

IncidentBot installs on the phone home screen as a web app with push notifications. There is no native store app. SMS and voice call paging work without any app, so an engineer is reachable by phone even if the web app was never installed or notifications were turned off.

Will I still get paged if my phone is on silent?

A silent push can be missed, which is why a voice call is the third step in a typical rule. Set your personal notification rules to move from push to SMS to voice within a few minutes,.

Can I try the on-call app before buying?

Yes. The incident simulator runs a sample page end to end without an account, and you can create your account and import a schedule when you are ready.

Get your on-call rota onto a pager that does not give up

Try a sample page in the simulator, then create your account and add your first schedule.