CATI (Campaign) Manager - Builder

Owned by Scott D Child
Last updated: Jul 12, 2021
11 min read

CATI (Campaign) Manager is a section available from the side menu available to authorised users. 

CATI (Campaign) Manager - The INVADE CATI & Campaign Manager, this section allows you to load sample stored in a .csv style document such as Microsoft Excel. This section works directly with CATI Interviewer section allowing the interviewer to interact with the sample loaded. Supported dial methods are Predictive, Preview, Manual (Manual Dial Solution). Not all CATI has the same information available



CATI Manager default page header


Title CATI Manager = current module you are viewing

Live 'Tab' = Lists all active campaigns created within this section

Old 'Tab' = Lists all archived campaigns created within this section


Icons top right= INVADE Solution connected


User = Currently logged on Username and INVADE Solution Web Portal Version, with the ability to 'Logoff'

NOTE. The ability to Monitor, coach & barge is not available in this section

Once in the CATI (Campaign) Manager, the left-hand side will display a list of campaigns that are configured using CATI (Campaign) Manager. The list is providing CampaignName, Ready state and Live state of the campaign.

  • Ready - represents the state of the campaign configuration values. Ready - true means that the parameters are locked in and can not be changed. Not Ready state will enable to change the campaign configuration parameters.
  • Live - represents the campaign status on the dialler. If the campaign is started and active this value will be true, otherwise false.


As seen at the top there is a button "Create new campaign" used to create a new campaign object.

When the campaign is in a Ready state it will have parameters locked in and uneditable 'Campaign is in Ready state' below.

The campaign is in UnReady state

When the campaign is in UnReady state, the wizard-like stepper will guide you through the campaign creation process.

Parameters section


The configurable campaign parameters are:

  • Campaign name - the name of the campaign 
  • No Answer timeout - timeout used to determine when the Ringing call can be treated as No Answer.
  • Abandon target - preferred abandon target rate
  • CLID - Caller Line Identification (Optional) 
  • Dial Method - the starting dialling method to be used when the campaign starts
  • Call Recording - whether call recording is enabled or not  when the campaign starts
  • AMD - whether to enable AMD 
  • Start Activity - predefined campaign activity start time (These are for information only)
  • End Activity - predefined campaign activity end time (These are for information only)
  • Create and Next - Saves Campaign metadata and moves to Sample 

Sample Stats


The Sample Stats table is a output from AutoRecallDelta field in the Completion codes section.
If a sample is to be recycled (called again) but no specific time is required, then this time delta (format Day.Hour:Minute:Second) will be used to determine what the sample will be called back. It adds the time delta to the current time. It is important to understand that as sample re-call will not be set to a time outside of the activity hours of a campaign. If the addition of the delta falls in a period of inactivity it will be shifted to be within the next active period.

Key to Table

Total = Total Sample (telephone numbers) loaded to the campaign
Fresh = New sample ready to be dialled
In Progress = Sample already dialled
Live in 1 hour = Callback sample available in 1 hour
Live in 4 Hours = Callback sample available in 4 hours
Live in 24 hours = Callback sample available in 24 hours
Live total = Total of all callback sample

Sample section

This section will allow you to upload the sample, for more in-depth explanation see our white paper Sample Management, Completion Codes and Recycle Rules. Sample upload file has to be in .csv format and be named with the following format {CampaignName}_Upload.csv

"Upload sample file" button will let you select such a sample file. 

Once the sample file is selected the list of files ready to upload will appear. Clicking on "Upload" will attempt to upload the file.


Note. Successful imports will have green bordered card with batch details & Failed imports will have red bordered card with failed batch details

Successful Imports, end box showing green border



Unsuccessful Imports, end box showing red border



When attempting to start campaign that has failed imports you will be presented with a dialog box notifying that there are failed imports and asking for your confirmation.


When the file is uploaded and parsed successfully the sample list should appear.

Note. the Columns & Filter Panel is available from the right-hand side as shown here.

Filters will allow you to pick values for the matching column's cell value

The following sections below describe when the column selector is available

Full information is available Sample Management, Completion Codes and Recycle Rules white paper


Columns

RecordID - Unique reference for the sample record
InterviewID - Unique reference for the sample Interview 
CampaignName - Given name for the campaign
TelNum - Telephone number dialled
CallerID - CallerID used for that sample
CompletionCode – the code number of last completion code applied to this sample
Code Description – the code Description of last completion code applied to this sample
Appointment – This value (Yes/No) shows if there is an appointment set for this sample
NextCallDateTime – this is the time an appointment call or re-call is scheduled. It is set if wither Appointment=Yes or Recall=Yes.
Callback – This value (Yes/No) shows if there is a re-call schedule set for this sample. This would be set after a call fail.
InProgress – This value (Yes/No) shows if the sample is in the diallers predictive pool of sample records about to be called
Fresh – This value (Yes/No) shows if a sample has not been called yet
Exhausted - This value (Yes/No) shows if a sample has exceeded its call failure limits (See Recycling Rules). The sample will not be called again by the dialler in predictive mode, but may be retrieved as preview and called that way
CycleNO - Number of times the sample has been retrieved by the dialler
Terminated - This value (Yes/No) shows that the sample will not be called again. The last code applied did not indicate a re-call or an appointment. It is likely to relate to a completed or refused (or similar) survey. The sample will not be called again by the dialler in predictive mode, but may be retrieved as preview and called that way
Tries_NOANSWER – this is the count of how many NO ANSWER outcomes have been coded. Once a respondent is contacted this is reset to 0 (See recycling rules).
Tries_BUSY – this is the count of how many BUSY outcomes have been coded. Once a respondent is contacted this is reset to 0 (See recycling rules).
Tries_CONGESTION – this is the count of how many CONGESTION outcomes have been coded. Once a respondent is contacted this is reset to 0 (See recycling rules).
Tries_BADNUMBER – this is the count of how many BAD NUMBER outcomes have been coded. Once a respondent is contacted this is reset to 0 (See recycling rules).
Tries_AMD – this is the count of how many AMD (AnswerMachine/VoiceMail) outcomes have been coded. Once a respondent is contacted this is reset to 0 (See recycling rules).
Tries – this is the count of how many of any failed outcomes have been coded. Once a respondent is contacted this is reset to 0 (See recycling rules).
SamplePoint - See Quota Points
SampleExtraDate -  MEMBER & EVENT additional data that does not match quota points

Quota section

For more information on how Quota Management is implemented within the dialler see Quota Management

This section will allow you to upload the sample. Sample upload file has to be in csv format and be named with the following format {CampaignName}_Quota.csv.

"Upload sample file" button will let you select such a sample file. 

Once the sample file is selected the list of files ready to upload will appear. Clicking on "Upload" will attempt to upload the file.

When the file is uploaded and parsed successfully the sample list should appear.

Completion code section

This section provides with the editable list of completion codes to be used by this campaign, for more in-depth explanation see our white paper Sample Management, Completion Codes and Recycle Rules

Right-clicking on any of the records you will be able to perform certain actions:


  • Add - will create blank completion code entry, all values need to be filled in. Double-clicking on the individual cell will make the cell value editable.
  • Duplicate - will duplicate selected completion code. The new record will have Code number incremented by one from biggest Code value in the table. Description will have suffix "_copy" added.
  • Delete - will delete the completion code record

In order to save the changes "Update" button needs to be pressed. If there are no errors the update was successful.

Completion code specific Answer Machine Playback

Any campaign started on the dialler will check “/playback/AMDFiles/{campaign_name}_Codes/” directory for any audio files that has completion code as a file name.

For example 22.gsm will match


When the dialler call/call is coded with that specific code the audio file will be played to the far end. Once the playback is complete the call will be coded and terminated.

Columns available

Code – a unique number relating to the code. If a new code is added the user is able to specify a code number. This should be unique. By convention codes denoting call connection failure should be < 10. A set of such code is automatically available on the creation of a new campaign.

Outcome – an optional field determining to which failure outcome the completion code is associated. This allows users to customise the completion codes associated with standard outcomes (eg BUSY, NOANSWER, AMD). If a code has an associated outcome, then when it is applied it will increment the “Tries” count in the sample record. Some outcomes (NOANSWER, BUSY, BADNUMBER, CONGESTION, AMD) have their own try counts. The try count associated with one of these outcomes will get incremented if a code with that outcome is applied (See Sample Management for more details
Description – a human-readable tag or description of what the code should indicate.
Schedule – This field determines if the code should come with a date and time at which the sample should be recalled. The values for this field are NOT_REQUIRED, OPTIONAL and COMPULSORY. COMPULSORY or OPTIONAL should be used when an appointment for a call back is required. This field is passed to the interviewer’s console application. The application will make sure data and time come with the code.
AutoRecallDelta – if a sample is to be recycled (called again) but no specific time is required, then this time delta (format Day.Hour:Minute:Second) will be used to determine what the sample will be called back. It adds the time delta to the current time. It is important to understand that as sample re-call will not be set to a time outside of the activity hours of a campaign. If the addition of the delta falls in a period of inactivity it will be shifted to be within the next active period.
Recycling – If “Yes” then the dialler will try and call the sample again. the sample is scheduled to be called back based on the AutoRecallDelta (see next item). If set to “No” then the sample will not be called back unless an appointment is made (see Schedule). The value is normally set to “Yes” for codes indicating failed call that require a re-call of the sample. The value is normally set to “NO” for codes indicating contact had been made with the respondent and no more calls are required
HideFromAgent – this value (Yes/No) determining if this code should not be available to an Interviewer.
NextCallPreview – this value (Yes/No) determines if the coded sample should be previewed at next call. This might be used for an appointment re-call
NextCallAgent – this is the interviewer name for which this sample will be given at the next call. If that interviewer is not available within 15 minutes of any scheduled call time then the sample will be given to another interviewer
Dialler – this denotes if the code can be used by the dialler (as opposed to the interviewer) for coding the call. This code will relate to call failure codes only
Changed - Denotes if a change has happened

Recycle rule section

Recycling rules can be edited by double-clicking on the "MaxTries" value, save by clicking enter, for more in-depth explanation see our white paper Sample Management, Completion Codes and Recycle Rules

Columns available

Outcome - Friendly name for the underlying code
Outcome Code - Outcome code mapped to a friendly name
Max Tries - The maximum number of tries a sample may be coded with a combination of failure outcomes 
Changed - If the code has been changed

Review section

This section has the button to Ready to make the campaign ready on the dialler and lock in the parameters.

The campaign is in Ready state

Parameters section

The default campaign parameters are:

  • Campaign name - the name of the campaign 
  • No Answer timeout - timeout used to determine when the Ringing call can be treated as No Answer.
  • Abandon target - preferred abandon target rate
  • Dial Method - the starting dialling method to be used when starting the campaign
  • Call Recording - whether call recording is enabled or not initially
  • AMD - whether to enable AMD 
  • Start Activity - predefined campaign activity start time (not yet implemented)
  • End Activity - predefined campaign activity end time (not yet implemented)

The set of buttons at the bottom of the card enables you to:

  • Start - start the campaign on the dialler
  • Stop - stop campaign on the dialler
  • UnReady - unready campaign configuration fur further editing

Sample section

Sample section will provide you with a list of the loaded sample. Note. If requested the sample can be dialled at random (Sample Randomization), this is an INVADE Predictive Dialler configuration, applied to all campaigns and will require a change request.

Clicking on the "+" on sample record will allow you to see associate call stat records

Note available from March 25, 2021

You can now import sample into the INVADE CATI Manager which contains multiple telephone numbers to dial. Maximum numbers allowed is 3. In the sample csv add extra values named TelNum, TelNum_1, TelNum_2. The sample file should look like this:

RecordID,TelNum,TelNum_1,TelNum_2,Age,Gender,Location,URLTOSURVEY1,10000001,10000002,10000003,88,M,London,http://google.com2,20000001,20000002,20000003,55,F,London3,30000001,30000002,30000003,13,M,London4,40000001,40000002,40000003,54,F,London

The dialler should attempt to dial all numbers if the previous numbers are failing.

Quota section

This section will allow you to see campaign associated Quota records

Completion code section

This section will allow you to see campaign associated Completion code records

The column for Dialler shows what codes are fixed within the dialler, you can add additional completion codes to use with the as completion codes within the CATI Interviewer