Verify a Voila Norbert Export Before You Send

What Voila Norbert says about pricing and verification

From Voila Norbert's pricing page, read 9 November 2026:

• Prospecting plans run from Valet (up to 1,000 leads a month) to Counselor (up to 50,000 leads a month), and the page lists credit rollover on all four.
• Sequences plans (Starter, Teams, Scale) list Email Verification as a feature.
• Pay-as-you-go verification is "$.003/email up to 500k and $.001/email above that. $2 min." Enrichment is listed separately.
• The FAQ says it counts "only successful email founds," and that new accounts get 50 free credits.

The page doesn't say how verification works, what happens on catch-all domains, or how long a result stays fresh. That is common for finder pricing pages, and it is the reason a send-day check belongs in your routine. For plan-by-plan context see Voila Norbert alternatives.

Why a found email can still bounce

• Catch-all domains. The server accepts every address during a check, so no finder or verifier can confirm the mailbox. Some bounce after the send (what to do with catch-all emails).
• Age. A find done weeks ago and exported today. People move jobs often (email valid but person left the company).
• Mixed files. A Voila Norbert export merged with another source. One file, several ages of data.
• Guessed patterns. Any row built from a company naming pattern instead of a confirmed mailbox is the likeliest to bounce. Verify those first.

The export-to-send routine

1. Export to CSV and keep context

Keep email, first name, last name, company, domain and any source column. A source column lets you compare bounce rates by origin later (bounce rate by source).

2. Clean the file

• Remove repeats with remove duplicate emails.
• Cap people per company with limit contacts per company, so one bad week at a company doesn't hit six inboxes at once.
• Tag catch-all domains with the bulk catch-all checker.

3. Verify every row

Upload the file at /verify. Each address gets a live SMTP check:

Result	Action
Valid	Main sequence
Risky (catch-all)	Second wave, best grades first
Risky (role, disposable, full)	Drop for outreach
Invalid	Suppress
Unknown	Re-check tomorrow

SimpleVerifier reports catch-alls as risky with a grade and a reason, never as valid (catch-all scoring).

4. Send in waves

Valid rows first. Catch-alls a day later, a few hundred at most. Stop that wave if hard bounces climb past your platform's pause line; bounce rate thresholds by platform lists them.

5. Test a new source before you scale it

If Voila Norbert is new to you, send a small sample and measure before loading the whole list. Test a new lead source explains how.

Do you need both a finder's verification and a separate check?

Using the finder's own verification is a fine first pass, and for a small list it may be all you need. A separate check earns its place when:

1. The file is more than a few days old.
2. You merged exports from several tools.
3. You send from a new domain with little reputation, where each bounce counts for more (email warmup schedule covers ramping one up).
4. You want a risky bucket with reasons rather than a pass or fail.

If the finder's price per email is low and your list is small, the extra step costs little. At volume, a flat plan keeps it predictable. See the bulk email verifier page for how options compare.

What to do with each group after the check

Valid rows go into your main sequence. Keep the verification date in a column.

Risky catch-all rows are the judgment call. A catch-all server accepts anything during the check, so the best any tool can give you is a grade and a reason. Send the best-graded rows a day after the valid wave and stop if bounces rise. Weak grades can wait for a later campaign.

Risky role, disposable and full-mailbox rows are poor outreach targets. Role addresses like info@ rarely reach a decision maker, disposable addresses vanish, and a full mailbox defers or bounces.

Invalid rows go to your suppression list so they never return in a future import. Cold email suppression lists covers the setup.

Unknown rows mean the server didn't answer in time. Retry the next day before deciding.

Keeping the habit cheap

A check only becomes routine if it is cheap enough to run every time. A flat monthly plan means you don't count rows or pick a pack size first. Compare approaches on the bulk email verifier page, or read how the fair-use line works at unlimited email verification.

Mistakes that turn a good Voila Norbert export into a bounce problem

1. Verifying once and sending for weeks. A check is a snapshot. If the campaign runs over several weeks, re-check the rows you haven't mailed yet before each batch.
2. Loading everything into one step. Even a clean list should go out in waves. If something is wrong with a domain or a segment, a wave catches it before the whole file is gone.
3. Merging suppression files too late. Add your suppression list before you verify, not after, so you never spend a check on someone you can't mail.
4. Treating risky as valid. Risky means the server wouldn't confirm the mailbox. It is a decision to make with a smaller batch, not a pass.
5. Ignoring the first bounce messages. The first few bounces tell you whether the problem is the list, the domain or the content. Paste them into the bounce message analyzer before you send more.
6. Skipping authentication. A clean list on a domain with failing SPF, DKIM or DMARC still lands in spam. Run the email domain health checker once a month.

Quick answers

• Is a Voila Norbert "found" email verified? The page describes found emails and sells verification separately. Check it again before sending.
• What do I do with catch-all rows? Send them after the valid rows, in a small batch, and watch bounces.
• How often should I re-verify? Before each send of an older file; how often to verify an email list gives a schedule.

Try it on your own export

Upload a slice at /verify. The first 100 checks are free with a Google sign-in, no card.

Pro, $39 a month: Unlimited email verification.* Never metered, never cut off. See pricing.

*Fair use: the first 100,000 checks a month at full speed, then slower, never cut off.