Updated · 9 min read
Reputation recovery: the 90-day playbook for dropping from High to Low
Postmaster Tools just flipped you to Low. The complaint spike happened three weeks ago and you missed it. Deliverability is sliding and the CMO wants it back by Friday. The honest answer: 6–12 weeks of disciplined recovery, and the playbook is the same every time.
By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
Accept the timeline first
Reputation damage compounds fast and heals slowly. The 6-week floor isn't because the work is slow — it's because ISP trust rebuilds through sustained positive signal across rolling windows, and there is no shortcut.
Set expectations with stakeholders on day one. Six weeks minimum before Postmaster Tools starts drifting back toward Medium. Twelve weeks to reach High. Push volume during recovery and you extend the timeline — the recovery moves exactly as fast as your willingness to throttle, and not a day faster.
The sooner you say that out loud, the better the rest of the quarter goes. A finance team told "two weeks" in week one gets angry in week six. A finance team told "twelve weeks" in week one is pleasantly surprised in week nine.
Week 1 — Diagnose and stop the bleeding
Before anything else, find the cause. Complaint spike? A dormant segment reactivated into a campaign? New ESP or IP? Authentication regression? The fix depends on the root cause, and skipping the diagnosis to "move fast" is how teams spend week six discovering they rebuilt the wrong thing.
Suppress dormants immediately. Anyone who hasn't engaged in the last 30 days comes off marketing today. This is the single biggest lever in week one — it cuts the bad-signal volume at source and lets the rolling windows start seeing clean sends.
Audit authentication. SPF, DKIM, DMARC all passing at 99%+ in Postmaster. Any dip gets fixed here first. Recovering reputation on unauthenticated mail is impossible — the receiving server can't tell your recovery sends from someone spoofing you.
Audit recent content. Subject lines pinging filters? Image-heavy templates? Shortened URLs from a sketchy domain? Fix the obvious ones. You're not hunting for perfection — you're removing the things that made last week's numbers worse.
,
Weeks 2–4 — Rebuild on engaged users only
The goal for the next three weeks is simple: feed the reputation algorithm as many positive signals as possible while adding zero negatives. Engaged users plus known-good content plus reduced volume equals the signal mix that repairs reputation. That's the entire formula.
Audience: last-30-day engaged users only. Anyone who opened or clicked in the last 30 days. This is your safe cohort — high probability of positive signal per send, near-zero probability of complaint.
Volume: 30–50% of pre-incident. If you were pushing 500K/day, you're pushing 150–250K/day now. Ramp slowly or not at all.
Content: your best-performing campaigns only. Not promotional-heavy broadcasts. Not the experimental template you've been itching to test. Your known-winners, reused.
Monitoring: daily. Postmaster Tools, complaint rate, bounce rate. Any regression and you throttle further. Discipline here is boring and load-bearing.
Weeks 5–8 — Cautious volume expansion
If Postmaster has drifted Low to Medium or the complaint rate is sitting below 0.2%, you can start expanding. Cautiously.
Engagement window: 30 days becomes 60 days.
Volume: 60–75% of pre-incident.
Content variety: seasonal campaigns and launches come back in — but as smaller test sends first, not to the full reactivated file.
90-day dormants stay suppressed. These are the users who triggered the original incident. Keep them off.
If Postmaster hasn't moved by week five, the recovery isn't working. Almost always because the root cause wasn't fully addressed. Re-diagnose before pushing further volume — compounding a broken send into a broken reputation makes week eight worse, not better.
Weeks 9–12 — Return to normal operations
Postmaster at Medium, complaint rate below 0.15%, bounces stable. You're through it.
Volume back to 100%. Full pre-incident restored.
Audience expansion. 90-day engagement window; some dormants re-enter via win-back flows (winback flows guide). Never re-include the full dormant cohort at once — that's how incidents recur.
Permanent list hygiene. The hygiene policy becomes standing operations, not a one-time cleanup. If the policy holds, the next incident doesn't happen.
,
What to tell stakeholders
Here's a workable week-one comms template for executives:
"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, sending volume reduces 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."
Specific, honest, dated. Avoid the trap of soft-pedalling the timeline to make the news easier — a two-week promise that becomes ten is far worse politically than a ten-week promise up front. The finance team can model a long recovery. They cannot model a lie.
A few things that come up in every recovery: yes, you can keep sending transactional — in fact you should, if transactional sits on a separate subdomain with its own reputation. If it doesn't, it's currently riding the damaged marketing domain, which is a great argument for setting up subdomain separation as part of this project. And no, switching IPs doesn't help. Modern ISPs weight domain reputation over IP reputation, so a new IP resets nothing meaningful while adding a warmup on top of the recovery you're already doing. Stay put.
Revenue impact is roughly proportional to the volume cut. Sending 40% of normal to 40% of the list lands you at 30–50% of normal revenue in weeks 2–4, 60–80% in weeks 5–8, back to normal by week 12. Model it into the comms so finance isn't surprised.
The Deliverability Management skillcovers this 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 — and panicked recoveries are how programs end up in week fourteen still explaining to the CFO why this isn't fixed yet.
Frequently asked questions
- How do I recover email sender reputation?
- Four-step playbook. (1) Pause all non-essential sending for 3-7 days so the reputation signal stabilises. (2) Resume with only your most engaged audience — past-30-day-openers or past-7-day-clickers — for 2-3 weeks at reduced volume. (3) Gradually re-introduce broader segments week by week, watching spam rate and complaint rate at each expansion. (4) Do NOT return to full volume until Google Postmaster Tools shows stable High domain reputation for 14+ consecutive days. Total recovery time: 4-8 weeks.
- How long does email reputation recovery take?
- 4-8 weeks for most programs. Faster only if the damage was minor (a single send to a dirty list) and caught quickly. Slower if the damage accumulated over months (gradual list decay producing rising complaint rates). The actual speed depends on mailbox providers evaluating your most recent 30-60 days of sending — there's no trick to accelerate their re-scoring; you can only produce the cleanest possible recent sending history and wait.
- What's the fastest way to damage email reputation?
- Sending a large campaign to an unengaged or purchased list. Mailbox providers register the complaint spike within hours, and the reputation damage shows up in placement across all your future sending within 24-72 hours. Recovery from a single purchased-list blast routinely takes 6-10 weeks. The next fastest damage vector is failing-DMARC authentication (often from a third-party sender you forgot to include in your SPF record) — which can land your legitimate mail in quarantine or reject.
- Should I change IPs during reputation recovery?
- Usually no — it's a short-term workaround that makes the problem worse long-term. Domain reputation (not just IP) is now the primary signal mailbox providers weight, and domain reputation doesn't reset by changing IPs. Switching IPs also means starting warmup from scratch on the new IP, which throttles your recovery ramp. The exception: if a specific IP is blocklisted at Spamhaus or similar RBL, a temporary IP change buys time while you remediate the underlying sending behaviour.
- Will my reputation come back if I stop sending?
- Only partially. Sender reputation requires recent positive engagement signals to recover. Stopping sending removes the negative signal but doesn't produce positive ones — reputation will plateau rather than improve. Real recovery requires resumed sending, at low volume, to highly-engaged recipients, so the positive engagement signal (opens, clicks, replies, out-of-spam moves) rebuilds the reputation score.
This guide is backed by an Orbit skill
Related guides
Browse allDomain vs IP reputation: which one actually matters
Deliverability reputation is two parallel scores, not one. IP and domain behave differently, recover differently, and the balance between them has shifted hard toward domain over the past five years. Here's what that means for what you monitor and how you warm up.
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.
Email deliverability — the practitioner's guide
Deliverability isn't a setting. It's the running total of every send decision you've made since you bought the domain. Four pillars hold it up. Break one and the whole program starts leaking.
The unsubscribe page is the most important page in your lifecycle program
The page every lifecycle team ignores is the one quietly deciding sender reputation, suppression-list quality, and the fate of next quarter's deliverability. A short defence of why it deserves 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 made all three mandatory for bulk senders in 2024, and the grace period is over. This is the practitioner's explainer: what each one does, how they interact, and the setup order that won't block your own mail.
Dedicated vs shared IP: the real decision
Every ESP sales conversation pitches the dedicated IP as an upgrade. For most lifecycle programs it isn't — it's a trade, and often a losing one. Here's the volume threshold that actually justifies dedicated, the risks most teams don't anticipate, and when the shared pool is genuinely the better call.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 54 lifecycle methodologies, 55 MCP tools, native Braze integration. Pay what it's worth.