Feature Release Summary: Enhanced Solved Ticket Reassignment
Zendesk is excited to announce the release of an enhanced Solved Ticket Reassignment feature, designed to give our customers more control over their ticket management workflows. This feature addresses a long-standing challenge related to the handling of solved tickets when the assigned agent is removed from a group or downgraded to an end-user status.
Previous Challenge
Traditionally, when an agent solved a ticket and was later removed from the group, the ticket was reassigned to the admin performing the removal (provided they were in the same group) or, if not, to the oldest agent in that group. Feedback from our customers indicated that this approach could lead to confusion and did not meet all administrative needs.
New Reassignment Options
With the development of per-group settings, administrators now have the flexibility to choose what happens to an agent's solved tickets when they are removed from a group. The update introduces four configurable options within group settings:
- Assign to a Random Member: The ticket is reassigned to a random agent within the group, distributing the attribution in an equitable manner.
- Assign to a Particular Member: Target a specific agent to receive the solved ticket, allowing for strategic allocation based on expertise or availability.
- Assign to the Group: The agent is removed, and no particular member is assigned, leaving the ticket under the purview of the entire group to claim.
- Legacy Behavior: Retains the previous system of reassignment to the admin or the oldest agent, maintaining consistency for those who prefer the traditional method.
Benefits
This feature introduces a significant improvement in ticket lifecycle management by accommodating various scenarios that arise with team changes. It provides a clear, customizable process for reassigning solved tickets, enhancing operational clarity and ensuring continuity in ticket resolution.
