Win back users who went quiet

Paying customers who stop using your product are on their way out, even if they have not cancelled yet. Many drift away because they got stuck, got busy, or forgot what the product could do for them. A small, well-timed message can bring them back while they still have an account and a reason to return.

Why it works

Inactivity comes before cancellation. Users who go quiet often have reasons that are easy to fix: they got stuck on a step, got busy, or forgot what the product could do. A timely message reaches them while they still have an account and data inside it.

Specific messages work because they lower the effort of coming back. A link to the exact skipped step, or a reminder of saved work, makes returning feel like a small task. A personal note invites a reply, and replies tell you what went wrong.

How to do it

1. Define inactivity for your product. Pick the key action that shows real use, such as sending an invoice or publishing a report. Flag users who have not done it within a set window.
2. Split inactive users into groups. Someone who never finished setup needs different help from someone who used the product for months and then stopped. Use what you know about their past activity.
3. Write one specific email per group. Point to a single next step. For stalled setups, link to the step they skipped. For lapsed regulars, show a feature they have not tried or remind them of work saved in their account.
4. Send it from a person. A plain-text email from a founder or support lead, with a reply address that a human reads, feels like a check-in. Ask a simple question, such as “Did something get in the way?”
5. Add an in-app prompt for when they return. If they log in, greet them with a short checklist or a shortcut back to where they left off.
6. Stop after two or three messages. If they still do not engage, tag the account for review and move on.
7. Read the replies. The reasons people give for going quiet often reveal gaps in your onboarding or product.

Example

An online booking tool for fitness studios flags any account that has not taken a booking in 21 days. Studios that never connected a payment method get an email linking straight to that setup step. Studios that were active for months and then stopped get a note from the founder asking what changed, plus a link to a new class-pack feature. Several replies mention a confusing calendar sync, which the team then fixes for everyone.

Metrics to track

• Reactivation rate. The share of contacted users who do the key action again within a set window. Should beat a similar group you did not contact.
• Reply rate. The share who answer the personal email. Higher means the tone and question are working.
• Cancellation rate of inactive users. Compare contacted and uncontacted groups. Contacted users should cancel less.
• Unsubscribe rate on win-back emails. Should stay low. A rise means the messages are too frequent or too generic.

When it backfires

• Generic “we miss you” emails. Messages with no clear next step get ignored and can prompt people to cancel sooner, because they remind them they are paying.
• Wrong threshold. Flagging users too early annoys people who simply use the product on a slower rhythm.
• Ignoring account roles. In a team account, one quiet user may be normal. Look at the whole account before sending.
• Too many emails. A long sequence teaches people to unsubscribe from all your messages, including the important ones.

Questions people ask

How do I decide when a user counts as inactive?

Base it on how often a healthy customer normally uses your product. A daily tool might flag someone after a week of silence. A monthly reporting tool might wait six weeks. Look at your active customers first and set the threshold just past their normal gap.

Should I offer a discount to bring them back?

Usually not as the first step. Inactive users rarely leave because of price. Help them get value again first, and keep discounts for customers who say cost is the problem.

Can I use push notifications instead of email?

For mobile apps, yes, if the user allowed them and the message points to something specific. The same rules apply. Give one clear next step and keep a strict cap on how many you send.