A Service Territory is a geographic boundary in Zoho FSM that defines the area covered by a specific group of field agents. Territories can be defined by city, region, postcode, or a custom boundary. When a Work Order is created for a customer address, FSM matches it to the appropriate territory and routes it to agents assigned to that territory, ensuring jobs are always handled by the team closest to the customer.
Service Territories can be nested in a hierarchy. A parent territory might represent a state or large metropolitan area, with child territories for individual districts or zones. This hierarchy allows escalation rules to move a job up to a parent territory when no agents in the child territory are available, preventing jobs from going unassigned.
Each Field Agent is assigned to one or more Service Territories in their profile. When a Work Order falls within a territory, only agents assigned to that territory appear as scheduling candidates in the Dispatch Console. This restriction ensures dispatchers don’t accidentally assign a job to an agent based in a different city, and reduces travel time across the entire operation.
Yes. A Field Agent can be a member of multiple Service Territories simultaneously. This is common for agents in border zones who serve two adjacent territories, or for senior technicians who cover a wider area than standard agents. Their work queue will include jobs from all assigned territories.
Territories are defined by the administrator in the FSM settings using postcode ranges, city or region names, or manually drawn boundaries on the territory map. For precise geographic boundaries, map-based drawing is the most accurate method. For simpler operations, postcode or city-based definitions are faster to set up and maintain.
Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.