SALES
Departure-News Agent: Research and Rebuild Org Plan
When a champion is detected as departed, an agent researches the move, maps the new buying committee at the account.
How it runs
The automated pipeline, trigger to output.
- TriggerDeparture event receivedHTTP webhook
- ActionResearch new role + account leadershipExa
- ActionPull account pipeline + contactsSalesforce
- LogicAgent assesses exposure, builds rebuild plan
- ActionWrite plan + tasks to SalesforceSalesforce
- OutputPost rebuild brief to SlackSlack
What it does
Given a departed champion, an agent investigates where they went, who now holds their responsibilities at the account, and what the renewal exposure is. It then builds a structured rebuild plan: who to re-engage, what messaging to use, and which internal owner runs each thread. The plan is written into Salesforce and the team workspace.
When to use it
Use it for high-value accounts where losing a champion is a material renewal risk and a templated email is not enough. This produces the analysis and the org-level plan a senior rep would build manually, in minutes.
How it works
- 1A departure event from an upstream detector triggers the run.
- 2The agent uses Exa to research the contact's new role and the account's current leadership.
- 3It pulls the account's open pipeline, renewal date, and contact roster from Salesforce.
- 4The agent reasons over exposure and drafts a multi-thread rebuild plan with owners and messaging.
- 5It writes the plan and tasks back into Salesforce on the account.
- 6It posts a structured rebuild brief to the deal's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ExaNeural search across the web.
- 3Connect SalesforceAccounts, opportunities, cases.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
API-Usage Surge PQL Router
When an account's API call volume surges past a rolling baseline in the product DB, it qualifies the account as a product-qualified expansion lead.
Seat-Limit Approaching Upsell Alert
Fires the moment an account's active-seat count crosses 90% of its contracted limit in the product database.
Enrich new MAP steps with Salesforce deal context on creation
When a new card is added to the mutual action plan Trello board, it looks up the linked Salesforce opportunity and writes deal owner, amount, and close date onto the card…
Power-Feature Adoption Expansion Digest
Each Monday, finds accounts that started heavily using a premium or add-on feature in BigQuery, ranks them by expansion potential.
Send buyers a weekly mutual action plan health recap
Each week it reads the MAP Trello board, computes completed, on-track, and overdue steps, and emails the buyer champion a clean recap of progress and what is due next.
Escalate to the deal team when the buyer side of a MAP stalls
Detects when buyer-owned mutual action plan steps have been idle past their due date and escalates with a Slack alert to the AE plus an email summary to the account executive's…
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.