Solar leadgen agencies face a routing problem that generic automation tools weren't built for: each installer has a fixed service territory, a capacity limit, and an expectation that no other installer calls the same homeowner. Get any of those three wrong and you lose the installer relationship.
The distribution setup that works at 2 installers (a shared spreadsheet and some Zapier steps) falls apart at 5. Territory overlap starts causing complaints, daily caps require manual monitoring, and exclusivity is nearly impossible to enforce in real time. This guide covers how structured solar lead distribution actually works.
The three rules that drive solar lead routing
Solar distribution is built on three conditions evaluated at the moment a lead arrives:
- Territory match: Does the installer cover the lead's zip code or state?
- Cap headroom: Has the installer hit their daily (or weekly) lead limit?
- Exclusivity: Has this lead already been sent to another installer?
All three must pass before a lead routes to an installer. If territory matches but the cap is full, the lead rolls to the next eligible installer. If no installer claims the lead, it goes to a fallback queue rather than getting dropped.
Zip-code territory assignment
The standard approach is to give each installer a zip list — a fixed set of zip codes they exclusively cover. The router checks the lead's zip against each installer's list in priority order and delivers to the first match.
Complications arise when territories overlap. Two installers might both cover a border zip between their markets. You handle this with either priority ranking (installer A always wins that zip) or a shared-mode split (both get the lead at a lower per-lead price). Most solar agencies choose priority ranking to protect installer relationships.
For multi-state campaigns, add a state-level filter on top of zip rules: a Texas lead only reaches Texas-licensed installers. This matters for contractor licensing compliance in states with stricter rules.
Daily caps and overflow routing
Installers have real capacity limits — their crew can only handle so many site visits per day. Sending 30 leads to an installer who can close 8 creates resentment and poor contact rates. Daily caps enforce that limit automatically.
When an installer hits their cap, the router needs an overflow rule: skip to the next eligible installer in the same territory (if another one exists), or pause delivery for that installer until the cap resets at midnight. Neither option requires manual intervention if the router enforces caps natively.
Dedicated routers like LeadProsper ($499+/mo), Boberdoo ($1,000+/mo), and LeadMove ($149/mo) all enforce caps natively at the routing layer. Zapier and Sheets track caps manually, which means a burst of 20 leads arriving in 30 seconds will over-deliver before anyone checks the count.
Exclusive mode: one homeowner, one installer
Shared leads in solar damage everyone: the homeowner gets multiple calls and ignores all of them; installers blame each other for poor contact rates; your agency takes the credibility hit. Exclusive mode — one lead delivered to exactly one installer — is the standard for quality solar distribution.
The exclusivity check happens at delivery time, not after. The moment a lead is sent to installer A, it's marked exclusive and no other installer receives it, even if installer B's territory also covers that zip. The ordering of who gets first shot is determined by priority or weighted split pre-configured per campaign.
Comparison: solar lead distribution tools
| Tool | Zip territory rules | Daily caps | Exclusive mode | Installer portal | Starting price |
|---|---|---|---|---|---|
| Sheets + Zapier | Manual lookup only | Manual check | Not enforced | None | $50-300/mo (task costs) |
| LeadMove | Native zip + state rules | Daily/weekly/monthly | Yes, per campaign | Yes, from $149/mo | $149/mo |
| LeadProsper | Yes, on $499+ plans | Yes, on Pro tiers | Yes | Yes, enterprise | $499/mo |
| Boberdoo | Yes (ping/post model) | Yes | Yes | Yes | $1,000+/mo |
| Custom build | Whatever you code | Whatever you code | Whatever you code | Rarely built | $20k-80k dev cost |
Installer-facing dispute resolution
Even with clean routing, installers dispute leads: wrong phone number, homeowner was renting not owning, property was already contracted with a competitor. A dispute workflow gives installers a structured way to flag these cases with a reason code, and gives your team a queue to review and issue credits.
Without a portal, disputes arrive as emails or texts and credits get missed. At 200+ leads/month across 8 installers, that's a meaningful revenue and relationship problem. The portal also builds trust: installers can verify their lead counts in real time rather than waiting for a monthly reconciliation call.
The agencies that run solar distribution cleanly share one pattern: they get the territory, cap, and exclusivity logic locked in before they scale past 5 installers, because retrofitting those rules into a Sheets workflow at 10 installers is significantly harder than starting with a purpose-built tool.