Many of the statistics available within the reporting and real-time interfaces are 'Aggregated Statistics', these statistics are based on data from multiple call segments which have been grouped together.
There are two types of call list available; 'Segmented and Non-Segmented'. Segment call lists show data directly from the database with the addition of some computed columns like call duration. No data aggregation occurs on these reports.
Non-segmented call list show a single row per call, no matter how many segments make up the call. This means that the call data from each call segment is aggregated to create the data for the whole call.
In addition to showing segmented or non-segmented data, some reports group data by a specific column to allow the data to be analyzed. Once data has been grouped, a whole new set of summarized statistics become available like; Totals, Averages, Minimum and Maximum values.
Some grouped reports use segmented call data and some use non-segmented data. Grouped reports that use non-segmented data merge the call segments together first before grouping the data.
The historical reporting system provides templates which group data by the following call data columns:
Grouped reports are really useful for assessing performance and getting an overall view of the number and types of calls being processed. For example, a report grouped by extension can be used to see how many calls each extension handled and what their total talk time was.
Report that use non-segmented data, merge all segments of a call together (by grouping Trunk + CallID) before any other grouping (if there is any) is applied to the report.
When grouping by trunk line occurs, the segmented call data needs to be aggregated. The following section outlines the effect aggregation has on a report's available columns.
Column Name | Aggregation Effect |
---|---|
Account Code | The last account code entered, on any segment. |
Agent / Agent Name | If the call was answered, this will contain the details of the agent logged in if available. Other wise it will contain the agent details where the call first rang. If no agent was logged at all, these fields will be blank. |
Answer Time | The time the call was first answered. |
Call Answered | If any segment of the call was answered. |
Call Duration | The cumulative call time of all segments. |
Call Type | The call type of the first segment. |
CallID | The call id of the first segment. |
End Event | The end event of the last segment. |
End Time | The end time of the last segment. |
Extension / Extension Name | If the call was answered, this will contain the details of the extension that answered the call. Otherwise it will contain the details of the extension where the call first rang. |
Hold Duration | The cumulative hold duration for all segments. |
Hunt Group / Hunt Group Name | The details of the first hunt group the call passed through if applicable. |
Lost Call | Was the last segment of the call answered. |
Rec ID | The database Record ID of the first segment. |
Ring Duration | The ring duration until the call was first answered. |
Start Time | The start time of the initial segment. |
Tag Fields 1 to 5 | The last valid entry in each field. For example, if field 1 was tagged on segment 1 and field 2 was tagged on segment 3 then both tag fields 1 and 2 would show on the report unless overridden with a valid tag in subsequent segments. |
Talk Duration | The cumulative talk duration for all segments includes any ring time after the call was first answered. |
Transferred Agent From | Contains the transferring agent's details the first time the calls was transferred if applicable. |
Transferred Agent To | Contains the transferred to agent's details the first time the calls was transferred if applicable. |
Transferred From | Contains the transferring extension's details the first time the calls was transferred if applicable. |
Transferred To | Contains the transferred to extension's details the first time the calls was transferred if applicable. |
Username | If the call was answered, this will contain the details of the username of the MiVoice Office Application Suite user that answered the call. Otherwise it will contain the username where the call first rang. |
When analyzing a summarized (grouped) report, it is important to understand what has happened to each call. This is done by evaluating similar summarized columns to make sure they add up to the total number of calls (e.g. Total Calls Handled = Total Calls In + Total Calls Out).
Depending on how the report is grouped or whether the report is using segmented call data or not, the way the summarized data adds up is different.
The follow table shows how call totals and durations can be analyzed in the context of a grouped report using segmented data.
Call Totals |
Calls Handled |
= Calls Inbound + Calls Outbound |
= Calls Internal + Calls External |
||
= Calls Answered + Calls Lost + Calls Refused + Calls Overflowed Out |
||
Calls Answered |
= Calls Completed + Calls Transferred Out |
|
Call Durations | Total Call Time |
= Total Ring Time + Total Talk Time + Total Hold Time |
Total Call Time (In) |
= Total Ring Time (In) + Total Talk Time (In) + Total Hold Time (In) |
|
Total Call Time (Out) |
= Total Ring Time (Out) + Total Talk Time (Out) + Total Hold Time (Out) |
The follow table shows how call totals and durations can be analyses in the context of a grouped report using non-segmented data.
Call Totals | Calls Handled |
= Calls Inbound + Calls Outbound + Calls Internal* |
= Calls Internal + Calls External |
||
= Calls Answered + Calls Lost |
||
Call Durations | Total Call Time |
= Total Ring Time + Total Talk Time + Total Hold Time |
Total Call Time (In) |
= Total Ring Time (In) + Total Talk Time (In) + Total Hold Time (In) |
|
Total Call Time (Out) |
= Total Ring Time (Out) + Total Talk Time (Out) + Total Hold Time (Out) |