Most cold email failures happen before anyone ever reads a word of your copy. The email lands in spam, or gets rejected by the receiving server entirely, and the campaign quietly underperforms while everyone debates whether the subject line was the problem.

Deliverability is the foundation every campaign sits on. At Fox Outreach, it is the first thing we focus on and the last thing we stop monitoring. Here is exactly how we approach it for every client.

We never touch your primary domain

The first thing we do before any outreach begins is set up dedicated sending infrastructure that is completely separate from your company's primary domain.

Your primary domain carries your brand reputation, your transactional email, and years of sending history. Using it for cold outreach is an unnecessary risk. One complaint spike can damage your domain's reputation and start routing legitimate business communications to junk folders. We have seen it happen to companies that tried to run outreach themselves before working with us.

Instead, we register dedicated sending domains for every client. These are branded variants that look like they belong to your company, patterns like get[yourdomain].com or try[yourdomain].com, completely isolated from your primary domain's reputation. Whatever happens on a sending domain stays contained there.

We also calibrate the number of domains to the intended campaign volume. A rough rule we follow: one domain for every 30–50 emails per day. Staying below this threshold per domain keeps volume patterns from triggering spam filters at scale.

We configure authentication before anything goes out

Authentication records tell receiving mail servers that email claiming to come from your domain actually comes from you. Without them, major providers increasingly reject mail outright, not just filter it to spam.

We configure three records on every sending domain before a single outreach email is sent:

SPF (Sender Policy Framework) specifies which servers are authorized to send on behalf of a domain. If the sending server is not on the list, receiving servers will reject or flag the mail.

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every outgoing message. Receiving servers verify this signature against a public key stored in DNS, confirming the message has not been altered in transit.

DMARC (Domain-based Message Authentication, Reporting & Conformance) tells receiving servers what to do when mail fails SPF or DKIM checks, and sends reporting data back to us so we can monitor authentication results. We start with p=none for visibility, then tighten the policy once we have confirmed everything is passing correctly.

We verify all three are configured and passing before any campaign is approved to launch.

We warm up every inbox over 2–4 weeks

A freshly created inbox sent to hundreds of prospects immediately is a signal that something is wrong. Mail servers track sending patterns, and an inbox that jumps from zero sends to high volume overnight looks like a compromised account or spam operation.

Warmup is the process of gradually building a sending reputation for a new inbox over 2–4 weeks. We use dedicated warmup tools that simulate realistic engagement: sends, opens, and replies, gradually increasing volume each day while building a positive sending history with major mail providers.

After warmup, we keep daily send volume per inbox below 50. For campaigns that require higher volume, we use multiple warmed inboxes spread across the client's sending domains. This is how we achieve scale without triggering the volume patterns that damage deliverability.

We verify every contact list before sending

A cold email list that has not been properly validated will generate hard bounces, attempts to send to email addresses that do not exist. Bounce rates above 2% are a serious deliverability signal that can get sending domains blacklisted.

Before any list enters a campaign, we run every address through email verification. We remove invalid addresses, addresses flagged as high-risk, and addresses associated with role-based inboxes that are unlikely to be monitored by an individual. Our target going into any campaign is a hard bounce rate below 1%.

This step also catches list quality problems early. A list with a high rate of invalid addresses is a sign the targeting data needs attention before we spend sends on it.

We monitor inbox placement, not just open rates

Open rate tells you what percentage of delivered emails got opened. It does not tell you how many emails reached the inbox versus the spam folder.

We use seed testing tools to check inbox placement directly, sending test messages to a panel of addresses across Gmail, Outlook, Yahoo, and other providers and measuring where they land. This gives us a placement report that shows inbox rate, spam rate, and missing rate by provider.

We run placement tests before every new campaign, after any significant volume change, and any time we see unexpected drops in engagement. It is the earliest indicator of a deliverability problem and gives us the opportunity to diagnose and correct before the issue affects a live campaign.

We track complaint rates as a primary health metric

The percentage of recipients who click "Mark as spam" is one of the most important metrics we monitor. Google's documented threshold for action is 0.1%. We aim to stay below 0.08% on every sending domain.

Complaint rates spike when outreach is sent to unqualified contacts, when list quality is poor, or when a sequence continues beyond the point where engagement suggests the audience has lost interest. We monitor complaint rates after every campaign and pull back volume on any domain approaching threshold before it can cause lasting damage.

What happens if a domain's deliverability degrades

Despite careful setup and monitoring, deliverability can degrade, usually due to list quality issues or unexpected complaint spikes. When it does, our process is:

1. Pause sending from the affected domain immediately.
2. Identify the source of the issue, specifically which campaign or list contributed to the problem.
3. Lower volume on that domain and begin the re-warmup process.

A domain with damaged reputation can take weeks to recover. This is another reason we invest heavily in prevention: dedicated domains per client, conservative volume limits, list verification, and continuous monitoring. It is far easier to protect a healthy domain than to recover a damaged one.

Per-lead personalization removes the template fingerprint

There is one more layer protecting every campaign we send, and it has nothing to do with DNS records or warmup schedules.

Spam filters at Gmail and Outlook are pattern-matching systems. When hundreds of near-identical messages move through their infrastructure, the shared template is easy to detect, and once it is flagged, every remaining send in the sequence inherits the penalty. This is how entire campaigns die at once, even on well-configured domains.

Our emails do not share that fingerprint. Because every message is written for the individual lead, with its own subject line, opener, and hook, there is no repeated pattern for a filter to catch. Each email looks like what it is: one person writing to another. We break down how that works in how we personalize every email.

Why this matters for your campaigns

The most common version of cold email failure we see from companies before they come to us is not bad copy. It is bad infrastructure. Emails going to spam. Domains getting flagged. Lists with 10% bounce rates burning through sending reputation in a week.

The work described above is not exciting. It is not the kind of thing that gets written about in marketing blogs. But it is what makes the difference between a campaign that reaches inboxes and one that disappears. Every campaign we run for clients is built on this foundation, and it is monitored continuously for as long as the program runs.