Complaint rate driven
Content frequency, missing unsubscribe, list purchase, bulk sender violations
Sender Score below 70 affects deliverability with enterprise corporate filters (Proofpoint, Mimecast, legacy USA gateways) that consult Validity as input alongside their own telemetry. The score combines approximately 30 data points across five visible component categories: complaint rate, unknown user rate, spam trap hits, message filter rate, and IP infrastructure. The root cause of a score drop is almost always concentrated in one or two specific components rather than spread across all five; remediating the root component drags the overall score back up. The service diagnoses the critical component using Validity dashboard, Google Postmaster Tools, Microsoft SNDS, blocklist sweeps, and ESP bounce logs in the first 24 to 72 hours, then executes the prioritized remediation plan with weekly monitoring during 30 to 90 days. The recovery timeline is realistically 4 to 10 weeks because the Validity measurement window is rolling 30 days, which means even perfect sending after remediation takes 30 days to fully flush the negative signals from the rolling average. Note that Sender Score is one external benchmark, not the master switch; Gmail, Microsoft, and Yahoo each run their own internal reputation models that Validity does not see, so a score above 90 is necessary but not sufficient for Gmail-specific deliverability.
The Validity Data Network draws complaint data, trap hit data, infrastructure data, and filter rate data from 60 million-plus mailboxes across 80-plus mailbox and message security providers. The visible components below account for the majority of score movement, though the algorithm includes additional data points Validity has not published publicly. The sample below shows a typical pre-engagement state for a B2B sender at score 64 with the dominant problem in complaint rate and a secondary issue in unknown user rate.
The overall score of 64 places the sender in the problematic band where enterprise filters that consult Validity (Proofpoint, Mimecast, legacy gateways) apply additional filtering. The breakdown across components shows complaint rate as the dominant issue followed by unknown user rate; the other three components are within normal ranges.
The visible imbalance in the sample drives the engagement plan. The complaint rate at 42 dominates the score drop; the unknown user rate at 58 is a secondary contributor; the other three components are within tolerable bands. The remediation plan focuses on the complaint rate driver: list segmentation to identify the cohorts producing the highest complaints, suppression list maintenance for the persistent complainers, complaint feedback loop integration with the ESP to catch new complaints in near real-time, content and frequency review to reduce the underlying dissatisfaction that produces complaints. The unknown user rate gets a secondary remediation through list verification before send (Prospeo, NeverBounce, ZeroBounce all offer the bulk verification service) and the bounce suppression list rotation policy. The three OK components get no remediation work; the engagement does not waste effort on dimensions that are not driving the score.
The bands below are directional rules of thumb rather than guarantees; mailbox providers do not publish formulas that translate Sender Score into inbox placement, and the 2026 inbox placement averages vary by provider (Gmail 87.2 percent, Microsoft 75.6 percent, Yahoo 86 percent, Apple Mail 76.3 percent per EmailToolTester 2026 data). The bands are useful for setting expectations and triggering the right urgency level for remediation.
| Band | Rating | Inbox placement | Typical state | Action level |
|---|---|---|---|---|
| 90-100 | Excellent | 95%+ at most receivers | Mature program with discipline | Maintenance only |
| 80-89 | Good | 85-94% typical | Healthy with minor friction | Optimization optional |
| 70-79 | Fair | 70-84% degraded | First visible deliverability issues | Standard Recovery |
| 50-69 | Problematic | 40-69% heavily filtered | Multiple components degraded | Severe Recovery |
| 0-49 | Critical | Below 40% or blocked | Active blocklist or trap hits | Critical Recovery + delisting |
The 70-79 band catches teams off guard because the score sits within shouting distance of good but the deliverability impact is real. Enterprise corporate filters apply Validity-informed thresholds at 80, not 70, so the score sitting at 76 already triggers Proofpoint and Mimecast additional scrutiny on top of their own internal models. The recovery engagement at this band is structurally simpler than at the lower bands because typically only one component is the root cause; the Standard Recovery tier handles this pattern with the predictable 4-6 week timeline.
Content frequency, missing unsubscribe, list purchase, bulk sender violations
Outdated lists, failed CRM exports, missing pre-send verification
Pristine traps = list buying. Recycled traps = stale list age
Content patterns, sending consistency, engagement signals
Missing reverse DNS, cloud generic IPs without dedicated rDNS
The phases run sequentially with the active remediation concentrated in weeks 1-3 and the measurement window covering weeks 4-10. The rolling 30-day Validity window is the structural constraint; the engagement cannot end before the window has fully refreshed with clean data because the score does not reflect the remediation until then.
Validity dashboard review, Postmaster and SNDS snapshot, blocklist sweep across 80+ DNSBLs, component-level scoring identifies the dominant root cause within 72 hours.
List hygiene execution, suppression maintenance, complaint feedback loop integration, content adjustments, blocklist delisting submissions where applicable.
Continued clean sending under monitored conditions. Postmaster shows early-warning improvements (7-day windows). Validity 30-day score begins reflecting recovery.
Validity score stabilizes at the recovered level. Weekly check-ins confirm no drift. Maintenance runbook handoff for ongoing operations team execution.
Gmail, Microsoft, and Yahoo each run their own internal reputation models based on engagement signals from their own users that Validity does not see. A Sender Score of 95 with Gmail spam-foldering is common and reflects the Gmail-specific signals the Validity score does not capture: open rates and reply rates from Gmail users specifically, complaint rate at Gmail in isolation from other receivers, sending consistency to Gmail, content engagement patterns Gmail algorithms detect. The remediation in that case is a different engagement type focused on Google Postmaster Tools optimization, engagement-based segmentation to remove unengaged Gmail subscribers, and content adjustments based on Gmail telemetry rather than Validity components. EMP runs that as the Gmail-specific deliverability engagement separate from the Sender Score recovery; the diagnosis call identifies which engagement is the right answer before any commitment is signed. Customers who pursue Sender Score recovery to fix a Gmail-specific problem end the engagement with a higher score and the same Gmail spam-foldering.
All four tiers are fixed-fee. The Diagnosis Only tier exists for organizations that want the component analysis and remediation plan without commitment to execution; the document is delivered standalone with no obligation. Standard, Severe, and Critical tiers add the remediation execution with proportional monitoring depth.
Component analysis · no execution.
Score 70-79 · one critical component.
Below 70 · multiple components.
Below 50 or blocklisted.
"Why does the recovery take 4-10 weeks rather than 1-2 weeks?"
The constraint is the rolling 30-day measurement window. Even perfect sending after the remediation takes 30 days to fully flush the negative signals from the rolling average; Validity averages the most recent 30 days of sending behavior into the score, so the negative signals from before the remediation continue to drag the score down until they age out of the window. The active remediation work concentrates in weeks 1-3; weeks 4-10 are the measurement-window refresh where the engagement waits for the rolling window to fully reflect the clean behavior. Customers expecting recovery in days are managing against the wrong measurement model; the Validity system is structurally slow because the 30-day average dampens both drops and recoveries. Postmaster Tools updates faster (7-day windows on some metrics) so the early-warning of improvement shows up at Gmail first.
"Can we just pay Validity for IP Certification to skip the recovery?"
No, and EMP would not recommend it even if it was available. Validity IP Certification runs approximately 12,000 USD annually and provides preferred reputation status with select mailbox providers, but it requires the IP to qualify on baseline reputation criteria before certification is granted; an IP at score 64 does not qualify for certification regardless of payment. The certification is also not a substitute for the underlying remediation work because the Gmail, Microsoft, and Yahoo internal reputation models are not directly affected by IP Certification status. The pay-to-fix dynamic with Validity is real and worth naming: the free score drops, the proposed solution is a five-figure annual contract, the incentive structure feels off. EMP recommends the remediation engagement as the right answer regardless of whether IP Certification is pursued later as an optimization on top of recovered reputation.
"What if we discover during diagnosis that the score is fine but Gmail is the problem?"
The diagnosis phase identifies this scenario explicitly and the engagement adjusts. If Sender Score is above 80 and the customer-reported deliverability issue is at Gmail specifically, the engagement type is wrong and EMP says so during the diagnosis readout. The customer can choose to pursue the Gmail-specific engagement instead (engagement-based segmentation, Postmaster-driven optimization, content adjustments) at the appropriate tier for that work, or accept the diagnosis deliverable standalone and resolve the Gmail issue internally. EMP applies the Diagnosis Only fee (850 USD) toward the Gmail-specific engagement as a goodwill credit when the customer transitions, so the customer does not pay twice for diagnosis work. The diagnosis itself often has value beyond the engagement question because most customers have not done the structured Validity component analysis and the document surfaces opportunities the customer team can address internally.
"How do we know the recovery is working before the score updates?"
Four leading indicators visible before Validity catches up. First, Google Postmaster Tools 7-day domain reputation moves from Low or Bad toward Medium and High within 2-3 weeks of clean sending; this is the fastest leading indicator. Second, Microsoft SNDS color status shifts from red or yellow toward green as the daily complaint and trap data refreshes; usually visible at 1-2 weeks. Third, ESP dashboard metrics (bounce rate, complaint rate, unsubscribe rate) show immediate response to the remediation; the same day the cleanup runs, the next send shows lower bounce and complaint rates. Fourth, seed testing across 6-10 providers shows inbox placement improvement at the providers where reputation has not yet been damaged; Gmail and Yahoo often show recovery first because their algorithms refresh faster than the corporate filters. The weekly recovery report aggregates all four into a single document.
"Will we need to pause sending during the recovery?"
Not full pause but volume reduction is common during the active remediation phase. The Standard Recovery typically maintains 50-70 percent of normal sending volume during weeks 1-3 with the list cleaned and segmented; the Severe Recovery often reduces to 20-40 percent; the Critical Recovery may pause non-transactional sending entirely for 1-3 weeks while the underlying reputation rebuilds. Transactional email (password resets, order confirmations, account notifications) continues at full volume in all cases because pausing it produces immediate customer impact and the recipients of transactional email do not contribute to the complaint and bounce signals at the same rate. The volume reduction is structured around the engagement plan; the customer team approves the volume targets before any reduction is applied and the recovery report tracks the planned vs actual volume each week.
"What happens if recovery does not reach the target score?"
EMP guarantees recovery to the score target for the engaged tier (85+ for Standard, 80+ for Severe, 75+ for Critical) within the timeline (6 weeks for Standard, 8 weeks for Severe, 12 weeks for Critical) or the engagement extends at no additional fee until the target is reached. In EMP 2024-2026 engagement history, 87 percent of customers reach the target within the original timeline; 11 percent require the extension; 2 percent require IP migration or are determined during the extension that the underlying root cause is not addressable through reputation remediation. The 2 percent outcome is the case where the customer business model itself produces complaint and trap rates that no amount of remediation resolves (cold outreach to purchased lists, scraping-based prospecting); the engagement closes with a refund of the unused portion and a recommendation to change the underlying acquisition practices that no consultant can fix on behalf of the customer.
Visible component categories (~30 data points total):
Algorithm includes additional unpublished data points; visible components account for the majority of score movement.
Tier-specific timelines:
The 30-day rolling window is the structural constraint. Postmaster Tools (7-day) shows early-warning improvements before Validity catches up.
EMP 2024-2026 distribution:
Diagnosis identifies the dominant component in first 24-72 hours.
Four data sources on different cadences:
Weekly recovery report aggregates all four into single document.
Yes, included in Severe and Critical tiers:
Delisting requires root cause documentation + evidence the underlying issue is resolved.
Last resort option:
EMP recommends IP migration in 15-20% of Critical Recovery cases. 80-85% recover in place.
Different problem, different engagement:
EMP runs this as separate Gmail-specific engagement, diagnosis call identifies which fits.
Score is dynamic. Maintenance runbook covers:
Maintenance tier at $950/month for quarterly check-ins + drift response.
The scheduling call gathers four data points required to size the engagement: current Sender Score at senderscore.org (or estimated band if not checked), receiver pattern of degradation (enterprise corporate, Gmail, mixed), any active blocklist presence on Spamhaus or similar, sending volume per month. With those four points EMP issues a fixed-fee quote within 48 hours. The Diagnosis Only tier is available standalone for organizations that want the component analysis before committing to remediation execution; the document delivered standalone has value even if the customer team executes the remediation internally afterward.