Residential solar has vertical-specific routing constraints. TCPA one-to-one consent, utility territory filtering, homeowner qualification, monthly-bill thresholds, and state-by-state incentive rules all have to be enforced before a bid request reaches an installer. Lead Router runs all of it on one routing engine.
Sub-100ms
Routing decision
FCC 23-107
Consent model
All US IOUs
Utilities supported
Aurora, OpenSolar, CRM
Delivery integrations
The Reality
General-purpose lead distribution software does not know what a utility territory is or why NEM 3.0 changes the contract economics in California.
Solar sits in the top three verticals for TCPA class-action exposure. The FCC 23-107 ruling (issued 2023, original effective date before court vacatur, and still the practical industry standard) pushed the enforcement line from a generic "partners" consent box to one-to-one consent against the specific seller that calls the prospect. Solar plaintiff firms have built entire docket pipelines around this. Lead distribution for solar has to capture the specific installer name at consent or the chain breaks.
Utility territory is the next filter most platforms skip. An installer based in San Jose serves PG&E customers but not SCE, SDG&E, or LADWP customers. An installer in Raleigh serves Duke Energy Carolinas but not Dominion. Without zip-to-utility filtering at the routing layer, installers burn appointment-setter time on leads that physically cannot buy their panels. Lead Router uses contract-level zip allow-lists to enforce this, and operators run one contract per utility territory per installer.
Homeowner status, monthly electric bill, household income, and roof condition are the qualification filters that separate a residential solar lead from a waste of an installer's phone minutes. All four are custom field filters on the contract, evaluated before the bid step, so rejected leads never reach an installer.
State incentive rules change the economics enough that distribution has to be state-aware. NEM 3.0 cut the California export credit and shifted value toward battery attachment. New Jersey and Massachusetts run SREC and SMART programs that change the dollar-per-watt installer payback. Texas and Florida are pure-retail-offset markets. Pricing, cap, and priority logic have to sit per contract per state.
How Lead Router Solves It
Each capability maps to a specific solar failure mode and is enforced at the contract level.
The form captures consent against the specific installer that wins the lead, not a generic "partners" bucket. Timestamp, IP, user agent, the installer name, and the consent language shown at submission are stored with the lead. That is the record of evidence required when a solar class-action plaintiff subpoenas your consent chain.
Each contract carries its own zip allow-list. Operators run one contract per utility per installer: PG&E, SCE, SDG&E, Duke Energy Carolinas, Duke Energy Florida, NYSEG, ConEd, Dominion, APS, Xcel, PSE&G. Zips outside the utility territory are rejected in the routing engine before the bid step.
Homeowner = true is a contract-level custom field filter. Renters are screened out before the buyer sees a bid request, so installer dialers do not burn minutes on leads that cannot install panels. The same pattern covers roof condition, roof age, and shading flags when the intake form captures them.
Monthly electric bill is a numeric custom field with range filters. A contract can require bills over $150 or $200 to match an installer that will not quote smaller systems. Household income buckets and FICO buckets work the same way, and all three are evaluated before bid, not after.
One offer can route to multiple installers with separate contracts per state. An installer in California runs on NEM 3.0 pricing logic, the New Jersey contract carries SREC-aware pricing, and the Massachusetts contract carries SMART-program logic. Exclusive, multisell, and hybrid distribution are all supported per offer.
Schedule filtering on every contract enforces the federal 8am to 9pm local-time window by the prospect zip, not by the buyer time zone. State-level stricter windows (for example Florida Sunday rules) are configured per contract. Off-hours leads are queued or rejected so your installers never dial outside the window.
Where It Fits
Residential solar is the primary use case. Adjacent sub-verticals reuse the same contract structure.
Delivery
Lead Router delivers to generic CRMs and to the solar-specific design, proposal, and CRM tools installers actually use.
Delivery happens over HTTPS POST. Field mapping is configured per contract so the outbound payload matches what each system expects. Salesforce and HubSpot are the default CRM destinations. For solar-specific tools, Lead Router delivers to Aurora Solar (design + proposal), OpenSolar (design + CRM), Sighten (financing + proposal), and Solo (proposal + close). Installer-specific platforms like Enerflo, Solargraf, and Bodhi accept the same payload structure.
Consent artifacts travel with the lead. TrustedForm cert URLs, Jornaya LeadiD tokens, and ActiveProspect identifiers are forwarded in the delivery payload so the installer can pull the cert independently and match it to their own audit trail. That matters when a TCPA complaint comes in twelve months after the install and the discovery request arrives.
Frequently Asked
The questions solar operators ask before they migrate their routing.
Does Lead Router filter solar leads by utility territory?
Yes. Every contract carries its own zip allow-list, which is how utility territory filtering is enforced in practice. A contract scoped to PG&E receives only zips inside PG&E territory. The same pattern covers SCE, SDG&E, Duke Energy, NYSEG, ConEd, Dominion, APS, Xcel, and any other investor-owned or municipal utility. Zip-to-utility mapping is maintained at the contract level so operators can run separate contracts for each utility a given installer serves.
How does Lead Router handle TCPA for solar leads?
Lead Router is architected for the FCC 23-107 one-to-one consent model, which matters for solar because the vertical has been a top class-action surface since the 2023 ruling. Consent metadata (timestamp, IP, user agent, campaign, the specific installer name the lead consented to, and the consent language shown at submission) is captured per buyer and stored with the lead record. The same identifiers ride through the call log, posting log, and lead record for discovery response.
Can I filter solar leads by homeowner status?
Yes. Homeowner status is a contract-level custom field filter. A contract can require homeownership = true and reject renters before the buyer ever sees a bid request. The same custom field pattern supports roof condition, roof age, roof type, and solar shading flags when those are captured on the intake form.
Does Lead Router support monthly-bill bucket filtering?
Yes. Monthly electric bill is a numeric custom field with range filter support. Contracts can require bills above a given threshold (for example $150 or $200) to screen out prospects too small to justify a residential solar quote. Income and credit bucketing work the same way. Filter evaluation happens in the routing engine before bid, so rejected leads never hit the buyer.
Does Lead Router integrate with Aurora or Sighten?
Yes. Delivery to solar-specific tools like Aurora Solar, OpenSolar, Sighten, and Solo happens over REST webhook or the standard HTTPS post. Field mapping is configured per contract so the payload matches what each downstream system expects. TrustedForm cert URLs, Jornaya LeadiD tokens, and ActiveProspect identifiers are forwarded in the same payload for buyer-side consent audit.
Route Solar, Not Generic Leads
Utility territory, homeowner qualification, monthly-bill thresholds, NEM 3.0 and SREC-aware contracts, and per-buyer TCPA consent capture on one engine. Free trial to start.
No credit card required. All features included from day one.