Changing Call by Call Stats to keep less days 3

[scriptscience]

We have turned on the call by call stats for one of our areas and it is keeping 14 days (dbo.ecallbycall20070303, etc.). We want to turn it on for other areas and download daily it to local server for data queries and therefore do not need to keep 14 days. Is it an all or nothing thing. Either 14 days or nothing? Or can we change it do just store 1 day? Help.

 

[carolien]

You can change the Duration (in days) in Configuration: Historical Statistics

 

[Milesprower]

You can also select the applications for which you want to collect call by call data.

 

[scriptscience]

Can you clarify what you mean by applications? and describe how you would do this, thanks.

 

[Milesprower]

As carolien stated, in web client (or CCMA) go to Configuration, then Historical Statistics. There are several tables - you will have to scroll around the page to see them all. One of the tables deal with duration. In that table is an entry for the number of days to keep call by call data. There is another table where you select the Scripts (applications) for which you want to collect call by call data. You'll almost always want to select the Master Script and the ACD DN script in addition to the primary scripts of which you want to keep track.

 

[Supernn]

Application: an primary script (so directly accessed via the Master_Script) on which the rest of the call is pegged against.

Example: A call is routed to DNIS 1234. In the Master_Script it is pegged for opening hours. Within opening hours the call is routed to script "test". This script is now an application.
Within that "test" script you can add another script for example for bank holidays, say to script "bankholidays". This script cannot be an application as the call is transferred by an application and not by the Master_Script to this script.

If you would run an application based report you can report how many calls are presented to the primary script in total but not report on how many calls have been presented to the secondary script.

For CallByCall Statistics to work you have to always include the Master_Script and any application (primary script), otherwise you might not have all required data (e.g. DNIS data missing, CDN data, callerID etc.)

Supernn

 

[monkeybarfan]

How are you going to download them?

I would like to know of an automatic way to do this, as I haven't managed it in SQL Server TS packages, due to the different table name every day.

 

[scriptscience]

For now we are going to do it manually. I do not know of automatic way yet.