Use the Interviewing activity to produce the following reports for your interviewing project that utilizes sample management.

For more information about customizing these reports or running them outside of the Interviewing activity, see the notes at the end of this topic.

The following reports are based on the project’s contact history data:

The following reports are based on the project’s sample data:

All reports display counts and percentages that are zero as a hyphen (-) and counts and percentages that are rounded to zero as an asterisk (*).

Reports include charts only if you have enabled the charting feature in UNICOM Intelligence Interviewer. For more information, see Running reports.

The rest of this topic describes the reports in detail.

For projects that use an autodialer, this report shows a frequency table of the time taken by participants to answer calls. The categories are one second to 20 seconds in one second intervals, with an additional category for durations greater than 20 seconds. Each cell shows a count, a column percentage, and cumulative column percentage.

You might want to use the statistics in this report to adjust the minimum length of time that an unanswered phone call must ring before the autodialer terminates the call. However, your local laws might specify the minimum value that you must use.

Note that this report always includes data for both real and test interviews – you cannot choose to include only one or the other. For projects that do not use an autodialer, selecting this report might display an empty table or an error message.

For projects that use an autodialer, this report shows the busy, wait and idle times for each interviewer who has worked on the project. The definition of these times is as follows:

Each cell, which corresponds to the busy, wait, or idle time for one interviewer, shows the mean time, the total time, the minimum time, and the maximum time. All times are shown in days, hours, minutes, and seconds.

If you specify a time period when you run the report, the report includes only interviewers who made calls during that time period.

The Busy, Wait, and Idle Time report does not include a chart, even if you have enabled the charting feature.

This report always includes data for both real and test interviews; that is, you cannot choose to include only one or the other. For projects that do not use an autodialer, selecting this report might display an empty table or an error message.

This reports provides busy, wait, and idle information across projects for each interviewer and project for the last 8 hours. This report is similar to the Busy, Wait, and Idle Time report, except this report always includes data for both real and test interviews and it cannot specify a time period.

For more information about across project reports, see Across project reports.

This report provides the project’s full contact history. The report’s default fields are:

You can update the MaxRows property in DPM to indicate the maximum number of rows that will display in the report. The default value is 10000. The property is in DPM at: Site > Servers> [Server_Name] > Applications > CatiReports > ApplicationSettings > ContactHistory.

You can update the SortOrder property in DPM to indicate whether the report’s rows are sorted in ascending (ASC) or descending (DESC) order. The default value is DESC. The property is in DPM at: Site > Servers> [Server_Name] > Applications > CatiReports > ApplicationSettings > ContactHistory.

This report shows a frequency table of contact outcomes. Each cell shows a count and a column percentage. For projects that use an autodialer, the contact outcomes include those selected by the autodialer.

This report provides dialer specific statistics over the past eight hours.

This report contains two tables. The first is a crosstabulation that shows, for each interviewer, the total time that the Interviewing Participants activity was open (“Session Time”), the total number of calls made (“Attempts”), and the number of calls that resulted in each of the following groups of contact outcomes. The report always includes both real and test data.

For each column, each cell contains a count and a row percentage. Note that the number of calls includes multiple calls to the same participant.

For projects that use an autodialer, the Terminates and Recalls columns include call outcomes selected by the autodialer. Autodialed calls that did not result in a connection (for example, unanswered calls that were returned to the RECALL queue) are shown against an interviewer ID called “__Autodial”, whose figures are included in the Base statistics.

The second table shows some additional statistics for each interviewer, as follows:

If you specify a time period when you run the report, the report includes only interviewers who made calls during that time period.

Note that the Interviewer Statistics report does not include a chart, even if you have enabled the charting feature.

This report provides interviewer productivity information across phone projects for each interviewer and each phone project for the last 8 hours. The report always includes both real and test data.

For more information about across project reports, see Across project reports.

This report provides interviewer productivity information across personal projects for each interviewer and each personal project for the last 8 hours. The report always includes both real and test data.

For more information about across project reports, see Across project reports.

For projects that use an autodialer, this report can be used to compare the number of “silent calls” with both the number of calls that were answered by participants (shown as “Connected” calls) and the total number of calls made by the autodialer. Silent calls can occur when an autodialer generates more connected calls than there are interviewers available to handle the calls. Each cell of the report shows a count and a row percentage.

Note that this report always includes data for both real and test interviews – you cannot choose to include only one or the other. For projects that do not use an autodialer, selecting this report might display an empty table or an error message.

This report shows a frequency table of appointments arranged for the next two days. The categories are 09:00 to 23:00 in one hour intervals, with two additional categories for appointments taking place before 09:00 and after 23:00. Each cell shows a count and a column percentage.

This report shows a frequency table of appointments, per interviewer, arranged for the next two days. The categories are 09:00 to 23:00 in one hour intervals, with two additional categories for appointments taking place before 09:00 and after 23:00. Each cell shows a count and a column percentage.

Lists all appointments arranged for a particular time period. You specify the time period before running the report.

A crosstabulation showing the number of contacts for each combination of Queue (the rows in the table) and Contact Outcome (the columns). Each cell contains a count and a column percentage. For projects that use an autodialer, the contact outcomes include those selected by the autodialer, and the table includes the autodialer-specific queues called CHECK_NUMBER and SILENT.

If the project’s sample table contains segment information, the data is further broken down by segment. For more information, see About segments. The example report below shows the data broken down by location, which is one of the segments that the Interviewing activity recognizes.

This report shows, for each queue, the frequency of the number of attempts required to contact participants. The first set of categories, from one attempt to three attempts, excludes attempts made after arranging an appointment. The second set of categories, also from one attempt to three attempts, includes only attempts made after arranging an appointment. Participants requiring more than three attempts are not shown separately, but are included in the base statistics. For projects that use an autodialer, the report includes the autodialer-specific queues called CHECK_NUMBER and SILENT.

If the project’s sample table contains segment information, the data is further broken down by segment. For more information, see About segments. The example report below shows the data broken down by location, which is one of the segments that the Interviewing activity recognizes.

This report provides an industry standard calculation for incidence. CASRO (Council of American Survey Research Organizations) defines incidence as the number of potential respondents screened and eligible or qualified who agree to participate divided by the number of potential respondents screened.

For more information about across project reports, see Across project reports.

This report displays the last call outcome across phone projects for each participant record, organized by project, and always includes both real and test data. The report does not filter data, and does not specify a time period.

This report displays the last contact outcome across personal projects for each participant record, organized by project, and always includes both real and test data. The report does not filter data, and does not specify a time period.

This report shows two tables. The first is a frequency table showing the number of participant records in each queue. Note that the FAILED queue is not included in this table. For projects that use an autodialer, this table includes the autodialer-specific queues called CHECK_NUMBER and SILENT.

The second table shows some additional statistics, as follows:

This report displays the queue status for each interviewer. The interviewer queue status can help a supervisor decide how many participant records are available and what can be done to make more records available.

This report displays the queue status for each available time zone. The queue status can help a supervisor decide how many participant records are available and what can be done to make more records available.

Cross tabulates the data in two columns of the history table to produce a calling profile.

Variables that you can use in the tabulation for Web mode interviews are Queue, Test, InterviewerId, TimeZone, DayPart, Screener, and CallOutcome.

Personal mode includes Queue, Test, AppointmentTryCount, CallOutcome, ConnectCount, InteriewerId, InterviewMode, Screener, TimeZone, TryCount, AssignedInterviewerId, and DistributedTo. Phone mode includes Queue, Test, AppointmentTryCount, CallOutcome, ConnectCount, InterviewerId, InterviewMode, Screener, TimeZone, TryCount, and UserId.

For example, a table of UserId by CallOutcome shows one row for each interviewer and one column for each contact outcome code. The cell for an individual interviewer and contact outcome combination tells you how many contact that interviewer made that resulted in that contact outcome. It also shows the total and mean amount of time that the interviewer spent on those contact.

If you use the Email activity on a project that allows telephone interviewing, the history table for the project contains a history record for all participants who received the message. These records have an empty UserId value and a duration of either 1 or 0, and they appear in the base of your tables.

This report displays the supervisory accept and reject rate percentage for each interviewer’s completed interviews.

This report shows a frequency table of the number of participant records in each queue. Each cell contains a count and a column percentage. For projects that use an autodialer, the report includes the autodialer-specific queues called CHECK_NUMBER and SILENT.

This report shows a frequency table of the number of participant records in each queue, across projects, for each phone project. The report always includes both real and test data. Each cell contains a count and a column percentage. For projects that use an autodialer, the report includes the autodialer-specific queues called CHECK_NUMBER and SILENT.

For more information about across project reports, see Across project reports.

This report shows a frequency table of the number of participant records in each queue, across projects, for each personal project. The report always includes both real and test data. Each cell contains a count and a column percentage.

The standard Sample Usage report displays both CAPI and CATI contacts by default. The InterviewMode filter can be used to filter the report to a particular mode.

For more information about across project reports, see Across project reports.

This report displays a list of all time zones in use by the project and whether the time zones are active or inactive based on valid call times or day parts.

You can customize many of the reports listed above, or even add your own reports to the Interviewing activity. For more information, use the search function in the UNICOM Intelligence Developer Documentation Library documentation to search for the text ‘Customized Interviewing Reports’ and in the search results open the topic with that title.

Instead of using the Interviewing activity, you can produce all of the reports listed above by running an UNICOM Intelligence script. The script is called RunAllPhoneReports.mrs, which by default is installed by the DDL in the Scripts\General\mrScriptBasic folder. By editing a parameter in the script, you can select any of the following report formats: HTML; Microsoft Excel; Microsoft Powerpoint; Microsoft Word; delimited text (.csv) file. You can also specify a date range for those reports that require one, and whether the reports should use real or test data.