How do I handle exclusive territory rules for solar installers?

August 3, 20264 min read

Exclusive territory rules protect the core promise you make to solar installers: if you send a homeowner's lead to installer A, no other installer from your network calls the same homeowner. Breaking that promise once is usually enough to lose the installer relationship.

The mechanics of enforcing exclusivity — matching a lead's zip to exactly one installer, handling overflow for unclaimed areas, and resolving overlaps — are straightforward in concept but require real tooling to enforce reliably at scale.

How exclusive territory assignment works

The setup has three components:

Installer zip list: Each installer claims a set of zip codes or states they serve. This is the territory definition.
Exclusive mode flag: The pipeline is configured so each lead can only match one installer, regardless of how many installers' territories include the lead's zip.
Priority or weight: For overlapping zips, the router needs a tiebreaker — which installer gets the lead when two or more are eligible. Priority ranking (installer A always first) or percentage weight (60/40 split) are the standard approaches.

When a lead arrives, the router evaluates each installer's territory list in priority order and delivers to the first match. That installer is recorded as the exclusive recipient; no subsequent routing decision can assign the same lead elsewhere.

State-level vs zip-level exclusivity

For single-state pipelines, zip-level rules are usually sufficient. For multi-state operations, a state filter adds an important layer: only installers licensed to operate in that state are eligible to receive that lead, regardless of zip overlap.

Consider an installer with territory in New Mexico who has expanded their zip list to include border zips that technically fall in Colorado. If they're not licensed in Colorado, they shouldn't receive Colorado leads. A state filter prevents this at the rule level, which matters for contractor licensing compliance.

LeadProsper and LeadMove both support state + zip combined conditions on a single routing rule. The state check runs first, narrowing the eligible pool, then zip matching selects among licensed installers.

Overflow rules for unclaimed zips

Every territory map has gaps: rural zips that no installer covers, new areas where you haven't onboarded an installer yet, or zips that installers explicitly excluded. Leads from those areas need a defined outcome.

The options are: route to a national fallback installer who accepts out-of-territory leads at a lower price, hold in a queue for manual review, or reject and log as unmatched. Each is valid depending on your business model. The important thing is that unclaimed leads produce a logged outcome rather than silently disappearing.

Without overflow rules, unmatched leads become a black hole that you only discover when a buyer asks "where are the Texas leads?"

Comparison: exclusive territory enforcement

Tool	Exclusive mode	Zip + state rules	Real-time enforcement	Overflow routing	Price
Sheets + Zapier	Not enforced natively	Manual lookup	No (polling delay)	Manual	$50-300/mo + time
LeadMove	Yes, per pipeline	Native zip + state	Yes, at ingestion	Yes, configurable	$149-499/mo
LeadProsper	Yes	Yes, Pro+ plans	Yes	Yes	$499+/mo
Boberdoo	Yes (enterprise)	Yes	Yes	Yes	$1,000+/mo
Custom build	Depends on build	Depends on build	Depends on build	Depends on build	2-6 weeks dev time

Handling territory disputes from installers

Even with clean territory rules, installers will occasionally claim they didn't receive a lead they should have, or that they received one outside their territory. A dispute workflow — where the installer logs a complaint with the lead ID and reason, and your team can review the routing log — is the clean way to handle this.

The routing log matters here: you need to be able to show the installer exactly which rule matched (which zip, which priority, what timestamp) to either confirm the routing was correct or identify a configuration error.

Agencies running territory rules without logging end up resolving disputes over gut feel, which erodes installer trust faster than the occasional routing error.

Territory rules need to be set up once and then maintained as your installer network changes — new installers join, existing ones expand or shrink their coverage, and market conditions shift. The lighter the maintenance burden, the more reliably the rules stay accurate.

Frequently asked questions

what does exclusive territory mean for solar installers?

Exclusive territory means one installer holds the right to receive solar leads from a specific geographic area — a zip code, a group of zips, or an entire state — with no other installer receiving the same leads from that region. It's the opposite of shared distribution, where multiple installers compete for the same homeowner. Exclusive territory arrangements typically command a higher per-lead price because the installer has no competition from your distribution.

how do I set up zip-based exclusive territories without code?

In a dedicated routing tool, you create an installer profile and attach a zip list to it, then enable exclusive mode on the pipeline. The router checks the lead's zip against each installer's list at the moment of ingestion and delivers to the first match. LeadMove ships this natively from the $149 plan — no scripting required. With Sheets + Zapier, you'd need a custom lookup table and Zapier cannot enforce exclusivity in real time if leads arrive simultaneously.

what happens when a lead's zip isn't covered by any installer?

Leads from unclaimed zips need an overflow rule: either route them to a fallback installer who accepts out-of-territory leads at a lower price, hold them in a queue for manual review, or discard them if no match exists. The router should flag these as unmatched rather than silently dropping them. Defining an overflow rule for unclaimed zips is as important as setting up the territories themselves.

can I give an installer a state-level territory instead of zip codes?

Yes, and for national pipelines you often combine both: state-level exclusivity first, then zip-level exclusivity within that state for multi-installer states. State-level rules are common when installer licensing is state-specific. A Florida-licensed installer should only receive Florida leads regardless of zip overlap with installers in neighboring states. LeadProsper and LeadMove both support state-level and combined state + zip filters.

what happens if two installers want the same zip code territory?

You have three options: assign priority (one installer always wins that zip, the other is secondary overflow), split by percentage weight (60% to installer A, 40% to installer B), or run a shared mode where both receive every lead at a lower per-lead price. Most solar agencies choose priority or weighted split because shared mode in solar tends to hurt contact rates — homeowners getting multiple calls tend to ignore all of them.

how does LeadMove enforce exclusivity when leads arrive simultaneously?

LeadMove assigns each lead to an installer atomically at ingestion — the router locks on the lead record before evaluating rules so simultaneous leads from the same zip don't both route to the same installer. This is a technical requirement for real exclusivity enforcement. LeadMove handles this from the $149 Starter plan. Zapier-based setups have no such mechanism: two leads arriving within the same polling cycle both get the same routing result.

how do I handle territory changes when an installer leaves or a new one joins?

Update the zip list in the installer profile and adjust priority ordering for any affected zips. In a dedicated routing tool, this takes minutes and takes effect immediately. With custom-built routers, the change might require a code deployment. With spreadsheet-based routing, you update a lookup table and hope the Zapier step picks it up correctly. Plan for territory changes to happen a few times per year as your installer network evolves.