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
| Tool | Native daily caps | Timezone-aware reset | Cap-aware overflow | Weekly/monthly caps | Price |
|---|---|---|---|---|---|
| Sheets + Zapier | Manual only | No | No | Manual | $50-300/mo + time |
| LeadMove | Yes, per installer | Yes | Yes | Yes | $149-499/mo |
| LeadProsper | Yes, Pro+ plans | Yes | Yes | Yes | $499+/mo |
| Boberdoo | Yes | Yes | Yes | Yes | $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?
what happens when an installer hits their daily cap?
can I set different caps for different days of the week?
how do I track daily caps without dedicated software?
what is cap-aware overflow routing?
can I set weekly or monthly caps in addition to daily caps?
what's the difference between pausing delivery and overflow routing when a cap is hit?
Continue reading

Lead Routing Software: The Complete Guide for B2B Teams
Optimize your B2B pipeline with lead routing software. Automate distribution, enforce SLAs, and increase qualification rates with rule-based logic.
What's the best lead distribution software for mortgage agencies?
Mortgage lead distribution tools compared: ping/post aggregators vs rules-based routers. Pick the right model.
What's the best lead routing software for solar agencies?
Lead routing tools built for solar workflows: zip territories, installer caps, exclusivity. LeadMove vs LeadProsper compared.