Verify a Wiza Export Before Your Sequence: A Pre-Send Routine

What Wiza's plans include

From Wiza's pricing page, read on 6 November 2026, per user:

Plan	Yearly billing	Included
Free	$0	20 valid emails, 5 phone numbers
Email	$83 a month, billed $990 a year	Unlimited email reveals, $0.35 per phone number, 2,500 exports a month
Email + Phone	$166 a month, billed $1,990 a year	Unlimited email and phone reveals, 2,500 exports a month

With monthly billing, the page showed tiers at $49, $99 and $199 a month. The sign-up box offers 25 free credits with no card.

Note the wording on the free plan: "valid emails". That suggests Wiza checks emails before counting them, which is good. The page doesn't say how, when, or what it does with catch-all domains. So treat "valid" as "valid when Wiza checked", and check again before you send.

Why a Wiza list still bounces

Wiza builds lists from LinkedIn and Sales Navigator, where profiles are often updated late. Common causes of bounces on these lists:

1. Job changes. The profile still shows the old employer; the mailbox has been closed. That's a 550 5.1.1 hard bounce. See hard bounce vs soft bounce.
2. Catch-all domains. Many company domains accept mail for every address, so a check can't confirm the mailbox. Some of these bounce after the server has accepted them.
3. Time between export and send. Lists sit for weeks in a CRM before a sequence picks them up.
4. Your setup, not the list. A new inbox with no warm-up, or a domain without SPF and DKIM, gets blocked; those rejections look like bounces. Check with the cold email domain checker.

Most cold email platforms start worrying above about 2% hard bounces. See Instantly bounce rate and what to do after a high bounce rate.

The pre-send routine

1. Export with the LinkedIn URL

Export the Wiza list to CSV with the profile URL, name, company and email columns. The URL is your key for mapping results back to the CRM. If you'll call, keep the phone column and don't open the file in Excel first (it strips leading zeros).

2. Clean the obvious

• Remove duplicates with remove duplicate emails.
• Strip role addresses (info@, hello@) from person-level campaigns with the role-based email filter.
• Cap people per company with limit contacts per company so you don't hit one domain twenty times.

3. Verify every row

Upload the file to the verify page or the CSV email verifier. You get each row back with a status and the reason:

Status	Meaning	Action
Valid	Server accepted the mailbox	Main sequence
Risky (catch-all)	Server accepts every address; graded higher, medium or lower likelihood	Second batch, best grades first
Risky (role, disposable, full)	Real but poor targets	Usually drop for cold
Invalid	Mailbox or domain doesn't exist	Suppress
Unknown	No answer from the server	Re-check tomorrow

SimpleVerifier never marks a catch-all valid. It reports them risky and grades them with the reason, so you can see why (how grading works).

4. Phones, if you'll call

The same upload validates any phone column against its country's numbering plan, writes it in E.164 and tags country and type. For US numbers where you need mobile vs landline, add a live carrier lookup. See validate Apollo phone numbers for the column-choice rules, which apply to Wiza exports too.

5. Send in two waves

• Wave 1: valid rows.
• Wave 2: higher-likelihood catch-alls, a few hundred at most, a day later. Stop if hard bounces in this wave pass 2%.
• Suppress: invalid rows, in the sequencer itself, so a future import can't re-add them. See suppression list from lemlist and Instantly.

You can also verify after import: SimpleVerifier connects to Instantly, Smartlead and lemlist.

The bounce math on a big export

Say you export 5,000 leads and 4% would hard-bounce today, some from job changes, some from closed mailboxes. Sending blind gives you about 200 hard bounces, spread across your inboxes. At 50 sends a day per inbox over 10 inboxes, that is roughly 20 bounces a day, a 4% bounce rate every day of the campaign. Those are illustrative numbers, but the shape is typical: a few percent of dead rows is enough to push every inbox over the line. Plug your own figures into the cold email bounce cost calculator.

Can't I rely on the sequencer's own check?

Some sequencers verify leads on import or offer verification as a paid add-on. That helps, but check three things first: whether it runs a live mailbox check or only syntax and domain checks, what it does with catch-all rows (pass them, block them, or flag them), and whether it charges per lead. If catch-alls are passed through silently, you lose the two-wave send above. Running your own check first keeps that decision in your hands.

What it costs to check

Unlimited reveals and per-check verification credits don't mix well. SimpleVerifier is flat:

• Pro, $39 a month: Unlimited email verification.*
• Starter, $9 a month: 2,500 emails a month.
• Free: 100 checks with a Google sign-in, enough for a sample.

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

Pro includes phone format checks, the email finder, an API and an MCP server. Live carrier lookups are on Pro + Phone ($49.99 a month, 5,000 a month). See pricing.

Not sure the list needs it? Sample 200 rows with the email list sampler and verify them free. If 10% or more come back invalid, the whole segment is stale.

More reading: verify a Kaspr export, why cold emails bounce, verify Instantly leads with the native integration, catch-all leads in sequences.