The Cold Email Deliverability Playbook for B2B Teams (2026)
By Puzzle Inbox Team · Jun 21, 2026 · 15 min read
Cold email deliverability playbook for 2026: SPF DKIM DMARC, sender reputation, domain reputation, IP reputation, warmup, and inbox placement that actually works.
Why Cold Email Deliverability Is the Real Bottleneck
Most cold email teams obsess over copy, offer, and lists. Those things matter, but they only matter if your message reaches the inbox. In 2026, cold email deliverability is the single biggest predictor of pipeline. You can have the best subject line in the world and a perfect ICP match, and still see a 4% reply rate if your sender reputation is broken. The math is brutal: if 70% of your sends land in spam, you are paying full price for 30% of the volume you think you are running.
Cold email is not the same problem as transactional email or newsletter email. The receiving systems at Google and Microsoft treat unsolicited outbound from a new domain as a high-risk signal by default. Inbox placement is not a setting you turn on. It is the cumulative output of authentication, domain age, sending patterns, recipient engagement, and the IP reputation behind your sending infrastructure. Skip any one of those and your campaigns suffer.
This playbook is written for B2B founders, SDR leaders, and growth operators who are running real outbound in 2026. We will walk through every layer of the deliverability stack, in the order it actually breaks. If you want the short version of how Puzzle Inbox runs this stack for you, start with how it works and the our process page. If you want to keep reading, here is the long version.
The 5 Factors Google and Microsoft Score
Inbox placement is decided by a scoring engine on the receiving side, not by your sending tool. Both Gmail and Outlook 365 weigh five factors when they decide whether your cold email lands in the primary inbox, the promotions tab, the spam folder, or the void. Understanding these five factors is the foundation of every spam folder fix that actually works.
1. DNS Authentication
SPF, DKIM, and DMARC are not optional anymore. Since February 2024, Google and Yahoo require all bulk senders to authenticate properly, and Microsoft tightened the same requirements through 2025. If your DNS authentication is incomplete or misaligned, you are starting every send at a deficit. We cover the exact records below, and you can also read the dedicated SPF DKIM DMARC setup guide for a deeper walkthrough.
2. Domain Reputation
Every sending domain accumulates a reputation score. New domains start neutral, then move up or down based on recipient behavior. Spam complaints, hard bounces, and low engagement push the score down. Replies, opens from real users, and clean send patterns push it up. Domain reputation is portable across IPs, which means once you burn a domain you cannot fix it by switching infrastructure. Read more about how email domain reputation is calculated.
3. IP Reputation
The IP address that delivered your message also has a reputation. This is the layer most cold emailers get wrong. We will return to IP reputation in detail below, but the short version is this: you do not control it, and the only safe bet in 2026 is sending from Google or Microsoft's own IP pools.
4. Recipient Engagement
Mailbox providers track whether your messages get opened, read, replied to, marked as important, marked as spam, or deleted without reading. The ratio of positive to negative signals across your last 30 days of sending feeds directly into your sender reputation. This is why a clean list matters more than a big list.
5. Sending Patterns
Volume spikes, sudden geographic changes, identical content blasts, and inconsistent timing all look like spammer behavior. A warm sending pattern is gradual, varied, and matches a believable human work schedule.
DNS Authentication Step by Step: SPF, DKIM, DMARC
If you do nothing else from this guide, get your DNS authentication right. Every cold email deliverability audit we run starts here, and roughly one in three teams has a misconfigured record that is silently tanking their inbox placement.
SPF: Sender Policy Framework
SPF tells receiving servers which IPs are authorized to send mail on behalf of your domain. The record lives as a TXT record at the root of your sending domain. For a Google Workspace sending setup, the minimum record looks like this: v=spf1 include:_spf.google.com ~all. For Outlook 365, you want v=spf1 include:spf.protection.outlook.com -all. Two rules to remember. First, you can only have one SPF record per domain. If you add a second, both fail. Second, the -all hardfail is stricter than ~all softfail, and most deliverability operators recommend hardfail for cold email domains.
DKIM: DomainKeys Identified Mail
DKIM signs every outgoing message with a cryptographic key. The receiving server fetches your public key from DNS and verifies the signature. If the signature is valid, the message is proven to come from your domain and to be untampered in transit. Google Workspace publishes the key at google._domainkey.yourdomain.com, and you generate the key from the Workspace admin console. Outlook 365 uses two selectors, selector1 and selector2, as CNAME records pointing to your Microsoft tenant. Both providers handle the key rotation for you once the records are in place.
DMARC: Domain-based Message Authentication, Reporting and Conformance
DMARC ties SPF and DKIM together and tells receiving servers what to do when authentication fails. A starter DMARC record looks like v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. The p=none policy is monitor-only and is the right starting place for a new sending domain. Once you have 30 days of clean DMARC reports, move to p=quarantine and eventually p=reject. Skipping the monitor phase is a common mistake that nukes legitimate mail during the rollout.
Domain Selection: The Decision Most Teams Get Wrong
Your main company domain should never be used for cold outbound. If you send cold email from yourcompany.com and you hit a bad list, you can damage the domain reputation of your transactional, sales, and recruiting mail for months. Every serious cold email program uses dedicated sending domains.
The two viable patterns are alternate TLDs of your brand (try-yourcompany.com, get-yourcompany.com, yourcompany.co) and unrelated generic domains. Both work. The brand-adjacent pattern gives you a slightly higher reply rate from prospects who recognize the name. The generic pattern is cheaper and faster to scale, especially when you need dozens of inboxes.
For teams running Puzzle's Google Workspace cold email inboxes on the Standard plan, you bring your own domain from any registrar and we provision the Workspace tenants and configure all DNS authentication. For teams that want speed over branding, the Pre-Warmed plan runs on Puzzle's generic .info, .help, and .site domains, which have already been aged and warmed before you receive them. Compare the two options on the pricing page.
One more rule on domain selection. Do not buy expired domains for cold email, no matter how cheap they look. Expired domains carry hidden reputation baggage. A clean new domain that you warm up correctly will outperform a 10-year-old expired domain with a polluted history every time.
IP Reputation: The Layer You Do Not Control
This is where most cold email infrastructure decisions go wrong. Around 2020, the standard advice was to rent dedicated IPs from SMTP relay providers, configure rDNS, warm the IPs manually, and run cold campaigns through them. That stack stopped working around 2023, and in 2026 it is actively harmful.
The reason is simple. Google and Microsoft now heavily weight whether the sending IP belongs to a known consumer mailbox provider. When a message arrives from a Google Workspace IP into a Gmail inbox, the receiving server treats it as a peer-to-peer message between two real Gmail accounts. When that same message arrives from a third-party SMTP IP, even one with a clean reputation, it gets scored as bulk commercial mail and routed accordingly.
This is why Puzzle Inbox runs cold email exclusively through real Google Workspace and real Microsoft 365 mailboxes. You are not sending through our IPs. You are sending through Google's IPs and Microsoft's IPs, because the inboxes are real. There is no SMTP relay in the path, no third-party IP, no shared sending pool. Each inbox uses OAuth with email and password to connect to your sequencer, and the actual SMTP traffic goes directly from Google or Microsoft to the recipient.
The practical consequence is that IP reputation is no longer a knob you turn. It is decided by which mailbox provider you sit behind. Once you accept this, the cold email infrastructure question gets a lot simpler. Read cold email sender reputation for a deeper dive into how the two layers, domain and IP, interact.
Warmup Mechanics: What Actually Happens
Warmup is the process of sending controlled, engaged-looking mail from a new inbox before you turn on cold outbound. The goal is to teach mailbox providers that your inbox sends real, wanted messages, so that when you start cold sending, your messages are scored against an established baseline of positive engagement.
A correct warmup network sends mail between participating inboxes, opens those messages, replies to a percentage of them, marks some as important, and pulls others out of spam if they land there. Over two weeks, this creates a synthetic but consistent engagement pattern that pushes your sender reputation upward.
The mistake most teams make is rushing the warmup. A Google Workspace inbox needs at least 14 days of warmup before it can safely handle 12 cold emails per day. An Outlook 365 inbox needs the same 14-day warmup before it can safely handle 3 cold emails per day. There is no shortcut. If you skip the warmup and start blasting from day one, you will be in the spam folder by day three and you will not recover the domain.
Puzzle's Pre-Warmed inboxes ship with the 14-day warmup already complete on Puzzle-owned generic domains, which is why they can be deployed faster. Standard inboxes ship to your own domain and warm up in parallel with your live sending. For the full warmup walkthrough, read the cold email warmup guide.
Critical detail. Warmup does not stop when cold sending starts. You keep the warmup running at full volume forever. Every Google inbox runs 12 cold and 12 warmup per day. Every Outlook inbox runs 3 cold and 3 warmup per day. The warmup traffic is what keeps your engagement ratio positive when your cold replies are running at 2 to 8 percent.
Per-Inbox Volume Math: Why 12+12 and 3+3 Are the Ceilings
The single biggest mistake we see in cold email infrastructure is overloading each inbox. The numbers below are not aspirational targets. They are the safe upper bounds based on years of inbox placement data across thousands of accounts.
Google Workspace
Twelve cold emails per inbox per day. Twelve warmup emails per inbox per day. Twenty-four total per inbox per day. You can put three Google Workspace inboxes on a single sending domain, which means each domain can carry 36 cold sends per day. The three-inbox-per-domain rule is not a guideline. It is mandatory. Cramming four or five inboxes onto one domain crashes domain reputation within a week.
Outlook 365
Three cold emails per inbox per day. Three warmup emails per inbox per day. Six total per inbox per day. Outlook 365 tolerates significantly less volume per inbox than Google Workspace does, which is the price of access to Outlook recipients. You can put 100 Outlook inboxes on a single domain, which means each Outlook domain can carry 300 cold sends per day. Outlook also requires that mandatory 100-per-domain density because the cost structure only works at scale.
Doing the Math for Your Pipeline
If you need 1,200 cold sends per day, you have two clean paths. Path one is 100 Google Workspace inboxes across 34 sending domains. Path two is 400 Outlook 365 inboxes across 4 sending domains. Most teams mix the two because some prospects are on Google and some are on Microsoft. Read how many cold email inboxes for help sizing your infrastructure to your actual pipeline targets.
If a vendor or in-house operator is telling you that you can run 50 or 100 cold emails per day per Google inbox, walk away. That advice was true in 2019. It is not true in 2026, and following it will burn your domains in under a month.
Spam Folder Diagnostic Checklist
When cold emails are landing in spam, work through this checklist in order. Each step is cheap to verify and the order matters because each layer assumes the layers below it are correct.
- Authentication. Run an SPF, DKIM, and DMARC check on your sending domain. Use mxtoolbox.com or any DMARC analyzer. All three must pass, and DMARC must be aligned.
- Domain age. If your domain is less than 14 days old and you skipped warmup, that is your problem. Stop sending, warm up for two weeks, and restart slowly.
- Blacklists. Check Spamhaus, Barracuda, SORBS, and SURBL. If your domain or sending IP appears on a blacklist, identify the cause and request delisting.
- Volume. Are you exceeding 12 cold per Google inbox per day or 3 cold per Outlook inbox per day? If so, drop the volume immediately.
- List quality. Run your list through a bounce verifier like ZeroBounce, NeverBounce, or MillionVerifier. Bounce rates above 3% are a red flag for mailbox providers.
- Engagement ratio. What is your reply rate? Open rate? If you are below 1% reply and 20% open, your content or targeting is the problem, not your infrastructure.
- Content patterns. Are you using the same exact subject line across thousands of sends? Are you including more than two links per message? Are you sending images? All three signal spam.
- Inbox provider. Are you sending through real Google or Microsoft mailboxes, or through a third-party SMTP relay? If it is the latter, that is likely your problem.
For the full walkthrough of each step, read cold emails landing in spam fix, which goes deeper on each diagnostic layer.
What to Do When Placement Drops
Even with everything configured correctly, placement will sometimes drop. A new mailbox provider algorithm rolls out. A specific list segment had a higher complaint rate than expected. Your sequence had a subject line that triggered a filter. When this happens, the temptation is to keep sending and hope it recovers. Do not do this.
Step 1: Stop Sending Immediately
Pause the affected inbox or domain entirely. Continuing to send while your reputation is dropping accelerates the damage. Twenty-four hours of pause costs you almost nothing in pipeline. Twenty-four hours of bad sending can cost you the domain.
Step 2: Run a Seed Test
Send a manual message from the affected inbox to a set of seed addresses you control on Gmail, Outlook 365, and Yahoo. Check which folder each message lands in. This tells you whether the drop is provider-specific or general.
Step 3: Investigate the Trigger
Look at the last 100 sends from the affected inbox. Were complaint rates higher than normal? Was bounce rate elevated? Did the subject line change? Was there a content change that introduced a new keyword? Almost every placement drop has a specific trigger.
Step 4: Restart the Warmup
If the drop is general and severe, treat the inbox as if it were new. Run another 14 days of pure warmup with no cold sending. After 14 days, run a fresh seed test. If placement is restored, resume cold sending at half volume for one week before returning to the 12+12 or 3+3 cap.
Step 5: Decide Whether to Retire the Domain
If after 14 days of pure warmup the seed test still shows spam placement, the domain is likely burned. Retire it and provision a fresh domain. This is painful but it is cheaper than continuing to send from a dead domain.
This playbook is why teams use Puzzle's features for monitoring and our deployment flow on the getting started page makes provisioning a replacement inbox fast.
Tools to Monitor Inbox Placement
You cannot improve what you do not measure. Every cold email program should have continuous monitoring across these four tool categories.
Authentication Monitoring
DMARC reports tell you which messages are passing and failing authentication. Use a tool like Postmark DMARC, Valimail, or Dmarcian to parse the daily reports and surface issues. Without this, you will miss authentication failures until they cause a placement drop.
Placement Testing
Tools like Glockapps, Mailreach, and Inboxally let you send a test message to a panel of seed addresses across all major mailbox providers and see where it lands. Run a placement test at least weekly for every active sending domain. Run one immediately after any major sequence change.
Blacklist Monitoring
MXToolbox, HetrixTools, and similar services check your domain and IP against major blacklists daily. Set up alerts so you know within hours if a listing appears.
Engagement Analytics
Your sequencer should report open rate, reply rate, bounce rate, and complaint rate per inbox and per domain. Watch the ratios. A sudden drop in open rate is usually the first sign of a placement problem, and it shows up before your seed tests do.
Putting It All Together
Strong cold email deliverability in 2026 comes from five disciplined choices. Use dedicated sending domains, never your main domain. Configure SPF, DKIM, and DMARC correctly from day one. Send only through real Google Workspace or Microsoft 365 inboxes so you sit behind first-party IP reputation. Warm every inbox for 14 days before any cold send, and keep the warmup running forever at full volume. Cap per-inbox volume at 12 cold per Google inbox and 3 cold per Outlook inbox, with the mandatory 3-per-domain density on Google and 100-per-domain density on Outlook.
That is the entire playbook. Everything else is execution. If you want to skip the execution and have the whole stack delivered ready to send, Puzzle provisions Google Workspace and Outlook 365 cold email inboxes with all DNS authentication configured, all warmup running, and your inbox credentials delivered within 24 to 72 hours via WhatsApp or email. Compare the Standard and Pre-Warmed options on the pricing page, or start with how it works to see the full flow.
Related Reading
- Cold emails landing in spam: the diagnostic fix
- Cold email warmup guide: the 14-day method
- SPF, DKIM, and DMARC setup guide
- Email domain reputation explained
- How many cold email inboxes do you need