AI Skills Marketplace / Email & Automation

Winback Sequence Architect

The Winback Sequence Architect is a free Claude Skill that decides when to trigger a winback attempt (tiered by engagement history), whether it is currently safe to send given real deliverability risk, and when to suppress instead of emailing a customer indefinitely.

↗ View Source ⬇ Download Full Repo (.zip)
MIT
License
4 action outcomes
Decision branches
3-attempt suppression
Escalation rules
Yes
Multi-tool support
Aug 14, 2026
Last updated
15/15 passing
Tests
README.md View raw ↗

What this is (and isn’t)

A decision function over a customer’s engagement history and, optionally, live domain risk metrics, not a hosted service or an ESP integration.

Files

FilePurpose
architect.jsplanWinback() — zero dependencies
test.js15-test suite covering tiered triggers, spacing, suppression, and the deliverability gate
SKILL.mdFull skill definition, loadable in Claude Code/Desktop

The real tension this resolves

Winback timing needs to account for both the customer’s own engagement history AND the sending domain’s current health, or it risks damaging deliverability while chasing customers unlikely to return. Three real guardrails: tiered trigger timing by engagement history, suppression after repeated non-response, and a deliverability gate that holds sends when the domain is already at risk.

FAQ

Is this skill free to use?

Yes. Free to download and run yourself. MV3 charges $175/hr only for implementation help wiring this into your real ESP and domain-health data.

How does tiered timing work?

A customer who was highly engaged before going quiet gets a longer grace period (45 days) than one who was never very engaged (15 days), since their inactivity patterns mean different things.

What happens after repeated winback attempts with no response?

After 3 attempts, the skill recommends suppression rather than continuing to email indefinitely, a real list-hygiene practice that protects sender reputation.

What is the deliverability gate?

Even a customer due for a winback attempt gets held back if the sending domain's bounce or complaint rate is already elevated, so a re-engagement push does not compound an existing deliverability problem.

Does my customer data get sent to MV3?

No. The decision function runs entirely in your own environment.

JR
Jordan Reeves
ABM & Outbound Pipeline, MV3 Marketing