Verify a SalesQL Export Before You Send

What SalesQL says

From SalesQL's pricing page, read 9 November 2026:

Plan	Price	Reveal credits a month	Verifier credits a month
Free	$0	50	100
Basic	$39	2,000	5,000
Professional	$79	5,000	10,000
Premium	$119	12,000	20,000

• A reveal credit unlocks a prospect's emails, phones and company data, and the page says you're only charged when it finds results.
• "Verifying an email costs 1 verifier credit," from "a separate pool for checking addresses you already have."
• The page calls the data "high-quality B2B contact data" but gives no accuracy rate, verification method or freshness detail.

Why the verifier pool matters for a cold list

Verifier credits are for addresses you already have, which is the exact situation of a file merged from several sources. The pool is also finite: 5,000 on Basic is 5,000 addresses a month. If your list is larger, you have three options:

1. Verify a slice with the allowance and send to the rest unchecked. Not recommended for cold email.
2. Spread the file across months, which delays campaigns.
3. Verify the whole file with a service priced for volume, then use the SalesQL allowance for single checks in between.

For how plans compare, see the bulk email verifier page.

Why a SalesQL row can still bounce

• Catch-all domains. Nothing outside the mailbox can confirm a catch-all address (catch-all emails: what to do).
• Age. A reveal from weeks ago, exported today.
• Job changes (email valid but person left the company).
• Merged sources. A SalesQL file combined with Sales Navigator or a purchased list. See clean a Sales Navigator lead list for that side.

The send-day routine

1. Export and tag

Keep email, name, company, domain and LinkedIn URL. Add the export date and a source column.

2. Clean

• Remove duplicate emails.
• Clean LinkedIn URLs and dedupe people.
• Limit contacts per company.
• Tag catch-alls with the bulk catch-all checker.

3. Verify

Upload 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

4. Send in waves

Valid first, catch-alls a day later in a small batch. Stop if hard bounces pass your platform's pause line (bounce rate thresholds by platform).

5. Test a new source

If SalesQL is new to you, send a small sample and measure the bounce rate before loading everything (test a new lead source).

What to do with each group after the check

Valid rows go to the main sequence with the verification date in a column.

Catch-all rows go in the smaller second wave, best grades first, and the weakest wait for another campaign.

Role, disposable and full-mailbox rows are poor outreach targets.

Invalid rows go to a permanent suppression file merged into every import (cold email suppression lists).

Unknown rows get one retry the next day.

Budget the check before you buy more reveals

Reveals are what you spend on finding people. The check is what protects the sending domain they will be mailed from. If you're choosing between 2,000 more reveals and a flat verification plan, remember that every invalid address you pay to reveal and then send to costs reputation as well as credits. Unlimited email verification explains the Pro fair-use line.

Mistakes that turn a good SalesQL 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.

A simple weekly rhythm

If you prospect continuously, a rhythm beats a one-off scramble.

• Monday: reveal and export the week's prospects. Note the date.
• Tuesday: clean, tag catch-alls and run the live check on the whole file.
• Wednesday: send the valid wave.
• Thursday: send the catch-all wave if the valid wave's bounces stayed low.
• Friday: add this week's bounces and invalid rows to the suppression file, and record bounce rate by source.

Done weekly, the file never gets old enough to surprise you, and the verifier allowance in your plan can go to the quick single-address checks it suits best.

Sizing the send

Before you load a file, count three numbers: rows exported, rows valid after the check, and rows risky. Your first wave is the valid count. Your second wave is a fraction of the risky count, chosen by grade. Anything beyond that waits. Writing these numbers down for each campaign gives you a record you can compare across sources, and it makes it obvious when one export is much dirtier than the others. If one export comes back with far more invalid rows than usual, stop and look at where the data came from before sending anything to it.

Quick answers

• Can I use only SalesQL's verifier? For a file that fits your monthly pool, yes. Re-check old or merged files on send day.
• Does SalesQL state how accurate its emails are? Not on the pricing page we read.
• What about phone numbers in the export? Phone checks are a separate job; see validate Lusha phone numbers for the approach.

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.