CRM

Cadence Gap to Re-Engagement Email Draft

When an account crosses its meeting-silence threshold, an AI drafts a personalized re-engagement email referencing the last meeting and recent context.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionRead recent calendar eventsOutlook
  • LogicFlag accounts past cadence gap
  • ActionPull owner, last touch, open oppSalesforce
  • ActionDraft personalized re-engagement emailOpenAI
  • OutputSave as Outlook draft for ownerOutlook

What it does

It closes the loop between detection and action. The moment an account exceeds its expected meeting gap, this workflow writes a ready-to-send re-engagement email — grounded in the last meeting's subject and recent account activity — and parks it as a draft in the owner's Outlook so the rep just reviews, tweaks, and hits send.

When to use it

Use it when the bottleneck isn't spotting cold accounts but writing the outreach. Great for reps who want a warm, specific first draft waiting for them instead of a blank compose window.

How it works

  1. 1The run triggers on a schedule (e.g., every morning).
  2. 2It reads recent Outlook calendar events and identifies accounts whose days-since-last-meeting now exceeds their normal cadence.
  3. 3For each flagged account it pulls the owner, last touch, and open opportunity from Salesforce.
  4. 4An OpenAI step drafts a concise, personalized re-engagement email referencing the last meeting and a reason to reconnect.
  5. 5It creates the message as a draft in the account owner's Outlook mailbox, ready for human review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Connect OpenAIModels, embeddings, files.
  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.