Re-engagement Drip Campaigns: Win Back Inactive Subscribers
How to define inactive subscribers, build a re-engagement drip sequence, and choose between Drip, Sender, Make and Segment based on list size and budget.
For most teams running a win-back sequence on a list of a few thousand people, Drip is the best starting pick. Its workflows let you build the whole re-engagement path in one place: a trigger for silence, a timed series of emails, and an exit rule for people who click, reply or stay quiet. The entry plan covers 1 to 2,500 people at $39 a month on monthly billing. Drip offers a 14-day free trial with no credit card required and no ongoing free plan, so you can build and test the sequence before you pay anything.
This guide covers how to define an inactive contact, how to structure the sequence, which tools fit which list sizes, and what each option costs according to the vendor pricing pages. Prices are quoted as published and may change, so confirm them on the linked pricing page before you commit.
Defining an inactive subscriber
A re-engagement drip is only as good as the definition behind it. If "inactive" means "hasn't opened in 30 days" for a weekly newsletter, you will email people who are simply reading in bursts. If it means "hasn't logged in for a year" for a daily product, you will let paying users drift for months. Pick the definition before you build anything, and write it down as a rule a tool can evaluate.
Email engagement
A subscriber is inactive when they have not opened or clicked anything for a set period. The period should match how often you send. Common thresholds:
- 30 days for daily or weekly senders
- 60 to 90 days for senders who email every one or two weeks
- 90 to 180 days for monthly newsletters
Open tracking is becoming less reliable, so many teams use clicks, replies and site visits as the main signal and treat opens as a weak secondary one. If your tool reports opens, use them only alongside a stronger signal.
Product or purchase activity
For software, the stronger signal is product use: no login, no use of a key feature, or no completed action. For an online shop, it is the time since the last order. Typical product windows are 7 days for a daily-use product, 14 to 30 days for a weekly-use one, and 30 to 60 days for an occasional-use one. These are starting points. Adjust them using your own churn data, not anyone else's benchmark.
Combined signals
The most useful segment combines both. A person who opens every email but never logs in needs a different message from someone who uses the product daily and ignores email. Drip's dynamic segments are built for this kind of rule, and the same idea works with any tool that can filter on two fields at once.
The tools compared
Four options come up most often for re-engagement work. They solve different parts of the problem, so the table below lists what each one is best at, its starting price with the plan and billing view, and the main limitation to plan around.
| Tool | Best for | Starting price (plan, billing) | Key limitation |
|---|---|---|---|
| Drip | Teams that want segments, timed workflows and sending in one product | $39/month, 1 to 2,500 people, monthly billing | No ongoing free plan; the price rises with the number of people in each tier |
| Sender | Small lists that need email sending on a tight budget | Free Forever: 2,500 subscribers and 15,000 emails/month; Standard $6.30/month for 6,000 emails/month | Published paid prices stop at 12,000 emails/month; larger volumes need a quote |
| Make | Triggering win-back from events in other systems, such as a cancelled plan in a billing tool | Free: 1,000 credits/month; Core $9/month on annual billing ($10.59 monthly) for 10k credits/month | Make is an automation layer, not an email sender; each action uses a credit |
| Segment (Twilio Segment) | Companies with many data sources that need one profile to drive win-back | Pricing on request (custom) | No public prices; a larger setup than a standalone email tool |
Drip: the best starting pick for win-back workflows
Drip suits teams that want the trigger, the segment, the email content and the exit rule in one product. You can build a workflow that starts when a person meets your inactivity rule, sends a timed sequence, and removes anyone who clicks or converts. Drip's published plans include unlimited email sends, dynamic segments, onsite campaigns and up to 50 workflows on the lower tiers. Higher tiers add chat and email support, and the 22,501 to 25,000 people tier includes a free migration and personalized onboarding.
Where Drip falls short: the price is set by the number of people in the tier, not by how many emails you send, so a large dormant list can move you into a more expensive band. Clean the list before you launch, and remove hard bounces and complaints, so that the people you pay for are the ones you can actually reach. Drip also has no ongoing free plan, only a 14-day trial, so a small team on a shoestring budget should look at Sender first.
Price: $39/month for 1 to 2,500 people; $89/month for 4,501 to 5,000 people; $154/month for 9,001 to 10,000 people. The published Drip prices above are monthly, and annual billing is not listed for these tiers. Full pricing is on Drip's pricing page.
Sender: the budget option for small lists
Sender's free plan is the most generous starting point in this comparison for a small team. It covers 2,500 subscribers and 15,000 emails a month at no cost, which is enough to run a three-email win-back to a modest list every month. The paid Standard plan is listed at $6.30 a month for 6,000 emails, and Professional at $10.50 a month for 12,000 emails.
Where Sender falls short: the published paid prices stop at 12,000 emails a month. If your re-engagement sequence goes to a larger audience, you will need to request pricing directly. Sender is also the right choice when your rules are simple. If you need many branches, several exit conditions and a long series of workflows, compare it carefully with Drip during the trial stage before you commit to a workflow design.
Price: Free Forever for up to 2,500 subscribers and 15,000 emails a month; Standard $6.30/month for 6,000 emails; Professional $10.50/month for 12,000 emails. Full pricing is on Sender's pricing page.
Make: the trigger layer
Make does not send the email. Its job is to watch other systems and start the right action. That matters for re-engagement because the most reliable inactivity signal often sits in your billing tool, your CRM or your product database, not in your email tool. A scenario in Make can detect that a subscription was cancelled, or that a user has not logged in for a set period, and then add that person to a win-back list in your email sender.
Make's free plan includes 1,000 credits a month with no time limit, but it allows only two active scenarios and a 15-minute minimum interval between runs. Paid plans start with the Core plan at $9 a month on annual billing ($10.59 a month billed monthly) for 10,000 credits a month. Each module action in a scenario uses one credit, so count your actions before you assume the price covers your volume. Make has a visual, no-code builder, access to more than 3,000 apps, and routers and filters for branching logic.
Price: Free for 1,000 credits a month; Core from $9/month (annual) or $10.59/month (monthly) for 10,000 credits a month. Full pricing is on Make's pricing page.
Segment: when the profile is the problem
Twilio Segment is a customer data platform. It collects first-party data from your sites and apps, sends it to downstream tools and builds a unified customer profile. For win-back, that profile can answer questions that a single email tool cannot, such as whether someone bought in a store, used the app last week, and opened a support ticket. The Connections product covers data collection and delivery, and the higher Customer Data Platform tier adds identity-resolved profiles and audience building.
Where Segment falls short: pricing is custom and not published, and the setup is heavier than any of the other tools here. Segment is worth considering when you already have several data sources and a dedicated person who owns the data model. For a list of a few thousand people, it is almost always more tool than you need. Segment's Connections plan mentions a free trial, but the page does not list its length or limits.
Price: pricing on request. Details are on Segment's pricing page.
What it costs at real list sizes
The cost of a re-engagement program depends on the total size of the list you run it against, not just the inactive part, because most tools price by all the people they hold. The table below uses Drip's published tiers to show the monthly and yearly cost at four list sizes. The yearly figure is simply 12 times the monthly price.
| People on list | Drip plan | Monthly price | Yearly cost (12 × monthly) |
|---|---|---|---|
| 2,000 | 1 to 2,500 people | $39 | 12 × $39 = $468 a year |
| 5,000 | 4,501 to 5,000 people | $89 | 12 × $89 = $1,068 a year |
| 10,000 | 9,001 to 10,000 people | $154 | 12 × $154 = $1,848 a year |
| 20,000 | 17,501 to 20,000 people | $289 | 12 × $289 = $3,468 a year |
Two things stand out. First, a list that sits just over a tier boundary costs noticeably more than one just under it, so pruning dormant contacts before a tier threshold can save real money. Second, Sender's free plan covers a list of up to 2,500 subscribers at no cost, which makes it the cheaper choice for very small lists, provided you stay within its limits. For lists above 12,000 emails a month on Sender, request a quote from the vendor.
Designing the sequence step by step
A re-engagement drip usually has three to five emails over two to four weeks. Each email should have a single ask. After the sequence ends, non-responders are suppressed or moved to a long-term sunset list. The example below is a four-email version that works with any of the tools above.
Email 1: the honest check-in
Send this at the inactivity threshold. Say plainly that you have noticed the person has been away, and ask a simple question, such as whether they still want to hear from you or whether their interests have changed. The ask is a click on a preference link or a reply. Keep the subject line specific to the person's last action, such as "Still using the reporting dashboard?", rather than a generic "We miss you".
Email 2: the new-angle message
Send this a few days later. Do not repeat the first email. Show something they have not seen: a new feature, a guide that answers the question they had when they last used the product, or a case study from a customer in their role. A good test is whether the email would still be useful if it arrived with no mention of the person's absence.
Email 3: the offer, if the margin allows
Only include an incentive if the margin supports it. An offer can work, but it also trains people to wait for discounts. If you use one, make it time-limited, name the exact benefit, and link to the single action you want. For a SaaS product, a short onboarding call or a personal walkthrough is often more useful than a discount.
Email 4: the sunset notice
Tell the person that this is the last email unless they take action, and give one clear link to stay subscribed. Anyone who does not click after this email should be suppressed. Keep the sunset email short. It is the one message most likely to be read, so make it a clean, honest close rather than another pitch.
Setting it up in Drip
In Drip, the build sequence follows the same logic as the design above. Create a segment with your inactivity rule, start a workflow from that segment, add the timed emails, and set the exit rule so that anyone who clicks or converts leaves the workflow and returns to normal communication. Drip's workflow limit on the lower tiers is 50, which is plenty for one win-back program alongside your onboarding and transactional flows. Test the full path on a small internal list before you point the workflow at real subscribers.
How to choose a tool for your re-engagement program
Start with three questions: how many people are on your list, where the inactivity signal lives, and how many branches your sequence needs. A list of a few thousand people with the signal inside the email tool points to Drip or Sender. A signal that lives in billing or a CRM points to adding Make as a trigger layer. A company with many data sources and a dedicated data team should look at Segment, but only once the basic sequence already works.
| If you need | Pick | Because |
|---|---|---|
| Segments, timed workflows and sending in one product | Drip | Segment, workflow and email content sit together, and the trial lets you test the sequence first |
| Email sending on a small budget | Sender (Free Forever or Standard) | The free plan covers 2,500 subscribers and 15,000 emails a month at no cost |
| Win-back triggered by billing or CRM events | Make, plus your existing sender | Make watches the other system and adds people to the right list; the Core plan starts at $9/month on annual billing |
| One customer profile across many data sources | Segment | Profile and audience tools fit companies with data teams; pricing is on request |
Setup checklist
Use this checklist before you launch. It applies whichever tool you choose, and it is most important in the first two steps, because a bad segment or a dirty list undermines the whole program.
| Step | What to do | Done when |
|---|---|---|
| 1. Define inactivity | Write the rule with a real event: no clicks, no logins, or no orders for a set period | The rule can be written as one filter in your tool |
| 2. Clean the list | Remove hard bounces and complaint addresses before the sequence starts | Bounce and complaint lists are suppressed |
| 3. Build the segment | Add the inactivity rule and an exclusion for anyone already in an active sequence | The segment count matches a manual spot check of 20 contacts |
| 4. Write the emails | Three to four emails, one clear ask in each, with a specific subject line | Each email still makes sense if read on its own |
| 5. Set exit rules | Anyone who clicks, replies or buys leaves the sequence | A test contact who clicks exits the workflow automatically |
| 6. Test on a small list | Run the full path with internal addresses | Every email and exit rule behaves as written |
| 7. Launch to a sample | Send to a random 10% of the inactive segment first | Unsubscribes and replies are reviewed for two weeks |
| 8. Suppress non-responders | Move people who ignored the full sequence to a sunset list | The sunset list is excluded from regular sends |
Measuring whether it works
Measure the outcomes that matter for the business rather than only opens. Track the share of inactive contacts who clicked, replied or bought, the unsubscribe rate, and whether re-engaged people are still active 60 to 90 days later. An unsubscribe rate that rises during a win-back sequence is expected and healthy, because those people were not going to read your email anyway. A re-engagement rate that is high but followed by a fast drop-off means the offer or the message is buying attention, not interest.
For SaaS products, add revenue and retention to the report. Compare the revenue from re-engaged users with the same metric for users who were never in the sequence, and check whether re-engaged users are still using the product after the sequence ends.
Common mistakes
- Never removing non-responders. Contacts who ignore every email hurt deliverability and make your metrics harder to read.
- Sending too often. Daily "come back" messages make the sender look desperate and teach people to ignore the brand.
- No defined end. The sequence needs a clear last email and a clear suppression step.
- Generic messages. Refer to what the person actually did, such as the feature they used or the plan they cancelled.
- Ignoring the people who come back. Re-engaged subscribers should get a short welcome-back message, not return to a generic newsletter on the same day.
- Pricing blind. Before widening a win-back sequence, check how your tool counts people, because a larger audience can move you up a tier.
Frequently Asked Questions
How many emails should a re-engagement sequence have?
Three to four is usually enough. Each email should have one job: a check-in, a new reason to return, an optional offer, and a final sunset notice. Longer chains tend to train subscribers to ignore the sender, and a clear sunset is better for list quality than an open-ended series.
Should I offer a discount in a re-engagement drip?
Only if the margin supports it. Send the same content without an offer first, and compare the response with a version that includes one. If people return without the discount, you have kept the margin. If you do offer one, make it time-limited and tie it to the specific value of the customer you are trying to win back.
When should I suppress a contact instead of emailing them again?
Suppress contacts who ignored the full sequence and the sunset email. Suppress them immediately after a complaint or a repeated hard bounce. Keep them on a sunset list for occasional sends only if your tool and your policy allow it.
What is the cheapest way to run a win-back sequence?
For a list of up to 2,500 subscribers and 15,000 emails a month, Sender's Free Forever plan costs nothing. Once you need workflows, segments and a larger audience, Drip's entry plan starts at $39 a month for 1 to 2,500 people on monthly billing. Confirm current prices on each vendor's pricing page before you choose.
Does Make send the re-engagement emails?
No. Make detects events in other systems and triggers an action, such as adding a contact to a list in your email sender. You still need a sending tool. Make's free plan includes 1,000 credits a month and two active scenarios, and paid plans start at $9 a month on annual billing for 10,000 credits.
Do I need Segment for a re-engagement program?
Usually not. Segment is a customer data platform that makes most sense when you have several data sources and a team that manages them. For most lists, a segment rule inside your email tool, plus a trigger from Make if the signal lives elsewhere, is enough. Segment's pricing is on request, so ask for a quote before you plan around it.
How long should I wait before starting a re-engagement drip?
Many teams start after 60 to 90 days of silence for a regular sender, and after a shorter window for daily products. Waiting too long makes recovery harder, while starting too early can email people who are simply on a seasonal or occasional cycle. Set the window from your own data, then review it after the first full sequence.