Developer Documentation Library > Dialer SDK > UNICOM Intelligence Dialer SDK components > Features > Sample selection and calling rules > Interviewing Options overview
 
Interviewing Options overview
The Interviewing Options activity tabs (discussed in Configuring a project) configure the Phone Participants activity's available options and are used by the supplied sample management script to configure record selection and dialer interaction. See Interviewing Options on each tab.
Fields
Relevant to UNICOM Intelligence Dialer: No
Allows the supervisor to setup the sample fields that can be viewed and edited in Phone Participants.
Parameters
Relevant to UNICOM Intelligence Dialer: Maybe
Allows the supervisor to setup sample selection parameters. Dialers that handle retries might use the retry delay parameters (such as no answer and busy delays).
Ordering
Relevant to UNICOM Intelligence Dialer: No
Allows the supervisor to setup the order of selection of records
Call Times
Relevant to UNICOM Intelligence Dialer: Yes
Used to setup valid calling hours or day parts. Valid calling hours support weekday and weekend defined hours and a maximum number of total times to retry the record. Day parts are used to divide the day into parts and define the maximum number of tries for each day part.
Either type of valid calling interval is relative to the TimeZone as setup in the sample record.
Sample records are retrieved only if they are valid at the time of retrieval. The dialer will need to ensure that the record is dialed before the valid calling interval for the record has passed. This can be implemented simply by stating that each record is returned after a short interval (5 or 10 minutes).
Your dialer might have the capability to handle retries (calling a record more than once). It is recommended that your dialing provider implementation use the UNICOM Intelligence Interviewer to handle retries rather than using your dialer implementation, thereby allowing the configuring user to use one interface, the UNICOM Intelligence interface to specify dialing rules. This also avoids additional work in your dialing provider to schedule recalls based on valid calling hours or day parts.
Appointments
Relevant to UNICOM Intelligence Dialer: Yes
The options set on the Appointments tab are used by Phone Participants to guide the interviewer to valid appointment times.
The tab also supports setting a project end time, which is used when selecting a sample. As with the call times, the dialer must ensure that the record is dialed within a reasonable time to ensure that the expiry time for the project or record does not pass.
Appointments should be prioritized over other types of calls since we know a possible respondent is available.
Overrides
Relevant to UNICOM Intelligence Dialer: Maybe
Overrides are generally used for sample selection. However dialers that handle retries might need to use overrides for the retry delay parameters (like the no answer and busy delays) and for the maximum number of tries.
Call Outcomes
Relevant to UNICOM Intelligence Dialer: Maybe
These return codes are displayed to the interviewer on the Phone Participants screen.
If interviewer chosen outcomes are passed to the dialer, this screen and the associated DPM properties define the outcomes that could be passed.
Interview Settings
Relevant to UNICOM Intelligence Dialer: No
The options on this screen impact Phone Participants and the Session Engine. The options in the Dialing Options defines the dialer and type of dialing (extension vs. group). This information is used to load the appropriate dialing components.
Dialer Settings
Relevant to UNICOM Intelligence Dialer: Yes
Most of the settings on this tab are used to control the dialer.
The dialer provider is responsible for implementing the NoAnswerTimeout (Cancel if interviewer not connected after). The provider should block on the Get until a record is returned or this interval has been reached.
Your supplemental documentation should cover any of these settings that are not applicable to your dialer. For instance, your dialer might not support a project specific silent call announcement.
See also
Sample selection and calling rules