Lead Screening Tool: How to Qualify Your Leads
Lead Screening Tool Lead screening comes down to list quality: you have records to sort, weak rows to catch, and a next action to choose. Before your...
Marcus focuses on identifying invalid, duplicated, outdated, or high-risk records before they enter CRM, messaging, fraud-review, or customer-acquisition workflows. He writes about responsible verification, data hygiene, lead screening, and the operational limits of phone and account signals.
View full author profile →Lead Screening Tool
Lead screening comes down to list quality: you have records to sort, weak rows to catch, and a next action to choose. Before your sales team wastes time on dead numbers or your campaign spends money on undeliverable ones, run the list through Phone Validator on ZelNum.
The point isn’t a perfect match rate. It’s splitting a raw list into segments your team can act on: route, repair, suppress, or retry.
CSV setup (do this once)
Every row needs a stable ID. Row numbers aren’t IDs — they shift when you sort. One phone column plus source fields is all you need.
| Column | Example | Why |
|---|---|---|
record_id |
crm_10492 |
Join back to source without guessing |
phone |
+14155552671 |
One number per row |
source |
signup_form |
Shows which channels produce bad data |
segment |
trial_users |
Makes post-export reporting easier |
last_updated |
2026-06-18 |
Older records warrant more scrutiny |
After the check, keep the result file next to the source file. Teams that copy only the good rows and dump the rejects end up with no explanation for why half the list failed.
Running the screen
1. Pilot with 500 rows
Run a test batch before the full list. It catches broken encodings, format issues, empty columns, and duplicates. It also tells you roughly what share of your list is usable before you pay for the full run.
2. Export more than pass/fail
| Field | Why |
|---|---|
input_number |
The exact value you uploaded — traceable |
normalized_e164 |
One consistent format downstream |
valid_format |
Format problem, or something else? |
country_or_region |
Routing and regional reporting |
status |
Forward, review, or discard — unambiguous |
3. Route, don’t hoard
valid→ Next workflow. Done.invalid→ Fix or suppress. Don’t keep paying for bad data.unknown→ Retry once. Escalate only high-value records.
Unknown ≠ invalid. Different bucket, different decision.
Decision rules before uploading
| Result | Default | Override if… |
|---|---|---|
| Good match | Route to workflow | Another field on the record looks suspicious |
| Bad format | Fix if source matters | Same source keeps sending broken rows → suppress |
| Wrong channel | Redirect | Only keep if you have a fallback |
| Unknown | Retry once | Manual review for high-value only |
| Duplicate | Keep most trusted version | Merge after confirming ownership |
FAQ
What is lead screening?
It’s the process of validating a list of contacts before sales or marketing acts on it — checking which numbers are real, active, and routable so you don’t waste calls or sends on dead records. Phone validation is the technical backbone; routing rules turn the results into action.
How does lead screening work?
Upload a CSV with phone numbers and record_id. The tool normalizes each number, validates it, and returns status plus supporting fields. You join results back to your CRM and route each row: usable leads forward, bad formats to repair, unknowns to retry, and junk to suppression.
What data can I export from Phone Validator?
Original input, normalized E.164 value, status, reason code, checked timestamp, and the fields the tool returns. Keep unknown rows separate from failures — they’re different decisions.
Can I run this in bulk?
Yes. Upload a CSV with one phone per row, a stable record_id, and source fields to trace bad data to its origin. A 10K-number list finishes in a few minutes.
What should I do after reviewing Lead results?
Split into usable, repair, suppress, and retry groups. Route only the right records — don’t push the whole list through one channel.