reactivation-specialist

Featured

Use when the user asks to "build a win-back campaign", "re-engage lapsed subscribers", "run a re-permission / re-consent sweep", or "sunset my dead list"; produces a closed-loop reactivation program — a lapsed-cohort definition, a staged offer ladder, a re-consent (re-permission) capture step, and a sunset-confirm / suppression rule. Owns none of the SEND-N sub-item notes: engagement-decay / sunset is email-sequence-designer's and preference-center / frequency options is preference-frequency-manager's — this skill references those notes, it does not re-emit them. Not for the general lifecycle flows (welcome/cart/post-purchase) — use email-sequence-designer; not for the preference-center / opt-down ladder — use preference-frequency-manager; not for the consent record itself — use consent-registry; not for computing EQS or the N1 veto — use email-quality-auditor. 流失召回/重新授权/沉默用户清理

Web & Frontend 2,766 stars 358 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 98/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Reactivation Specialist Designs a closed-loop reactivation program for lapsed email cohorts — the win-back offer ladder, the re-consent (re-permission) capture step, and the sunset-confirm / suppression rule. It defines the lapsed cohort by a no-engagement window, stages an offer ladder that escalates then stops, requires re-engaged subjects to re-affirm opt-in, and specifies the terminal rule that either re-permissions a subject or suppresses them. It does **not** author the SEND **N (Nurture / Lifecycle)** sub-item notes: engagement-decay / sunset is owned by [email-sequence-designer](../email-sequence-designer/SKILL.md) and preference-center / frequency options by [preference-frequency-manager](../preference-frequency-manager/SKILL.md) — this program feeds both owners its sunset-confirm and re-consent facts to fold in, and references their notes rather than re-emitting them. It does not design the everyday lifecycle flows, own the consent record, or compute the final EQS. ## Quick Start ``` Build a win-back campaign for subscribers who haven't opened in [N] days on [ESP]. Here is my engagement export: [paste/path]. I can offer [incentive]. ``` ``` My unengaged tail is [X]% of the list and complaints are creeping up. Design a re-permission sweep with an offer ladder and a sunset-confirm rule. ``` ``` I need to clean the dead weight off my list without a bulk delete. Design a reactivation program that re-consents the recoverable subjects and suppresses the rest. ``` ...

Details

Author
aaron-he-zhu
Repository
aaron-he-zhu/aaron-marketing-skills
Created
8 months ago
Last Updated
today
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

email-sequence-designer

Use when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound sequence"; produces general lifecycle automation flows (welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound) with trigger, step timing, branch/exit conditions, goal, frequency governance (send caps, quiet hours, fatigue guardrail), a sunset path, and a SEND N-dimension score. Not for the closed-loop win-back / re-consent (re-permission) program on a lapsed cohort — use reactivation-specialist; not for writing each email's copy — use email-creative-builder; not for computing EQS or the N1 unsubscribe veto — use email-quality-auditor. 邮件自动化流程设计/购物车挽回/流失召回序列

2,766 Updated today
aaron-he-zhu
AI & Automation Listed

reengagement-segmenter

Segment a lapsed audience by the actual blocker that stalled each relationship, then plan a distinct reengagement motion per segment, including the segment that should be left alone. Works on dormant pipeline, lapsed customers, cold trial users, or an inactive list. Applies a blocker taxonomy (never activated, timing, lost to incumbent, price, trust damage, drifted, unknown), enforces hard exclusions first (unsubscribed, complaints, active competitor contracts), flags records whose stated reason contradicts their evidence, and drafts sequences through the outbound-engine gate. Use whenever the user says "win-back", "reengagement", "re-engage", "lapsed customers", "dormant accounts", "stalled deals", "gone quiet", "cold pipeline", "churned users", or wants to revive a list without blasting it. Consumes icp-research and brand-voice-guide; sequences inherit outbound-engine's no-send discipline.

0 Updated 6 days ago
esmefong
Web & Frontend Listed

customer-win-back

Guidance for re-engaging dormant leads and churned customers; trigger when a user needs to rebuild relationships with lapsed prospects or lost accounts before pitching product or features.

8 Updated today
the-nam-shub