Skip to main content

Territories and capacity

Match storm-response work to places and teams that can actually service it.

Organize states, ZIP codes, trades, travel limits, licensing, crew capacity, budgets, and account configuration before an event creates demand.

Request a walkthrough Review all capabilities

Operating workflow

01

Define

Document the geography, trade, licensing, travel, scheduling, and budget constraints for each operating team.

02

Match

Compare candidate impact areas with configured serviceability and capacity rather than map size alone.

03

Throttle

Pause, cap, or expand activation based on provider readiness, workload, appointment availability, and observed economics.

Activation review

Questions the demo should answer

  • Can the business legally and operationally serve each selected market?
  • How are overlaps, waitlists, plan limits, and changes handled?
  • What happens when crews, calendars, or budgets are full?
  • Does territory configuration affect research, spend, and every downstream action?

Evidence boundary

A configured ZIP is an operating preference, not proof of exclusivity, customer demand, storm damage, or guaranteed lead volume.