Customer Winback Email Examples

Sent after a user has not completed a meaningful product action for a defined inactivity window.

Hi {{first_name}},

{{product_name}} has not seen activity from {{account_name}} recently.

If {{outcome}} is still useful, the fastest next step is here: {{return_url}}

If the product no longer fits, no action is needed.

{{sender_name}}

The email names the missing behavior and gives one return path. It also leaves room for the customer to ignore it without pressure.

Tie the send to a real inactivity rule and one product action.

Do not use guilt, fake urgency, or a long feature recap.

Sent to cancelled accounts when a specific product change addresses a known churn reason.

Hi {{first_name}},

{{account_name}} previously cancelled {{product_name}} after running into {{churn_reason}}.

{{feature_name}} now addresses that workflow: {{feature_url}}

If it is worth another look, the account can be restarted here: {{restart_url}}

{{sender_name}}

The reason for the email is explicit. The message connects a product change to the reason the customer left.

Use this only when the churn reason is known and the product change is relevant.

Do not send generic release notes to every cancelled account.

Sent to churned customers tagged with a price or budget reason.

Hi {{first_name}},

{{product_name}} now has {{plan_name}}, a smaller plan for teams that only need {{plan_scope}}.

Plan details: {{plan_url}}

If budget was the blocker, this may be a better fit than the old plan.

{{sender_name}}

The copy does not pretend price was not the problem. It presents a specific plan change and lets the customer decide.

Send only to customers with a price-related churn reason.

Do not discount by default when a smaller package would be clearer.

Sent to an account admin when several users have gone dormant but the account is still active.

Hi {{first_name}},

Activity in {{account_name}} has dropped over the last {{window}}.

The fastest way to restart momentum is {{recommended_action}}: {{action_url}}

If the team moved to another workflow, this can be ignored.

{{sender_name}}

The email is account-aware and gives the admin one restart action instead of a generic engagement prompt.

Use account-level activity, not only one user login signal.

Do not send to every teammate when one admin can fix the account state.