Zendesk has enhanced its End session feature for messaging conversations to automatically capture and display the agent name in ticket event logs when a session is manually terminated. Previously, session-end events were recorded without identifying which agent performed the action, forcing administrators and QA teams to rely on manual workarounds or macro-based solutions to audit agent behaviour. This update shifts accountability tracking from reactive investigation to proactive system-generated logging, eliminating the friction that previously existed around identifying protocol violations or detecting patterns of abnormal session-ending behaviour.
The implications for CX teams are straightforward but consequential. Organisations can now enforce session-end governance without additional tooling or process overhead—the visibility is native to the platform. For teams already managing large contact centres or those operating under strict compliance requirements, this removes a notable gap in audit trails that previously required workarounds. The change is particularly relevant as teams scale agentic AI deployments; as automation handles more of the conversation layer, the ability to track human intervention points—including when and by whom sessions are terminated—becomes more critical for understanding handoff quality and agent decision-making. The zero-implementation requirement also means adoption is immediate across all accounts, making this a baseline expectation rather than an optional enhancement.
Announced on Rollout on March 26, 2026 March 24, 2026 Zendesk is pleased to announce an enhancement to the End session capability for messaging. Now, when an agent ends a messaging session manually, Zendesk will capture and display that agent’s name in the ticket event log.This announcement includes
Announced on Rollout on March 26, 2026 March 24, 2026 Zendesk is pleased to announce an enhancement to the End session capability for messaging. Now, when an agent ends a messaging session manually, Zendesk will capture and display that agent’s name in the ticket event log.This announcement includes