Búsquedas recientes
No hay búsquedas recientes

James Cory
Incorporación 16 abr 2021
·
Última actividad 03 feb 2022
Seguimientos
0
Seguidores
0
Actividad total
7
Voto
1
Suscripciones
2
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de James Cory
James Cory hizo un comentario,
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.
Ver comentario · Publicado 03 feb 2022 · James Cory
0
Seguidores
5
Votos
0
Comentarios
James Cory hizo un comentario,
@...
I'd be happy to.
Send me an email at and we can set some time up.
Ver comentario · Publicado 13 ene 2020 · James Cory
0
Seguidores
1
Voto
0
Comentarios
James Cory hizo un comentario,
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.
Ver comentario · Publicado 11 jun 2019 · James Cory
0
Seguidores
1
Voto
0
Comentarios
James Cory hizo un comentario,
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
Ver comentario · Publicado 26 feb 2019 · James Cory
0
Seguidores
0
Votos
0
Comentarios