Zendesk continues its relentless pace of innovation, dropping new features and enhancements on a near-daily basis. Keeping up is a challenge, but we’re here to cut through the noise. Here’s our expert analysis of the latest update from July 2026.
A Small Zendesk Asset Management Tweak with a Big Impact
What We Think:
Zendesk has rolled out a seemingly minor but operationally massive enhancement to its asset management capabilities within the Agent Workspace. Agents can now view and manage assets for any user or organisation directly from the ticket’s context panel, not just the ticket requester. This is a huge quality-of-life improvement that eliminates frustrating workarounds, especially for IT and internal support teams. Our verdict: This is a fantastic, common-sense update that directly addresses a major pain point and makes Zendesk’s ITSM offering significantly more fluid.
The Reality Check: What’s Really Changing?

Let’s talk about the old way of doing things, which was, frankly, a bit of a clunker. Imagine a manager submits a ticket to get a new laptop for a team member who is starting next week. Previously, the Zendesk asset management panel in that ticket would only show assets linked to the manager (the requester). To assign the new laptop to the new employee, the agent had to perform some awkward ticket gymnastics: either change the ticket requester to the new employee (which messes up the ticket’s history and communication thread) or navigate away from the ticket entirely to the main IT Assets page, breaking their workflow.
This was inefficient and disruptive. It added unnecessary clicks, created potential for errors, and made handling multi-user scenarios a real chore.
With this new enhancement, that entire convoluted process is gone. Now, within the IT asset side panel on a ticket, there’s a simple way to select a different user. The agent can keep the manager as the requester but simply choose the new employee from a list. The panel then displays that employee’s assets, and the agent can assign the new laptop directly to them, all without ever leaving the ticket interface. All assign and unassign actions within the panel now apply to the *selected* user, not necessarily the *requester*.
Our Expert Opinion: The True Operational Impact
While Zendesk frames this as a simple update for “flexibility,” we see it as a fundamental workflow improvement that unlocks new levels of efficiency. This isn’t just about saving a few clicks; it’s about reducing agent friction and cognitive load, which is critical for any high-performing support team. The need to “change the ticket’s requester in order to inspect assets” was a workaround, not a feature, and we’re thrilled to see it addressed.
Here are the scenarios where we believe this change will have the most significant impact:
- Employee Onboarding/Offboarding: This is the most obvious and powerful use case. An HR manager can raise a single ticket for a new hire, and the IT agent can use that same ticket to select the new hire and assign them a laptop, monitor, and phone. Similarly, for offboarding, a manager’s request can be used to view and unassign all of a departing employee’s hardware. This streamlines two of the most common IT processes.
- Manager-led Requests: Any time a manager or team lead requests something on behalf of their staff—be it a software licence, a hardware repair, or an accessory—the agent can now directly interact with the correct end-user’s asset list. No more “Can you ask Susan to raise a ticket for her broken mouse?”
- Multi-User Incidents: Consider a ticket about a faulty network switch affecting an entire team. An agent can now use that single ticket to cycle through each affected user, check the status of their connected devices, and log actions against each asset without needing a dozen separate tickets.
By keeping the agent within the ticket context, Zendesk is empowering them to resolve issues faster and with greater accuracy. This change strengthens the case for using Zendesk asset management as a core component of your internal IT support and moves it closer to a full-fledged ITSM solution.
How We’d Handle the Rollout
Zendesk has confirmed that this update is being rolled out automatically to all plans with IT asset management, so there’s nothing technical you need to do to enable it. However, “no action required” doesn’t mean “do nothing.” To get the most out of this change, we are advising our clients to focus on process and communication.
Here’s a simple, strategic checklist for a smooth internal rollout:
| Action Item | Our Rationale |
|---|---|
| 1. Announce the Change | Don’t let your agents discover this by accident. Send a clear, concise internal communication explaining the ‘before’ and ‘after’ and highlighting the benefits for their daily workflows. |
| 2. Update Internal Documentation | Your internal knowledge base or training guides likely detail the old, clumsy workarounds. Proactively find and update these documents to reflect the new, streamlined process. This prevents confusion and reinforces best practices. |
| 3. Host a Quick Demo Session | Schedule a brief, 15-minute optional training session. Share your screen and walk the team through a typical onboarding request using the new user selection feature. Seeing it in action is the fastest way to drive adoption. |
| 4. Review and Refine Workflows | Challenge your team to think about which existing processes can be improved. Could you consolidate multiple ticket types now? Can you create new macros or triggers based on these streamlined actions? Use this as a catalyst for optimisation. |
| 5. Gather Agent Feedback | After a week or two, check in with the team. Ask them how the new feature is working and if it has genuinely made their jobs easier. This feedback is invaluable for understanding the real-world impact. |
In summary, this is an excellent and much-needed enhancement to Zendesk’s asset management capabilities. By removing a long-standing point of friction, Zendesk has made the Agent Workspace a more powerful and intuitive environment for internal support teams, reinforcing its commitment to the ITSM space.



