Question
Why is there a discrepancy between accepted and served chats and how does this affect the acceptance rate?
Answer
The number of accepted chats can differ from the number of served chats for a given agent because an agent can serve more chats than they are assigned by the system.
Accepted chats only include chats that are assigned to the agent by the system through the Assigned routing option.
Served chats also include chats that are manually assigned to the agent. A chat can be manually assigned to an agent in the following scenarios:
- Proactively initiating chats with visitors
- Joining chats served by other agents
- Receiving chats that are transferred from other agents
- Manually picking up unassigned chats when the chat limit is reached
When calculating the acceptance rate, only accepted chats are considered. The formula to calculate the acceptance rate is as follows:
Accepted Chats / Assigned Chats = Acceptance Rate
For more information about Chat Analytics, see the article: Chat Analytics CSV glossary.
6 comments
CJ Johnson
I don't see any metrics for "accepted chats". I do have a metric, "Accepted Assignments". Was this metric renamed since this was written?
My problem is that the "Accepted Assignments" metric is actually higher than the number of served chats, total. Is this a known issue as well? I'm completely baffled how more chats could be accepted through assigning, than were served.
Edit: I now know the reason Accepted Assignments can be higher than Served Chats, is because agents can accept an assignment, but fail to get a message in before the requester exists, which is marked as a Missed Chat, not a Served Chat, but is still an Accepted Assignment.
1
Jahn
Zendesk Team - I was also told by your customer support team that Served Chats also includes missed engagement/assignments.
0
Joe | PX
The definition still isn't making sense to me. My agents are only assigned chats by the system, these situations can not occur
Yet we still have a discrepancy
0
Ryan K.
Hi team!
A quick question, if an end-user were to start a chat but then leave right before it's accepted, would this negatively impact the agent's chat acceptance rate?
If so, is there a way to prevent that from happening? I don't want the team to be negatively impacted because the end-user leaves the chat early/within seconds of starting.
0
Viktor Osetrov
No, it's not impacted if you use the following Engagement metrics:
Hope it helps
0
Ryan K.
Thanks, Viktor. It actually looks like acceptance rate is impacted if a user 'starts a chat', the chat is then assigned to an agent, but then the user leaves the chat before the agent has a chance to accept it.
I just confirmed this on my end. Thanks!
0