Home / Glossary / Deliverability vs reputation
Glossary entry · distinction

Deliverabilityvsreputation

The most-confused distinction in cold-email infrastructure. Deliverability is whether your email arrives in the inbox. Reputation is whether the human who receives it opens, replies, or marks spam. The two are upstream of each other — bad reputation eventually destroys deliverability — but they're optimized differently, measured differently, and fixed by different people on different timelines.

First written: May 22, 2026 · Category: distinction Reading time: 6 min
01

Plain English.

TLDR
Deliverability is the question "did the email arrive in the recipient's inbox at all?" — that's a technical question about authentication, sending infrastructure, content patterns, and domain reputation as seen by the receiving mail server. Reputation (in the human sense) is the question "did the recipient find it worth opening, replying to, or not marking as spam?" — that's a behavioral question about content quality, send timing, ICP fit, and sender brand. Both matter; neither replaces the other.

The confusion comes from the word "reputation" appearing on both sides — sending-domain reputation (a technical deliverability concept) and sender reputation in the recipient's mind (a behavioral concept). They're related but not the same. A sender can have perfect technical reputation (every email lands in the inbox) and zero human reputation (every email gets archived). The opposite case is rarer but possible.

This distinction matters because most "deliverability problems" are actually content/quality problems showing up downstream — and most "reply rate problems" are actually deliverability problems hiding upstream. Diagnosing the wrong layer wastes weeks.

02

The actual definitions.

Side by side, in operating terms.

Deliverability
The technical layer
Whether a sent email actually arrives in the recipient's inbox vs spam folder, promotions tab, or being rejected outright.
  • Measured by — inbox-placement rate (IPR); typical target: > 90%
  • Owned by — RevOps / IT / sending-infra owner
  • Determined by — SPF, DKIM, DMARC, domain age, sending volume, warmup, content-spam triggers
  • Fix timeline — weeks to months
  • Failure mode — emails land in spam or bounce — you never had a chance
Reputation (human)
The behavioral layer
Whether the recipient who received the email finds it worth opening, replying to, and not marking as spam.
  • Measured by — open rate, reply rate, spam-complaint rate, archive rate
  • Owned by — SDR / AE / outbound team
  • Determined by — subject line, opener quality, ICP fit, send timing, sender brand familiarity
  • Fix timeline — campaign-by-campaign (immediate)
  • Failure mode — email arrives but is ignored, archived, or spammed — you had the chance and lost it

The key insight: deliverability is upstream of reputation, but reputation is also upstream of deliverability — they form a loop. If your content is bad (low opens, high spam complaints), receiving mail servers eventually learn to filter your domain. If your domain is filtered, your good content never gets a chance to land. The loop runs in both directions over time.

03

The send-to-reply funnel.

The honest version of "what happens to a sent cold email" — where deliverability ends and reputation begins. Numbers are typical for signal-anchored cold outbound, honestly measured.

Stage-by-stage drop-off · honest numbers
From "send" to "reply" — and which layer governs each transition.
Emails sent (your sequencer fires)
100% baseline
100%
Delivered (passed receiving server's gates)
96% — deliverability
~ 96%
Inbox-placed (not spam, not promotions)
84% — deliverability
~ 84%
Opened (subject earned a click)
50% — reputation
~ 50%
Read past line 1 (opener earned attention)
28% — reputation
~ 28%
Replied (human response, OOOs excluded)
~ 8% — both layers
~ 8%

Read carefully: the first 16 percentage-point drop (100 → 84) is deliverability. The next 56 points (84 → 28) is reputation. The biggest single drop in cold outbound is the open-rate gap — and that's a reputation problem masquerading as a deliverability one in most diagnostic conversations.

04

When each one is the problem.

Two diagnostic patterns that look similar from the dashboard but require completely different fixes.

Deliverability ok · reputation bad
Emails arrive but nothing happens.
96% delivery, 84% inbox placement, ~ 2% open rate. Emails are landing in the inbox; recipients see them and skip. Symptoms: open rates < 25%, reply rates < 1%, no spam complaints. Fix the subject line, the opener, the ICP fit — not the sending infrastructure.
Reputation ok · deliverability bad
When people see it, they engage — but few people see it.
96% delivery, 42% inbox placement, ~ 60% open rate among those delivered. The content works, but most emails are getting routed to spam. Symptoms: high engagement among the small number that arrive, sudden drop in open rates correlating with a domain or volume change, bounce rate creeping up. Fix the sending infrastructure — auth records, warmup, volume ramp, domain reputation.
The diagnostic mistake
The most common mistake is blaming "deliverability" when the actual problem is content. Teams pay deliverability consultants to audit infrastructure when their open rates would be 8% even if every email arrived in the bolded primary inbox. If your content fails the receipts test, no amount of SPF tuning will save it.
05

How to fix each.

Different layer, different toolkit, different team.

  • Deliverability fix: authentication records. Confirm SPF, DKIM, and DMARC are configured for every sending domain. The single most common deliverability problem is misconfigured DMARC with a "none" policy that does nothing. Move to "quarantine" once SPF/DKIM are clean.
  • Deliverability fix: dedicated sending domains. Never send cold from your primary domain. Buy a similar variant (yourcompany.co, yourcompany-team.com), warm it up over 4-6 weeks, and use it as the cold-outbound origin. If the cold domain's reputation tanks, your primary inbox stays clean.
  • Deliverability fix: volume discipline. Cold senders that ramp from 0 to 200/day in week 1 land in spam by week 3. Start at 30/day per inbox, ramp 10/day/week, cap at 80–120/day per inbox depending on warmup state.
  • Reputation fix: subject line discipline. Generic subjects ("quick question," "thoughts?") sit at the bottom of open-rate ranges. Specific subjects that reference the actual signal anchor land 2-3× higher. See the opener playbook.
  • Reputation fix: opener quality. If line 1 doesn't pass the receipts test, the recipient archives by paragraph 2. Reputation lives in line 1.
  • Reputation fix: ICP tightening. The biggest reply-rate lever isn't writing better emails — it's emailing better-fit recipients. Tighten the ICP rubric; smaller list, deeper context, higher reply rate. See the ICP rubric entry.
06

How Mama relates to both.

Mama doesn't send the email — your sequencer does — so we don't own the deliverability layer directly. What Mama affects is the reputation layer: by making the opener materially better-anchored, signal-rich, and recipient-specific, the open rate, read-through rate, and reply rate all move up the funnel. Spam-complaint rates drop because the email reads as relevant rather than templated.

If your deliverability is broken, Mama can't fix it — fix the technical layer first (auth, domains, warmup, volume). Once emails are arriving, Mama is the layer that makes them worth opening. Both layers have to work; Mama is honest about which one we operate on.