Back to Blog

How do I cap solar leads per installer per day?

5 min read
How do I cap solar leads per installer per day?

Solar crews run on appointments. An installer who books 8 site visits on a Tuesday can't absorb 25 leads in a day just because your pipeline is running well. Daily caps are the mechanism that keeps lead flow and installer capacity in sync — and without native enforcement, they fail under real-time load.

This guide covers how daily caps work in practice, what overflow behavior should look like, and what tools actually enforce caps reliably versus those that require manual monitoring.

How daily caps work in lead routing

A daily cap is a maximum lead count per installer per 24-hour window. The router checks the installer's count at the moment a lead arrives: if they're under the cap, deliver; if they've hit the cap, apply the overflow rule.

The 24-hour window can be defined two ways: a fixed midnight-to-midnight reset in the installer's timezone, or a rolling window (e.g., the last 24 hours from the current timestamp). Fixed midnight resets are simpler to communicate to installers ("your cap resets every morning"). Rolling windows are stricter but can be confusing when an installer asks "why did I stop getting leads at 3pm?"

For most solar agencies, fixed midnight resets work well. The key is that the reset happens automatically and timezone-correctly — a West Coast installer shouldn't have their cap reset at midnight Eastern time.

Why manual cap tracking fails

The failure mode is predictable: two leads arrive at the same time from the same territory. Both pass the "is installer A under cap?" check simultaneously, before either one increments the counter. Both get routed to installer A. The cap is exceeded by one lead.

At low lead volumes (under 20/day across all installers), this happens rarely. At 200 leads/day to 8 installers, parallel arrivals are constant and over-delivery is systematic. Manual spreadsheet tracking has no defense against this because the human checking the count introduces a time gap between the check and the delivery.

Zapier-based setups face the same problem: Zapier executes steps sequentially per task, but multiple tasks triggered simultaneously don't coordinate with each other. Two Zaps running concurrently can both read the same cap count before either writes the increment.

Cap-aware overflow routing

Overflow routing is what makes caps useful rather than just restrictive. When installer A hits their cap, the lead doesn't get dropped — it routes to installer B in the same territory (if B has capacity), or to a fallback installer who accepts overflow leads from anywhere.

The router evaluates each installer in priority order against both territory match and cap headroom. An installer who matches the territory but has hit their cap is skipped. This is cap-aware routing: the cap status is part of the eligibility check, not an afterthought.

Without overflow, every cap hit either wastes a lead or requires manual re-routing. With overflow, capped installers are transparently bypassed and lead flow continues.

Comparison: daily cap enforcement by tool

ToolNative daily capsTimezone-aware resetCap-aware overflowWeekly/monthly capsPrice
Sheets + ZapierManual onlyNoNoManual$50-300/mo + time
LeadMoveYes, per installerYesYesYes$149-499/mo
LeadProsperYes, Pro+ plansYesYesYes$499+/mo
BoberdooYesYesYesYes$1,000+/mo

Combining caps with operating hours

Daily caps tell the router how many leads to send; operating hours tell it when to send them. Together, they give you full capacity control per installer.

An installer with a daily cap of 10 and operating hours of 8am-5pm Monday-Friday won't receive leads on weekends and won't receive more than 10 on any given weekday. Leads that arrive outside those windows either overflow to another installer or queue for the next working window.

This combination is standard for solar agencies with multi-state operations where installer crews have defined schedules. LeadMove and LeadProsper both support operating hours + caps as combined conditions per installer.

Communicating caps to installers

Installers need to know their cap and when it resets so they can plan their day. A buyer portal where installers see their current count and cap limit in real time removes a lot of inbound questions. Without visibility, installers assume something is broken when leads stop around mid-day.

A simple "you've received 10/10 leads today, cap resets tomorrow morning" view in the installer portal handles this. It's a small feature with a meaningful impact on installer satisfaction.

Daily caps are one of those features that seem optional until the first time an installer calls to say they got 40 leads in a day and stopped answering their phone. Setting them up once — with proper overflow rules — prevents that conversation entirely.

Frequently asked questions

why do solar installers need daily lead caps?

Solar installers have real capacity limits: a crew can physically visit and quote only so many homes per day. Sending 30 leads to an installer who can handle 8 creates several problems — stale follow-up, low contact rates, installer complaints, and potential homeowner complaints about repeated calls. Daily caps enforce a lead volume ceiling so installer capacity and lead flow stay aligned.

what happens when an installer hits their daily cap?

The router should apply an overflow rule: skip the capped installer and deliver to the next eligible installer in the same territory, or pause delivery to that pipeline until the cap resets. Without an overflow rule, leads either over-deliver (causing the installer to ignore them) or get silently dropped. The cap reset time is usually midnight in the installer's timezone, though some agencies use rolling 24-hour windows instead.

can I set different caps for different days of the week?

Yes — if your router supports it. Some installers want lower caps on Fridays or no leads on weekends because their crews don't work those days. Combining daily caps with operating hours (no delivery on weekends, reduced caps on Friday) gives you precise capacity management. LeadMove supports per-installer operating hours and daily caps together from the $149 plan.

how do I track daily caps without dedicated software?

Manual cap tracking means someone checks a spreadsheet every time a lead is assigned, increments a counter, and decides whether to route or hold. This breaks immediately when leads arrive in parallel: two leads arriving simultaneously can both pass the cap check before either increments the counter. Zapier can't solve this because its steps execute sequentially with polling delays, not atomically.

what is cap-aware overflow routing?

Cap-aware overflow means the router checks each installer's cap status before assigning a lead, and automatically skips capped installers in favor of the next eligible one. LeadMove and LeadProsper both implement this natively. The alternative — routing first and checking caps after — creates over-delivery errors that require manual credits. Cap-aware routing prevents the problem at the source.

can I set weekly or monthly caps in addition to daily caps?

Weekly and monthly caps complement daily caps for installers who want to control total lead volume across a period, not just per-day flow. Some installers cap monthly rather than daily because their scheduling is more project-oriented. LeadMove enforces daily, weekly, and monthly caps with configurable overflow rules on every plan from $149/mo. LeadProsper supports caps on Pro tiers at $499+/mo.

what's the difference between pausing delivery and overflow routing when a cap is hit?

Pausing delivery stops all leads to the capped installer (and potentially to the whole pipeline) until the cap resets. Overflow routing keeps the lead flowing by routing to the next eligible installer. Pause mode protects a specific installer from any additional volume; overflow mode keeps your overall lead flow running. Most agencies prefer overflow routing so no lead is wasted when one installer is capped.

Start distributing leads smarter today

Ingest. Score. Route. Track. One platform.