// Recruitment Technology, Recruitment Strategies
Your Cold Outreach Is Sending Interview Invites to Junk
Published: 05 November 2026,
8 min to read
The bottom line
Bulk campaigns and everyday candidate email leave your agency from the same domain. One high-volume send that mailbox providers read as spam drags down everything behind it. Booking confirmations, spec CVs, client shortlists and interview invites land in junk for reasons that have nothing to do with them.
Separating your sending identities and throttling campaign volume is a commercial decision about candidate experience. It belongs with the people who own billings, not with whoever answers IT tickets.
Why a quiet campaign week shows up in your interview attendance
Every agency has one campaign that went to twelve thousand contacts on a Tuesday. Nobody mentioned it again, because the response rate was poor and the matter felt closed. What nobody checked was the damage that send did to the domain reputation the whole business emails from. It shows up later and somewhere else. A candidate never sees a confirmation. A client swears the shortlist never arrived.
Mailbox providers score the domain, not the campaign. Gmail and Outlook watch how recipients treat mail from your sending domain. They apply that judgment to every message carrying it. Your consultants’ one-to-one email sits inside that score with the bulk send, and it cannot opt out.
What does domain reputation actually measure?
Domain reputation is a running score mailbox providers keep on your sending domain. It is built from how recipients behave, not from what your email says. Spam complaints, deletions without opening, replies, hard bounces and spam folder rescues all feed it. Nothing about the quality of your roles enters the calculation.
The thresholds are tighter than most agency owners expect. Google asks senders to keep spam rates below 0.3% in Postmaster Tools. That is three complaints in every thousand messages. One enthusiastic afternoon on a dormant database clears it comfortably.
IP reputation sits alongside it and matters less for most agencies. Teams on Google Workspace or Microsoft 365 send through shared IP pools. The domain is the part you control, and the part you can damage. Your reputation score is visible in Google Postmaster Tools. Free tools will check your blacklist status in under a minute.
Almost nobody looks until something breaks. A quiet week reads as a soft market. It rarely reads as deliverability issues, which is why the problem runs for months before anyone names it.
How does one bulk campaign push interview invites into the spam folder?
Because the campaign and the invite are the same sender as far as Gmail is concerned. A mass send to a stale list produces hard bounces and spam complaints within minutes. The domain’s score drops, and filters start treating everything from that address with suspicion. The next messages out are the ones that matter. An interview invite with a time on it, or a spec CV heading to a key account.
Volume is rising at exactly the moment this gets expensive. Atlas research with more than a thousand agency recruiters found that 61.64% now use AI for candidate outreach or messaging. That turns a four-thousand-contact sequence into a ten-minute job. Sending capacity grew. List quality did not.
The commercial damage is quiet and real. A candidate who never sees the invite is recorded as a no-show. The client hears that as poor candidate control. A client who never sees the shortlist assumes you went slow. Fall-offs and lost exclusivity both start with a message somebody never read.
Candidate experience is where it lands hardest. Asking a senior hire to check their junk folder sets the tone for everything after it. You get one chance at that impression.
Can separate sending domains protect candidate email deliverability?
Yes, and it is the highest-leverage change available to an agency this quarter. Campaign traffic moves to its own subdomain, something like mail.youragency.com. Consultants keep the main domain for one-to-one candidate and client email. Reputation then accrues separately. A rough week on the campaign subdomain never reaches the mailbox your recruiters work from.
Authentication setup has to follow the split, because a new sending domain starts with no history. SPF, DKIM and DMARC records belong on every domain and subdomain you send from. Microsoft now requires all three from domains sending more than 5,000 emails per day to Outlook. The direction of travel across mailbox providers is one way only.
Then warm up the new domain rather than opening with your largest list. Modest daily volume to your most engaged recipients builds a good domain reputation from scratch. Skip that step and your first campaign leaves a domain with no sending history. To a filter, that looks like a spammer who bought a fresh domain on Monday.
Throttling is the other half. Caps on daily sends per consultant keep your sending pattern looking like a business. Stagger them across the week instead of firing everything at nine on Monday. Recruiters rarely argue once response rates move. Personalized candidate outreach at lower volume tends to beat the blast anyway.
Where should list hygiene and sending limits sit in your workflow?
Inside the system your recruiters already work in, running continuously. List hygiene fails as an initiative and works as a default. Four controls carry most of the benefit.
Suppress every address that hard bounced, and anything untouched for two years, before a campaign is built. Cap daily campaign volume per sending identity. Route interview invites, booking confirmations and offer paperwork through the consultant’s own mailbox, and send spec CVs from there too. Then check your score in Google Postmaster weekly, and treat a fall the way you would treat a drop in CVs sent.
Contact records rot faster than anyone budgets for. Data decay turns a once-clean database into a bounce generator. A database that updates itself protects the score that protects your invites. The fix for email deliverability is structural, not a better subject line.
One platform holding all of this is what makes it survive a busy desk. That is what Atlas is built for, an AI-powered CRM that uses agentic AI to strip admin out of recruitment workflows. It runs multi-step outreach campaigns and speculative campaigns in the same platform that stores every candidate email. Interviews are booked through self-scheduling calendar links inside that system. Campaign volume, contact freshness, suppression and one-to-one sending stop being separate tools with separate owners.
The output is the point. Ethea Solutions runs GTM search across APAC on Atlas. The firm reports 500% more BD outreach and a 50% improvement in candidate response rates. More outreach with better responses is what disciplined sending looks like.
Frequently asked questions (FAQs) on domain reputation and recruitment email
Google Postmaster Tools reports spam rates, authentication results, delivery errors and a reputation score for mail sent to Gmail. It is free once your DNS record is verified. Microsoft offers equivalent reporting through Smart Network Data Services. A domain reputation checker will also confirm your blacklist status in seconds.
A subdomain of your main domain is the usual choice for recruitment agencies. It keeps the brand recognizable while giving campaign traffic its own reputation to build or burn. A separate domain adds brand confusion and starts from zero sending history. That is a harder position to recover from.
Expect four to eight weeks of consistent, low-volume sending before mailbox providers soften their treatment of your domain. Recovery depends on sustained behavior rather than a single fix. Authentication records and list suppression need to be in place before the clock starts. Sending another large campaign during that window resets your progress.
Rarely, at agency sending volumes. Dedicated IPs suit senders pushing hundreds of thousands of messages a month. Below that threshold, a shared IP pool from an established provider carries better standing. An IP with no traffic history has nothing to vouch for it.
Most agencies settle between 100 and 300 campaign emails per consultant per day, with one-to-one email on top. That assumes a warmed-up sending domain. The safer ceiling depends on your complaint rates and bounce rates rather than a universal number. Stop raising the cap when replies start falling.
Operations, with technical support rather than technical ownership. The decisions that matter are commercial: how much the business sends, and what protects candidate communication from it. Leaving it with IT means nobody connects a falling reputation score to missed interviews.
What the desk looks like when every send lands
A recruiter who trusts their email stops hedging. No chasing call to confirm the invite arrived. No candidate lost between booking and interview because a confirmation sat in junk. That time goes back into calls and the roles on the desk.
Protecting domain reputation is part of what makes that week possible. It holds when campaign sending and day-to-day candidate email live in one platform. Two tools that have never met will keep undoing each other. Both can sit on one system, and that is what Atlas is built to do. Its AI agents handle the sequencing, logging, reminders and follow-up that recruiters would otherwise do by hand.
Worth a look if your team is still asking candidates to check their junk folder.
