SALES

Route replies to a lost-deal re-engagement campaign

When a contact from a closed-lost account replies to a re-engagement email, it classifies intent, re-opens warm deals in HubSpot.

CategorySales
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerInbound reply to campaign in GmailGmailGmail
  • ActionClassify reply intent with OpenAIOpenAI
  • LogicBranch on interested / not now / unsubscribe
  • ActionReopen deal and set follow-up in HubSpotHubSpotHubSpot
  • OutputRoute hot reply to rep in SlackSlack

What it does

Sending the re-engagement email is easy; handling the replies fast is where deals are won or lost. This workflow reads each inbound reply, decides whether interest is real, and acts on it within minutes instead of letting it sit in an inbox.

When to use it

Use it after launching a win-back email sequence to a list of closed-lost contacts. Best when replies land in a shared Gmail inbox and you want consistent triage without a human reading every message first.

How it works

  1. 1An inbound Gmail reply to the re-engagement campaign triggers the workflow.
  2. 2An OpenAI classification step labels the reply as interested, not now, or unsubscribe.
  3. 3A logic branch routes on that label.
  4. 4For interested replies, it re-opens the matching deal in HubSpot, sets a follow-up task, and posts the thread to the rep's Slack channel for an immediate response.
  5. 5For not-now replies, it logs a nurture date on the HubSpot contact and stops.
  6. 6For unsubscribes, it flags the contact suppressed in HubSpot so no further outreach goes out.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect HubSpotCRM, deals, marketing, support.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.