SALES

Champion Reply-Gap Revival Draft

Detects when a buyer champion has gone unanswered or unresponsive on the MAP for several days and drafts a tailored re-engagement email for the rep to review and send from Gmail.

CategorySales
Enginepaperclip
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionRead recent champion threads from GmailGmailGmail
  • LogicFlag reply-gap threads with open steps
  • ActionPull open step context from SalesforceSalesforce
  • ActionSave revival email as Gmail draftGmailGmail
  • OutputNotify rep in Slack that draft is readySlack

What it does

Watches the email thread cadence with the buyer champion and, when the conversation stalls past a set gap, drafts a context-aware revival email referencing the specific MAP step that is waiting on them.

When to use it

Use it when champion responsiveness is your slippage signal and reps lose deals simply by not following up in time. Ideal for sellers who run deal comms in Gmail and want a ready-to-edit draft rather than starting from blank.

How it works

  1. 1A daily schedule checks recent champion email activity.
  2. 2Read the latest deal-thread messages and timestamps from Gmail to find the last champion reply.
  3. 3Logic flags threads where the champion has been silent beyond the gap threshold and an open MAP step depends on them.
  4. 4Pull the relevant open step and deal context from Salesforce.
  5. 5Draft a tailored re-engagement email naming the waiting step and proposed next date, saved as a Gmail draft.
  6. 6Notify the rep in Slack that a revival draft is ready to review and send.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.