DevRev

What it is

DevRev is a support platform built on the premise that a B2B ticket is rarely finished inside the support tool. The bug the customer reported has to become an engineering work item, and the fix has to travel back to the customer who asked. DevRev keeps both sides on one object graph, so a ticket and the issue it spawned stay linked instead of being copied between a helpdesk and a tracker by a human.

The company sells this as Computer, the brand it converged its previously separate pieces under — AgentOS, the Support App, the Build App, the search and CX agents, and the PLuG SDK now sit behind one conversational interface. Underneath it is Memory, DevRev’s knowledge graph over your connected systems. Founded in October 2020 by Dheeraj Pandey and Manoj Agarwal, both from Nutanix, DevRev raised a $100.8M Series A led by Khosla Ventures at a $1.15B valuation in August 2024. That round is now two years old, which matters more than the headline: treat the unicorn label as history, not as evidence about current traction.

Why it shows up in Customer Success stacks

• The support-to-engineering handoff is the actual product. Most helpdesks treat “escalate to engineering” as an integration that fires a webhook at Linear or Jira and loses the thread. DevRev models the ticket and the work item as linked objects, so when engineering closes the issue, every customer attached to it is known and reachable. If your escalation path is a Slack message and a copy-pasted link, this is the gap being closed.
• Agent Studio makes the agents yours. Shipped March 2026, it lets teams build, deploy, and govern custom agents without writing code, alongside expanded Text2SQL analytical reasoning and human-in-the-loop execution steps. The distinction from a fixed deflection bot is that you define the agent’s tools and approval gates.
• Voice runs on the same memory as chat and email. DevRev added Voice AI to the Customer Agent on 23 July 2026 — SIP-based, inheriting field-level permissions, recording and transcribing every call, and handing off to a human with the context preserved. One organizational memory across channels is the part worth caring about; a voice bot with its own separate knowledge base recreates the problem it was bought to solve.
• It is real AI-native plumbing. A DevRev MCP server exposes search and get_object against the DevRev APIs to clients like Claude, plus documented REST APIs and AirSync for keeping connected data current.

Pricing

DevRev publishes three tiers and a real price for exactly one of them. Mini is free — conversational search across connected org data, basic task automation, one-click connectors (Slack, Notion, Jira Cloud, Google Drive/Calendar, Microsoft Teams/OneDrive/SharePoint), and Bronze support. Pro and Max are both contact-us. Pro adds the 100-plus connector marketplace, Text2SQL conversational analytics, Agent Studio, Silver support, and discounted credits via subscription. Max adds an embedded team from DevRev’s Applied AI department, SCIM provisioning, near-real-time AirSync, and Gold support.

The commercial mechanic is credits, not seats: DevRev bills on consumption and says every dollar spent converts to credits. Note what this means for a support buyer — the Support App and Observe App are add-ons available only on Pro and Max, so the tier that makes DevRev a helpdesk is the tier with no published price. Third-party listings quoting $9.99 or $19.99 per user per month do not match the vendor’s current page and should not be used as an anchor. Budget from your own volume: ticket count, agent actions, and voice minutes are what move the bill.

Best for

Support and CS leaders at B2B software companies — roughly 20 to 500 support and engineering staff — where a meaningful share of tickets end as engineering work, and where the current cost is the manual round trip between the helpdesk and the tracker. It fits best when you are consolidating rather than adding: DevRev replacing a helpdesk plus a separate escalation bridge is a coherent purchase; DevRev alongside a healthy Zendesk install is an expensive second brain.

Watch-outs

• The tier that matters has no public price, and credits make the bill hard to forecast. Consumption pricing on AI actions means a deflection win and a cost increase can arrive together, and the Support App sits behind a quote. The guard: before signing, make DevRev quote Pro or Max with the Support App as a separate line item against your actual last-quarter ticket volume, and require a written credit-burn estimate plus what happens at overage — then re-price at 2x volume to see the slope.
• Consolidation is the value and the risk. Putting support, engineering work items, and analytics on one graph is why the handoff works, and it is also why a migration touches three teams’ daily tools at once. The guard: run one product line or one support queue end-to-end through DevRev for a full release cycle, and confirm engineering actually works its items there — if engineers stay in their old tracker, the linked-object model is dead and you have bought a normal helpdesk.
• Vendor case-study numbers are not your baseline. DevRev’s own Bolt case study reports 60% of ticket volume deflected, 30% faster resolution, and 25% higher CSAT. Those are vendor-published figures from one customer with their data and their content quality. The guard: agree on a measured deflection floor against your own tickets during a paid pilot, defined as resolved-without-human rather than “contained,” and make renewal contingent on hitting it.
• Not the pick for consumer or ecommerce support. DevRev’s model assumes named accounts and tickets that can become engineering issues. High-volume B2C or DTC support has neither. The guard: if under a quarter of your tickets ever reach engineering, the handoff you are paying for is not the problem you have.

Alternatives, and when to pick them instead

Zendesk and Intercom are the two incumbents you are most likely displacing, and the rule for staying is straightforward: if your ticket volume is high, largely resolvable at tier one, and rarely engineering-bound, their AI agents cover the deflection case with published pricing you can model. Pick Zendesk when process maturity and the admin ecosystem matter more than the engineering link; pick Intercom when in-product messaging is the primary channel.

Pylon is the fastest-growing entrant in B2B support and the sharper choice when your customers live in shared Slack Connect channels — Pylon owns that surface, and DevRev does not. Pick Pylon when the problem is where support happens; pick DevRev when the problem is what happens after the ticket. If your need is search and answers across company systems without the ticketing layer at all, Glean does that job and DevRev’s Mini tier is the free way to test whether you needed a support platform in the first place.