Skip to main content

Zendesk's Specialist Bet Is the Right One; and Here's What Would Make It a Moat

If you only read the press releases, Zendesk Relate 2026 told a strong, clean story. The era of the chatbot is over. Welcome the Autonomous Service Workforce. Resolution replaces deflection. Outcome-based pricing is the new norm. Specialization beats generalist orchestration.

That’s strong. Really strong.

If you also watched the customer panel, listened to the day-two keynote, and had the chance of having analyst one-on-ones, you got a richer story. One in which the strategic bets are well-placed, the customers describe a more nuanced reality than the slogans, and three specific refinements over the next twelve months that would turn a strong position into a durable moat.

I came home quite positive. Here is why, and where I think the next twelve months are important.

What Zendesk announced and why it lands

The headline product story was the Autonomous Service Workforce: a network of specialized AI agents working alongside humans, orchestrated through what Zendesk now calls the Resolution Platform and improved continuously by the Resolution Learning Loop. Agent Builder gives customers a no-code interface to build bespoke agents. The Copilot suite expanded to four personas: Agent, Admin, Knowledge, Analyst. Voice AI handles 60+ languages mid-conversation. Employee Service AI agents from the Unleash acquisition live inside Slack and Teams. Knowledge Graph spans SharePoint, Google Drive, Notion, Guru, Contentful and Document360. Model Context Protocol support is bidirectional. Quality Score evaluates every interaction.

This is quite a handful.

Two of these messages are more powerful than the others. The first is resolution over deflection. Zendesk charges only when a resolution is verified by a second AI evaluation model; outcome-based pricing as the natural commercial expression of the philosophy, and a model Forrester has been telling vendors to move toward for the past year. The second is specialization over generalization. The argument is that 19 years of CX data, billions of  service interactions, and an opinionated service stack beat horizontal platforms using commoditized LLMs.

It is a strong argument. It is also working. Zendesk reported 130% year-over-year AI ARR growth, 20,000 active AI customers out of an 80,000 base, and more than 1,500 competitor replacements in 2025. Salesforce's own May 2026 State of Service survey shows agentic AI adoption in service jumping from 39% to 66% in twelve months. This is independent confirmation that the market is genuinely re-platforming, not just re-branding, and that Zendesk's growth sits inside a rising tide.

What customers told us and what it confirms

The customer panel completed the story. Stacy Niven of Direct Supply, Dena Fuentes of Emburse, Sam Bellach of Lyra Health, Jessica Hsieh of Levi's, Elymae Cedeño of Bumble, and Rob Giglio of Canva each added a dimension the headlines could not.

First, data foundation is more important than vendors usually admit. Stacy described Direct Supply's multi-year rebuild. Half of orders have been manually touched, processes worked in spreadsheets, an internally developed chatbot they walked back on because the product data was bad. Sam Bellach put it plainly: AI is only as good as the data feeding it. Salesforce's research confirms this: 59 to 72% of service professionals name data readiness as the top AI blocker. The Zendesk message would land even more cleanly if it acknowledged this work upfront. The customer panel, by being candid about it, did the job the brand did not need to.

Second, customers want more human connection in the AI era, not less. Jessica Hsieh cited research that 61% of CX leaders see live volumes rising. Elymae Cedeño at Bumble was emphatic that in a trust-and-safety product, humans are foundational. Levi's deploys AI for "where's my stuff" so human agents can be reserved for judgement and empathy. This is a tailwind for Zendesk's design philosophy — human-as-architect, AI-as-tool — and it argues for sharpening the messaging around that strength, not against the strategy itself.

Third, the outcome-pricing model has earned its lead, and the field will likely catch up over the next year. Sam Bellach, who is on Zendesk's Customer Advisory Board,  pushed back on the rigidity in what she describes as a candid debate. This debate is about the chicken-and-egg problem of spending ahead of proven RoI, the lack of mid-contract convertibility between agent-seat and resolution spend, and the ambiguity in what counts as resolved.

Forrester's Q2 2026 Conversational AI Wave found only one vendor scored above 3 of 5 on pricing flexibility. The fact that Sam is comfortable having that debate in public is a signal in itself. Zendesk leads the category and is co-designing the next version with its best customers.

Fourth, the most interesting moment of the week. Rob Giglio's part of the day-two keynote was structured around his recent frustration with someone else's deflection bot; he half-named "a name that sounds a lot like Zierra”. His thesis is that deflection causes churn, while resolution drives loyalty. Salesforce's State of Service report approvingly features Smarsh's 68% call deflection as "a phenomenal win". Zendesk is apparently on the right side of a still-unsettled industry debate, and Giglio's anecdote made the case more vividly than any product slide could.

The orchestration position is right. It just needs one more slide

Zendesk's Chief Product Officer Shashi Upadhyay was deliberately precise when I asked about orchestration. Zendesk wants to orchestrate every service interaction, they close the learning loop on every service interaction, and they do not pretend to orchestrate sales or marketing or the rest of the company. That is the honest answer. Salesforce, ServiceNow, SAP, Microsoft and Adobe are all pitching cross-system orchestration, with Google Cloud now positioning on top of them. Zendesk wisely declines that fight, interestingly using the same argument that SAP does against ServiceNow: You cannot govern what you cannot understand.

This strategic position is correct. What the messaging needs is one additional slide saying *we orchestrate service interactions; we hand off to your meta-orchestrator at these named integration points*. This single piece of clarity would turn a defensible boundary into an attractive value proposition. CIO buyers who currently hear "platform" and wonder whether to default to the suite would have a clear reason to choose the specialist for service while keeping their meta-orchestrator for everything else. The position is built. The slide is the missing piece.

The autonomy framing has room to grow into the brand

Salesforce measures 40% autonomous resolution today. Gartner optimistically projected 80% by 2029. The trajectory points exactly where Zendesk has bet. Independent analysis suggests today's genuine autonomy figure across the industry is closer to 20-30%, because much of what is marketed as agentic is nothing more than rebranded chatbot functionality. Zendesk's actual product reality of supervised agentic, with humans correcting, retraining and approving, is materially better than that field average, and is also the design that operationally safe service AI requires today.

This is a real strength, and it deserves equally real framing. "Supervised agentic resolution" or "agentic service workforce" would probably describe the product more accurately and would shift the conversation away from the autonomy bar to the supervised-agentic bar, which is a bar Zendesk easily clears. It is one of those cases where I think that a slightly more conservative brand line might be both more credible and more competitive.

The learning loop is the next big story

In the analyst one-on-ones I asked how Zendesk ensures the Resolution Learning Loop is learning in the right direction. If the system optimizes for what counts as a verified resolution under the current rubric, what stops it drifting toward easy-to-verify outcomes at the expense of harder ones? What stops the rubric from being gamed?

The answer covered the basics: multi-LLM grading, customer dispute mechanism, "a little conservative" on what counts as resolved. That is a solid, customer friendly foundation. What would turn it into a competitive advantage is a public, documented governance posture covering drift detection methodology, rubric versioning, human review cadence, adversarial test cases, audit visibility. Once that exists, the Resolution Learning Loop stops being a feature and becomes a moat that nobody else in the field is anywhere near ready to match. This is the most under-told story in Zendesk's deck.

My point of view

Three bets are working, three twelve-month refinements are available. The refinements: one more orchestration-boundary slide, a slightly more accurate autonomy line, and a public learning-loop governance posture, are all communication and documentation projects, not architecture ones. The strengths are outcome pricing years ahead of the field, a real data moat, an integrated platform, and partner ecosystem leverage, are durable, defensible, and can get stronger.

For buyers, the practical lessons are important, regardless of which vendor wins your shortlist.

Fix your data foundation before going agentic! Every successful customer at Relate 2026 did this first.

Demand outcome-priced contracts and negotiate flexibility into them. Design for supervised agentic, not autonomous. Stress-test demos on the hard cases.

Treat change management as a primary project. The 5-10% edge cases determine real-world performance. And the customers who built for those cases are the ones now reporting the strongest results.

Zendesk has built something real. The next twelve months are about telling that story as clearly as the customers are already telling it.

Kudos to Zendesk! 

Comments

Last Year's Top 5 Popular Posts

You are only as good as your customer remembers

As you know, I am very interested in how organizations are using business applications, which problems they do address, and how they review their success. In a next instance of these customer interviews, I had the opportunity to talk with Melissa Gordon , Executive Vice President, Enterprise Solutions at Tidal Basin about their journey with Zoho. You can watch the full interview on YouTube. Tidal Basin is a government contractor that provides various services throughout the government space, including disaster response, technology and financial services, and contact centers. Tidal Basin started with Zoho CRM and was searching for a project management tool in 2019. This was prompted by mainly two drivers. First, employees were asking for tools to help them running their projects. Second, with a focus on organizational growth and bigger projects that involved more people, Tidal Basin wanted to reduce its risk exposure and increase the efficiency of project delivery. This way, the compa...

SAP Draws a Perimeter around Agentic AI and What That Means for the Rest of US

The most consequential enterprise AI governance document published this year arrived in late April with surprisingly little fanfare. SAP's updated API Policy, version 4/2026 , is a short document in plain English. The clause that is most interesting is Section 2.2.2. It restricts how autonomous and generative AI systems are permitted to interact with SAP APIs. Read literally, it has the potential to change the architecture of agentic AI projects across every SAP customer landscape. Read carefully, it is also more interesting than the lock-in headlines suggest. The policy targets a specific category of AI behavior, not AI as such. It connects to commercial mechanics that go well beyond API stability. And the literal text, in its current form, will probably not survive the next two policy revisions intact. There is a lot to unpack. I will walk through what the policy actually says, how the SAP-watching community is reading it, what the rest of the major enterprise vendors are doin...

The Illusion of Value: Why Salesforce’s Agentic Work Unit is the New "Bad Query" of the AI Era

The News On February. 25, 2026, Salesforce announced a pricing and metrics update . During the company’s Q4 FY2026 earnings call, CEO Marc Benio ff, together with CMO Patrick Stokes , unveiled the Agentic Work Unit (AWU). Positioned as a metric to quantify the labor performed by autonomous digital systems, Salesforce defines an AWU as one discrete task accomplished by an AI agent. According to Salesforce, this discrete task represents the exact moment " raw intelligence is converted into real work ". It is not a fixed unit but measured as a processed prompt, a completed reasoning chain, or an invoked tool. Salesforce explicitly designed the AWU to move the industry conversation away from the raw consumption of Large Language Model (LLM) tokens. As Benioff noted, tokens only measure "how much an AI talks," whereas the AWU is intended to measure actual business execution. The scale of this rollout is massive. Salesforce reported that its platform has already processe...

Data Wars: SAP Vs. Salesforce In The AI-Driven Enterprise Future

The past weeks certainly brought a lot of news, with SAP Sapphire and Salesforce's surely strategically timed announcement of acquiring Informatica , ranging at the top. I have covered both in recent articles. The enterprise software landscape is crackling with energy, and Artificial Intelligence (AI) is certainly the star of the show. It isn't anymore about AI as a mere feature; it's about AI as the strategic core of enterprise software. Two recent announcements underscored this shift: SAP's ambitious AI-centric vision that was unveiled at its Sapphire 2025 conference, and, arriving hot on its heels, Salesforce's agreement to acquire data management titan Informatica for $8 billion. Both signal an intensified battle for AI supremacy, where trusted, enterprise-wide data is the undisputed new monarch. Of course, SAP and Salesforce are not the only ones duking this one out. SAP's Sapphire Vision: An AI-Powered, Integrated Enterprise At its Sapphire 2025 event in ...

CPQ, Meet Price Optimization: Your Revenue Lifecycle Just Got Serious

The news On October 1, 2025, Conga announced its intent to acquire the B2B business of PROS , following PRO’s acquisition by Thomas Bravo . At the same time, ThomaBravo and PROS announced that PRO’s travel business segment will be run as a standalone business . The bigger picture Revenue operations, revenue management and revenue lifecycle management have become a thing in the past years, as evidenced by the number of specialized companies that solve parts of the overall problem of optimizing revenue. It also got abused to some extent (e.g., surge pricing models) when the users of the corresponding capabilities consider optimizing being the same as maximizing. Reality check: It is not. While optimizing involves a bit of identifying how much a customer is willing to pay, it also involves the thought of repeat business, or in other words customer loyalty, even without a formal loyalty program. And that involves the customer experience, part of which the speed of creating a quote with mat...