Zenduty alternative and Xurrent IMR alternative with Zenduty pricing compared

IncidentBot is a Zenduty alternative for engineering and IT teams that want on-call schedules, escalation, SMS and voice paging, Slack incident channels, a status page and postmortems on one published seat price from an independent vendor. Zenduty is now sold as Xurrent IMR. Its Growth plan stops at 50 users and lists status pages as an optional add-on at 10,000 USD a year, and its Starter plan stops at 5 users. In IncidentBot a public status page is part of every plan and no plan has a user cap. Plans start at 24 USD per user billed annually.

Run a sample incident

What changed when Zenduty became Xurrent IMR

Engineering lead and an IT manager reviewing a vendor contract next to a laptop

Xurrent, an IT service management vendor, announced that it had acquired Zenduty in February 2025. In November 2025 the product was renamed Xurrent IMR (Incident Management and Response), and the pricing page, mobile apps and emails now carry that name. The product still does what it did: alert routing, on-call schedules, escalation and incident response from Slack or Microsoft Teams, at one of the lowest seat prices in the category. Plenty of teams should stay.

The teams that start comparing usually have one of four reasons.

The vendor changed. A pager bought from a small independent company is now one module of an ITSM platform. Security and procurement often re-review the contract, and some teams would simply prefer a vendor whose only product is incident response.
The status page is a large add-on. On Growth, status pages are listed as an optional add-on at 10,000 USD a year. They are included only on Enterprise, which is priced by quote.
The plans have user caps. Starter covers up to 5 users on 1 team with up to 5 integrations. Growth covers up to 50 users and 5 teams. User 51 or team 6 means an Enterprise conversation.
Support hours. Starter comes with community support and Growth with business hours support. Round-the-clock priority support is an Enterprise feature, which matters for a tool whose whole job happens at 3 a.m.

Who switches, and who should stay

Teams that switch are usually 10 to 150 engineers who run incidents in Slack, page people at night and have to keep customers informed on a status page. Teams that should stay on Zenduty: teams of up to 50 that only need paging and escalation and already have a status page they like, teams that want single sign-on on the cheapest plan, and companies that run Xurrent for service management and want incidents in the same platform. On seat price alone Zenduty is cheaper than IncidentBot, and the tables below say so.

Zenduty vs IncidentBot at a glance

Zenduty details come from the public Xurrent IMR pricing page on zenduty.com, checked in October 2026. Confirm on their site before you sign, since packaging changes.

What you check	Zenduty (Xurrent IMR)	IncidentBot
Seat price	Starter 6 USD per user a month billed yearly, up to 5 users. Growth 16 USD billed yearly, up to 50 users. Enterprise by quote	Starter 24 USD per user annual, 49 monthly. Team 49 annual, 99 monthly. Business 99 annual, 199 monthly
User and team caps	Starter 5 users and 1 team. Growth 50 users and 5 teams. Enterprise unlimited	No user cap on any plan. Starter is limited to 3 schedules and 3 escalation policies; Team and above are unlimited
SMS and voice	Starter 100 per user a month in the US, Canada and India, 25 elsewhere. Growth and Enterprise unlimited	Starter 100 SMS and voice notifications per user a month. Team and Business unlimited (fair use)
Status pages	Not on Starter. Optional add-on at 10,000 USD a year on Growth. Included on Enterprise	1 public page on Starter, 3 public or private on Team, unlimited on Business
Integrations	Up to 5 per team on Starter, unlimited on Growth	Datadog, Prometheus Alertmanager, Grafana, CloudWatch, Sentry, email and webhook on every plan
Incident response in chat	Slack, Microsoft Teams and Google Chat on every plan	`/incident` in Slack on every plan with commander, comms and scribe roles from Team; Microsoft Teams on Business
Single sign-on	Listed on every plan	SSO and SAML on Business
Support	Community on Starter, business hours on Growth, 24x7 priority on Enterprise	Support by email at [email protected], priority support on Business
Vendor	Part of Xurrent, an IT service management platform	Independent, incident response is the only product
Trial	14 day trial on every plan, no credit card	No free plan; the incident simulator runs without an account

Where Zenduty wins: a much lower seat price, unlimited SMS and voice from 16 USD, single sign-on on every plan, Google Chat support and a 14 day trial. Where IncidentBot wins: a status page in the base price of every plan, no user caps that force a quote, private status pages on Team, and a vendor whose roadmap is only about paging and incidents.

Zenduty pricing compared for a 10 and a 40 responder team

List prices per month with annual billing. The scenario: every responder carries the pager and the company publishes one customer status page. Zenduty prices come from zenduty.com/pricing; the 10,000 USD yearly status page add-on is shown as 833 USD a month. Atlassian Statuspage Startup is 99 USD a month on atlassian.com.

Setup	10 responders, per month	40 responders, per month
Zenduty Growth, no status page	160 USD	640 USD
Zenduty Growth plus its status page add-on	993 USD	1,473 USD
Zenduty Growth plus Atlassian Statuspage Startup	259 USD	739 USD
Zenduty Enterprise (status pages included)	Custom quote	Custom quote
IncidentBot Starter (1 public page, 100 SMS and voice per user)	240 USD	960 USD
IncidentBot Team (3 public or private pages, unlimited SMS and voice)	490 USD	1,960 USD

Read it honestly. If you need paging and nothing else, Zenduty Growth is cheaper than every IncidentBot plan at any team size up to 50. If you need a status page from the same vendor, the Growth add-on makes Zenduty the more expensive option at both sizes, and IncidentBot Starter costs about a quarter of it at 10 responders. The middle road, Zenduty plus a separate status page tool, is close to IncidentBot Starter at 10 responders and cheaper at 40, at the price of two vendors, two logins during an outage and a status page that does not know about the incident. Above 50 responders there is no Zenduty list price to compare, only a quote.

IncidentBot pricing has a seat calculator if your team size is somewhere in between.

From an alert to a status update in one record

Your monitoring stays where it is. Only the place alerts are sent changes.

Datadog, Prometheus Alertmanager, Grafana, CloudWatch, Sentry and anything that can call a webhook or send an email open alerts on the matching service. Repeat alerts group into one on Team and above, so a flapping check does not page forty times. See incident alerting for the routing rules.
The alert pages the on-call engineer through an escalation policy by push, SMS, voice, email and Slack, and moves to the next tier if nobody acknowledges.
/incident opens a dedicated channel in Slack, sets severity SEV1 to SEV4, assigns commander, comms lead and scribe, and posts the runbook attached to the service. The Slack incident management app page shows the commands.
The comms lead drafts the customer update from the live incident and publishes it on the status page app. On Team and above, subscribers are notified. Nothing goes to customers on its own.
When the incident closes, the timeline becomes a blameless incident postmortem draft with the impact window, response times and action items synced to Jira or Linear.

Moving off Zenduty in five steps

On-call engineer checking a test page on a phone beside a laptop at night

A paging migration is a translation, not a rebuild. Most teams of 10 to 50 responders finish in two to three weeks, and nobody is unreachable in between because both tools page in parallel.

Inventory: list your Zenduty teams, services, schedules, escalation policies and integrations. Note overrides, hand-off times and which alert rules route to which service.
Rebuild rotations: recreate schedules with on call scheduling software, keep the names your responders know, and copy escalation policies tier by tier.
Re-point alerts: add the IncidentBot webhook or inbound email address in each monitoring tool next to the Zenduty one, one service at a time, so both receive the same alerts.
Parallel run: keep both paging for one to two weeks, and have every engineer install the mobile app and confirm a test page by push, SMS and voice.
Cut over: remove the Zenduty integrations from your monitoring tools, publish the status page (on your own domain from Team) and cancel before the yearly renewal date.

Other Zenduty alternatives and competitors

The usual Zenduty competitors are PagerDuty, Opsgenie (end of support April 5, 2027), Squadcast, incident.io, Rootly, Better Stack, AlertOps and Grafana Cloud IRM. PagerDuty is the paging-first incumbent; our PagerDuty alternative page covers that comparison. Squadcast is the closest on price and went through its own acquisition, see the Squadcast alternative. Budget-focused IT teams also look at AlertOps, covered on the AlertOps alternative page, and teams with dashboards in Grafana should read Grafana IRM pricing first. For a shortlist by team type see best incident management software.

What is the best alternative to Zenduty?

The best Zenduty alternative depends on what you need beyond paging. Teams that want the lowest seat price compare Squadcast and AlertOps. Enterprises with ServiceNow workflows compare PagerDuty. Engineering teams that run incidents in Slack and need a status page on a published price, with no user cap, pick IncidentBot.

Is Zenduty now Xurrent IMR?

Yes. Xurrent announced the acquisition of Zenduty in February 2025, and the product was renamed Xurrent IMR, short for Incident Management and Response, in November 2025. The Zenduty website, pricing page and mobile apps now use the name "Xurrent IMR (formerly Zenduty)".

How much does Zenduty cost?

Zenduty, now Xurrent IMR, costs 6 USD per user per month on Starter for up to 5 users and 16 USD per user per month on Growth for up to 50 users, both billed yearly. Enterprise is priced by quote. Status pages are a 10,000 USD per year add-on on Growth. Checked on zenduty.com in October 2026.

Does Zenduty include a status page?

Not on Starter or in the Growth price. The pricing page lists status pages as an optional add-on at 10,000 USD a year on Growth and as included on Enterprise. IncidentBot includes one public status page on Starter, three public or private pages on Team and unlimited pages on Business.

Is Zenduty cheaper than PagerDuty?

Yes, on list price. Zenduty Growth is 16 USD per user per month billed yearly with unlimited SMS and voice, and PagerDuty Professional is 21 USD and Business 41 USD billed annually. The gap closes if you buy Zenduty's status page add-on, and Zenduty Growth stops at 50 users. See PagerDuty pricing for the full plan list.

Can we try IncidentBot before we migrate?

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

Keep your alerts and move the pager

Create your account, point one integration at IncidentBot and run both tools side by side until every page lands.