deliverability-incident-response
Triage playbook for when cold email deliverability breaks. Decision-tree guidance for "I landed in spam", "bounce rate spiked", "domain blacklisted", "inbox blocked in warmup", "reply rate dropped". Tells you what to check first, what to fix, and how long the fix takes. Pair with /email-deliverability-audit for diagnosis.
growthenginenowoslawski · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-incident-response技能说明
name: deliverability-incident-response description: Triage playbook for when cold email deliverability breaks. Decision-tree guidance for "I landed in spam", "bounce rate spiked", "domain blacklisted", "inbox blocked in warmup", "reply rate dropped". Tells you what to check first, what to fix, and how long the fix takes. Pair with /email-deliverability-audit for diagnosis.
Deliverability Incident Response
Things break. When they do, you need a playbook — not panic. This skill is the triage decision tree.
The five incident types
| Symptom | Most likely cause | First action | Fix time |
|---|---|---|---|
| Reply rate dropped sharply | Deliverability — emails in spam | Run spam placement test | 1-14 days |
| Bounce rate spiked >3% | Bad list OR domain reputation | Check bounce types | 1-3 days |
| Domain blacklisted | Shared IP bad actor OR your domain got flagged | Check blacklists, rotate if needed | 7-30 days |
| Inbox blocked in warmup | Warmup network flagged sending patterns | Pause, investigate, maybe replace | 1-7 days |
| Gmail marking as promotional | Content triggers (links, images, HTML) | Simplify content | 1-3 days |
Decision tree: "my reply rate dropped"
Step 1: Quantify the drop
Was this week's reply rate < 50% of last 4 weeks' average?
Yes → real drop, continue triage
No → noise, wait another week
If drop is real:
Step 2: Is it campaign-specific or fleet-wide?
Are ALL campaigns dropping, or just one?
All → fleet-level issue (infrastructure or copy pattern)
One → campaign-specific (targeting, copy, list)
Step 3: Fleet-wide drop — check these in order
-
Smartlead Smart Delivery spam test (
/email-deliverability-audit→run-spam-test.ts)- If inbox placement <70% → real deliverability issue, skip to Step 4
- If inbox placement >85% → deliverability is fine, look at copy/targeting instead
-
Check domain authentication (
/email-deliverability-audit→check-domain-auth.ts)- Missing DKIM on any domain → fix immediately (see
/zapmail-domain-setup-publicfor reconnect steps) - DMARC policy=reject with alignment failures → temporarily lower to quarantine
- Missing DKIM on any domain → fix immediately (see
-
Check warmup status (
/smartlead-inbox-manager→list-health.ts)- If multiple inboxes blocked in warmup → warmup network flagged you
- If reputation dropped "good" → "fair" on many inboxes → slow down sending volume
-
Check bounce rate (
/email-deliverability-audit→audit-performance.ts)- If bounce >3% → list quality degraded
- If bounce <1% but reply rate low → emails landing in spam (Step 1 result)
Step 4: You have a spam-placement problem — what to do
Time-ordered actions:
- Immediate (today): Pause the highest-volume campaign. Stop damage.
- Day 1: Run spam placement test on 2-3 sender subsets (tag=active vs tag=new). Find which cohort is worst.
- Day 1: Check the spam-filter-details report from Smart Delivery — specifically which filters are firing. Common:
DKIM_INVALID,HTML_MESSAGE,LINK_REDIRECT. Each has a specific fix. - Day 2: Fix the identified issues:
- DKIM_INVALID → verify DKIM records across all domains, re-publish if needed
- HTML_MESSAGE → simplify email body (fewer fonts, no inline CSS, no tracking pixels)
- LINK_REDIRECT → remove or reduce links in email 1 (ideally 0 links)
- Day 3-14: Slow down send volume. Cut daily send per inbox by 50% for a week. Reputation rebuilds slowly.
- Day 14: Re-test spam placement. If back above 85% → resume normal volume.
Decision tree: "bounce rate spiked"
Step 1: What kind of bounces?
Smartlead categorizes bounces as hard (invalid address) or soft (temporary).
bounce_rate > 3% AND mostly_hard_bounces
→ list quality problem, verify with MillionVerifier
bounce_rate > 3% AND mostly_soft_bounces (greylist, temp)
→ domain reputation problem, slow sending
bounce_rate > 5% either type
→ stop the campaign immediately to prevent ISP suspension
Step 2: If list problem
- Export remaining leads from the campaign
- Run through MillionVerifier (batch, ~$2 per 1,000)
- Only reuse emails with status "ok"
- Discard the rest
Step 3: If reputation problem
Slow way down. Cut daily volume 50% per inbox for 2 weeks. Run warmup more aggressively.
Decision tree: "domain blacklisted"
Step 1: Confirm the blacklist
Check:
- Spamhaus, Barracuda, SURBL via
/email-deliverability-audit→ spam-test report → blacklist detail - MX Toolbox (https://mxtoolbox.com/blacklists.aspx) for a second opinion
Step 2: What tier of blacklist?
- Domain on Spamhaus DBL or SURBL → serious. You may need to replace the domain entirely.
- Sending IP on a DNSBL → usually the IP pool's fault (not yours, if on Zapmail shared IPs). Zapmail rotates IPs; wait 1-2 weeks.
- Minor list (e.g., Barracuda) → submit delisting request at their portal. Usually resolved in 3-7 days.
Step 3: Replace vs repair
- Domain <30 days old + blacklisted → replace. Not worth the cleanup effort.
- Domain >90 days old + blacklisted → try repair. Stop sending for 7 days, submit delisting requests, slowly resume.
- If you replace: archive the old domain, buy a new lookalike via
/zapmail-domain-setup-public, warm it for 2 weeks before reusing.
Decision tree: "inbox blocked in warmup"
Step 1: Why is it blocked?
Smartlead's is_warmup_blocked: true flag usually means:
- Your warmup emails looked like spam to the warmup network
- Too many warmup peers marked them as spam
- The inbox type/provider is rate-limiting
Step 2: Triage
- Check the
blocked_reasonfield (if populated) - If warmup network issue → the inbox reputation may be damaged. Cost-benefit:
- Young inbox (<30 days) → retire, provision new
- Established inbox (>90 days, previously good reputation) → try disabling and re-enabling warmup with lower
total_warmup_per_day(try 15 instead of 40)
- If ISP rate-l