What is the difference between dropped chats and missed chats?
Dropped chats are the number of chats where the conversation with an agent ended with an unanswered message from a visitor.
Missed chats are the number of chats where the visitor left without being served by an agent. Missed chats also include chats served by an agent, but no agent message was sent before the chat ended.
For more information about Chat metrics, see the article: Metrics and attributes for Zendesk Chat.
There is something still unclear in dropped chats metric. At the mentioned "Metrics..." article is said that dropped chats are "accepted by or assigned to the agent where the visitor responds to an agent message, then leaves the chat". Does it mean if at the end of the chat the customer writes "thank you, goodbye" and closes the chat or the page with the chat - it will be counted as dropped chat? If yes, are there any good practices to influence statistics of dropped chat by such cases?
You are correct. If the chat ends with the visitor entering a reply, then quickly dropping off before the agent can respond again, that is being counted as a dropped chat. This is a tricky thing to filter out. The data stored from the chat doesn't have a smooth way of differentiating between a chat that had gone on for a while and ended with "goodbye" as compared to a chat that had gone on for a while and suddenly ended without reaching a conclusion.
While there isn't a perfect solution to this, you could try out a few different attributes based on what you find causes dropped chats the most. For example, you could include attributes for Chat Agent Messages Brackets and Chat Visitor Messages Brackets. With those, you could see how many dropped chats had very few messages exchanged, or perhaps had an uneven number of messages sent between the agent and visitor. Those could be useful pieces of information in assessing whether chats were truly dropped mid-chat or if they may have concluded naturally with a final comment from the visitor.
I'll relay this feedback to our team as well, but I hope this at least helps clarify things!
I fervently support your point. The lack of proper "drop chat metric" in Zendesk has forced us to go the extensive route of data mining in order to understand the nature of this issue.
from our research, Zendesk can identify % of chats which unexpectedly ended on the agents end.
Can we get a metric which identifies:
1) "Chat which unexpectedly ended" from agents side
2) "Chat which unexpecetedly ended" on the end user side.
3) "Total chats which unexpectedly ended.
Hi ZD: Is there possible to use function in ZD to separate the chats which are really dropped? Can we find type is chat.memberleave in ZD query? Then can we separate the member is agent instead of user?
Thanks for your query. Dropped chats will only really have one factor to take into consideration, which is that the chat was ended by the agent with an unanswered message from a visitor. Not sure what you mean by finding the type that is chat.memberleave in ZD query, as well as separating the member, but dropped chats will only be counted if the agent leaves with an unanswered message, hence if it is the end user that leaves, then it is not counted as a dropped chat.
Hope this helps clarify it for you! Cheers!
You can see the details I got from API of audit.
It's too complex to use API for analysis.
IS there convenient way in ZD's dashboard to find the leave member is agent or customer?
As mentioned before, dropped chats will only count chats where the agent left the chat with an unanswered message by the customer, but if it is the agent that left the chat without an unanswered message then it would be counted as a completed chat.
Hope I was able to clarify it. Thanks!
Above, Marco says this:
Mark's original answer says this:
In the linked documentation, it says this:
Mark's answer seems to suggest that it counts as a dropped chat even if it was ended by the end user. Marco is saying it only counts if it was ended by the agent.
Can someone from Zendesk tell us which is correct? Do the metrics distinguish between a chat dropped by an agent and one "self-dropped" by the end user?
A chat will be considered as a Dropped Chat when a conversation ended, either closed by an agent or end-user, and there is a message that was not answered by an agent. I understand that there are also some similar requests to modify how Dropped Chats are calculated. As it turns out, it's not yet on our roadmap. You can also try to use Messaging, which does have different classifications of conversation types.
Linked out page is dead
Hello ZD. If we were to change the origin of a missed/drop chat from chat to email, would this throw off our D_COUNT for missed chats in Explore? Or are D_COUNT missed chats tracked separately from the ZD fields?
If you are pertaining to just simply changing the channel of your responses, it will not have any effect on it as they are from two different datasets.
Hope this helps!
Please sign in to leave a comment.