lead_filter

What Lead Filter Does

A SQL WHERE clause expression applied to lead records before they enter the hopper. Allows granular filtering by any lead field — state, zip, custom data fields, source, etc. This enables precise targeting without managing separate lead lists for each segment.

Recommended Configuration

| Center Size | Recommended Value | Notes |

| --- | --- | --- |

| 10–25 Agents | Configure based on campaign targeting needs | Start conservative, monitor for 48 hours before adjusting |

| 25–100 Agents | Configure based on campaign targeting needs | Scale gradually — larger operations amplify effects of misconfiguration |

| 100–500 Agents | Configure based on campaign targeting needs | Consult ViciStack optimization team for enterprise-scale tuning |

How to Change This Setting

• Navigate to Admin > Campaigns

• Select campaign

• Find Lead Filter field (or Lead Filter ID)

• Create filter expressions in Admin > Lead Filters

• Reference the filter ID in this field

• Test with a small list before going live

• Submit

Common Problems

Overly restrictive filters empty the hopper unexpectedly

SQL syntax errors in custom filters cause campaign to stop dialing

Filters not updating when lead data changes mid-campaign

ViciStack Module

ViciStack’s List Management & Optimization module automatically monitors and optimizes lead_filter based on real-time performance data from your operation. Instead of manual tuning, ViciStack continuously analyzes call outcomes, agent performance, and contact rates to recommend and implement optimal values — often catching configuration drift before it affects your numbers.