Custom Query in SpitFire
The Custom Query option in SpitFire Predictive Pro and SpitFire X Pro systems allows you to specify records to be dialed, based on the data that has been imported with ListMaker Pro.
For instance, if you wanted to dial only a certain city within a list of 10 cities, you can input a Query into the Campaign window Preferences that would do that. This can be changed in mid-campaign so that you do not need to stop dialing to start dialing a different city or zip code, etc.
Note: This feature ONLY applies to the Pro (MySQL) versions of the SpitFire software.
Accessing the Custom Query Field
1. From the Campaign window in SPD or SPX, click on Options-->Preferences-->Database Settings
At the bottom of that tab is a Custom Query: field. This is where a specific query can be input.
2. In the example below, we have set it to dial only Dallas records in the list.
Note: This would apply to any list that had been loaded into the Campaign window.
3. Click OK and the change will take effect as soon as the records that were already in queue have been dialed.
Custom Query Rules and Samples
If you are familiar with MySQL queries, you may have noticed that the Custom Query in the example above is only a partial statement. This is because the 'select' part of the statement has already been hard-coded. So you only need to set the part of the query to indicate what parameter you want to apply to the select query.
Here are some examples:
Dial one city or one zipcode:
Dial more than one city:
and (city='dallas' or city='toledo' or city='new york')
Notice that capitalization is not important. The city part of the query could be changed for zipcode or state or even Spare1 through Spare10. Any field that has data imported in it can be used.
Dialing by partial field name can be done with the like command and % sign.
For instance, if you wanted to dial all the records on a particular street:
and address like '%Dallas Pkwy'
and (address like '%Dallas Pkwy' or address like '%commonwealth dr')
Dialing by two different parameters:
and spare2='r003'and zipcode='79835'
In this example we have mapped the Carrier Route to the Spare2 field and are using it and the zipcode field.
Note: These settings will be subject to Global parameters in your Campaign like the FailSafe Schedule, Time Zones, CallBacks and of course if the list has available records that fit within the parameters you have specified in the Custom Query.
A common issue is to load a list of records into the Campaign window that do not have any fields matching the Custom Query. An Example would be ifyou had set the Custom Query to dial only Dallas records but had loaded a list of California records into the Campaign. This would, of course, not work.
No related articles were found.
No attachments were found.
20th of March, 2009