--- title: "Sales Territory Reassignment When Reps Leave | Kylon" description: "How sales operations reassigns accounts from departed reps, books handover calls and re-spreads quota in one Kylon room, with every assignment approved by a person." url: "https://kylon.io/use-cases/territory-reassignment" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Territory Reassignment: Departed Reps' Accounts Handed Over Cleanly, Under the Cap Use Case8 min read # Territory Reassignment: Departed Reps' Accounts Handed Over Cleanly, Under the Cap Accounts from departing reps are reassigned under the territory policy, handovers are booked and quota is re-spread, with reruns for objections and closed deals. The sales operations manager approves every move before a deal owner changes. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Two reps leave, and their pipeline has to land somewhere sensible When two account executives leave in the same month, their books do not wait for a replacement. Thirteen accounts sit in Pipedrive under their names, with open deals at every stage and weighted values that count toward somebody's quota. The territory policy says how to move them: same region first, then industry fit, then the rep with the lightest weighted pipeline, with a cap on how much any one rep can take on. The policy is simple. The work around it is not. Handover calls need the new rep, a manager and sometimes customer success on one calendar. Reps object in Slack to an account they think belongs elsewhere. Deals close in the middle of the move and the weighted numbers shift under the plan. The quota re-spread lives in a spreadsheet that gets rebuilt from memory, and the handover notes for each account end up in four different places. ## Who works in the room People - Sales operations manager Runs the reassignment, approves every account move and signs each handover doc - Regional sales director Decides objections and approves the quota re-spread - Receiving account executives Accept their new accounts, run the handover calls and send each introduction Agents - NovaTerritory planner Proposes each account's new owner under the policy and the cap, re-runs single accounts on objection and writes approved deal fields PipedriveGoogle Drive - FinPipeline and quota Reads weighted pipeline from Pipedrive, recounts load after closed deals and cap corrections, and drafts the quota re-spread PipedriveGoogle Drive - RyanHandover coordinator Books handover calls, writes the account docs and drafts customer introductions for the receiving rep to send Google CalendarGoogle Docs[Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) The move gets a Kylon room of its own for as long as it runs. Nova, the room's default agent, owns the assignments, so a question about why an account went to a particular rep reaches it first. Fin answers anything about weighted pipeline or quota, and Ryan owns the handover calendar, the account docs and the introductions to customers. Nova and Fin read Pipedrive through one lasting grant the sales operations manager approved for the room, and only Nova writes, only to deal fields. When an assignment is approved, Nova opens a thread for Ryan whose first message lists the account, the new owner and who belongs on the handover call. ## The move, one account at a time Two things hold for the whole move, and both are in the room guidelines: the cap, and the one account that stays put. The policy and the quota sheet are in Google Drive. ```mermaid flowchart TD leave([Account executives leave]) stays([One named account stays put]) assign["Nova matches accounts by region,
industry and load, under the cap"] ok1["Sales operations manager
approves before owners change"] fields["Nova writes owner and handover
fields on each open deal"] calls["Ryan books a handover call per account"] accept["Receiving rep accepts each call"] rerun["Nova re-runs an account a rep
objects to, others as fixed load"] recount["Fin recounts load after closed
deals and a cap correction"] decide["Regional sales director
decides the objection"] ok2["Sales operations manager
approves any changed assignment"] quota["Fin drafts the quota re-spread
by weighted pipeline taken"] ok3["Regional sales director
approves the new quota lines"] docs["Ryan drafts one handover doc per
account with Fin's fresh figures"] ok4["Sales operations manager
approves each doc"] leave --> assign stays -.- assign assign --> ok1 --> fields --> calls --> accept accept --> rerun & recount rerun --> decide recount --> ok2 decide & ok2 --> quota --> ok3 --> docs --> ok4 class assign,fields,calls,rerun,recount,quota,docs agent class ok1,accept,decide,ok2,ok3,ok4 person class leave,stays event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Assignment | Twelve accounts are matched to remaining reps by region, industry and load, under the cap | Nova, from Pipedrive | The sales operations manager approves before any deal owner changes | | Deal fields and handovers | New owner and handover fields are written on each open deal, and one handover call is booked per account | Nova for the fields, Ryan for the calendar | The manager approves; each receiving rep accepts the call | | Objections | An account a rep objects to is re-run alone, with every other recorded assignment held as fixed load | Nova | The regional director decides the objection | | Cap correction and closed deals | Load is recounted after the cap is corrected, and closed deals drop out of each account's weighted pipeline | Fin | The manager approves any assignment that changes | | Quota re-spread | The departed reps' remaining quota is spread across receiving reps by the weighted pipeline each one took | Fin | The regional director approves the new quota lines | | Close-out | One handover doc per account, with weighted pipeline read fresh from Pipedrive | Ryan, with figures from Fin | The manager approves each doc before Ryan creates it | Stages of a territory reassignment. Accounts, reps and figures in this example are illustrative. ## Objections and closed deals in the middle of the move An objection is a request to re-run one account, not the whole plan. For example, a rep writes in Slack that one of the accounts is a former employer and asks not to own it. Nova re-runs that account alone. Every other account keeps the owner already recorded in Pipedrive, and those recorded assignments count as fixed load, so the rerun cannot quietly push another rep over the cap. Closed deals change the arithmetic every day of the move. When a deal in the set closes, won or lost, it leaves the account's weighted pipeline, and the figure is corrected on every open deal for that account. Fin recounts each rep's load before the next proposal, and a cap correction from finance is handled the same way. The close-out never reuses numbers from earlier in the week: Fin reads weighted pipeline from Pipedrive the morning the handover docs are written. ## What the checks catch - A write aimed at an organization record, when only deal fields should change - The named account that stays with its current owner, left untouched in every rerun - A rerun that counts load from earlier proposals instead of the assignments recorded in Pipedrive - A deal that closed this week still counted in its account's weighted pipeline - Close-out figures carried over from earlier in the week instead of read from Pipedrive on the day ## What stays with people - Approving every assignment before a deal owner changes - Deciding objections and approving the quota re-spread, which belong to the regional director - Sending each customer introduction, which Ryan drafts for the receiving rep - Signing off each account's handover doc ## Integrations in this workflow Kylon is not a territory planning tool, and Pipedrive remains the record of who owns what. Kylon sits beside it and the other tools sales operations uses, and holds the coordination while the move runs. - [Gmail](https://kylon.io/integrations/gmail) - Google Calendar - Google Docs - Google Drive - Pipedrive - [Slack](https://kylon.io/integrations/slack) - **Pipedrive** holds the accounts, open deals and weighted pipeline, and deal fields are the only records written - **Google Calendar** carries each handover call with the receiving rep and the manager - **Google Docs** holds the handover doc for each account - **Google Drive** keeps the territory policy, the cap and the quota sheet - **Gmail** carries introductions to customers and notices to reps, sent by a person from Ryan's drafts - **Slack** is where reps raise objections and managers post corrections ## Where to start Use the next departure, even if it is a single rep. Give the room a Pipedrive grant, put the policy and the cap in the cycle folder, and write one line into the room guidelines: deal owners change only after the sales operations manager approves, and organization records are never written. > “The plan was never the hard part. Keeping twelve moves straight while the numbers changed underneath them was.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our territory reassignment desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Gmail, Google Calendar, Google Docs, Google Drive, Pipedrive and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the sales operations manager, the regional sales director and the receiving account executives. Help me invite them to this Room. 3. Build an Account Moves App with columns Proposed, Approved, Handover booked and Closed out, one record per account. Pull the open accounts from Pipedrive and create a row for each. 4. Check each proposed assignment against region, industry fit and weighted pipeline load in Pipedrive, and our policy in Google Drive. Flag any account over the threshold we set, any rerun counting load from earlier proposals instead of recorded assignments, any closed deal still in weighted pipeline, and any write aimed at an organization record instead of a deal field. 5. Draft each deal field update, each handover doc and each customer introduction for review. The sales operations manager approves every assignment before a deal owner changes and approves each handover doc. The regional sales director decides objections and approves each quota re-spread line. Each receiving rep sends their own introduction from the draft. 6. Write the approval order, our cap rule and the rule that only deal fields are written into this Room's guideline so every account follows the same path. 7. After the move closes, offer to turn the daily load recount into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Price List Migration: Each Account Moves Once, at the Right New Amount Moving thirty wholesale accounts to a new price list means a disposition, an amount and sometimes a notice for each one. In a Kylon room, agents read HubSpot, Stripe and Mailchimp to propose them, and the revenue operations lead approves every change before a notice goes out. Retail & e-commerceRevenue operationsEmail operations ](https://kylon.io/use-cases/price-change-migration)[ ### SaaS Customer Renewal Desk: Renewals Closed or Held for a Reason That Is Still True Renewal dispositions, dunning, the order file review and late customer replies run through one Kylon room. Agents check every HubSpot deal against Stripe and both mailboxes, and the controller approves each stage change before it is written. Software & SaaSRevenue operationsFinance operations ](https://kylon.io/use-cases/saas-renewal-desk)