Use case · SimpleVerifier Team
Email verification for marketing agencies
Agencies send lists they did not build: client CRM exports, inherited newsletters, event lists. Verify each client's list before its first campaign through you, keep each client's files separate, and audit the client's sending domain at the same time, because a clean list on a domain with broken SPF or DMARC still struggles to reach the inbox.
When a campaign underperforms, the agency gets the blame whether the problem was the creative, the list or the client's DNS. Checking the last two at onboarding takes minutes and tells you which conversation to have.
What agencies inherit
You don't know how the list was built
A client's list may include purchased contacts, scraped addresses or years-old imports. Ask, and verify before the first send. If the answer is 'we bought it', read purchased lists before going further.
One client's bad list can hit a shared account
HubSpot, Brevo and Amazon SES act on the whole account when bounce or complaint lines are crossed; HubSpot's line is a 5% hard bounce rate in a month and Brevo's is 2%. If several clients send through one account, one bad import can stop all of them. Sources in bounce limits by platform.
Authentication problems look like list problems
Missing DKIM, a DMARC record that fails alignment or a blocklisted IP all show up as poor delivery. Run the deliverability audit on the client's domain before you blame the list.
Metered pricing punishes re-verification
Re-checking a client list before every campaign is the right habit, and on per-credit pricing it is also a line item. On Pro, verification is not metered, so re-runs do not change the bill. The cost calculator compares per-address pricing.
An onboarding checklist for a new client
Audit the sending domain
Run the deliverability audit, then the SPF, DKIM and DMARC checkers and a blocklist check on anything it flags.
Export the client's list from their platform
Guides for HubSpot, Mailchimp, ActiveCampaign and 36 more tools on the export hub.
Verify and report the split to the client
Share the valid, risky and invalid counts with the client before the first send. It sets expectations and documents the list's condition when you took it on.
Import the valid file; agree a rule for risky
Decide with the client whether risky addresses are mailed, and how, based on what kind of list it is.
Re-verify on a schedule
Before each major campaign or quarterly, whichever comes first.
What to tell the client about each result
| Result | What to do | Why |
|---|---|---|
| valid | Ready to send | Confirmed by the recipient's server. |
| risky | Client's call, with your recommendation | Catch-all, role or unconfirmed. Mail if they are engaged customers; hold if it is a cold or old list. |
| invalid | Remove before your first send | Would bounce on your watch. |
Common questions
- Can an agency verify lists for several clients on one account?
- Yes. Upload each client's file as its own job and download its results separately. Pro has no monthly verification cap, so the number of clients does not change the price.
- Should we verify a client list before the first campaign?
- Always. You do not know the list's history, and its first bounces land on the sending setup you manage.
- What else should we check besides the list?
- The client's sending domain: SPF, DKIM, DMARC alignment and blocklist status. Poor authentication causes delivery problems that no list cleaning can fix.
Verify client lists
Pro is $29.99 a month with no cap on verifications: CSV uploads, the API, the Google Sheets add-on and the email finder are all included. Cancel any time.
See plans and pricing