CRM
Outlook key-account silence-gap detector and re-engagement alert
Scans monitored Outlook threads on a schedule for accounts that have gone quiet past their normal cadence.
How it runs
The automated pipeline, trigger to output.
- TriggerRecurring schedule scans monitored mailboxes
- ActionRead active key-account threads from OutlookOutlook
- LogicCompute silence gap vs thread cadence baseline
- ActionConfirm pre-silence tone was positive via Hugging FaceHugging Face
- OutputSend re-engagement alert to Teams ownerMicrosoft Teams
What it does
Not every cooling signal is an angry email; often the relationship goes silent. This workflow detects the absence of reply, the silence gap, on key accounts. It learns each thread's typical response cadence, then flags conversations where the contact has stopped replying for noticeably longer than usual, especially ones that were previously positive. The owner gets a Teams alert with the last exchange so they can re-engage before the deal goes cold.
When to use it
Reach for this when ghosting is your churn signal rather than complaints, common in mid-funnel deals and quiet renewals. It catches the accounts that disappear instead of objecting.
How it works
A recurring schedule scans the monitored Outlook mailboxes for active threads on key accounts. For each thread it computes the time since the contact's last reply and compares it to that thread's established cadence baseline. A logic step flags threads that have exceeded their normal gap and were warm before stalling. The flow uses Hugging Face to confirm the pre-silence tone was positive, avoiding alerts on already-dead threads. Qualifying threads produce a Teams re-engagement alert to the owner with the contact, the gap length, and the last message snippet.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
Dormant Account Check-In Call Scheduler
On the anniversary of an account's last touch, books a tentative check-in call on the owner's Google Calendar and emails the contact a scheduling invite.
Weekly Dormant-Anniversary Cohort Digest
Every week, groups dormant Attio accounts by which last-touch anniversary they hit that week, builds a prioritized digest.
AI-Personalized Dormant Account Win-Back
On a dormancy anniversary, an agent researches the account's history and recent public signals, drafts a genuinely personalized win-back email.
Backfill Intercom conversation topics onto stale HubSpot contacts
Finds HubSpot contacts with no recent Intercom topic, pulls their conversation history from Intercom, classifies the dominant topic with OpenAI.
Daily orphaned-opportunity sweep with manager Slack digest
Each morning this scans Salesforce for open opportunities owned by inactive users and posts a per-manager digest in Slack listing the orphaned deals that need a new owner.
Tag closed Intercom conversations onto Salesforce contacts in real time
On each Intercom conversation close, classifies the topic with OpenAI and appends it to the matching Salesforce contact's activity timeline so the topic never goes stale…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
