Validation Approaches
Pre-Import Batch Validation
Validate lists before importing to your dialer:
- Export list from CRM or lead source
- Upload to VeriRoute Intel batch processor
- Preview results before paying
- Download enriched CSV
- Import only valid numbers to dialer
Best for: Large campaigns, list purchases, periodic data refresh
Real-Time Pre-Dial Validation
Validate each number moments before dialing:
# Dialer integration pseudocode
def before_dial(phone_number):
result = veriroute_lookup(phone_number, lrn=True)
if result['lrn']['status'] == 'disconnected':
return SKIP_AND_FLAG
elif result['lrn']['line_type'] == 'landline':
if is_business_hours():
return SKIP_FOR_LATER # Call evenings
else:
return PROCEED
else:
return PROCEED
Best for: High-value contacts, compliance-sensitive campaigns
Hybrid Approach
Most call centers use both:
- Batch for initial list cleaning and periodic refresh
- Real-time for new records and callback numbers
Clean your dialer list. Batch validation with preview before payment.
Try Bulk UploadDialer Integration Patterns
Predictive Dialers
Predictive dialers benefit most from pre-validated lists:
- Algorithm works better with accurate abandon rates
- No wasted over-dialing on invalid numbers
- Better agent utilization predictions
Progressive Dialers
Progressive dialers can use real-time validation:
- Validate while agent wraps previous call
- Skip invalid numbers without affecting pace
- Display enriched data to agent before connect
Power Dialers
Power dialers benefit from both approaches:
- Batch validate for initial list quality
- Real-time check before presenting to agent
- Flag records for list management
Useful Data Fields
| Field | Use in Dialer |
|---|---|
| is_valid | Skip/include in dial list |
| line_type | Campaign segmentation, time-of-day routing |
| carrier | Least-cost routing decisions |
| cnam | Agent screen pop, personalization |
| last_validated | Trigger re-validation for stale data |
Implementation Steps
1. Export and Validate
# Export from dialer to CSV
dialer_export.csv:
phone,first_name,last_name,lead_source
5551234567,John,Smith,website
5559876543,Jane,Doe,trade_show
...
2. Batch Process
# Upload to VeriRoute Intel
# Returns enriched CSV with:
phone,first_name,last_name,lead_source,is_valid,line_type,carrier
5551234567,John,Smith,website,true,wireless,Verizon
5559876543,Jane,Doe,trade_show,false,disconnected,
3. Import Valid Records
# Filter and import
valid_records = [r for r in results if r['is_valid']]
mobile_campaign = [r for r in valid_records if r['line_type'] == 'wireless']
landline_campaign = [r for r in valid_records if r['line_type'] == 'landline']
Best Practices
- Validate before import — Don't pollute your dialer with bad data
- Store validation date — Track when records were last checked
- Re-validate periodically — Numbers change status over time
- Segment by line type — Different calling strategies
- Flag disconnected — Don't delete, flag for suppression