Now that you understand how to create a target, let’s review how quota targets actually work. As discussed above, targets are criteria-based, and they offer conditional statements that indicate the circumstances under which the system should stop dialing leads.
Say you’re conducting a survey, and you’re only looking to dial 50 women over the age of 35. This statement represents your target. Now, since the maximum you wish to dial is 50 women, your target count would be 50, your first comparison would be ‘females,’ and your second comparison would be ‘over 35 years of age.’
To relay this information to the system, you’ll first want to set the Target Count to 50, which will represent the 50 females over the age of 35 that you wish to dial before the system will cease dialing any leads that meet the criteria in this target.
After providing the target count, the comparison statement is next. The Field setting is first and it will tell the system which column in your lead list file contains data related to your first comparison, which in this example is the gender of each lead. Later, when we upload the new lead list, we’ll map this lead gender column to the Aux Data 1 field, so in the Field dropdown menu of the comparator statement, we’d want to select the Aux Data 1 option.
Next, you’ll want to indicate to the system what information to look for in that Aux Data 1 column. In this case, we would input ‘Female’ in the Criteria Value field.
After that, you’ll want to select a comparator from the Comparator dropdown menu to use when analyzing the Criteria Value you indicated above. Since you only want the system to dial female leads, you must let the system know that the data in the lead gender column has to be an exact match to the word Female. To do so, you would select the Equal to comparator.
Now let’s add our second comparator statement. When you wish to apply multiple statements, you can click the blue Add another comparison text at bottom right to reveal an and/or toggle button and a new empty comparison statement for you to configure.
All statements linked via the and option will be given equal weight; the system will continue down your statement list, satisfying all the indicated requirements before it considers the task complete.
Any statements linked via the or option will be considered a strictly either/or command, which means that even if only one of the three or statements matches any leads on your lead list, the system will dial on any of the three comparison statements (that have matching inputs) in question.
So using the example above, let’s say we’d like to create another conditional statement to indicate that the system should also look at another field that contains information on the lead’s age. Later, when we upload our new lead list, we’ll map this lead age column to the Aux Data 2 destination.
In the new conditional statement, we’ll set the and/or toggle to and because not only do we want the system to dial female leads, we only want the system to dial the female leads that are over the age of 35. In the second comparison, we’ll set the Field setting to Aux Data 2, the Comparator to Greater Than, and the Criteria Value to 35.
Now we have two comparator statements that will tell the system to perform the following task:
If the fields selected in the Field setting (in this case, Aux Data 1 and Aux Data 2) is exactly equal to whatever you input in the Criteria Value fields (‘Female’ and 35), then only dial 50 leads who meet this criteria (that is, those who are female and over the age of 35), and stop dialing leads that match this criteria once you reach the specified target count (50 females over the age of 35).
Altogether, these statements might look something like this: