CRM

Reassign a Departing Rep's Accounts by Round-Robin and Notify New Owners

When a Salesforce user is deactivated, redistributes their open accounts evenly across the remaining team and DMs each new owner a Slack handoff card with the account's last…

CategoryCRM
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSalesforce User deactivated (IsActive → false)Salesforce
  • ActionQuery departing rep's open accounts + activitySalesforce
  • LogicBuild round-robin map across active reps in territory
  • ActionBatch-update Account OwnerIdSalesforce
  • ActionDM each new owner a handoff cardSlack
  • OutputPost reassignment summary to sales-ops channelSlack

What it does

Watches for a Salesforce user record flipping to inactive, pulls every account that rep still owns, and reassigns them round-robin across the active reps in the same role/region. Each newly assigned owner gets a Slack direct message summarizing what they just inherited.

When to use it

Run this the moment a rep resigns, is terminated, or goes on extended leave. It prevents accounts from going dark during the gap between offboarding and a manager's manual cleanup, and it spreads load fairly instead of dumping everything on one person.

How it works

  1. 1Trigger fires when a Salesforce User's IsActive field changes to false.
  2. 2Query all open Accounts owned by that user, plus each account's last activity date and open opportunity count.
  3. 3Logic step builds a round-robin assignment map across active reps sharing the departing rep's territory.
  4. 4Update each Account's OwnerId in Salesforce in a batched write.
  5. 5For each new owner, post a Slack DM with the account name, last touch, open pipeline, and a deep link.
  6. 6Output a summary message to the sales-ops channel confirming counts reassigned per rep.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SalesforceAccounts, opportunities, cases.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.