Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

James Cory
Beigetreten 16. Apr. 2021
·
Letzte Aktivität 03. Feb. 2022
Folge ich
0
Follower
0
Gesamtaktivitäten
7
Stimme
1
Abonnements
2
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von James Cory
James Cory hat einen Kommentar hinterlassen
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.
Kommentar anzeigen · Gepostet 03. Feb. 2022 · James Cory
0
Follower
5
Stimmen
0
Kommentare
James Cory hat einen Kommentar hinterlassen
@...
I'd be happy to.
Send me an email at and we can set some time up.
Kommentar anzeigen · Gepostet 13. Jan. 2020 · James Cory
0
Follower
1
Stimme
0
Kommentare
James Cory hat einen Kommentar hinterlassen
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.
Kommentar anzeigen · Gepostet 11. Juni 2019 · James Cory
0
Follower
1
Stimme
0
Kommentare
James Cory hat einen Kommentar hinterlassen
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
Kommentar anzeigen · Gepostet 26. Feb. 2019 · James Cory
0
Follower
0
Stimmen
0
Kommentare