Skip to content
IncidentBot

ServiceNow on-call scheduling alternative with paging, escalation and a status page

ServiceNow On-Call Scheduling works well when every person on the rota already holds an ITSM fulfiller license and an admin has set up Notify with a Twilio account for SMS and voice. When engineers who live in Datadog, Grafana and Slack have to be added to ServiceNow just to carry the pager, the cost and the setup grow fast. IncidentBot is a separate on-call tool for those engineers: schedules, escalation, push, SMS and voice paging and a status page from 24 USD per user a month billed annually, while tickets stay in ServiceNow.

When to keep ServiceNow on-call and when to move the pager out

IT and engineering leads reviewing an on-call rota on a shared screen

Keep the rota inside ServiceNow if your service desk and infrastructure teams already work every incident there, all responders already have the itil role and SMS through Notify is in place. Moving the rota then buys you little.

Move the pager out when one or more of these is true:

  • Software engineers carry the pager but never work tickets, and each would need a fulfiller license only to appear on a schedule.
  • SMS and voice escalation are not set up because nobody owns the Notify and Twilio configuration.
  • Alerts come from Datadog, Prometheus, Grafana, CloudWatch or Sentry and reach ServiceNow late, after an event rule turns them into a record.
  • The incident is actually worked in Slack, and the ServiceNow record is filled in afterwards.
  • Customers need a public status page, which On-Call Scheduling does not provide.

What ServiceNow on-call scheduling needs before it pages anyone

On-Call Scheduling is an IT Service Management application, activated with the On-Call Scheduling plugin (com.snc.on_call_rotation). ServiceNow community answers list an ITSM Standard or higher subscription as the prerequisite, and rota managers work with the itil role, which in most contracts means a fulfiller license. ServiceNow does not publish per-fulfiller prices, so the cost comes from your account team.

Email notifications work out of the box. SMS and voice escalation are a separate piece: ServiceNow documents that the Notify integration with On-Call Scheduling needs a Twilio account and a Twilio number configured in the instance, and an escalation workflow such as assign by acknowledgement. Twilio usage is billed by Twilio. None of this is hard for an experienced ServiceNow admin, but it is a project, and engineering teams often wait months for it.

What you needServiceNow On-Call SchedulingIncidentBot
License for each person on the rotaITSM fulfiller license (itil role), price by quoteResponder seat, 24 USD a month on Starter billed annually
People who only watchRequester users cannot see schedules without a rota role, per community reportsStakeholder viewers included and never billed
SMS and voice pagingNotify plus your own Twilio account and numberYour own Twilio account, connected under Integrations: 100 per user a month on Starter, no limit on Team and above
Mobile pushServiceNow mobile appInstalled web app with push
EscalationEscalation policies per group, voice workflowsEscalation policies per service with personal notification rules
Alert sourcesEvent Management or integrations into an incident recordDatadog, Prometheus Alertmanager, Grafana, CloudWatch, Sentry, email, webhook
Incident run in SlackThrough separate integrations/incident opens a channel, pages the on-call and keeps the timeline
Public status pageNot part of On-Call Scheduling1 public page on Starter, 3 on Team
Setup time for a 10 person teamWeeks, depends on your admin queueAn afternoon to import and a week of parallel paging

What a 10, 20 and 40 engineer rota costs outside ServiceNow

List prices per month, annual billing, every engineer on the rota holds a seat. ServiceNow lines are by quote because ServiceNow does not publish fulfiller pricing; if your engineers already hold fulfiller licenses, the extra cost of the rota itself is close to zero, apart from Twilio usage.

Setup10 engineers20 engineers40 engineers
ServiceNow fulfiller licenses for engineers who do not have oneQuoteQuoteQuote
PagerDuty Professional (21 USD per user)210 USD420 USD840 USD
IncidentBot Starter (24 USD per user, 1 public status page)240 USD480 USD960 USD
IncidentBot Team (49 USD per user, 3 status pages, SMS and voice through your own Twilio account)490 USD980 USD1,960 USD

The comparison that matters is your own quote. Ask your ServiceNow account manager what 10 more fulfiller licenses cost on your current contract, then put that number next to the IncidentBot line. For many teams a fulfiller license costs several times a pager seat, and the engineers would use about one percent of what it unlocks. The full PagerDuty math, including the platform plans, is in PagerDuty vs ServiceNow pricing, and our plans are on the pricing page with a seat calculator.

Keep tickets in ServiceNow and page from IncidentBot

You do not have to choose one system for everything. Most teams who move the pager out keep ServiceNow as the record of work and let IncidentBot wake people up.

We do not offer a two-way ServiceNow sync. If your process needs fields kept in sync both ways, PagerDuty or xMatters with their ServiceNow integrations fit better, and our PagerDuty vs xMatters page compares the two.

  • Monitoring sends alerts straight to IncidentBot, so the page does not wait for an event rule or an incident record.
  • The escalation policy of the service decides who is paged and how: push first, SMS after a minute, a voice call after three.
  • The on-call engineer acknowledges from the phone, and /incident in Slack opens a channel with the alert context.
  • A ServiceNow email notification or outbound REST message can also raise an alert in IncidentBot, through the email address of a policy or the webhook, when a P1 ticket must page an engineer.
  • After resolution the timeline and a postmortem draft are ready; the service desk copies the summary into the ServiceNow record.

Teams that move their on-call rota out of ServiceNow

Engineers who want the rota on their phone first can see how the on-call app with push, SMS and voice behaves at 2 a.m., and the on-call scheduling page covers rotations, overrides and swaps.

  • Platform and SRE teams of 5 to 50 engineers inside a company that runs ServiceNow for IT.
  • SaaS companies whose IT team bought ServiceNow, while product engineering needs a pager and a customer status page.
  • Teams leaving Opsgenie before Atlassian ends support on April 5, 2027, who were told to use ServiceNow and found the licensing cost. The Opsgenie shutdown plan lists the dates.
  • MSPs and IT departments with a few engineers on the rota and dozens of people who only need to see who is on call.

Moving the rota without a gap in paging

A team of 10 to 30 engineers usually needs two to three weeks of calendar time. The how it works page shows the setup.

  • Export: the rota members, shifts and escalation policies from the ServiceNow on-call calendar for each group.
  • Import: build the same rotations in IncidentBot or import them, then compare who is on call for the next four weeks side by side.
  • Route alerts: point each monitoring source at IncidentBot next to the current path, one service at a time.
  • Parallel run: one to two weeks where both systems notify, and each engineer confirms a test page by push, SMS and voice.
  • Switch off: disable the ServiceNow rota for that group once the parallel run matches. Tickets keep working as before.

FAQ

Does ServiceNow have on-call scheduling?

Yes. On-Call Scheduling is a ServiceNow IT Service Management application, activated with the com.snc.on_call_rotation plugin. It manages rotas, shifts, coverage and escalation for assignment groups, and it can page by email, or by SMS and voice when Notify is configured with a Twilio account.

Is ServiceNow on-call scheduling included in ITSM?

ServiceNow community answers say On-Call Scheduling comes with ITSM, with ITSM Standard or higher as the prerequisite. The people on a rota work with the itil role, which normally needs a fulfiller license. Exact entitlements depend on your contract, so confirm them with your ServiceNow account team.

What is the best alternative to ServiceNow on-call scheduling?

For teams with deep ServiceNow workflows, PagerDuty and xMatters, because they sync with ServiceNow records. For engineering teams that run incidents in Slack and need a status page on a published price, IncidentBot, from 24 USD per user a month billed annually, with SMS and voice through your own Twilio account.

Can IncidentBot create incidents from ServiceNow tickets?

Yes, one way. A ServiceNow email notification or outbound REST message can send a P1 ticket to IncidentBot, which pages the on-call through the escalation policy. We do not sync fields back into ServiceNow, so the service desk updates the record from the IncidentBot timeline.

Do people who only need to see the schedule need a paid seat?

No. In IncidentBot stakeholder viewers are included in every plan and never billed, so managers, support and account teams can see who is on call and follow incidents. Only responders who carry the pager hold a seat.

Can we try it before moving the rota?

Yes. The incident simulator runs a sample incident in your browser, with an alert, escalation through a policy you build, a Slack channel, a status page draft and a postmortem skeleton. No account is needed: run the demo yourself.

Give your engineers a pager without a ServiceNow fulfiller license

Create your account, import the rota and page in parallel with ServiceNow until every test lands.

Run a sample incident