An agency sends from domains it does not own, with lists it did not build, on a reputation it will be blamed for. That is why email verification for agencies belongs in the intake process rather than in the scramble after a campaign goes sideways. The rule that prevents most of the damage fits on one line of an onboarding checklist: no client list enters a campaign until it has been verified, and nothing older than about 30 days goes out without a fresh check.
The rest of this is how to run that rule across several accounts at once, what to hand the client as proof you ran it, and how to keep one messy account from spoiling the others.
The exposure is different when the list is not yours
A client sends you a spreadsheet and calls it “our list.” You rarely get its history. It might be a CRM export nobody has opened since 2022, a stack of trade show badge scans, or a purchase that felt like a shortcut at the time. You inherit all of it, including the parts the client has genuinely forgotten about.
Send to that file unverified and two failures arrive in the same week. The client’s sending domain (the domain in your from address, the one receiving servers judge when they decide between the inbox and the spam folder) picks up a bounce rate that mailbox providers read as carelessness. Meanwhile your campaign report shows weak opens and almost no replies, which looks to the client like an agency that cannot write. Same event, two bills to explain.
Bought lists deserve their own warning, because clients bring them more often than they admit to. We went through what buying an email list really costs separately, and the number on the invoice is the smallest part of the total.
Then the problem specific to agencies: shared infrastructure. If every client runs through one sending platform on one pool of IP addresses, the fallout from one bad list does not politely stay inside that account. Reputation attaches to the sending identity, and a shared identity shares its bad weeks.
What email verification for agencies actually protects
Worth naming the assets out loud while the client is in the room. Their domain, which they keep long after your contract ends. Your campaign numbers, the only evidence of your work. And the sending setup every other account shares, which nobody is paying you to protect, though it decides how the next client’s first campaign lands.
The intake rule, written where someone will see it
Put it in two places and it survives a busy quarter.
First, the onboarding checklist, as a step with a box next to it: list verified before anything gets scheduled. Checklists outlive whoever wrote them, and they do not care how hectic the week is.
Second, the scope of work. One plain sentence covers it: lists are verified before sending, addresses that come back invalid or disposable are removed, and the client sees the breakdown. That sets the expectation in week one that part of their list will be deleted, which is a far easier conversation than the same one in week six with a bounce report attached. Worth adding in the same breath that how the list was collected, and whether those people agreed to hear from the client, stays on the client’s side of the fence.
A workflow you can run per client
The underlying sequence of finding, verifying, segmenting and sending is laid out in our B2B outreach workflow. What follows is the agency layer that sits on top: the same work, repeated per account, with a record at every point where a client might later ask “what did you do with our data?”
Verify at intake, before the calendar fills up
Run the whole list the day it lands, not the night before the first send. You need the invalid share for the kickoff conversation, and if 40% of the file is dead you want that known while the schedule is still a draft and nobody has promised a volume target.
Split by status, and decide once per client
Verification returns a status per row. Invalid addresses go, and disposable ones (throwaway addresses from temporary mail services) go with them. Role addresses such as info@ or sales@ are a judgment call that depends on the client’s market: at small local businesses they often reach the owner directly, at large companies they reach a queue nobody owns. Catch-all addresses, where the domain accepts mail for any name so the server will not confirm whether that one mailbox exists, get their own segment and go out after the main batch has proved clean.
Make those calls once per account, write them in the client folder, and stop relitigating them before every campaign.
Re-verify anything older than about 30 days
Lists rot quietly while you are busy with other accounts. People change jobs, mailboxes get closed, small companies fold, domains lapse. A file verified in March and sent in July is a raw list wearing a verified label, and the bounce report will say so.
Keep one suppression list per client, permanently
A suppression list is the standing record of addresses and domains you will never contact again: hard bounces, opt-outs, complaints, and anyone who asked to be left alone. One per client, checked against every new upload, including the list they send you eighteen months from now after a quiet period. This is the artifact agencies most often lose during staff turnover, and losing it means writing again to someone who already said no.
Report the invalid share to the client
Two lines in the campaign report: what arrived, what survived, what was removed and why. It costs nothing, it explains your send volume before anyone questions it, and it quietly demonstrates that the list was the constraint rather than the creative.
Verify at the point of entry on client forms
For clients whose lists grow through a signup or lead form, checking each address as it is typed stops the mess accumulating between campaigns. Our comparison of real-time and bulk verification covers when each one earns its place. Most agency accounts end up using both: bulk for what the client hands over, real-time for what the client’s website collects from here on.
The list health report as an onboarding artifact
Package the intake verification as a deliverable and it stops being an invisible cost. A one page report per client, produced during onboarding, covering:
- The share of addresses that came back invalid
- The share that were disposable
- The share that were role based, with your recommendation for each group
- The share sitting on catch-all domains, and how you plan to treat them
- The size of the segment that is genuinely ready to send
One caveat belongs on that page in writing. These numbers describe the quality of the list, and nothing more. A clean list is a condition for good results, not a promise of them, and an agency that lets a client read it as a forecast has created a problem for itself three weeks out.
Protect your own reputation, not only theirs
Client work accumulates on your infrastructure, so separation is the whole game.
Give each client their own sending domain. Our piece on using a separate domain for cold email explains why that matters even for a single sender, and the argument gets stronger with every account you add. Never run two clients through one sending domain, however tempting it looks on setup day.
Authenticate every domain individually. SPF, DKIM and DMARC are the DNS records that let receiving servers confirm mail genuinely came from that domain, and they belong to the domain rather than to your agency.
Then warm-up: sending small and slowly rising volumes from a new domain over several weeks so it builds a normal history instead of appearing from nowhere with a thousand messages. It takes longer than most onboarding timelines assume, which is why how long domain warm-up takes belongs in the proposal conversation. Watch each domain’s standing afterwards too: our guide to checking sender reputation covers the tools that show what providers already think.
Several people, one pile of client data
In a two person shop everyone knows who uploaded what. At six people across three accounts nobody does, and that is when a list gets mailed twice or a suppression file gets skipped.
Keep a plain log: client, file name, date verified, who ran it, what the split was. A shared spreadsheet is fine. Give each person their own login rather than passing one set of credentials around, and remove access when someone leaves.
Where Reoon fits. The Reoon Email Verifier covers both halves of this: bulk CSV upload for the lists a client hands over, and an API for checking addresses live on the client’s own signup forms. Results separate catch-all domains, disposable addresses, known spam traps and role based accounts, and unknown results are never charged, so an unclear server response does not eat into a client’s budget. On data handling, uploads are encrypted with AES-256 and deleted from the servers after 15 days by default, which is a useful line to have ready when a client asks where their contacts went. Registration gives free daily credits with no card, enough to run a sample of a new client’s list before you quote the work.
The agency moments that decide the outcome
| Agency moment | The risk | What to do | What the client gets |
|---|---|---|---|
| New client onboarding | Inherited list of unknown age and origin | Verify the full file before anything is scheduled | A list health report with the invalid, disposable, role and catch-all shares |
| Before each campaign | A stale file treated as fresh | Re-verify anything older than about 30 days | A line in the plan confirming the send list was re-checked |
| A “fresh” list arrives mid-flight | Unverified rows slip into a running sequence | Hold the batch, verify it, check it against the suppression list | The new contacts counted separately in the report |
| Bounce rate climbs mid-campaign | The client’s domain reputation drops | Pause sending, re-verify what is left, find the source | An honest status note and a corrected send list |
| Client pushes for more volume | Pressure to mail catch-all and unknown rows | Send the safe segment first, catch-all later in a small batch | Your reasoning in plain words, before they have to ask |
| Engagement ends | Bounces and opt-outs scattered across tools | Consolidate them into the client’s suppression list | A suppression file that belongs to them |
An honest opinion about “your campaign did not work”
Agencies that verify at intake seem to lose fewer clients to that conversation. Not because their campaigns always perform, but because when one underperforms they can put a report on the table showing that a third of the supplied list was undeliverable before anyone wrote a subject line. It becomes a joint problem about lead sources. Without that report it stays a complaint about the agency, and you argue from memory against a client holding a spreadsheet.
That is experience rather than a measured claim, and it has limits. Plenty of campaigns fail with a spotless list because the offer was wrong, the targeting was lazy, or the market was saturated. Verification saves none of those. It removes the one failure that is both entirely preventable and impossible to prove after the fact.
If you want to see where a new account really stands, run the next list that arrives through a verifier before you write the campaign plan. Free daily credits are enough for a sample of a few hundred rows, and the invalid percentage you get back is the most useful number in the kickoff meeting.
FAQ
Should the agency or the client pay for email verification?
Either works, as long as it is decided in the contract rather than argued about later. Many agencies fold it into the setup fee and present the list health report as part of onboarding, which makes the cost invisible and the value visible. Others bill verification at cost per account. What causes friction is discovering the question mid-campaign, when the answer feels like a surprise charge.
What do we do if a client refuses to let us clean their list?
Put the risk in writing, then decide whether you want the campaign. Explain that the bounces will hit their domain and that the reputation damage outlasts the campaign by months. Some clients change their minds once it is framed as their asset rather than your preference. If they still insist, send in small batches from a domain used only for that client, and stop at the first bad bounce report.
How often should we re-verify a client’s list?
Before every campaign if the list has been sitting for more than about 30 days, and always after any gap in sending. Lists decay continuously, and faster in industries with high staff turnover. Addresses collected through a form and verified on entry are the exception: those are checked already and only need re-checking if months pass before the first send.
Can we use one verification account for all our clients?
Yes, and most agencies do. The separation that matters is on the sending side, where each client needs their own authenticated domain and their own suppression list. Verification is a lookup, so running several clients through one account causes no cross-contamination. Keep the uploaded files clearly named per client, log who ran what, and delete finished files rather than letting them pile up.
