[object Object]

Territories in Freshsales do four jobs at once: they auto-assign new leads, they scope reports, they roll up forecasts, and they gate record visibility when sharing rules are tight. That overload is why bad territory design hurts on every reorg.

Territory hierarchy versus flat list

You can build territories flat (“US-East,” “US-West,” “EMEA”) or hierarchical (“Americas > US > Northeast > NY-Metro”). Hierarchical wins for any team over 25 reps because forecast rollups follow the tree. The cost is that every rule needs a leaf node assignment. A rep cannot own “US” and have deals in “NY-Metro” automatically count.

Keep the tree at three levels max. Four levels make the territory picker unusable on mobile.

Assignment rule order matters

Freshsales evaluates territory rules top-to-bottom and stops on the first match. Put your most specific rules first: ZIP code lookups before state, state before country. Your last rule should always be a catch-all “Unassigned” territory routed to a sales ops queue, never to a default rep.

A common bug: rule 1 is “Country = US, route to US-East.” Rule 2 is “State = California, route to US-West.” Rule 2 never fires because rule 1 already matched. Reverse the order.

Account-based territories

If you sell to named accounts, do not use geographic rules. Use a workflow on the Account module that watches a “Strategic Tier” field and writes the territory directly. Geography becomes a tag, not the routing key.

Round robin inside a territory

A territory can hold a group of reps with round-robin assignment turned on. The counter is per territory, not global. If you split one territory into two, each new territory starts its round-robin counter at zero, which means the first rep in each gets two leads in a row. Pre-seed by manually assigning one lead per new territory before turning the rule on.

Vacation and capacity rules

Set a max-leads-per-day cap per rep inside the territory settings. Reps on PTO get marked unavailable from their profile and the round robin skips them automatically. Without this, the rep coming back from a week off has 40 untouched leads on Monday.

Reorg playbook

When the sales VP redraws the map, do this in order: clone the production territory tree to sandbox, edit the new tree, dry-run the assignment rules against last 30 days of leads, diff the assignment list with the old tree, fix exceptions, then promote. Never edit production territory rules during business hours.

Forecast scoping

Forecasts honor the territory hierarchy. A manager seeing “Americas” sees the sum of all leaf territories under it. If a deal is assigned to a rep but the rep is not in any territory, the deal disappears from forecasts. Audit weekly with a “Reps without territory” report.

What to do this week

Map your current territory tree on a whiteboard, find your catch-all rule (or add one), and run the “deals without territory” report. Fix orphans before the next forecast call.

[object Object]
Share