Key takeaways
- Separate finding an email from deciding whether it is ready to use.
- Use Clay’s validation strategy to make risk tolerance explicit.
- Test a representative sample before running a large waterfall.
- Treat catch-all acceptance as a deliberate policy choice.
- Use conditional runs and duplicate thresholds to control credit spend.
Clay email verification is part of a broader data-enrichment decision. A waterfall can find an address from several providers, but the workflow still needs to decide whether the result is safe enough for the next action.
The key setting is not simply which provider runs first. It is the validation policy that tells the waterfall what counts as an acceptable result.
Finding is not validation
A person’s name, company, and domain may be enough to find a work address. That does not prove the address is deliverable. Keep two questions separate:
1. Did the workflow find an address? 2. Is the address good enough for this use?
Configure the waterfall around risk
Clay’s Work Email waterfall documentation describes conservative, balanced, aggressive, and advanced validation strategies:
- Conservative prioritizes certainty and sender reputation.
- Balanced trades some certainty for more coverage.
- Aggressive maximizes coverage when review and testing exist.
- Advanced lets a team define exact accepted statuses.
There is no universal best setting. Signup, high-value account research, and broad prospecting should not necessarily use the same rule.
Handle catch-all deliberately
Catch-all domains accept mail broadly, which can make a found address look better than the evidence supports. Options include keeping catch-all in a separate field, excluding it from high-risk sends, testing a small monitored segment, requiring a second signal, or holding for review.
Do not silently mix catch-all rows into the ordinary valid bucket when campaign reports depend on a clear quality threshold.
Control credits and repeated work
Test a small run across industries and domain types. Inspect validation columns, confirm status mapping, check duplicates, estimate credits, and save the configuration. Clay documents controls such as infer-email, conditional runs, and duplicate thresholds that can stop a waterfall from spending after the answer is already clear.
Keep a simple output schema:
| Field | Why it matters |
|---|---|
| Original email | Audit and display |
| Normalized email | Matching and deduplication |
| Verification status | Product-level decision |
| Catch-all flag | Risk segmentation |
| Checked at | Freshness |
| Lead ID | Join back to CRM or sequencer |
If you need a separate bulk check outside the enrichment table, VeriMailX can process a CSV list and return a row-level verdict for mapping back into Clay.
The bottom line
Clay email verification is strongest when the waterfall is treated as a policy engine, not just a coverage machine. Define “good enough,” make catch-all handling visible, test before scaling, and keep each result linked to the original lead.
Sources
- Clay: Work Email waterfall
- Clay University: Enrich people with waterfalls
- Clay: Waterfalls
- - VeriMailX bulk email checker
Frequently asked questions
Ready to clean your list?
Verify your emails with VeriMailX and send your next campaign with more confidence, fewer bounces and better results. Unlimited free single email verification — no card required.