- Industry
- Retail
- Department
- Sales
- Team
- Pipeline Generation
- Kind
- Decision-maker
- Approver
- Head of B2B Sales
- Code
- SAL-06
It assigns corporate accounts and marketplace partners to B2B territories and reps by region and size, balancing pipeline potential (headcount, past order value, gifting season) and workload against each rep's capacity and quota. It keeps accounts with open deals or an order in fulfilment with their current owner and proposes the moves, with the effect on each rep's book, before anything changes.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the loyalty and CRM platform: corporate accounts and marketplace partners with owners, open deals, orders in fulfilment and past order value..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of B2B Sales with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the loyalty and CRM platform: it reassigns the approved accounts to their new owners. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The territory rules: the territory basis, rep capacity, account size bands, the rule for accounts with open deals or orders in fulfilment, and the freeze around the year-end gifting peak.
Reads from
the loyalty and CRM platform: corporate accounts and marketplace partners with owners, open deals, orders in fulfilment and past order value.
Acts in
the loyalty and CRM platform: it reassigns the approved accounts to their new owners.
Hands back
An object with moves (a list, each with account_id, from_rep, to_rep and reason), books (a list, each with rep, accounts_before, accounts_after, potential_before and potential_after) and kept (a list, each with account_id and reason).
Asks a person when
The plan moves more than 10 accounts, moves an account with an open deal, or falls in 1 October to 31 December.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Territory basis | region | How territories are drawn. |
| Most accounts per rep | 80 | A rep holds at most this many accounts. |
| Balance tolerance (%) | 15 | Reps' pipeline potential may differ by at most this much. |
| Keep owners with open deals | On | When on, accounts with an open deal or an order in fulfilment keep their owner. |
| Moves without approval | 10 | More moves than this in one run need the approver. |
| No moves during | 1 October to 31 December | The corporate gifting peak, when accounts stay with their rep. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Draw territories by region and keep each rep at or below 80 accounts.
- Balance pipeline potential across reps within 15 percent.
- When on is true, an account with an open deal or an order in fulfilment keeps its owner.
- Make no moves during 1 October to 31 December.
- More than 10 moves in one run go to the Head of B2B Sales.
See the Territory Planning Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.