メインコンテンツに戻る

The Future of Service Is Human-Led, AI-Powered

How Zendesk is designing for the new work of every agent.


Ben Mitchell

Head of Product Design at Zendesk

更新日 2026年10月12日

Graphic with text Designing the future of service.

For years, we treated the ticket as the product of customer service. We optimized queues, celebrated faster handle times, and built better ways to move work from open to closed. But customers never came to a business to raise a ticket. And agents don’t come to work to close them. Getting people real outcomes has always been the job. The ticket was only ever the container. And as an industry, we got very good at designing containers.

And now with AI, we get to answer all new questions as designers, going well beyond tickets and queues. But most importantly, AI is forcing us to ask a fundamental question -  what is the job to be done for humans in service?

The job was never just answering tickets

Ask a great human agent what they're proud of and they rarely say "I closed 47 tickets." They say they untangled a mess or caught something the system missed. They may have been able to go above and beyond for a customer in a tough spot – making sure a birthday gift arrived on time, or providing critical information ahead of a major life event. A customer left less frustrated than when they arrived, and often trusted the company even more as a result.

That work was always judgment, empathy under constraint, and recovery when things went sideways. We designed interfaces for throughput because throughput was measurable. The rest lived in the gaps.

AI doesn't invent a new purpose for service. It shows us how much of the old interface was just scaffolding around the core job.

AI finally allows service to focus on real outcomes for customers at scale. This forms the core of a human-led, AI-powered operating model: AI handles volume, speed and deciphering intent, while humans handle judgment, exceptions, and trust.

When AI can draft, retrieve, summarize, and take bounded actions, humans stop being the default keyboard for every step. That sounds like replacement if you're counting keystrokes. It's orchestration if you're counting outcomes.

As AI takes more tasks, the human agent's role gets more important, not less. Someone still sets intent, decides what's allowed, catches drift, repairs trust, and owns the ending. The human agent becomes the orchestrator.

I view this as a shift from AI-assisted customer service to AI-powered, human-controlled service. In an assisted model, the human does the work while AI suggests replies. In a controlled model, AI handles much of the execution while the human directs the overall system.

The design problem has changed

For years, product design in service meant interfaces people operate. The next job is designing intelligent systems people direct: goals, boundaries, delegation, intervention points, and a clear story of what happened.

The phrase "human in the loop" doesn't go far enough. At Zendesk, we’re designing for human in command, where human agency is amplified by AI rather than replaced by confidence scores. Humans manage priorities, exceptions, and accountability, while AI manages retrieval, drafts, and routine execution. If your tool only supports reply suggestions, you don't have agentic service; you just have a smarter inbox.

Control must be designed into the interaction

This is where design plays a vital role. As the saying goes, "Autonomy is an output of a technical system. Trustworthiness is an output of a design process." Great agentic UX doesn't hide complexity behind a black box that purports to handle everything. Instead, it makes progress, uncertainty, and control clear through previewing intent, establishing boundary lines, and providing easy ways to intervene. If control isn't clear in the UI, true empowerment is missing. 

At Zendesk, we thought about this with the redesign of our ticket logs. As AI takes on more of the interaction with customers, we asked what those logs need to help a human understand: what the AI was trying to accomplish, what informed its actions, how the resolution is progressing, and where uncertainty remains.

That led us to think beyond a record of what happened. Observability and traceability provide the evidence, but the design challenge is to help people synthesize that evidence, assess the situation, and take action. Could someone recognize when an AI agent’s approach was no longer moving the resolution forward? Could they understand what remained unresolved and intervene with enough context to change its direction? Could patterns across interactions help them identify and address a problem proactively?

These questions shaped how we thought about the relationship between visibility and control. Making complexity visible is useful when it helps a person decide what to do next. For us, designing for trustworthiness means connecting a clear account of the AI’s activity to meaningful opportunities for human judgment and action.

Graphic with text  If your AI rollout creates  a second full-time job  called "monitor the bots,"  you didn't empower agents.  You promoted them into unpaid QA.

Empowerment is less drag — not more supervision

I see this trap too often – we remove one manual, time consuming task and introduce another: watching the swarm. 

Human control should expand capacity rather than serve as a superficial promise that a person is monitoring behind the scenes. Oversight shouldn’t feel like babysitting a factory floor. 

If your AI rollout creates a second full-time job called "monitor the bots," you didn't empower agents. You promoted them into unpaid QA.

Good oversight expands capacity: fewer mechanical steps, clearer moments for judgment, faster recovery when something's off. The best automation removes operational effort while expanding the humanity of the experience.

When AI gathers context and coordinates routine steps, agents can spend more time understanding what matters to the customer and shaping a response that reflects it. They can also turn what they learn into improvements that help future customers, growing the strategic impact of their roles. The opportunity is to give people more scope to exercise their expertise, take on meaningful challenges, and see the difference their contribution makes.

What we should measure instead

You get the behavior you score. Average Handling Time (AHT) and volume made sense when the unit was the ticket. If the unit is resolution under human command, measure closer to the craft: decision quality, complexity handled, clean recovery when AI stumbled, and whether customer and agent understood what happened and felt in control.

Those are harder to instrument. Good, soft metrics were always where real service lived; we just lacked the honesty to lead with them.

The shift, plainly

Not human versus AI. Human agency, amplified.

AI will keep taking tasks. That's the point. The design question is whether humans remain operators of shrinking tools, or directors of systems that finally match the job: get people to the resolution they came for, with dignity intact, and someone accountable when it matters.

That's human-led. That's AI-powered. And it's a product design problem before it's a model problem.

Ben Mitchell

Head of Product Design at Zendesk

Ben Mitchell is Zendesk's Head of Product Design. He helps customers navigate the rapid shift to AI by transforming complex systems into simple, high-impact tools. Prioritizing low-ego, cross-functional partnerships, Ben focuses on bringing his 2+ decades of experience to delivering intuitive, end-to-end customer experiences that drive real business value.