Recherches récentes
Pas de recherche récente

James Cory
Adhésion le 16 avr. 2021
·
Dernière activité le 03 févr. 2022
Suivis
0
Abonnés
0
Activité totale
7
vote
1
Abonnements
2
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par James Cory
James Cory a ajouté un commentaire,
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.
Afficher le commentaire · Publication le 03 févr. 2022 · James Cory
0
Abonnés
5
Votes
0
Commentaire
James Cory a ajouté un commentaire,
@...
I'd be happy to.
Send me an email at and we can set some time up.
Afficher le commentaire · Publication le 13 janv. 2020 · James Cory
0
Abonnés
1
vote
0
Commentaire
James Cory a ajouté un commentaire,
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.
Afficher le commentaire · Publication le 11 juin 2019 · James Cory
0
Abonnés
1
vote
0
Commentaire
James Cory a ajouté un commentaire,
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
Afficher le commentaire · Publication le 26 févr. 2019 · James Cory
0
Abonnés
0
Votes
0
Commentaire