Q: Can a territory span multiple states?
Yes. Add ZIPs from any state to the ZIP list, or draw a polygon that
crosses state lines. There's no state-level constraint.
Q: What happens to jobs already tagged with a territory when I edit
that territory's boundary?
Nothing. Existing tags are preserved. Boundary changes only affect
future auto-assignments.
Q: Can I copy a territory to make a similar one?
Not directly. Create a new territory and paste the ZIP list from the
original, or import the same GeoJSON. Duplicate-territory shortcuts will
ship in a follow-up.
Q: How many territories can I have?
No hard cap. Ten to fifty is typical for most operations; if you're
setting up hundreds, ping support so we can help think through routing
performance.
Q: Do customers see territory names?
No. Territories are internal only. Customers see their site address and
service history, not the territory label.
Q: Can I set a territory that only runs on holidays or one week a
month?
The Schedule tab supports "Specific weeks" (Wk 1-5 of each month); that
covers the "one week a month" case. There's no holiday-only
frequency; use a monthly cadence and manage those routes as one-off
overrides on the dispatch board.
Q: What if a driver's ZIP list is different from the territory's?
Territories own the ZIPs. Drivers don't have their own ZIP lists;
their coverage is defined by which territories they're attached to.
Q: Do I need to define territories to use PortaPro?
No. Territories are optional. If you skip this whole section, PortaPro
still works; you just won't get automatic address tagging, the
territory overlay on the dispatch map, or territory-based route
suggestions.
Q: Can multiple drivers share a territory?
Yes. Attach as many primary and backup drivers as you need. Dispatch
will suggest any of them when routing.
Q: What's the difference between a Service Territory and a Service
Location (Site)?
A Site is one physical address for one customer. A Service
Territory is a geographic area covering many sites and many customers.
Territories describe *where you work*; sites describe *where each
customer is*. Auto-assignment links the two by tagging each site with
its territory.
Q: My old dispatch tool used "Service Zones." Are those the same?
Yes; Service Zones was renamed to Service Territories in the August
2026 update, and the underlying table was consolidated. Any old zones
are now territories with the same ZIPs, drivers, and schedules.