QueueMetrics forum
QueueMetrics => Running QueueMetrics => Topic started by: LostyJai on September 10, 2008, 05:47:06
-
Can someone tell me what the Total calls processed includes?
I also have a question regarding the following scenario:
1) Operator A is on the phone with a Caller 1.
2) Caller 2 calls our company.
3) Caller 2 tries to connect to Operator A.
4) Since Operator A is with Caller 1, Caller 2 tries to connect to Operator B.
During steps 1-3, Operator A's Total calls processed is 10.
But at step 4, Operator A's Total calls processed goes up to 11.
Is this a bug?
-
This looks strange indeed. Can you post some screesnshots?
-
Okay it's really weird, everything seems to be working again...
I didn't really do anything, but if it anything happens I'll post up some screenshots
-
This looks strange indeed. Can you post some screesnshots?
Report for everyone this morning
(http://members.westnet.com.au/simonliang/qmetrics1.jpg)
Report for Agent #508
(http://members.westnet.com.au/simonliang/qmetrics2.jpg)
Report for Agent #512
(http://members.westnet.com.au/simonliang/qmetrics3.jpg)
The total calls processed for everyone is 7, which is right!
Since Agent #508 was the only agent logged in and taking calls, he took 6 and missed 1.
However for Agent #512 who hasn't been logged on all morning, his total calls processed is still 1 (which is the unanswered call). It seems the unanswered calls is a global thing and when a customer hangs up, everyone is penalised with that one unanswered call... Can you please look into this asap.
Also when the report is generated for everyone... in the unanswered calls tab, there doesn't seem to be a unanswered calls by agent field... is this correct?
Added 11:51am 11/9/2008
Ran dbtest, but got the following error (not sure if they are related):
Problem encountered:
The required database table 'qa_data' is missing or unreadable. Please run the database update utility.
-
Ok this makes sense.
Lost calls are in effect GLOBAL as they were never taken up by any agents. So the very last version of QM just zeroes them when filtering by agent.
-
Ok this makes sense.
Lost calls are in effect GLOBAL as they were never taken up by any agents. So the very last version of QM just zeroes them when filtering by agent.
So by updating to the newest version (currently I'm using 1.4.4) everything should be fine? When you filter by agents, will the unanswered calls always be 0 because they were never taken by the agents?
In the reports, is there a way to show the last agent's queue the unanswered call was in?
And what is the qa_data table that I'm missing? Is it important?
-
Yes in the reports you see the queue, but not the last attempting agent.
You can have statst about agents not picking up in the "attempts" section.
-
Yes in the reports you see the queue, but not the last attempting agent.
You can have statst about agents not picking up in the "attempts" section.
So what you're saying is, the percentage for answered calls for any agent will always be 100%, and 0% for unanswered calls... since unanswered calls is GLOBAL.
In the ATTEMPTS tab, what is the "N. Taken"?
Is that just the amount of calls an agent has answered?