A database table that holds information about respondents who might take part in the survey, either by dialing in to your company’s web page or by being contacted by an interviewer working on an outbound calling project. For more information, see Sample table.

A database table that holds information about Sample records that were used for outbound telephone interviewing. History records are written to this table whenever an interview is terminated in some way (for example, stopped or completed) or when a telephone interview drops a Sample record for some reason (for example, because the line is engaged). The information in this table can be used for producing supervisory and productivity reports. For more information, see History table.

Scripts that define the way in which sample management will work for a project. For more information, see Sample management scripts.

Allow records to be grouped according to how the records have been or might be used in the survey. At the start of a survey, all records are usually held in a single queue. When an interview is in progress for an interview, the record moves into an Active or In-progress queue; when the interview ends, the record moves into a third queue depending on the outcome of the interview. For more information, see Queues.

(Known internally as Sample record return codes.) Define the result of an inbound or outbound call. When a sample record is returned to sample management at the end of a call, the interviewing program also returns a call outcome code indicating the result of the call. The sample management script uses these codes to decide which queue it should place the sample record in. For more information, see Call and contact outcome codes.

Define values for variables that are used in the sample management script; for example, callback delays for busy and no-answer callbacks, and the maximum number of recalls permitted per record. For more information, see Telephone interviewing project parameters.

If sample records contain a TimeZone field specifying the respondent's time zone, sample management can take into account time zone differences between interviewers and respondents when selecting records with appointments for recall. For more information, see Time zone management.

Assign sample records to interviewers who have the appropriate qualifications to deal with those calls. For example, if the respondent's preferred language is Spanish, the sample record might be assigned to a Spanish speaking interviewer. For more information, see Interviewer qualifications.

The process which validates respondents before an interview begins. For more information, see Authentication of inbound respondents.

The action to take when Sample records are returned to the sample management system at the ends of interviews. For more information, see End of interview.

Define the requirements for the sample in terms of the numbers of respondents who have certain characteristics or combinations of characteristics. For more information, see Quotas.

Each project has a collection of properties that store information about the project, and each interview has its own set of properties that contain information about that particular interview. You can access project and interview properties in the sample management script and can perform different actions for different types of projects or interviews. In some instances you can change property values or add new properties too. For more information, see Sample management scripts and Project and interview properties.

A SiteProperties object is available to the sample management script to provide read-only access to the Site.Properties.InterviewProperties property collection in DPM.

Use Site.Properties.InterviewProperties to define global settings or “environment variables” for an interview cluster. These can be SQL or mail server names that are cluster‑specific or API information that cannot be stored in an .mdd file that might be shared. This property collection is also available to the interview routing script.