What it does
Identifies ConvertKit subscribers who haven’t opened or clicked in 60+ days, enriches them with behaviour notes, and launches a multi-touch revival sequence that adapts based on their response so you can prune only the truly inactive contacts.
Why I recommend it
ConvertKit’s built-in cold-subscriber pruning is binary. This automation gives you a last-chance revival programme with personalised messaging so you keep valuable subscribers while still protecting deliverability.
Expected benefits
- 10 – 20% of “cold” subscribers reactivated
- Better deliverability by sunsetting only the unresponsive
- Clear audit trail of re-engagement attempts
- Less manual list hygiene work for marketers
How it works
Weekly job pulls ConvertKit subscribers with no opens/clicks in 60 days -> log them in Airtable with last activity + tags -> Claude drafts personalised revival copy referencing their signup source/content interests -> ConvertKit API adds them to a three-step automation (check-in, offer, last call) -> contacts who engage are tagged “revived,” non-responders are archived after sequence.
Quick start
Run ConvertKit’s cold-subscriber report manually, export to CSV, and send a single “still want to hear from us?” email. Track revival rate to set expectations before building the automated multi-step flow.
Level-up version
Tailor revival incentives by segment (VIP vs freebie seekers), insert dynamic content based on their most downloaded lead magnet, sync reactivated subscribers to CRM for follow-up, and alert sales when high-LTV contacts wake back up.
Tools you can use
Email: ConvertKit
Storage/logic: Airtable, Google Sheets
AI copy: Claude, Jasper
Automation: Zapier, Make
Notifications: Slack, email
Also works with
ESP platforms like Mailchimp, ActiveCampaign, Drip using similar list segments.
Technical implementation solution
- No-code: Scheduled Zapier search for cold subscribers -> write to Airtable -> Claude step drafts copy -> ConvertKit “Add to Automation” action -> Slack alert summarising revival stats.
- API-based: Cron job hits ConvertKit API -> stores cold list in Postgres -> serverless function generates copy + updates ConvertKit sequences -> dashboard in Looker tracks revival vs archive counts.
Where it gets tricky
Ensuring you respect consent/privacy rules when using AI for personalisation, avoiding over-emailing reactivated contacts, and keeping suppression rules synced across ConvertKit and paid audiences.
