> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Re-engage

> Salesbricks-backed closed-lost revival queue with re-engagement scoring and account context

The Re-engage page (`/success/re-engage`) is the winback workspace. It surfaces closed-lost opportunities from connected Salesbricks data, scores each one for re-engagement likelihood, and gives the team a prioritized outreach queue.

## Live Data Requirement

Re-engage currently requires **Salesbricks**. If Salesbricks is not connected, the page shows **Re-engage is not connected yet** with an **Open Integrations** action.

Unlike Health, Convert, Contracts, Pipeline, and Releases, the current Re-engage component does not expose a demo-mode preview button.

## Summary Cards

* **Total lost deals** - count of closed-lost opportunities.
* **Need re-engage** - high-priority candidates.
* **Should re-engage** - medium-priority candidates.
* **Lost value** - total value of the closed-lost pool.

## Live Re-engage Queue

The table shows closed-lost opportunities:

| Column              | Meaning                                               |
| ------------------- | ----------------------------------------------------- |
| **Company**         | Company name and the top score factor when available. |
| **Category**        | Loss or re-engagement category.                       |
| **Score**           | Re-engagement score.                                  |
| **Days since loss** | Time since the opportunity was lost.                  |
| **Value**           | Original deal value.                                  |
| **Contact**         | Contact email or company domain when available.       |

Accounts routed in from Health appear with the routed-account banner above the queue.

## Detail Sheet

Click a row to open the detail sheet. It shows:

* Category
* Score
* Days since loss
* Deal value
* Lost reason
* Score factors and their impact
* Account context panel when a company domain is available

## Score Factors

Score factors explain why an account may be worth revisiting. Common examples include:

* Lost on price but the context has changed.
* Lost on a feature gap that has since been shipped.
* Closed-lost timing is now far enough in the past to justify a new touch.
* Account signals or activity suggest renewed interest.
* Deal value is high enough to justify outreach.

## Workflow

<Steps>
  <Step title="Review the high-priority queue">
    Start with **Need re-engage** and highest deal value.
  </Step>

  <Step title="Open the detail sheet">
    Check the lost reason and score factors before contacting the account.
  </Step>

  <Step title="Open account context">
    Use the account context panel and customer detail page to review recent calls, signals, and contract history.
  </Step>

  <Step title="Coordinate the outreach">
    Route promising accounts into Pipeline when they become live opportunities.
  </Step>
</Steps>

## How It Connects to Releases

Re-engage should reuse the shipped-feature coverage from Releases / Close the Loop. If a deal was lost because a requested feature was missing, and that feature is now shipped, the account becomes a stronger re-engagement candidate.

<Tip>
  For the strongest winback message, filter mentally for **feature gap** reasons and cross-check Releases / Close the Loop. "We shipped what blocked you" is usually more actionable than a generic check-in.
</Tip>