Updated · 9 min read
Reputation recovery: the 90-day playbook for dropping from High to Low
Postmaster Tools moves your domain reputation to Low. Spam complaints spiked three weeks ago and you caught it late. Deliverability is tanking and stakeholders want it fixed by Friday. The honest answer: it takes 6–12 weeks of disciplined recovery — and the plan is the same every time. Here's the 90-day playbook.
Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
Accept the timeline first
Reputation damage compounds fast and heals slowly. The 6-week recovery isn't because the work is slow — it's because ISP trust is built through sustained positive signals over rolling windows, and there is no shortcut.
Before starting, set expectations with stakeholders: 6 weeks minimum to see Postmaster Tools move back toward Medium, 12 weeks to reach High. Pushing volume during recovery extends the timeline. The recovery is only as fast as your willingness to throttle.
Week 1 — Diagnose and stop the bleeding
1. Confirm the root cause. Complaint rate spike? Large dormant audience activated? New ESP/IP? Authentication failure? The fix depends on the cause; don't skip the diagnosis to act faster.
2. Stop all broadcasts to dormants. Suppress any user who hasn't engaged in 30 days from marketing. This is the single biggest lever — cuts the bad signal volume immediately.
3. Audit authentication. SPF, DKIM, DMARC all passing at 99%+ in Postmaster. Any dip fixes here first; reputation recovery on unauthenticated mail is impossible.
4. Audit recent content. Any subject lines or content triggering filters? Image-heavy templates? URL shorteners? Fix the obvious ones.
,
Weeks 2–4 — Rebuild on engaged users only
Audience: last-30-day-engaged users only. Users who opened or clicked in the last 30 days. This is your "safe" audience — high positive-signal probability per send.
Volume: 30–50% of pre-incident volume. If you were sending 500K/day, send 150–250K/day. Ramp cautiously.
Content: your best-performing campaigns only. Not promotional-heavy broadcasts. Not experimental templates. Known-good content with high engagement history.
Monitoring: daily. Postmaster Tools, complaint rate, bounce rate. Any regression = further throttle.
The goal of weeks 2–4 is to feed the reputation algorithm as many positive signals as possible without adding any negative ones. Engaged users + good content + reduced volume = the signal mix that slowly repairs reputation.
Weeks 5–8 — Cautious volume expansion
If Postmaster Tools shows improvement (Low → Medium directionally, or complaint rate dropping below 0.2%), begin expanding:
Expand audience window from 30 to 60 days engaged.
Volume: 60–75% of pre-incident.
Gradually reintroduce content variety. Seasonal campaigns, new launches — but in smaller test sends first.
Still suppressing >90-day dormants. These are the users who triggered the original problem; keep them off the list.
If Postmaster hasn't moved by week 5, the recovery isn't working — usually because the root cause wasn't addressed. Re-diagnose before pushing volume further.
Weeks 9–12 — Return to normal operations
Postmaster at Medium, complaint rate below 0.15%, bounce rate stable. Now:
Volume back to 100%. Full pre-incident volume restored.
Audience expansion. 90-day engagement window; some dormants may re-enter via win-back flows (winback flows guide). Never re-include the full dormant cohort at once.
Permanent list hygiene. The hygiene policy rules become a standing part of operations, not a one-time cleanup. The reputation incident is preventable next time if the policy holds.
,
What to tell stakeholders
Executive-level summary for week-1 communication:
"We've identified a deliverability issue — our sender reputation with Gmail has dropped. The cause is [X]. Recovery is expected to take 6–12 weeks. During recovery, our sending volume will be reduced to 30–50% of normal, focused on our most engaged users. Revenue impact during recovery: ~$[estimate] below forecast. Once recovered, we'll have a revised list-hygiene policy that prevents recurrence."
Clear, specific, honest. Avoid the trap of under-promising the recovery timeline to make the news easier to deliver; setting a 2-week expectation that becomes 10 weeks is worse than setting 10 weeks up front.
The Deliverability Management skill covers the recovery sequence as one of its core playbooks. Having it documented before you need it is the difference between a structured recovery and a panicked one.
Frequently asked questions
- Can I recover faster than 6–12 weeks?
- Rarely. Reputation healing runs on rolling time windows at major ISPs (Gmail uses roughly 7-day rolling windows for domain reputation). You can't force the windows to move faster; all you can do is ensure the signals in each window are clean. Pushing volume to 'prove' you're fine extends the timeline.
- Should I switch to a new IP or ESP during recovery?
- Usually not. Modern ISPs weight domain reputation more than IP reputation — switching IPs doesn't reset anything meaningful. Switching ESPs adds a new IP warmup on top of the domain recovery, compounding the pain. Stay put; fix the underlying issues on the existing infrastructure.
- What if Postmaster Tools shows no improvement after 4 weeks?
- The recovery isn't working. Three common reasons: (1) you didn't fully address the root cause, (2) you're sending too much volume for the 'safe' audience size, (3) another issue has emerged (authentication regression, new complaint source). Re-diagnose from scratch before continuing.
- Can I keep sending transactional during recovery?
- Yes, and you should — they're isolated by subdomain (if you set that up) and have high engagement. If you don't have subdomain separation, transactional might be riding the same reputation as the damaged marketing domain. Consider setting up a separate transactional subdomain as part of recovery.
- How do I prevent this from happening again?
- List hygiene policy enforced automatically, weekly Postmaster monitoring, complaint rate alerting, and an incident-response runbook. Most reputation incidents are slow-moving — a week or two of rising complaint rate before the impact lands. Weekly monitoring catches them early; automated hygiene prevents the buildup that causes them.
- What's the revenue impact during recovery?
- Roughly proportional to the volume reduction. If you're sending 40% of normal volume to a 40% subset of your list, expect revenue around 30–50% of normal during weeks 2–4, 60–80% during weeks 5–8, back to normal by week 12. Model this into the stakeholder communication so the finance team isn't surprised.
This guide is backed by an Orbit skill
Related guides
Browse all →Domain vs IP reputation: which one actually matters
Deliverability reputation splits across two systems: the sending IP and the sending domain. They behave differently, recover differently, and modern mailbox providers weight them differently. Here's what's actually going on and which one to care about.
Email deliverability — the practitioner's guide
Deliverability is the cumulative result of every send decision over the lifetime of a domain. This guide covers the four pillars — authentication, reputation, engagement, and list hygiene — and how to recover when one breaks.
The unsubscribe page is the most important page in your lifecycle program
The page every lifecycle team ignores is the one that quietly decides sender reputation, suppressed-list quality, and the fate of your next quarter's deliverability. A short defence of why it's worth the ten-minute rebuild.
SPF, DKIM, and DMARC explained for lifecycle marketers
Three DNS records decide whether your marketing email is trusted or binned. Gmail and Yahoo have required all three for bulk senders since 2024. This is the practitioner's explainer — what each one does, how they interact, and the configuration that actually works.
Dedicated vs shared IP: the real decision
Every Braze sales conversation pitches the dedicated IP. Most programs don't need one. Here's the volume threshold that actually justifies a dedicated IP, the risks most teams don't anticipate, and when the shared pool is genuinely the better call.
List hygiene: the six-rule policy
List hygiene isn't cleanup; it's a continuous policy that runs automatically. Here's the six-rule policy every lifecycle program should have written down, each tied to a specific deliverability outcome.
Found this useful? Share it with your team.