Create and Manage Territories

Note: The user interface for this video is outdated. We will refresh the video soon! In the meantime, if there is any confusion, refer to this guide for a rundown of the primary difference between the current and previous UI. 

Hierarchies serve as the primary means to organize elements within your go-to-market design, facilitating the grouping of accounts and teams for the management of assignments, targets, and security access. 

When you access a selection from the Territories tile, the collapsible menu on the left side showcases the go-to-market hierarchy, with each individual node representing a territory. 

Create Territories and Making Fields Available for Territory Segmentation

Whenever a field is required for territory segmentation, Hierarchy Participation must be enabled on the field. 

1. Click the Settings icon (gear) in the navigation bar. 
2. Click the Entities and Fields tab. 
3. Choose the appropriate entity from the dropdown menu.
4. Locate the field in the table and click on the edit icon. 
5. Click the Basic Information tab and check the box Hierarchy Participation. 
6. Click Confirm. 

Add Hierarchy vs Add Node

Under the segmentation menu, there are two options to create territories: Add Hierarchy, or Add Node. 

• Add Hierarchy: Creating multiple territories using the same rule type, geographic territories, or territories using a smart plan. 
• Add Node: Creating a territory using a different rule than existing territories (e.g., Employees and Vertical), or for Named or Global accounts. 

Creating Territories Using Different Methodologies

Fullcast offers five methodologies to categorize customer segments into territories or hierarchies. 

1. Unique: Generates child nodes for distinctly unique values in a selected field. 
2. Bucket: Allows the creation of specific buckets to categorize child territories based on predefined criteria. 
3. SmartPlan: Automates territory creation, particularly useful for dense postal code areas. 
4. Map: Segments customers based on geographical location using a lasso tool.
5. Industry: Segments customers based on industry vertical.  

Adding Custom Nodes

Custom nodes can be added under both the parent and child nodes to further segment territories based on additional criteria. Follow these steps to create custom nodes:

1. Select the node where you want to add the custom node.
2. Open the Hierarchy Options menu and choose Add Node.
3. Enter a name for the node and check the Use Rule option.
4. Select the Field from the drop-down menu for criteria.
5. Set filter operator and relevant filter values.
6. Save the node.
7. Re-run rules to move records meeting the custom node filter criteria into the new node.

Editing Territory Rules

1. Select the Parent Node from the list of hierarchies.
2. Click on the Segmentation 3 Dot menu and choose Edit.
3. Edit rules based on the hierarchy type used.

Changing Hierarchy Types

Once a hierarchy is built, its type cannot be changed. To change the hierarchy type, delete the existing hierarchy and rebuild it using the new type.

Renaming Territories

1. Select the territory.
2. Click on the Segmentation 3 Dot Menu.
3. Choose Rename.
4. Type the new territory name and Confirm.

Deleting Territories

Note: Deleting a node removes all related information, including targets, assignments, and contents.

• You cannot delete the All Companies or Unassigned node unless no other nodes exist in the hierarchy. 
• When deleting a node, its records move to the Unassigned node under the same parent. If all child nodes under a parent node are deleted, their contents transfer to the parent node. 

Delete All Children Nodes

1. Select the parent node containing the child nodes you want to delete. 
2. Click on the More Options icon (three horizontal dots) and select Delete All Children Nodes. 
3. Type DELTE (case sensitive) and click Confirm. 

What happens to the content of a deleted?

When you delete a node, the records within it are moved to the Unassigned node under the same parent. If all child nodes under a parent node are deleted, the contents of those children are transferred to the parent node upon deletion.