Pesquisas recentes
Sem pesquisas recentes

James Cory
Entrou em 16 de abr. de 2021
·
Última atividade em 03 de fev. de 2022
Seguindo
0
Seguidores
0
Atividade total
7
Votos
1
Assinaturas
2
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por James Cory
James Cory comentou,
This needs to be on the roadmap.
The quickest way to reduce average speed to answer is to take away the optionality of answering a call. If an agent is logged in and ready, they should get the call.
Exibir comentário · Publicado 03 de fev. de 2022 · James Cory
0
Seguidores
5
Votos
0
Comentários
James Cory comentou,
@...
I'd be happy to.
Send me an email at and we can set some time up.
Exibir comentário · Publicado 13 de jan. de 2020 · James Cory
0
Seguidores
1
Votos
0
Comentários
James Cory comentou,
Jose - Agreed!
I was able to build this report in Explore, but it wasn't simple and took a fair amount of work, which is frankly embarrassing for a telephony product.
However, Explore only updates every 2 hours, so real time service level is non-existent, and I can't see how I'm performing right now.
Exibir comentário · Publicado 11 de jun. de 2019 · James Cory
0
Seguidores
1
Votos
0
Comentários
James Cory comentou,
Jose -
I think your widget gets me close to what I'm looking for. However, It looks like the MAQL isn't quite right, as it's measuring accepted calls/total calls, rather than accepted calls where wait time is < 30 (or some number) / total calls.
Logically, I'm looking for this, but I'm getting a crazy high number for SL.
SELECT # inbound Calls WHERE Call Wait Time<30/# inbound Calls
Exibir comentário · Publicado 26 de fev. de 2019 · James Cory
0
Seguidores
0
Votos
0
Comentários