Zenduty

Name: Zenduty
Brand: Zenduty
Rating: 4.6 (142 reviews)

Xurrent IMR (formerly Zenduty) is an incident management & response orchestration platform for production engg. teams.

Est 2016|Valuation $6.3M|Raised $2.2M|68 Ref Customers

LinkedIn 25K|Website|Web traffic 20K|FTEs 40|HQ Bengaluru, Karnataka, IN

MarketsIncident Management & On-Call

Published Oct 15, 2026

01Common complaints

- When escalation workflows are complex and require advanced routing, override paradigms, or non-standard escalation patterns - When a best-in-class, global scheduling user experience is required out of the box - When the procurement process requires publicly documented compliance certifications (ISO, HIPAA, etc.) and data residency guarantees without an NDA - When vendor naming/ownership stability is a major procurement concern; the product underwent an acquisition and rebranding that may affect approvals, renewal communications, and marketplace listings - Scheduling complexity: reviewers report that schedule configuration can be confusing for teams operating across multiple time zones - Feature gating: some functionality is available only in higher-priced plans, which can affect total cost of ownership - Escalation and override UX limitations: some reviewers report limited escalation patterns and a confusing override interface in specific environments - Brand transition risk: the rebrand and acquisition can introduce friction in procurement, app listings, bot names, and support materials - Reliability transparency: public status information may show short-term operational windows; buyers should request historical incident data and contractual SLAs for reliability commitments

Deal disqualifiers (likely)

Requirements for highly complex escalation logic beyond basic top-down patterns
Strong requirements for out-of-the-box, easy multi-time-zone scheduling UX
Need for publicly available compliance certifications (beyond SOC 2 Type II) and documented data residency options without executing an NDA

02Why they buy

- Lower published list pricing relative to some enterprise-focused competitors (public list tiers at $6 and $16 per user per month) - Vendor emphasizes integration workflows inside collaboration platforms such as Slack and Teams for incident coordination - Analytics and post-incident learning features that provide MTTA/MTTR reporting and incident trend dashboards - Note: several differentiators are vendor-framed claims; buyers should validate performance and outcomes in their environment via trial or proof of concept

03Field reports

Review-platform signals (G2)

- G2 shows review counts and demographic signals; public snippets indicate some regional skewing in review distribution. - Example positive review excerpt (G2) - A reviewer described analytics-driven insights and trend tracking as useful for identifying recurring failures and reducing incident recurrence. - Example negative review excerpt (G2) - Some reviewers report scheduling complexity and note that particular features are limited to higher-tier plans.

TrustRadius (limited but accessible)

TrustRadius includes both vendor-curated and incentivized quotes; some quotes describe end-to-end alert management and Slack integration, while others highlight limitations in escalation options and override interfaces.
Interpretation: incentivized or vendor-selected quotes should be weighted with caution and corroborated with organic community feedback and trial experience.

Community/Social (Reddit)

Community threads show mixed signals; some participants expressed skepticism about promotional posts and questioned the authenticity of online endorsements, while others cited positive integration experiences but slower support in some incidents.

Vendor-published testimonials and case content

Vendor pricing and marketing pages include customer quotes that describe outcomes such as improved uptime and reduced time-to-detect/resolve. These are vendor-selected testimonials and should be treated as marketing evidence unless independently validated.

Chalo case study (vendor-published PDF)

- Stated problems prior to adopting the vendor: reliance on Slack-only incident communication, fragmented alert sources, and difficulty identifying critical alerts amid noise. - Reported outcomes (vendor-published; methodology not disclosed): vendor claims include elimination of SLA breaches, substantial improvements in MTTA/MTTR, reduced alert noise, and high availability figures. - Critical evaluation: these metrics are presented in vendor marketing material without disclosed baselines, time periods, sample sizes, or independent validation. Some availability metrics may refer to the customer’s service rather than the vendor platform.

General note on case studies

The vendor publishes multiple case studies; some materials were not accessible at the time of research. Where case study PDFs were unavailable, conclusions are limited.

04Best fit

Company sizes

Likely best fit (based on positioning and review signals): small-to-mid-size engineering organizations — teams from small groups up through several hundred engineers/IT responders; organizations that need core incident tooling without a large enterprise automation suite.
The product can scale to larger organizations where incident process maturity exists, but buyers should validate escalation patterns, override workflows, and governance features.

Industries and verticals where adoption is strongest

Public review distribution indicates usage in software, IT services, and certain financial services.
Vendor case studies emphasize adoption among regional consumer and transport tech companies, though these are vendor-selected examples.

Roles and personas

Decision makers: Head of SRE, DevOps Manager, Platform Engineering lead, IT Operations leadership
End users: On-call engineers, SREs, NOC/support engineers

Pain points the product addresses

Noisy alert streams and slow response
Fragmented communications across collaboration platforms and ticketing systems
Lack of consistent on-call schedules and clear escalation paths
Need for post-incident analytics and MTTA/MTTR reporting

05The pitch

What the product does (core value proposition in objective terms)

- Zenduty (rebranding to Xurrent IMR after joining Xurrent) is a software-as-a-service incident management and response orchestration platform that provides: - Alert ingestion and routing to reduce noise and notify designated responders - On-call scheduling and rotations with escalation policies - Major incident coordination via ChatOps-style workflows in collaboration platforms such as Slack, Microsoft Teams, and Google Chat - Post-incident activities including analytics and postmortems - The vendor describes the product as an incident management and response orchestration system and offers features under the "ZenAI" brand that it states are intended to use machine learning techniques to assist with reducing mean time to acknowledge/repair and lowering operational effort.

Target market and market positioning

- Marketed as an alternative to PagerDuty; vendor frames the product as providing core incident response, on-call scheduling, and ChatOps integration without some of the larger enterprise add-on suites. - Apparent target segments (based on vendor messaging and review demographics): - Small and mid-market engineering/SRE/DevOps teams seeking on-call and alerting functionality without an extensive enterprise ecosystem - Larger enterprises that require incident workflows and integrations but may prioritize lower list pricing relative to some incumbent vendors - Notable nuance: the vendor announced it is joining Xurrent in 2025 and is rebranding to Xurrent IMR later that year. This change may cause procurement and brand-lookup confusion if buyers search by the legacy name.

Get a comprehensive analysis of Zenduty including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →