The Spam Flag That Breaks Your Customer's Invoice

The Call That Made Me Stop the Screen Share

I was on a Galadon Gold onboarding call a little while back with an SDR - sharp person, clearly good at her job. She had just gotten promoted to a new territory, bumped to senior, and the company had moved her into a region where she couldn't just hammer phones all day. The decision-makers were harder to reach. The connect rate had cratered. Her new job was email, and she knew it.

She shared her screen. She showed me her sequences. She showed me a prospect clicking through her emails in real time - she could track every link, every open. She had done her homework on the accounts. She even had a 13,000-contact list she'd exported from HubSpot and was ready to run mass outreach on.

Then I asked one question: What domain are you sending from?

She said the company's main domain. The primary breezeway.io domain - the same one the company sends invoices from, the same one customer service replies come from, the same one every business-critical email in the organization touches.

I had to stop her right there.

Why This Is a Company-Wide Problem, Not Just a Deliverability Problem

Most people think about cold email risk as: what if I get marked as spam? They think the consequence is that a prospect doesn't reply. Maybe the email lands in junk. Annoying, but whatever, move on to the next one.

That's not what actually happens.

When you send cold email from your primary domain and someone marks you as spam, you're not just losing that prospect. You're damaging the domain-level reputation that controls the deliverability of every single email your company sends. Your whole domain's credibility - built over years - can get dinged because one stranger at a resort in Arizona hit a button.

Domain reputation is the trust score that mailbox providers assign to your sending domain. It's not tied to one email address or one inbox. It's tied to the whole domain. If that score drops, emails sent from anyone at your company - finance, support, sales leadership, the CEO - start landing in spam or getting quietly filtered out before they ever arrive.

Think about what that means in practice. Your company's finance team sends a customer their invoice from billing@yourcompany.com. The customer never gets it. Not because the invoice was wrong. Not because their email is down. Because you sent a cold email to some hotel chain executive last Tuesday, he was in a bad mood, hit "Report Spam," and your domain reputation just took a hit. Nobody will ever connect those two things. The customer will just think you didn't send the invoice.

I told her: this is probably why some of your emails are bouncing. It could be bad list hygiene, sure - unverified addresses, old contacts. But it could also be that your domain is already flagged somewhere and you don't know it yet.

The SDR Who Didn't Know She Was Playing With the Company's Infrastructure

She was completely unaware. And honestly, that's not a knock on her - it's the norm. SDRs are handed a company email and told to go book meetings. Nobody explains what domain reputation is. Nobody explains that the inbox they're cold emailing from is the same infrastructure that powers accounts receivable.

She also mentioned something that made the situation even more specific: her company uses a tracking platform that monitors all her email activity. She couldn't just switch to an external tool without her management seeing it. That's a real constraint, and I respect that. But it doesn't change the underlying risk she was creating every time she hit send from the primary domain.

The fix isn't complicated, but it requires a mindset shift: your primary company domain should never be used for cold outreach. Ever. Not even once.

What Alias Domains Actually Do (And Why You Need More Than One)

The solution we walked through is buying alias domains - variations of your real company name that you use exclusively for cold outreach. So instead of sending from breezeway.io, you'd set up something like breezewayapp.com or breezewayhotels.com or whatever variation is available and sounds plausible.

You buy several of these. You configure them properly - SPF, DKIM, DMARC records all set up correctly. You warm them up. And then you send all your cold outreach through those. If one of them gets flagged, that domain takes the hit. Your primary domain stays clean. Your company's invoices, your customer support replies, your internal communications - all untouched.

This is the whole point of the alias domain strategy. You're creating a firewall between your experimental outbound activity and your company's mission-critical communication infrastructure. The cold email domain is disposable. The primary domain is not.

On the sending tool side, we recommended EmailBison - it's what we use internally because it runs on private SMTP infrastructure rather than shared pools. Shared sending infrastructure means if someone else on the same platform does something spammy, you can inherit their reputation damage even if you did nothing wrong. Isolated infrastructure means your sending reputation is yours alone. Pair that with proper alias domains and you've got real protection. Tools like Smartlead and Instantly are solid options too, depending on where you are in your setup.

The Volume Question Nobody Gets Right

She also asked something that I hear constantly: How many emails should I actually be sending?

She wanted to book three to four meetings a week. I mapped it out for her using the worst-case scenario - which is how I always plan. If you assume a 0.25% positive response rate (the absolute floor, like everything goes wrong), and you want three or four meetings a week, you need to be sending around 1,600 emails a week. That's roughly 320 a day. That number goes up if your list quality is bad. It goes down if you have a strong offer and clean targeting.

The cold email coach on our team was going to get her set up with about 6,000 emails per month - around 1,500 a week. That's a reasonable starting point. Not spray-and-pray. Not the 100-emails-a-day-from-one-inbox nonsense that everyone was doing a few years ago and wondering why it stopped working.

The current model that actually works: custom SMTP, multiple alias domains, two emails per inbox per day, spread across 100-plus inboxes. That's how you hit volume without torching your domain. The infrastructure is the strategy. If you don't get that part right, the copy and the targeting don't matter because the emails aren't landing anyway.

If you want the full breakdown on setting this up, the Cold Email Manifesto covers the infrastructure section in depth.

The Two-Campaign Model for SDRs Working Inside a Company CRM

One thing we sorted out on the call that's worth spelling out: she was mixing two completely different strategies in her head, and they need to stay separate.

Strategy one is key account outreach. She had a handful of high-value targets - big resort groups, multi-property operators, executives at companies managing 10, 20, 30 locations. These are worth serious time. For these, yes, do the research. Find the operator, the VP of operations, the senior director. Call to verify what software they're using. Personalize. Multi-touch. Chase them down. These accounts shouldn't be thrown into a 1,600-email-a-week batch - they deserve their own focused effort.

Strategy two is mass outreach to backfill the pipeline. This is where cold email infrastructure actually shines. Build a search in Apollo (or pull leads using ScraperCity's B2B database or the Apollo scraper) that returns leads that are at least 80% qualified. Don't try to manually verify every single one before you send. That's the trap she was falling into - spending hours calling hotels to confirm what property management software they run before sending a single email. That's backwards.

Instead: get the list, verify the emails (not the qualification, the emails - run them through a validator to remove bounces), and send. If someone replies and turns out to be outside your territory or using incompatible software, you just don't proceed. You find that out after they raise their hand, not before. The email is the filter.

The time savings are massive. Instead of spending a full day researching 30 accounts before writing a single email, you spend that time building a clean list of several thousand leads, loading it, and letting the system run. The only thing in your workflow after that is replying to responses - and you want to do that within five minutes when they come in.

For lead verification, the flow we walk clients through is: pull the list, run it through an email validator to keep only valid addresses (zero tolerance for known bad emails), load the verified list into your sending tool, and send. Tools like Findymail work well for finding and verifying contact emails at scale before you load them in. If you want the step-by-step process for building this kind of list, the Best Lead Strategy Guide lays it out in full.

The HubSpot Problem: Don't Flood Your CRM With Unqualified Leads

She had 13,000 contacts in HubSpot and was thinking about just loading all of them into her sending tool. I told her not to do that - but more importantly, I told her not to import the mass outreach responses back into HubSpot indiscriminately either.

When you're running mass outreach alongside a managed CRM that your management can see, you don't want to be pumping 1,500 unvetted leads a week into the system. It creates noise, it looks messy, and it's going to confuse whoever is tracking pipeline health.

The right workflow: run the mass outreach separately, outside HubSpot, in your sending tool. When someone replies and they're qualified - right territory, right company size, right software situation - then you add them to HubSpot. You're using the cold email campaign as a qualification layer. Only hand-raisers make it into the CRM. That's how you keep the data clean and keep your management from questioning what you're doing.

And yes, you can keep a customer exclusion list. If you have a list of existing customer domains, load those into a domain blacklist in your sending tool so you never accidentally email a current customer with a prospecting sequence. That's table stakes.

What the Copy Problem Actually Is

She also asked me to critique one of her emails. It was long. It had bullet points. It scrolled past the bottom of the phone screen before you got to the ask.

My honest take: I'm not a fan of cold emails with bullet points, and I'm not a fan of cold emails longer than what fits on one phone screen without scrolling. Cold email is not a sales deck. It's a tap on the shoulder. Get in, make one clear point, ask one clear question, get out.

But I also want to be clear: the copy issue was secondary. The domain issue was immediate and existential. Bad copy means fewer replies. A compromised primary domain means your company's finance team can't reliably deliver customer invoices. One of those problems is annoying. The other is a company-level crisis.

The copy she can fix by working with a cold email coach who can rewrite her sequences from scratch once she knows her targeting. We have that built into the Galadon Gold program - you write a draft, post it in the Slack channel, and the cold email coach rewrites the whole campaign. That's the process. You're not on your own trying to figure out what a good subject line looks like.

For frameworks to get started before your first coaching session, the Top 5 Cold Email Scripts give you structures that have actually worked at volume.

The Honest Career Angle

She told me at the end of the call that she thought the company had hired cheaper reps specifically because they wanted her gone. She was too good on the phones and too expensive, and they were moving her into an email-heavy territory where her strength didn't apply. She was learning cold email partly to survive the current job and partly because she was planning to find something better.

That's a smart play. Cold email competence is a skill that follows you everywhere. If you can reliably book meetings over email, you can land a better sales job, you can start freelancing lead gen, you can eventually start your own agency. My entire career arc started from being the person at an agency who took it upon himself to figure out how to generate more meetings. I got good at it. They made me director of marketing. Then I emailed every company that looked like my old employer and said - here's what I did for them, want me to do it for you? That's how the agency started.

The SDR who masters cold email infrastructure and targeting while everyone else is still doing it wrong doesn't stay an SDR for long.

The Summary

If you take nothing else from this: never cold email from your primary company domain. The cost of getting it wrong isn't a prospect who ignores you. It's a deliverability problem that cascades through every email your company sends - including the ones to people who are already paying you.

Set up alias domains. Warm them up. Use proper infrastructure. Verify your list before you send. Keep your key account strategy and your mass outreach strategy separate. And reply to responses fast.

That's the system. Everything else is optimization on top of it.

If you want the infrastructure set up correctly from day one, that's exactly what we walk through inside Galadon Gold - live coaching, cold email review, and the full tech stack built out for you.