This starts happening to customers after CCR put the restriction that report duration has to contain either login/logoff at least for shift time to come up for a particular day. So I think if your report duration includes possible login/logoff timings this won't happen.
In IPOffice Manager it is specified
Once a call overflows, it is presented to the first available member of the first overflow group listed. The Ring Mode of the overflow group is used to determine its first available member. However the No Answer Time of the original targeted group is used to...
10 GB is defined because for SQL express 2008 maximum database size is 10GB. If it is full blown SQL then that limit in CCR WebClient doesn't matter. It will grow till the specified size in SQL without problems .
Your Agent login/logout time has to be included in the report schedule. If login is before 9 and logout after 6:30 it wont come . Either one activity should be there in the time selected.
Currently thing you can do is generate a League table with System HuntGroup and OutBound calls as statistic , though not exactly number of outbound calls you will get , Only the ranking
When you transfer the call to an agent then it will be considered as a direct call. I think You can get answered only in the form of Answered Ext non q for agent stat in real time
Mariah,
In that case before changing product maybe you can raise a ticket and get clarifications from Avaya. Some of our customers had confusions when there were overflow calls are also involved and there can be confusions around counting of calls with CDR and CSR as CDR
You might be getting different result in CCR because of the targets you select . I think if you use target as queue everywhere you may not face the problem for Answered calls and Lost calls
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.