QuickMail Prospect Import: Verify the CSV Before It Reaches a Campaign
QuickMail imports what you give it; it doesn't check whether the mailboxes exist. The CSV import maps columns and rejects duplicates, and verification is an add-on from a separate provider. So the cheapest place to catch dead addresses is the file itself, before it's a prospect list attached to a campaign and a sending inbox.
Sources, read 2 November 2026: QuickMail's integrations page, its knowledge base articles importing prospects from CSV and import report FAQ, and Bouncer's QuickMail integration guide. The QuickMail help site returned errors when we tried to load it directly, so its import details come from search-engine copies of those articles; check the import screen in your own account.
What QuickMail does on import
| Step | What happens |
|---|---|
| File format | Comma-delimited CSV. Semicolons and other delimiters aren't supported. Only the first sheet is imported. |
| Column mapping | Email, Firstname, Lastname and Company map automatically; other headers are mapped to attributes by hand |
| No company column | The email domain is used as the company name |
| Duplicates | Rejected, reported as "Email has already been taken" |
| Import Report | Emailed to Team and Agency admins with counts and rejected rows |
| Mailbox check | Only through a verification add-on (NeverBounce, BriteVerify, ZeroBounce, Dropcontact, Hunter, Bouncer) |
Step by step
- Combine and dedupe the sources. Lead files from several tools overlap. The remove duplicate emails tool drops repeats so the Import Report isn't full of "already taken" rows.
- Take out anyone you shouldn't email. Past unsubscribes, bounces and "not interested" replies from older campaigns; a cold email suppression list explains what to keep on it.
- Verify the file with the cold email list checker or on the verify page. Remove invalid results.
- Split risky from valid. Catch-all company domains accept every address, so a single mailbox can't be confirmed. Put those in their own campaign at a lower daily volume; catch-all leads in sequences covers how.
- Save as a comma-delimited CSV on one sheet, with Email, Firstname, Lastname and Company headers. The CSV import formatter fixes headers and delimiters, which matters if your spreadsheet app exports semicolons by default (common with European locale settings).
- Import, then read the Import Report before attaching the list to a campaign.
If you already pay for a QuickMail verification add-on, you can skip step 3 and let it run; just don't do both on the same file.
What verification can't settle
Verification confirms that a mailbox accepts mail. It can't confirm the person still works there next month, and some servers won't confirm a single mailbox: catch-all domains accept everything, and Microsoft consumer mailboxes (outlook.com, hotmail.com) often don't answer the check reliably. Those come back risky or unknown, not invalid. Send them after the confirmed group and let real bounces decide. Lists that sit for weeks between export and sending decay; re-check anything older than a couple of months.
Where SimpleVerifier fits
Verify the prospect file on the verify page; the first 100 checks are free with a Google sign-in. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See pricing, or Klenty and Mixmax list prep if you also run other sequencers.
Common questions
Does QuickMail verify email addresses on import?
Not by itself. QuickMail connects to verification providers as add-ons (its integrations page lists NeverBounce, BriteVerify, ZeroBounce, Dropcontact, Hunter and Bouncer). Bouncer's integration guide places the setting under Settings, then Add-ons, then Email Verification. Each provider charges for its own checks.
Why did QuickMail reject rows from my CSV?
The Import Report email lists rejected rows and the reason. 'Email has already been taken' means the prospect already exists in your account; duplicate addresses inside the same file are another common cause. A semicolon-delimited file or a workbook with data on a second sheet will also import badly.
Should I verify before importing or use a QuickMail add-on?
Either works; doing both pays twice. Verifying before import lets you drop invalid rows, keep risky ones in a separate campaign and import a file that's already clean. An add-on is simpler if you add prospects one at a time from other integrations.
What bounce rate should a cold campaign stay under?
QuickMail doesn't publish a hard limit for this, but mailbox providers judge your sending domain on bounces. Most cold email teams aim to keep hard bounces well under 2%; see bounce rate thresholds by platform for the published numbers from sending tools and ESPs.
Check your list before you send
Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.