TCPA compliance for solar leads before the first call
Solar inquiries arrive through online campaigns, door-to-door visits, and lead vendors. Your call center needs to know which evidence supports the next contact. ConsentVerified captures online consent records and checks certificate evidence before dialing, so operations can hold or reject leads that fail the acceptance policy instead of asking agents to resolve consent questions during a call.
- Keep door-to-door and online evidence clear
- Name the business that intends to make contact
- Apply the same checks across solar lead vendors
- Reject unresolved leads before dialing
- Review the intended contact alongside the certificate
- Retrieve the record when a contact is questioned
- Choose Scale for a solar call center
Keep door-to-door and online evidence clear
For online forms, add the ConsentVerified snippet to record the displayed disclosure, submission action, page URL, timestamps, and session details. Link the resulting certificate ID to the lead sent to your call center. That gives reviewers evidence from the submission event instead of a later copy of the landing page.
During a door-to-door visit, a representative may use a tablet or direct the homeowner to a web form. If that form uses the capture snippet, the certificate records the online action. It does not establish everything said at the doorstep or turn a conversation into recorded written consent. Keep any separate records your process requires and identify their source accurately.
Review whether the homeowner can see the wording and take the action independently. A representative's assurance that the person agreed does not replace evidence of the action your contact policy requires. Document the transition from the visit to the digital submission and the intended follow-up channel.
Name the business that intends to make contact
Solar campaigns can involve a publisher, lead distributor, appointment setter, installer, and financing provider. Review which business the consumer sees in the disclosure and which business plans to call or text. A generic reference to partners does not resolve that question. Use the Consent Language Checker to flag seller identification and other wording that needs review.
Check channel coverage, relevant automated technology language, the statement that consent is not a condition of purchase, and the action linked to agreement. For texts, review the messaging elements relevant to the program. Keep the disclosure legible where the consumer acts, including on a representative's tablet and on a personal mobile device.
Solar buyers still need consent that names the installer, even though the stricter FCC rule never applied. Our article on the status of the one-to-one consent rule explains the court history. Other requirements still apply. Review the actual seller and intended contact under current law and your policy rather than assuming that a reference to a category of businesses settles permission.
| Lead | Phone match | Seller | Consent age | Score |
|---|---|---|---|---|
| Lead 48213 | Yes | Named | 14 days | 92 |
| Lead 48214 | Yes | Needs attention | 3 days | 71 |
| Lead 48217 | No | Named | 41 days | 88 |
| Lead 48220 | Yes | Named | 1 day | 95 |
Apply the same checks across solar lead vendors
A call center buying from many vendors needs a consistent intake rule. Use the Lead Verification API to check phone match, seller named, consent age, and disclosure score before sending a lead to the dialer. Record the certificate reference and vendor alongside the result, so an unresolved finding has an owner and a clear next step.
Define acceptance requirements in your vendor instructions. Require evidence that your team can retrieve and inspect, rather than accepting a consent flag without the underlying record. If a vendor uses another evidence provider, keep that provider's identifier and verification process clear. Do not treat certificate types as interchangeable or assume automatic cross-provider verification.
A lead with a missing certificate or phone mismatch belongs in a hold or rejection path under your policy. A seller or disclosure concern may need compliance review before a final decision. Set those paths in advance so delivery pressure does not make the decision for the team.
Reject unresolved leads before dialing
Set the verification step before lead routing in your intake workflow. When a required check fails, hold or reject the lead according to your policy, and keep it out of the calling queue while the issue remains unresolved. Preserve the reason for the decision so your operations team can explain it to the vendor.
Use a consistent return process for leads that fail your agreed acceptance criteria. Send the relevant reference and failure reason through your vendor's agreed channel, without sharing more consumer information than necessary. Refunds and credits depend on your vendor agreement. A software finding does not itself create a right to payment.
Do not ask a vendor to replace the historical record with a new certificate that appears to document the original submission. A fresh disclosure and action can create a new event, but they do not rewrite what the earlier evidence shows. Keep both events distinct when further permission is obtained.
| Lead | Phone match | Seller | Consent age | Score |
|---|---|---|---|---|
| Lead 48213 | Yes | Named | 14 days | 92 |
| Lead 48214 | Yes | Needs attention | 3 days | 71 |
| Lead 48217 | No | Named | 41 days | 88 |
| Lead 48220 | Yes | Named | 1 day | 95 |
Review the intended contact alongside the certificate
Before each contact, apply the suppression and revocation controls relevant to the campaign. The DNC scrubber supports federal and state list checks and internal suppression lists. Your team remains responsible for deciding how those results affect the call and for applying calling restrictions, opt-outs, and other applicable requirements.
For appointment reminders or marketing texts, review SMS consent and 10DLC evidence separately from the calling workflow. Evidence for one type of contact does not automatically cover every later message, seller, or purpose. Registration and consent records also do not guarantee carrier approval or delivery.
ConsentVerified is a compliance tool, not a law firm, and does not provide legal advice. Use verification results as evidence for your compliance process. A passing score does not settle whether a particular call or text is lawful, whether permission has been revoked, or whether additional state rules apply.
Retrieve the record when a contact is questioned
When a homeowner questions a call, your team needs to find the disclosure and action linked to that phone number. The Evidence Vault keeps captured records accessible under the selected plan's retention terms. Export a PDF and JSON evidence package to support review by your compliance team or counsel.
Keep the record connected to the source campaign and vendor. That context helps reviewers see whether the contact follows an online inquiry, a tablet submission after a visit, or a separate lead delivery. It also helps distinguish a source disclosure issue from a routing mistake inside the call center.
Retention needs can outlast a campaign. Compare your contractual and legal obligations with the plan's storage period before relying on it. Assign responsibility for preserving older records and for responding to evidence requests if your vendor relationships change. Your lead data stays yours, and retention should support the obligations attached to it.
| Lead | Phone match | Seller | Consent age | Score |
|---|---|---|---|---|
| Lead 48213 | Yes | Named | 14 days | 92 |
| Lead 48214 | Yes | Needs attention | 3 days | 71 |
| Lead 48217 | No | Named | 41 days | 88 |
| Lead 48220 | Yes | Named | 1 day | 95 |
Choose Scale for a solar call center
Scale is the recommended plan for a solar call center buying leads across many vendors. It costs $1,299 per month, or $649 per month billed yearly. Its verification allowances, team controls, and evidence retention suit an operation that needs a repeatable intake process across campaigns. Review the exact allowances on the pricing page.
Growth is an option for a smaller operation whose usage and retention needs fit its allowances. Enterprise fits operations that need the highest volume, a security review, or invoicing. Monthly plan limits still matter when you budget around a flat subscription.
Start with one intake path, define the rejection rules, and test that unresolved leads cannot reach the dialer. Follow the lead buyer workflow to connect evidence review with a documented decision before expanding the process across your sources.