Re-engage closed-lost deals with sequences

Overview: Win back closed-lost deals with Attio sequences.

Table of Contents

Available on pro, enterprise and ultra plans.

Admins, or members with full access to the Deals object, can create the attributes this process uses.

All members can create sequences.

Sequences send from your synced Gmail or Microsoft 365 account, and sending limits apply.

Your closed-lost deals are some of the warmest leads you have. These prospects already know your product, and many said no for a reason that can change, such as a missing feature or bad timing. This guide shows you how to record why each deal was lost, find the deals worth a second conversation, and send those people a matched message with a sequence. You'll finish with a process you can run every month.

Decide which closed-lost deals deserve a second conversation

A closed-lost deal is worth contacting again when you can give the prospect a clear reason to hear from you. The strongest reasons are:

  • The lost reason has been addressed: For example, you've shipped the feature they needed, or you've introduced a plan that fits their budget.

  • The prospect asked you to come back: They gave you a date, or asked you to follow up next quarter.

  • You have something new that's relevant to them: For example, a guide, case study, or customer story about the problem they came to you with.

If you can't name a reason, leave the deal alone. A "checking in" email to your whole backlog uses up sending capacity and rarely gets replies.

Wait at least 90 days after a deal closes, unless the prospect gave you a date. That gives you a short, warm list which is the kind of targeted outreach Attio’s sequences are built for, rather than high-volume sends.

Before you start

Check that you have the following in place:

Record why each deal was lost and when to revisit it

To find the right deals to follow up with, Attio needs two pieces of information on every lost deal: why it was lost, and when it's worth revisiting. Deals don't include these by default, so you'll add two attributes.

This guide follows GreenLeaf, an analytics platform for SaaS teams. GreenLeaf has a backlog of closed-lost deals whose lost reasons sit in email threads and call recordings, and it has just shipped SSO, a feature several of those deals were waiting for. It starts by adding these attributes to its Deals object:

  • Lost reason: A select type attribute with the options Missing feature, Timing, Price, Competitor, No decision, and Went quiet.

  • Revisit on: A date type attribute.

You can have Ask Attio do this with the following prompt:

On the Deals object, create two new attributes:

"Lost reason", a select type attribute with the options 'Missing feature', 'Timing', 'Price', 'Competitor', 'No decision', and 'Went quiet'.

"Revisit on", a date type attribute.

Learn how to create attributes.

Choose how to capture the lost reason

A select type attribute is the right default for most teams. Reps pick a reason when they mark a deal as lost, and a short list keeps the data consistent enough to filter on. Start with GreenLeaf's six options, and adjust them to match how your team describes lost deals. Keep each option clearly different from the others.

Deals that go quiet can sit open for months without a lost reason. Agree on a rule for when a quiet deal counts as lost, such as no interaction for 30 days, and apply it with a weekly workflow that moves those deals to your lost status with the lost reason Went quiet. Reps who want to keep a deal open have to keep the conversation going. The revisit date workflow in the next section then sets the revisit date too.

To build the workflow with Ask Attio, paste the prompt below:

Build a workflow that closes deals that have gone quiet.

Schedule
- Run every Monday at 09:00 UTC.

Find records
- Use a single Find records step on Deals.
- Filter to deals where:
  - Deal stage is not won and not lost
  - The Associated company's Last interaction is more than 30 days ago
- Don't fetch deals and then check each one in the loop.
- Leave alone any deals with no associated company or no Last interaction.
- Set the Find records limit to the maximum allowed (500).

For each deal found
- Set Deal stage to lost.
- Set Lost reason to Went quiet.
- Make no other changes and send no notifications.

Checks
- If you're unsure which Deal stage options are the won and lost ones, check, don't guess.
- Check that a "Went quiet" option exists for Lost reason. If it doesn't, tell me instead of picking a different reason or creating one.

Check the blocks Ask Attio creates before you turn the workflow on. Tell your reps about the rule first, so a deal closing doesn't come as a surprise.

Set the revisit date when a deal is lost

Use a workflow to set Revisit on whenever a deal is lost. When a deal moves to your lost status and doesn't have a revisit date yet, the workflow sets Revisit on to 90 days from that day.

To build the workflow, paste the prompt below into Ask Attio.

Build a workflow that sets a revisit date when a deal is lost.

- Run it whenever a deal's Deal stage changes.
- Continue only if Deal stage is now lost and Revisit on is empty.
- Set Revisit on to 90 days after today.

If you're unsure which status is the lost status, check, don't guess.

If the prospect asked you to follow up at a specific time, the rep changes Revisit on to that date. The workflow only fills in empty dates, so it never overwrites a date a rep has set.

Fill in your existing lost deals

Your existing lost deals won't have a lost reason or a revisit date yet. Fill in both before your first send.

For Lost reason, choose how you’d like to fill in these values. You can:

  • Have reps fill in their own deals: Reps know the context behind each deal, so this is the most accurate option, but it takes the longest.

  • Build a workflow with a Custom agent block: This is the fastest option for a large backlog. Uses Attio credits.

  • Use an AI assistant: Connect an AI assistant such as Claude or ChatGPT to the Attio MCP server. It can read each deal's emails, call recordings, and notes, then update the deal after you confirm. It runs on your AI assistant's plan rather than Attio credits.

Have reps fill in their own deals

Create a Deals view filtered to your lost status where Lost reason is empty and Deal owner is Current user. Each rep who opens the view sees only their own lost deals without a lost reason, and fills in the lost reason and revisit date for each one.

If you have the Attio MCP connected to an AI assistant like Claude or ChatGPT, paste the prompt below into it to create the view.

Using the Attio MCP, create a saved table view on the Deals object called "My closed lost deals – no lost reason".

Filter (all conditions must match):
1. Deal stage is "Closed Lost"
2. Lost reason is empty
3. Deal owner is the current user, so each person who opens the view sees their own deals

Show these columns, in order: Deal value, Associated company, Lost reason and Revisit on. Don't add Deal name, Deal stage or Deal owner as columns. The record name is always shown, and the filters already fix the stage and owner.

Before creating the view, list the Deals object's attributes to check that each object, attribute and status above exists. If any of them is missing, has a different name (for example, the stage is called "Lost" rather than "Closed Lost", or the owner field is "Account owner"), or more than one candidate could match, stop and ask me which one to use. Don't guess. Once they're confirmed, create the view and tell me its name and the filters it applied.

Build the Custom agent workflow

You run the workflow manually. It finds lost deals without a lost reason, has a Custom agent read the conversations on each deal, and writes back the lost reason and any revisit date the agent finds. It starts with a test batch of 10 deals. After that, we recommend batches of about 50 (the maximum is 500), so you can keep an eye on quality and cost.

To build the workflow, paste the prompt below into Ask Attio.

Build a workflow called "Fill in the lost reason on lost deals".

TRIGGER: Manual run.

CHECK NAMES FIRST
Deals object, Deal stage, "Closed Lost", Lost reason and Revisit on are examples. Confirm each exists in this workspace before building. If a name doesn't match exactly, or several things could fit, stop and ask me. Don't guess.

STEPS
1. Find records (Deals)
   - Deal stage = "Closed Lost" AND Lost reason is empty
   - Limit 10

2. Loop over the deals found. For each deal:
   a. Custom agent
      - Prompt: see AGENT PROMPT, with the loop's current deal inserted at [deal]
      - Run as the workflow
      - Read-only tools: Emails, Call recordings, Notes, Meetings, Records
      - Structured output:
          lost_reason  (text, required)
          revisit_date (text, optional)
   b. Update record (the loop's current deal): set Lost reason = lost_reason
   c. Filter: continue only if revisit_date is not empty
   d. Update record (the loop's current deal): set Revisit on = revisit_date

AGENT PROMPT
(If Lost reason is named differently here, use that name.)

  You're working out why a closed-lost deal was lost.

  Deal to review: [deal]

  1. Look up the options for the Lost reason attribute on the Deals object. Only these values may be returned.
  2. Read the emails, call recordings, notes and meetings for this deal and for other people at its company. Choose the one option that fits best.

  Rules:
  - Base your answer only on what was said or written. Don't guess.
  - If the prospect stopped replying without giving a reason, choose the option meaning they went quiet.
  - If no clear reason comes up, choose the option meaning no decision was made.
  - If the prospect asked to be contacted at a specific time, return that date as revisit_date (YYYY-MM-DD, e.g. 2027-03-15), calculated from the date of the message or call. Otherwise leave it empty.
  - Return lost_reason exactly as the option is written, with no extra words.

BUILD RULES
- If Lost reason has no matching "went quiet" or "no decision" option, or the options are ambiguous, ask me which to use.
- Build one block at a time from the trigger. Connect it and clear its errors before adding the next.
- Send each block's config as one complete update. If a call fails, change something before retrying. Never resend the same call unchanged. If a block fails twice, stop and tell me the exact error.
- Find records filter fields: use the stage ID field for Deal stage and the option ID field for Lost reason. Don't guess other field names. If one is rejected, tell me.
- Update record: key each attribute by its attribute ID, not its name. Tag Lost reason (select) and Revisit on (date) values with the attribute's type. If rejected, copy exactly the type the error shows, including slugs.
- At the end, check the whole workflow for errors and tell me which warnings remain and why.

The agent runs as the workflow, so it reads every conversation that's visible across your workspace. To also include conversations that only you can see, open the Custom agent block and set Run as to yourself.

Run the workflow on your test batch and check the results. Reps can change any lost reason they disagree with. When you're happy, raise the Find records limit and run it again.

Deals that already have a lost reason no longer match, so each run picks up where the last one stopped. The run viewer shows how many credits each step used. Learn more in the workflows block library.

For Revisit on, any deal that's still empty needs a date: the date the prospect gave you, or 90 days after the deal was lost. The revisit date workflow only runs when a deal's stage changes, so it won't fill in deals that were lost before you built it.

You should now see a lost reason and a revisit date on every lost deal you plan to include.

Use an AI assistant

Paste the prompt below into your AI assistant like Claude or ChatGPT. It finds the deals itself, works through them in batches of 10, and only updates a deal after you approve it.

Fill in the lost reason on my lost deals in Attio.

1. Find deals on the Deals object whose Deal stage is lost and whose Lost reason is empty. Work through them 10 at a time.
2. Look up the options for the Lost reason attribute. Only these values may be used.
3. For each deal, read the emails, call recordings, notes and meetings for the deal and for other people at its company. Choose the one option that fits best.

Rules:
- Base each answer only on what was said or written. Don't guess.
- If the prospect stopped replying without giving a reason, choose the option meaning they went quiet.
- If no clear reason comes up, choose the option meaning no decision was made.
- If the prospect asked to be contacted at a specific time, use that as the revisit date, calculated from the date of the message or call. Otherwise leave it empty.
- If Deal stage, Lost reason, Revisit on or the lost status have different names in my workspace, or several could fit, ask me. Don't guess.

For each batch, show me a table with the deal, the lost reason, the revisit date and a one-line explanation. Wait for me to confirm, then update Lost reason and Revisit on for the deals I approve, and move on to the next batch.

Choose the lost reasons you have something new to say to

For each Lost reason, decide whether something has changed. If you can't name what's new for a group, skip it this month, and keep the lost reason recorded so you can find those deals again if that changes.

Here's how GreenLeaf could make these decisions in a month when it has shipped SSO:

Lost reason

What would count as a change

Contact this month?

Missing feature

The feature they needed has shipped

Yes, for deals lost over SSO

Timing

Their revisit date has arrived

Yes

Price

A plan or offer that fits their budget

No, nothing has changed

Competitor

A clear new advantage, or their contract is up for renewal

No

No decision

A change in their situation that you know about

No

Went quiet

Something new to share about the problem they came to you with

Yes, with a new guide to rolling out analytics across a team

That leaves GreenLeaf with three groups to contact this month: Missing feature, Timing, and Went quiet.

Build a view of the people to contact

Next, build a view of the people on those deals, so you can enroll them in a sequence.

Create a base view with your exclusions

Some people shouldn't hear from you whatever their lost reason. Set up these exclusions once in a base view, then copy that view for each group.

Create a view of People that filters out:

  • Existing customers, however your workspace marks them

  • Anyone linked to a deal that's still open

  • Anyone your team has been in touch with in the last 30 days

  • Anyone without an email address

To exclude open deals, add an is not condition on the associated deal's Deal stage for each of your open statuses. To exclude recent contact, filter on Last interaction, then set When to before 30 days ago using Number of days ago….

Save the view as "Re-engage: Base." It shows everyone you could contact again, before you narrow it down to one lost reason.

If you have the Attio MCP connected to an AI assistant like Claude or ChatGPT, paste the prompt below into it to create the view.

Using the Attio MCP, create a saved table view on the People object called "Re-engage: Base".

The view shows everyone we could contact again about a lost deal. Filter out (all conditions must match):
1. Existing customers. Before adding this filter, ask me how my workspace marks a customer, for example a company attribute or a won deal. If it's a won deal, add the won status to the Deal stage group in step 2 instead of creating a separate filter.
2. Anyone linked to a deal that's still open. Put all the Deal stage conditions in one filter group, joined by And: an "is not" condition on the associated deal's Deal stage for each open status. Don't add them as separate top-level filters. Treat every status except the won and lost ones as open, and confirm the list with me.
3. Anyone we've been in touch with in the last 30 days. Last interaction is before 30 days ago, set as a relative date so the view stays current.
4. Anyone without an email address. Email addresses is not empty.

Show these columns, in order: Email addresses, Company, Last interaction.

Before creating the view, list the People and Deals attributes to check that each attribute and status above exists. If any of them is missing, has a different name, or more than one candidate could match, stop and ask me which one to use. Don't guess. If you can't set a filter exactly as described, such as the relative date, the filter on associated deals or the Deal stage group, tell me which one instead of using a workaround like a fixed date. Once everything is confirmed, create the view and tell me its name and the filters it applied.

An unsubscribe only blocks someone from sequences with the same sender. Before you enroll a group, check the Unsubscribe list for anyone you're unsure about. To stop someone hearing from anyone on your team, add their email address to the list. To find it, navigate to Workspace settings, then Sequences in the sidebar, and open the Unsubscribe list tab.

Learn how to filter and sort views.

Create a view for each group

For each group you're contacting, copy the base view. In the list of views, click the ⋮ icon next to "Re-engage: Base," then select Duplicate. Add these filters to the copy:

  • The associated deal's Deal stage is your lost status.

  • The associated deal's Lost reason is the group you're contacting, such as Missing feature.

  • The associated deal's Revisit on is before Tomorrow. This includes every deal whose revisit date is today or has already passed.

Save the view with a name that matches its sequence, such as "Re-engage: Missing feature."

You should now see a count of people for each group. Review each list before you send. If someone has more than one lost deal, check that the deal with this group's lost reason is due, because each filter can match a different deal. GreenLeaf opens its Missing feature view, removes the people whose deals weren't lost over SSO, and is left with 23 people across 14 companies.

Write one sequence for each lost reason

Each lost reason needs a different argument for getting back in touch, so create a sequence for each group you're contacting and write its first email for that lost reason. Lead with what's changed, then make a soft ask: a question that's easy to answer, such as "Is this still something you're trying to solve?" Leave the demo request out of the first email. To someone who has already said no, it reads as a sales pitch rather than a reason to talk.

Here's how GreenLeaf builds the first email in its Missing feature sequence:

  • Opens with the change: SSO has shipped.

  • Connects it to the reason they gave: they needed SSO to roll GreenLeaf out across their company.

  • Explains what it means for them: their IT team can manage access for everyone from one place, which was the blocker last time.

  • Ends with a question that's easy to say yes to: "Is rolling out an analytics platform across the team still something you're trying to do?"

Keep each email short, and write subject lines that read like they came from a person rather than a marketing team, for example short, specific, and lowercase. Write the follow-up emails for each sequence too. They can follow the same structure across sequences, but each one should refer back to the lost reason and to the earlier emails.

Use variables to personalize each email with details from the person's record, such as their first name, and set a fallback value for any attribute that might be empty.

Decide who each sequence sends from. By default, send from the rep who worked the original deal, so the email comes from a name the prospect recognizes. That rep needs delegated sending enabled on the sequence, and the emails count toward their sending limits. If your reps haven't set that up, sending from your own address is a reasonable fallback.

Before you publish, set up these options:

  • Add Meeting booked as an exit criterion, so anyone who books time with the sender stops receiving emails. Reply received is always on.

  • Set a sending window if you want to send within specific hours.

Click Publish sequence. You can only enroll people in a published sequence.

Before you enroll any prospects, test the sequence on a colleague. Open their person record, click Enroll in sequence in the upper-right, and check each email as it arrives.

Learn more in Create a sequence.

Enroll each group in its sequence

With your views and sequences ready, enroll each group:

  • Open the People view for the group.

  • Select the people you want to enroll.

  • At the bottom of the page, click Enroll in sequence.

  • Select the matching sequence and the sender.

You can enroll up to 1,000 people at one time.

You should now see the group on the sequence's Recipients tab. Attio spaces out sends to stay within each mailbox's sending limits, so queued emails wait in your Outbox until they go out. Each synced mailbox can send up to 12 emails an hour and 200 a day, over a rolling 24 hours, including one-off emails. At that rate, GreenLeaf's 23 people take about two hours to receive their first email. Learn more about sending limits and the Outbox.

Track what each sequence produces

A re-engagement sequence has done its job when it turns into pipeline. Track results in two places.

In the sequence: A sequence's Insights show how many recipients are active, enrolled, and exited. Each recipient who exits is listed with the reason, such as Reply received or Meeting booked. Compare the exits across your sequences. A lost reason that gets few replies usually needs a stronger reason to get in touch. Learn more in Track status of sequence recipients.

In your pipeline: Insights don't show what happens after someone replies, so track the outcome on your deals. When a prospect re-engages, move the original deal back into your pipeline rather than creating a new one. Then create a Deals view where Deal stage was your lost status after the date you started this process, and Deal stage is not your lost status. This shows every deal you've reopened. Add Lost reason and Deal stage as columns to see which groups turn into open and won deals.

If you have the Attio MCP connected to an AI assistant like Claude or ChatGPT, paste the prompt below into it to create the view:

Using the Attio MCP, create a saved table view on the Deals object called "Re-engage: Reopened deals".

The view shows every deal that was set to "Closed Lost" at any point in the past and whose current stage is something other than "Closed Lost". Filter (all conditions must match):
1. Deal stage entered "Closed Lost" after 2000-01-01T00:00:00Z. This date only exists because the filter needs one; it stands for "at any point in the past". Don't change it.
2. Deal stage is not "Closed Lost".

Show these columns, in order: Lost reason, Deal stage, Deal value, Associated company.

Before creating the view, list the Deals object's attributes to check that each attribute and status above exists. If any of them is missing, has a different name (for example, the lost status is called "Lost" rather than "Closed Lost"), or more than one candidate could match, stop and ask me which one to use. Don't guess. If you can't filter on a status the deal had in the past, tell me instead of using a workaround. Once everything is confirmed, create the view and tell me its name and the filters it applied.

Give each group time before you judge it. Re-engaged deals still move through your normal sales process, so wait at least one full sales cycle, from first meeting to close, before you decide whether a sequence is working.

Run the process every month

Once the attributes, views, and sequences are in place, re-engagement becomes a monthly routine:

  • Check that every newly lost deal has a lost reason. The workflow sets its revisit date.

  • Once a month, decide which lost reasons you have something new to say to.

  • Open the matching views, review the people, and enroll them in their sequences.

Because the views filter on Revisit on, deals move into them as their revisit dates arrive.

Recipients who reply on the same thread exit the sequence automatically, and out-of-office replies pause them until the day after they're back. When someone replies with interest, move the original deal back into your pipeline.

You can automate enrollment with workflows. For example, a Recurring schedule trigger can find each month's people and enroll them with the Enroll in sequence block. The sender you pick in the block must have delegated sending enabled on that sequence, or the run fails.

Frequently asked questions

Attio won't enroll people who have unsubscribed from sequences sent by the same sender, and hard bounces are added to the unsubscribe list automatically. People also need an email address. Check the person's record for a missing email address. If they've unsubscribed, leave them out of your outreach.

Attio queues emails to stay within each mailbox's sending limits, and sends them during the sequence's sending window. To move faster, split a large group across several senders who have delegated sending enabled.