CRM
Agentic fair rebalance of a departed rep's book
Uses an agent to redistribute a departing rep's open opportunities across the active team on the same territory.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: rep marked as leavingHTTP webhook
- ActionFetch rep's open opps and team pipeline loadSalesforce
- LogicAgent proposes load-balanced assignment
- LogicValidate capacity ceiling per rep
- ActionUpdate OwnerId on each opportunitySalesforce
- OutputPost rebalance plan to leadership SlackSlack
What it does
When a rep leaves, this hands the agent the full book of open opportunities and the active team's current pipeline load, and lets it assign each deal to keep workloads balanced — accounting for deal size, stage, and existing rep capacity instead of dumping everything on one teammate.
When to use it
Reach for this when a departing rep carries a large or uneven book and a simple round-robin would overload someone. The agent reasons about fairness across the team, which a deterministic rule struggles to do well.
How it works
- 1A webhook trigger fires from your HR or admin system when a rep is marked as leaving.
- 2An action pulls the rep's open opportunities and the territory team's current open-pipeline totals from Salesforce.
- 3The agent proposes a balanced assignment, weighting deal amount and stage against each active rep's existing load.
- 4A logic step validates that no rep exceeds a configured capacity ceiling, looping back if needed.
- 5An action writes the new OwnerId to each opportunity in Salesforce.
- 6An output posts the rebalance plan and rationale to the sales-leadership Slack channel for review.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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
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.
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.
Dormant Account Anniversary Re-engagement Email
Each day, finds Attio accounts whose last activity was exactly N months ago and sends each owner's contact a personalized re-engagement email from Gmail.
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.
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.