US Territory
US Territory fields route leads to agents based on US geographic location. Agents configure their territories using US zip codes, counties, states, or regions. When a lead comes in, the input can be any location format — a city name, zip code, phone number, address, or state — and EnforcedFlow automatically resolves it to the right agent.
Creating a US Territory Field
Section titled “Creating a US Territory Field”- Navigate to the Fields tab in your group
- Click Add a New Field
- Select US Territory as the field type
- Click Save
Flexible Input Matching
Section titled “Flexible Input Matching”The input type doesn’t need to match how your agents are configured. A lead can come in as a city name while your agents are set up by zip code — EnforcedFlow decodes the input and matches it to the right agent automatically.
How It Works When Adding Agents
Section titled “How It Works When Adding Agents”When you add an agent to the group, the US Territory field appears as a location input. Enter zip codes, counties, states, or regions to define each agent’s territory. Agents can have territories at different granularity levels — one agent might cover specific zip codes while another covers an entire state.
How Matching Works
Section titled “How Matching Works”When a lead comes in, EnforcedFlow resolves the location through a three-step process, trying each step in order until a match is found.
Step 1: Direct Match
Section titled “Step 1: Direct Match”When the input type matches the agent config type (e.g., both are zip codes), the system does an exact value lookup. This is the fastest and most precise match.
Step 2: Inclusion Match
Section titled “Step 2: Inclusion Match”If no direct match is found, the system checks whether the input falls within an agent’s territory using the geographic hierarchy.
A state input like “California” includes all zip codes in CA. If multiple agents match equally, assignments are distributed via round robin.
Step 3: Distance Match
Section titled “Step 3: Distance Match”When no direct or inclusion match exists — for example, an unassigned zip code — the system falls back to geographic proximity and assigns the nearest agent.
Round Robin
Section titled “Round Robin”When multiple agents match equally at the same resolution step, leads are distributed using round robin.
Examples
Section titled “Examples”Below are 13 scenarios across 3 configuration types demonstrating how flexible matching works in practice.
Agents Configured by Zip Code
Section titled “Agents Configured by Zip Code”Agents: John (94103, 94110), Sarah (90012, 90210), Mary (60601)
Each agent is assigned specific zip codes. The input can be anything — a city name, a county, a phone number, or even a nearby unassigned zip — and the system resolves it to the matching agent.
City input resolves to matching zip
Section titled “City input resolves to matching zip”County input resolves to matching zip
Section titled “County input resolves to matching zip”Phone number resolves to matching zip
Section titled “Phone number resolves to matching zip”Nearest match when input zip is unassigned
Section titled “Nearest match when input zip is unassigned”Multiple agents in same state triggers round robin
Section titled “Multiple agents in same state triggers round robin”When the input is “California” and multiple agents have zip codes in CA, the system can’t pick just one — so it round-robins between all matching agents.
Agents Configured by County
Section titled “Agents Configured by County”Agents: John (San Francisco County, Marin County), Sarah (Los Angeles County, Orange County), Mary (Cook County)
Each agent is assigned specific counties. Inputs like zip codes, city names, or state names are resolved to the correct county and matched to the right agent.
Zip input resolves to matching county
Section titled “Zip input resolves to matching county”City input resolves to matching county
Section titled “City input resolves to matching county”State input matches counties in that state
Section titled “State input matches counties in that state”Nearest county match when input county is unassigned
Section titled “Nearest county match when input county is unassigned”Multiple agents in same state triggers round robin
Section titled “Multiple agents in same state triggers round robin”When the input is “California” and multiple agents have counties in CA, the system round-robins between all matching agents.
Agents Configured by State
Section titled “Agents Configured by State”Agents: John (California, Nevada), Sarah (New York, New Jersey), Mary (Texas)
Each agent is assigned entire states. Zip codes, phone numbers, and region names all resolve to the correct state.
Zip input resolves to matching state
Section titled “Zip input resolves to matching state”Phone number resolves to matching state
Section titled “Phone number resolves to matching state”Region input matches states in that region
Section titled “Region input matches states in that region”Use Cases
Section titled “Use Cases”Regional Sales Teams
Section titled “Regional Sales Teams”Assign agents to states or regions. A lead from any city or zip within that area routes to the right rep automatically.
Local Service Coverage
Section titled “Local Service Coverage”Assign agents to specific zip codes or counties for precise coverage areas. The system handles input in any format — a customer might provide their city, address, or phone number and still get matched to the right local agent.
Mixed Territory Teams
Section titled “Mixed Territory Teams”Different agents can operate at different granularity levels. One agent might cover all of California (state level) while another covers only Los Angeles County. The system respects the hierarchy — a lead from LA County goes to the county-level agent, while a lead from Sacramento goes to the state-level agent.
Using with Integrations
Section titled “Using with Integrations”US Territory fields work with Zapier (pass a location value into the US Territory field), email forwarding (location is auto-extracted from email content), and the API.