The update timestamp changes due to a 'chatended' event being added to audits, even if it's not visible in the event log. When a chat session ends, a 'chatended' event is appended in the audit endpoint, which updates the timestamp. This is normal behavior, especially when ticket status updates occur, as these events are logged and correspond with the timestamp.
However, if a session ends because the agent or visitor is idle for less than ten minutes, the update timestamp may not match the visible event log but will align with the 'chatended' event in audits. For more details, you can refer to the originalZendesk article.
A chat session in Zendesk can end due to several reasons, depending on whether you're using chat or messaging in the Agent Workspace. For chat users, sessions end when the visitor is idle, the visitor ends the chat, or the agent ends the chat. For…
Visitor idle timeout is a key factor in ending chat sessions in Zendesk. For chat users, if a visitor is idle, the session will end. In messaging, the idle timeout is set to 10 minutes, after which the session will automatically end if no activity…
The update timestamp might not match the event log due to the 'chatended' event being filtered out of the visible log. This event is still recorded in the audit endpoint, which updates the timestamp. This discrepancy typically occurs when a session…