Churn prevention emails: what to send when usage drops

A churn prevention email is a message to a paying customer whose usage has started to fall, sent before they decide to cancel and written about the specific thing that changed in their account. A cancellation is usually the end of a decline, not the start of one: logins thin out, the person who championed the tool stops showing up, a workflow quietly moves somewhere else. By the time someone clicks Cancel, the decision has mostly been made. The window where an email can help is the drop, not the exit.

This guide covers how to read a usage drop, when to write, what to say for each kind of drop, and what to avoid. It is for customers who are still paying. For people who have already stopped, see win-back emails; for the general approach, see the behavioral email guide.

Signs a SaaS customer is about to churn

A health score is only as good as the behavior under it. These are the signals worth watching, and each one points at a different email:

Compare each account with its own history, not with a global average. A team that logs in once a week by design is healthy at once a week. The signal is a change: the same account doing noticeably less than it used to.

When to send an at-risk customer email

Trigger on a sustained change, not a single quiet day. A week off is a holiday; two or three weeks well below their usual level is a trend. Waiting that long filters out the noise without waiting so long that the customer has already made other plans.

Two or three emails is enough, each with a different job. Stop the moment usage recovers, meaning they are back doing the core action, not just logged in once. Stop when they reply, and get that reply to a person quickly; an at-risk customer who writes back and waits two days has their answer about how much you care. If they cancel, they move to your win-back emails, not further down this sequence.

What to write when a customer’s usage drops

• Name what changed, in their terms. “The Billing queue has 23 open tickets and the oldest has waited six days” is something they can act on. “We noticed you’ve been less active” is something they can only feel bad about.
• Offer the one thing that restores the value. A rule, a shortcut, a reconnect. Not a feature tour, and not a newsletter.
• When the signal is friction, lead with the fix. One sentence on the step, one link to the screen.
• When the champion has gone, write to the people still there. They are the ones who will decide whether to keep paying, and they may not know how the account was set up.
• When seats sit unused, offer to remove them. It costs you some revenue now, but a customer who feels overcharged tends to leave at renewal, while one you helped save money has one less reason to.
• When they visit cancel pages, do not block them. Send a short, human note asking what is not working, and offer to fix it or to help them export cleanly. Either answer is useful.
• Keep retention offers for the cancel step, if you use them at all. A discount in the first usage email teaches customers that using less earns a lower price.

Churn prevention email examples

These use Kestrel, a made-up shared support inbox for small teams. Each one is tied to a specific change in the account.

Mistakes to avoid

• Waiting for the cancel button. An exit survey tells you why they left. It does not give you a chance to change it.
• Benchmarking against everyone. A global “healthy usage” number flags light-by-design accounts as at risk and misses heavy accounts that are quietly halving.
• “We noticed you haven’t logged in.” It is guilt dressed as concern, and it gives the reader nothing to do.
• Turning up the newsletter. Sending at-risk customers more of what they are already ignoring will not reverse the trend.
• Leading with a discount. It cheapens the product before you know what is actually wrong.
• Making cancellation hard. It turns a lost customer into an angry one who tells other people.
• Writing to the wrong person. The champion who stopped logging in is not reading. The teammates still using the product are.
• Automated replies to a human answer. When an at-risk customer replies, a person should answer, quickly.
• No stop when usage recovers. A customer back to normal should not get the third email in a sequence about how quiet they have been.

How to run churn prevention emails in Behavly

Behavly keeps one activity record per signed-in person, merged across their devices, and writes each email from what that person did, so the “what changed” part of the email comes from their own history.

1. 1Install the tracking snippet from User Activity → Setup on your signed-in pages. It records page views, clicks and scroll depth per person, with no identify call. For the core action itself, such as ticket_replied, send an event from your product with behavly.track so a path can check whether people are still doing it.
2. 2Find who is at risk. Behavly suggests patterns it found in your tracking, such as people who went quiet or got stuck, or you can describe one in plain language: “people with at least ten sessions who haven’t been seen for 14 days”. You see the group and its size before it is saved. Heatmaps shows rage clicks and dead clicks along with the people behind them.
3. 3Before writing to an important account, open the person in User Activity → Identified Users. Their row shows pages, sessions and last seen, and its heatmap button shows what that one person did across every browser they used.
4. 4Create a Behavly-Agent campaign in Campaigns → New Campaign with the at-risk pattern as who enters, and turn on Enroll people who already match so customers who are slipping today are included. Choose the Personal sender so emails read as coming from a real person on your team.
5. 5Add a Plain text by Behavly Agent step with Instructions for Behavly Agent such as: name the workflow that slowed down, offer one fix, no discount. Then Wait until they do something for your core action, But no longer than 7 days.
6. 6Before each later email, add a Branch on did an action in your product or logged in to your site, with Stop the path on the yes side. Someone who stops matching the group is not taken off a path on its own, so this branch is what keeps a recovered customer from getting the next email. A Branch on visited a page (Starts with /settings/billing, for example) can route people who look at billing to a shorter, more personal email.
7. 7Use Preview to read what Behavly writes for a real customer, and turn on Hold Behavly-written emails for approval so you approve the emails before they go out.

Emails go out from your own mailbox, connected in Settings → Email, and a reply ends the path by default. Replies arrive in the Inbox with the customer’s site history attached and are filed by status, such as High-intent or Follow up, so the ones that need a person get one. On an Agent, Behavly can also draft a suggested answer for you to check and send.

Agents are on Starter and above. On the free plan, a one-time campaign to the at-risk pattern reaches the customers who match it today, with each email written from that customer’s activity.