Skip to main content

Command Palette

Search for a command to run...

Nobody Told You Your Credit Score Was Falling. That Is Not How Credit Scores Work.

Your sender reputation is being calculated right now by three separate systems. You cannot see the score. You cannot appeal it. But your revenue already can.

Updated
14 min read
Nobody Told You Your Credit Score 
Was Falling. That Is Not How 
Credit Scores Work.

A family had been saving for three years.

The goal was specific and real — a home in the city where they had lived for a decade. They had the down payment. They had the employment history. They had done what they were told to do and saved what they were told to save.

They walked into the bank with everything the brochure said they would need.

The loan officer smiled. Typed. Paused.

The application was declined.

Not because of the down payment. Not because of the income. Because of a number they did not know was being calculated. A score built from three years of financial behaviour — credit utilisation, payment timing, account age, inquiry frequency — assessed by a system they had never directly interacted with, updated continuously without notification, and presented to them for the first time at the exact moment it was too late to change it.

The score had been falling for eight months.

Nobody called. Nobody emailed. Nobody sent an alert suggesting they might want to check something before the most important financial decision of their lives.

That is not how credit scores work.

You find out when the loan is declined.

invisible crash

What This Has to Do With Every Email You Have Ever Sent

There is a concept in behavioural economics called feedback deprivation — the condition of making decisions and taking consequential actions without receiving the signal that would allow course correction.

Feedback is identified as a mechanism that causes a change in behaviour such that decisions might converge to efficiency. Providing individuals with information about the consequences of their past behaviour represents a powerful strategy for enhancing learning and better performance.

When feedback is withheld — by design, by architecture, or by the structure of a system that was never built to share it — decisions cannot converge to efficiency. The person acts. The consequences accumulate. The signal that would enable correction never arrives. The consequence appears without warning because the feedback loop was broken long before the consequence became visible.

The family applying for the home loan suffered from feedback deprivation. The credit bureau was calculating a score. The score was changing. No feedback reached the family. The loan officer's folder held eight months of decline that the applicants had never been allowed to see.

Your sender reputation operates on exactly the same principle.

Gmail, Outlook, and Yahoo are calculating a score right now. Continuously. Based on every email you have sent and every recipient's response to it. The score is changing with every campaign. The signal that would allow you to course-correct exists — held by the ISPs, processed by their algorithms, used to make routing decisions that directly govern your revenue.

It is not shared with you.

You find out when the inbox placement collapses.

inbox placement collapses

What Is Actually Being Scored — While You Were Looking Elsewhere

The score is not one number. It is a composite of signals evaluated simultaneously across multiple dimensions. Here is what is being measured — and where most programmes have gaps they cannot see.


Authentication Posture — The Identity Check

Before engagement, before content, before any behavioural signal — ISPs verify that you are technically who you claim to be. Three protocols govern this.

SPF — Sender Policy Framework. A DNS record listing which IP addresses are authorised to send email on behalf of your domain. When your email arrives at Gmail, Gmail checks whether the sending IP is on your authorised list.

DKIM — DomainKeys Identified Mail. A cryptographic signature on every email, verified against a public key in your DNS. A valid signature confirms the email genuinely originated from your domain and was not tampered with in transit.

DMARC — Domain-based Message Authentication, Reporting and Conformance. The policy layer that tells receiving servers what to do when SPF or DKIM fail — ignore it (p=none), quarantine it (p=quarantine), or reject it outright (p=reject).

Gmail and Yahoo began requiring DMARC for anyone sending more than 5,000 emails per day in February 2024. Microsoft followed in early 2025. By 2026 — non-compliant messages face SMTP-level rejection before they reach spam.

Most brands have SPF and DKIM configured. Most have DMARC set to p=none — monitoring mode — and left it there. P=none tells receiving servers you are aware of the protocol and have chosen not to enforce it. It provides no protection and signals incomplete authentication posture to every ISP evaluating your credibility.

The credit score equivalent: knowing your credit report exists, requesting a copy once, and then making no changes to the behaviour it describes.

The DMARC progression that protects your domain — and signals authentication maturity to ISPs — is three steps:

Step 1: p=none    → Monitor for 30 days
        Review aggregate reports
        Confirm all legitimate senders pass
        
Step 2: p=quarantine → Monitor for 30 days
        Watch for legitimate mail being caught
        Confirm no false positives at scale
        
Step 3: p=reject  → Enforce permanently
        Full protection against spoofing
        Strongest authentication signal to ISPs

Thirty days at each stage. Most brands are stuck at step one — permanently.

authentication posture

Spam Complaint Rate — The Signal That Moves Fastest

This is the single most important metric in your deliverability stack. Gmail's threshold for concern is 0.10%. Above 0.30% and you are in serious trouble.

On a list of one million recipients — 0.10% is one thousand spam complaints. Three thousand complaints cross the 0.30% threshold.

The credit score equivalent: three thousand individual creditors reporting a missed payment to the bureau in a single month. Each one a data point. Each one moving the score.

Inbox placement rates drop by an average of 23% within 48 hours of a complaint rate spike above 0.10%. And Postmaster Tools spam rate data is delayed 24-48 hours — meaning by the time you see the spike in your dashboard, the reputation damage has already been done and the next campaign is already sending into a degraded reputation environment.

The complaint rate is not a lagging indicator presented as a warning. It is a leading indicator of inbox placement collapse — if read correctly, with the right frequency, at the right level of segmentation.

Most brands read it monthly. In aggregate. Neither is sufficient.

spam complaint rate

Domain Reputation vs IP Reputation — The Score That Follows You

Switching banks does not reset a credit score. The score follows the person — not the institution they borrow from.

Switching ESPs does not reset domain reputation. The reputation follows the domain — not the infrastructure it sends from.

Domain reputation is a composite score that mailbox providers build from every domain touchpoint in your email — the From address, the Return-Path, the DKIM signing domain, and the domains in your tracking pixels and links. Each is evaluated independently.

This last point is critical and almost universally missed. Your tracking pixel domain — the subdomain your ESP uses to register opens and clicks — carries its own reputation signal. If that subdomain is shared across your ESP's entire client base and another sender generates high complaint rates, their reputation signal appears in your emails through the shared tracking infrastructure.

This is why switching ESPs does not always immediately improve deliverability. The new ESP's shared tracking infrastructure brings its own reputation signals — good or bad — attached to your emails from day one.

The credit score equivalent: discovering that your credit score includes the payment history of every other customer at your bank — because you share the same branch address.

Dedicated sending domains, dedicated tracking subdomains, and dedicated IPs are not luxury infrastructure. They are the mechanism for ensuring your reputation signal belongs exclusively to you.

domain reputation

Engagement Quality — The Signal Most Brands Are Actively Blocking

By 2026, ISPs rely more heavily on first-party engagement signals — replies, forwards, time spent reading — and less on raw volume or open rates, which Apple Mail Privacy Protection has made unreliable.

The signals weighted most heavily:

Replies — A recipient replying to your email is the strongest positive reputation signal available. It indicates the email reached a human who found it worth responding to.

Most marketing emails go to no-reply@ addresses.

Which means the strongest positive reputation signal available to every email sender is being actively blocked by most sending configurations.

Read that sentence again in the context of your own from address. Then check what happens when a subscriber hits reply on your last campaign.

If the reply goes nowhere — you are refusing the most valuable reputation contribution your subscribers can make. Change your from address to a monitored inbox. Create genuine reasons for subscribers to reply. The reputation impact of even a modest reply rate is disproportionate to the effort required.

Dwell time — An email opened and closed in under two seconds is a scan-and-dismiss. An email with thirty or more seconds of engagement is substantive reading. Where ISPs can measure it — and Gmail increasingly can — these register differently in engagement scoring.

Archive versus delete — A recipient archiving your email signals it was worth keeping. A recipient deleting without reading signals the opposite. The distinction matters to Gmail's per-recipient scoring model.

The credit score equivalent: every interaction with a financial institution — on-time payment, early payment, account maintenance, direct debit setup — contributing positively to a score the institution is continuously updating based on your behaviour.

engagement quality

The Four Stages of Reputation Decay Nobody Sees Coming

This pattern appears consistently across email programmes experiencing deliverability collapse. These timelines are based on observed patterns across high-volume sending programmes rather than a single published benchmark — your specific programme may show compression or extension depending on list size, send frequency, and ISP distribution.

Stage 1 — The Silent Drop (Weeks 1 to 6)

Complaint rate crosses 0.10% on one campaign. Returns below threshold on the next. Postmaster shows no visible alarm. Gmail's internal reputation model begins adjusting. No signal reaches the sender. The next campaign sends. The complaint rate spikes briefly again. Returns below threshold.

The pattern continues. Each spike is individually below the level that triggers visible alarm. Cumulatively they are establishing a trajectory.

The bank has not called. The score is moving.

Stage 2 — The Promotions Tab Migration (Weeks 6 to 10)

Gmail begins routing a percentage of emails from primary inbox to Promotions — specifically for recipients showing lower recent engagement with this sender. Open rates dip slightly but not dramatically. The campaign team attributes this to a weak subject line or suboptimal send time. The structural cause is not investigated because the symptom does not yet look structural.

The loan application has not been submitted. Nobody knows there is a problem.

Stage 3 — The Spiral Begins (Weeks 10 to 16)

A growing percentage of sends route to spam for the least engaged segments. The campaign team increases frequency to compensate for declining performance — which increases complaint rate — which accelerates routing to spam. A self-reinforcing cycle begins. Each decision made in response to a visible symptom makes the invisible cause worse.

The application is under review. The score is what it is. The decisions that determined it were made months ago.

Stage 4 — The Decline Is Declined (Week 16 Onwards)

Postmaster finally shows visible degradation. Domain reputation is Low. Inbox placement has collapsed — including for previously engaged segments, whose signal is now contaminated by the pattern established with the unengaged segments. Recovery requires 30 to 60 days minimum of reduced sending volume, aggressive suppression, and painstaking reputation rebuilding from the healthiest cohorts first.

The family is sitting across the desk. The folder is open. The number is presented to them for the first time.

It is not the number they needed.

four stages

What To Monitor — In Order of Priority

First — Spam complaint rate by campaign and segment

Do not check complaint rate monthly in aggregate. Check it by campaign, by acquisition cohort, by send frequency group, after every major send.

A 0.08% overall complaint rate can contain a 0.40% complaint rate from subscribers acquired more than 18 months ago — which is the segment actively damaging your reputation while the aggregate number looks safe. The aggregate hides the problem. The segment is what ISPs are reading.

Second — Google Postmaster Tools daily

When Gmail rejects your mail outright rather than routing it to spam — the reason appears as an error code in the Postmaster Tools Delivery Errors dashboard. The codes tell you exactly what to fix:

5.7.26  →  SPF alignment failure — check DNS immediately
5.7.30  →  DKIM failure — check signing configuration  
5.7.29  →  TLS issue — check encryption settings
5.7.25  →  Missing PTR/rDNS — contact your ESP

5.7.xx codes mean Gmail is rejecting outright — not routing to spam, rejecting. Stop sending to Gmail recipients and fix the underlying cause before the next campaign.

Check Postmaster Tools daily during active campaign periods. Not weekly. Not when something breaks. Daily — because the 24-48 hour data delay means the Wednesday campaign may be sending into a degraded reputation that Tuesday's data will only confirm on Thursday.

Third — DMARC progression

If your DMARC is at p=none — set a calendar reminder for 30 days from today to move to p=quarantine. Review aggregate reports during that period. Confirm all legitimate senders are passing authentication. Move to p=reject 30 days after p=quarantine.

P=none to p=quarantine to p=reject. Three steps. Most brands are stuck permanently on step one.

Fourth — Microsoft SNDS for Outlook-heavy lists

Microsoft's Smart Network Data Services provides IP-level complaint and trap data for Outlook, Hotmail, and Live domains. Free. Register at postmaster.live.com. Almost nobody uses it.

For enterprise senders whose lists include significant Microsoft domain volume — SNDS is the only direct signal for what is happening at Outlook's infrastructure. A Red status in SNDS while Postmaster shows healthy means your Outlook deliverability has collapsed while Gmail numbers remain intact. Most teams discover this when enterprise clients stop receiving their emails.

Fifth — Seedlist testing before major campaigns

Run a seedlist test before any send over 500,000 recipients or any campaign to a list not mailed in the past 60 days. Not for precision — seedlists measure controlled active inboxes, not real disengaged subscribers — but for direction. Knowing whether you are hitting primary, promotions, or spam at major providers before sending to your real list is worth every minute of setup.

monitoring priorities

The Loan That Gets Approved

The family went back.

Six months later. After sitting with the declined application long enough to understand not just that the score was wrong — but precisely what the score was measuring and why.

They paid down the balance inflating their credit utilisation. Closed the account they had forgotten about. Made every payment on time for 180 consecutive days. For the first time they understood what the scoring system was watching — and built their behaviour around those specific signals rather than their intuition about what should matter.

Six months later they walked back in.

The number had moved. Significantly. The loan was approved.

Sender reputation recovery works the same way. Not fast. Not visible in real time. Requiring patience, reduced send volume, aggressive suppression of the segments generating the complaint signals, and a commitment to rebuilding engagement signal from the healthiest cohorts first — even when suppression feels like losing contacts and frequency reduction feels like losing revenue.

It is operational discipline applied to a score you cannot directly see — in service of an outcome you cannot afford to lose.

The family who went back had one thing the original applicants did not.

They finally understood what the score was measuring.

That understanding is what this post was for.

The inbox is the loan. The reputation is the score that governs access to it.

Check it daily. Build it deliberately. Protect it before you need it — because the day you need it is not the day to find out what it is.

invisible crash approved

If your brain is already triaging this page for a 5-second window, skip the reading—the complete narrative is perfectly laid out in the infographic below.

infographic

Published by Hetvabhas — independent analysis of brand communication infrastructure. No vendor agenda. No sponsored content. No false reasoning.

The Real Cause — Brand Communication Examined

Part 1 of 4

Every campaign debrief has a visible explanation. A weak subject line. The wrong send time. A list that needs cleaning. A channel that underperformed. Most of the time that explanation is wrong. The Real Cause is a series that examines what is actually happening beneath the visible explanation — in the infrastructure, in the customer's psychology, in the logic of the channel, and in the gap between the metric and the outcome. Across email, CPaaS, WhatsApp, SMS, RCS, MarTech, and AI in brand communication. No vendor agenda. No sponsored content. No tips. Just the real cause — and what to do about it.

Up next

You Don't Have a Channel Problem. You Have a Conversation Problem.

And the science that explains why has been sitting in evolutionary psychology since before WhatsApp existed.