ValueRamp
Book a demo

Win back a former customer

CSM · Admin · OM4 min read

Last verified 2026-09-17

Identify churned customer comeback opportunities, analyze historical exit feedback, review tailored re-engagement drafts, and dispatch outreach.

Before you start

  • ValueRamp CSM, Admin, or OM role
  • Open reactivation opportunities in the pipeline

Overview

A former customer already knows your product and has been through your security and procurement once, so a win-back conversation starts further along than a new sale.

ValueRamp operationalizes win-back efforts through the Reactivation Pipeline (/reactivation/pipeline) and dedicated Opportunity Workspaces (/reactivation/opportunities/[id]), ensuring outreach is timed to genuine catalysts rather than arbitrary calendar schedules.

The Win-Back Procedure

A successful customer win-back follows five structured phases:

  1. Trigger Identification: Filter the pipeline by reactivation path (Customer Comeback, Stakeholder Follows Person, Parent Company cycle, or Competitor Failure) and trigger event (such as buying-cycle anniversaries or competitor contract renewals).
  2. Prioritization by Weighted ARR: Focus effort on accounts where pre-churn ARR and win-back probability combine to yield the highest expected return.
  3. Contextual Brief Review: Read the AI Reactivation Brief to understand the captured exit reason (pricing, product fit, a champion's departure…) and the person's current state. Its What has changed on our side section reads Nothing recorded unless a change was captured — add anything relevant to the draft yourself.
  4. Draft Verification: Review the pre-drafted outreach touchpoint. Confirm that anti-pattern checks have passed, verifying that the copy acknowledges past feedback without high-pressure sales rhetoric.
  5. Approve and send by hand: Click Approve outreach (or acknowledge the flags and Approve anyway) — this also creates the reactivation plan. Copy the draft into your email client, send it, and click Mark as sent → to log the touch and advance the counter.
Reactivation pipeline filter strip with path and trigger dropdown controls

1 / 5Filter the Reactivation Pipeline by path to isolate direct Customer Comeback opportunities

Steps

  1. Filter the Reactivation Pipeline by path to isolate direct Customer Comeback opportunities

    Reactivation pipeline filter strip with path and trigger dropdown controls

  2. Select the highest-ranked opportunity card to open its win-back workspace

    Top-ranked reactivation card displaying weighted revenue and pre-churn ARR

  3. Review the AI Reactivation Brief and the captured exit reasons

    Opportunity workspace brief analyzing exit feedback and product updates

  4. Verify the drafted multi-touch message and ensure anti-pattern heuristics pass

    Outreach card showing pre-drafted email, subject line, and anti-pattern status

  5. Approve the draft, send it from your inbox, and click Mark as sent

    Outreach card showing approved send status and the Mark as sent action button

Common questions

When is the best time to attempt a customer win-back?

When a watch-list trigger fires — today, a time-based trigger such as a buying-cycle anniversary or a competitor contract renewal, or a champion's confirmed job change. Product-release triggers exist on the watch list but have no signal source yet.

Why must I send emails from my own email client?

ValueRamp never sends reactivation outreach itself: every touch needs a human approval and a human send, so the message goes from a real mailbox under your name.

What happens if a former customer responds positively?

Approving the first touch already creates a reactivation plan on the account. When the customer actually returns, use Reactivate on Former customers: it sets the lifecycle phase, archives the plans that are not resumed, and records a churn-recovery revenue movement.

How does the pipeline prevent spamming churned contacts?

Each reactivation plan allows a fixed number of touches (3 by default) regardless of response; once used, the opportunity stays blocked — the cap does not reset. Between touches, the minimum gap (7 days by default) and a cooldown after a decline (12 months by default) apply.

Was this helpful? Tell us what was missing