Solar AI Calling Compliance Guide (TCPA & State Rules)

Solar companies can legally use AI calling agents to contact inbound leads, but only with documented prior express written consent, honored do-not-call rules, and disclosure that an artificial voice is on the line. The reason the stakes are high: solar is one of the most heavily litigated verticals under the Telephone Consumer Protection Act (TCPA), and the FCC confirmed in a 2024 declaratory ruling that AI-generated voices are "artificial" under the statute — meaning the same consent and disclosure rules apply. Get consent capture right and you can call inbound leads in seconds; get it wrong and each improper call carries statutory damages of $500 to $1,500.

This is a playbook, not legal advice. Solar lead flows move fast and regulations shift, so treat the framework below as a starting point and confirm specifics with qualified counsel before launch.

AI voice calls are legally treated as "artificial voice" calls under the TCPA

Any AI calling agent that speaks with a synthesized or cloned voice is regulated as an "artificial or prerecorded voice" under the TCPA. The FCC's February 2024 Declaratory Ruling made this explicit, closing any argument that AI voices sit in a legal gray zone.

Practically, that means three things apply the moment your AI agent dials:

• Prior express written consent is required for AI-voice calls made for marketing to a wireless number.
• Identification — the caller's identity and a contact number or address must be disclosed during the call.
• The consumer must be able to opt out at any time, including mid-call.

The distinction that trips up solar teams: a purely informational or transactional AI call (confirming an appointment a homeowner already booked) sits under a lighter standard than a marketing call pitching a new system. When in doubt, treat the call as marketing and collect written consent, because the safe path costs you nothing and the risky path costs $500–$1,500 per call.

Speed and compliance are not opposites here. The fastest-responding solar teams win — approximately 78% of buyers choose the vendor that responds first — so the goal is compliant speed, not slow caution.

Solar is a TCPA litigation magnet — build for scrutiny

Solar lead generation attracts more TCPA lawsuits per dollar of ad spend than almost any consumer vertical. High-pressure lead aggregation, recycled lead lists, and multi-seller consent forms are the recurring triggers.

The most common failure points in solar calling programs:

• Blanket consent language buried in a form that names an unrelated brand, then the lead gets sold to a solar installer who calls anyway.
• Lead resale chains where the caller can't prove where consent originated.
• Recycled numbers — a homeowner surrenders a cell number, it gets reassigned, and the AI agent calls the new owner who never consented.
• Aged leads dialed months after the form fill, when the consumer's expectation of contact has evaporated.

Your defense is documentation. Every AI call should be traceable to a specific consent record: the exact form language, timestamp, IP address, and the URL where the homeowner opted in. If you can't reconstruct that chain, assume you can't defend the call.

For a deeper operational foundation on how fast lead contact drives conversion without cutting compliance corners, see the complete guide to speed to lead.

Prior express written consent: what a valid solar consent form actually needs

A compliant solar consent form must clearly authorize AI/automated and prerecorded calls, to a specific number, from a specifically named seller. Vague "we may contact you" language does not satisfy the written-consent standard for AI-voice marketing calls.

A defensible consent checkbox includes:

• A clear statement that the consumer agrees to receive marketing calls and texts using automated technology and/or an artificial or prerecorded voice.
• Explicit note that consent is not a condition of purchase.
• The specific seller's name — not just the lead-gen brand. If leads are sold to multiple installers, name them or the consent may not transfer.
• The consumer's phone number, captured with the checkbox, plus timestamp and IP.
• Conspicuous placement — not pre-checked, not hidden in a scrolling terms box.

Note the FCC's "one-to-one consent" direction from 2024, which pushed the industry toward consent that authorizes a single, clearly identified seller rather than a list of unnamed "marketing partners." Solar programs relying on shared or multi-seller consent should treat that model as high-risk and confirm current rules with counsel.

Store the consent artifact alongside the lead. A platform like Lead to Speed that logs every call recording, transcript, and AI summary in a built-in CRM makes the consent-to-call chain far easier to reconstruct if a claim ever lands.

State rules stack on top of federal TCPA — the strictest one wins

State telemarketing laws add requirements beyond the federal TCPA, and where they conflict, you must follow the stricter rule. Several states have passed "mini-TCPA" statutes with their own private rights of action, which means a call can be federally compliant and still violate state law.

Recurring state-level obligations solar callers should map:

• Calling-hour windows — many states restrict calls to roughly 8 a.m.–9 p.m. local time, and some are tighter. Always use the consumer's time zone, not your office's.
• State do-not-call lists and registration/bonding requirements for telemarketers in certain states.
• Additional disclosures — some states require you to identify yourself and purpose within the first seconds of the call.
• Curfews and frequency caps limiting how many calls you can place in a set period.

Florida, Oklahoma, and Washington are frequently cited examples of states with aggressive mini-TCPA regimes, but the list changes — verify each state where you generate leads before dialing. Because 30–40% of inbound solar leads arrive after hours, your AI agent needs geolocation-aware quiet-hours logic so a 9:15 p.m. West Coast form fill doesn't trigger a call into a stricter Eastern-time jurisdiction.

The speed-vs-compliance tension is solvable — call fast, gated by consent

The right architecture calls a consented lead within seconds while automatically suppressing any lead that fails a compliance gate. Speed and compliance conflict only when consent and suppression checks are manual.

Why the speed matters: the MIT/Oldroyd Lead Response Management study found leads contacted within 5 minutes are dramatically more likely to qualify — the widely cited figure is roughly 21x versus waiting 30 minutes — and Velocify research shows contact within the first minute produces the highest conversion of all. In solar, where a homeowner may fill three installer forms in one sitting, the first compliant caller usually wins the appointment.

A compliant fast-call flow should run these checks before the AI agent dials:

• Consent verified — a valid written-consent record exists for this exact number.
• Number scrubbed — checked against federal and applicable state DNC lists and any internal opt-out list.
• Reassignment risk checked — screened against a reassigned-numbers resource where available.
• Time-zone gate — local calling hours confirmed for the consumer's location.
• Disclosure ready — the AI opens by identifying the company and stating a real voice/transfer is available.

If any gate fails, the lead routes to a compliant channel (email, or a human callback within legal hours) instead of an automated call.

What your AI calling agent must say and do on the call

A compliant solar AI call identifies the seller, discloses automated contact, and offers an immediate opt-out. The agent's script and behavior are as important as the consent that authorized the dial.

Minimum on-call requirements:

• Identify the company by name at the start, plus a callback number or address.
• Disclose the automated nature where required, and never misrepresent the AI as a specific human employee.
• Honor opt-outs instantly — if the homeowner says "stop calling," the number is suppressed across every list in real time.
• Log everything — recording, transcript, and outcome tied to the consent record and timestamp.
• Warm-transfer to a licensed human for anything resembling a binding quote or contract, since solar sales often require state-licensed reps.

The AI agent's job in solar is qualification and speed: confirm homeownership, roof/utility basics, and interest, then transfer a warm, consented prospect to a human closer. Keeping the AI on the qualification side of the line — and the human on the sales/contract side — reduces both compliance and licensing exposure.

Compliance requirements at a glance

The table below maps common obligations. Rules and enforcement change frequently — treat this as a checklist to verify with counsel, not a legal determination.

Requirement	Federal TCPA	State mini-TCPA (varies)	Best for AI solar callers
Prior express written consent	Required for AI-voice marketing to cell numbers	Often required; some stricter	Capture named-seller, one-to-one consent with timestamp + IP
Artificial-voice disclosure	Yes — AI voice = "artificial" (FCC 2024)	May add specific wording	Disclose company + automated contact in opening line
Calling hours	8 a.m.–9 p.m. local (telemarketing)	Some narrower windows	Geolocate lead; gate to strictest applicable window
Do-not-call scrubbing	National DNC + internal list	State DNC lists in some states	Scrub against all applicable lists before every dial
Opt-out handling	Must honor promptly	Some require immediate	Real-time suppression across all lists mid-call
Recordkeeping	Retain consent proof	Varies; some require more	Store recording, transcript, consent artifact together
Private right of action	$500–$1,500 per violation	Yes in mini-TCPA states	Document the full consent-to-call chain per lead

Limitations: this table is a general planning aid. Statutory citations, calling windows, and enforcement posture differ by state and change over time — confirm each jurisdiction before dialing.

Build a defensible audit trail — because your records are your defense

In a TCPA dispute, the burden of proving consent falls on the caller, so your recordkeeping is your legal shield. A solar program that can produce the form language, timestamp, IP, and full call recording for any lead is in a fundamentally stronger position than one relying on a spreadsheet.

Retain, per lead:

• The consent artifact — exact form text, checkbox state, URL, timestamp, and IP address.
• The scrub results — proof the number was checked against DNC and reassignment data before the call.
• The call record — recording, transcript, AI summary, and disposition.
• The opt-out log — when and how the consumer was suppressed, if applicable.

This is where a calling platform with an integrated CRM earns its keep. When every recording and transcript lives next to the consent record automatically, you don't reconstruct a defense — you export it. To ground the speed side of this in fundamentals, review what speed to lead means and how sub-minute response changes solar close rates.

The takeaway: compliant AI calling in solar is not about calling less — it's about proving every fast call was authorized.