Understand Service Territory and how it routes work orders to the right geographic service area.
Service Territory defines the geographic area used to route work orders. In connector integrations, this feature lets external systems send territory identity data so Field Nation can align a work order to the intended region.
Use Service Territory when routing decisions depend on location-specific ownership, provider pools, or dispatch boundaries. It gives integration teams a direct way to pass territory context during work order lifecycle events.
Routing Outcome
Routes work orders to the intended geographic service area.
Integration Model
Supports bidirectional mapping in connector configurations.
Mappable Fields
Uses service_territory_id and service_territory_name values.
Validation Behavior
Uses non-blocking validation for territory mapping failures.
Service Territory helps ensure routing consistency when work order creation starts in an external platform. By sending a territory ID or territory name, integration workflows can preserve dispatch intent and reduce manual reassignment in downstream operations.
Continue to Work Order Routing to configure and validate Service Territory mapping for work orders.
Last updated on
