CRM

Dormant Account Win-Back Email Sequence Launcher

When an account crosses 120 days without a touch, drafts a personalized win-back email from its last-known context and sends it via Gmail.

CategoryCRM
EngineSim + Paperclip
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerAccount crosses 120 days dormantSalesforce
  • ActionPull account history and primary contactSalesforce
  • ActionDraft personalized win-back emailOpenAI
  • ActionSend win-back email via GmailGmailGmail
  • OutputLog activity and set follow-up in SalesforceSalesforce

What it does

This workflow turns the moment an account goes truly cold into an action: it generates a tailored win-back email grounded in the account's history and last interaction, sends it from the owner's Gmail, and records the touch back on the Salesforce account so the recency clock resets and the activity is auditable.

When to use it

Use it to automate the first re-engagement touch on accounts that have crossed a hard dormancy line, instead of letting them rot in the pipeline. Good for lean teams that can't hand-write every win-back note.

How it works

  1. 1An event fires when a Salesforce account's days-since-last-activity crosses 120.
  2. 2Pull the account's recent opportunity history, notes, and contact details from Salesforce.
  3. 3An AI step drafts a concise, personalized win-back email referencing the prior relationship and a relevant reason to reconnect.
  4. 4Send the email to the primary contact via the owner's Gmail.
  5. 5Log the send as a completed Salesforce activity and set a follow-up reminder.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SalesforceAccounts, opportunities, cases.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.