Lead Consent Language

Last updated: April 17, 2026

This page publishes the current draft consumer-consent language SolarCalc intends to use if and when a future solar lead handoff or quote-request workflow is launched. It exists for internal implementation clarity and external partner review. In particular, solar marketplace partners such as EnergySage and SolarReviews often require the publisher to show the exact disclosure and consent language that will sit next to a submission button before they approve an integration.

The public educational calculator does not currently require a lead submission to use the estimate tool. This page is therefore a publication of planned compliance copy, not a statement that a live lead form already exists. If a lead flow is introduced later, the final implementation must display the consent language in a clear and conspicuous way near the submit action and must preserve the associated consent record.

Current Draft TCPA / Marketing Contact Consent Block

TCPA lead consent language (review draft): By clicking "Get My Solar Matches" or any substantially similar submit button, I expressly consent to receive marketing and informational calls and text messages, including by use of an automatic telephone dialing system, artificial voice, prerecorded voice, or automated SMS technology, from Life of a Bit, EnergySage, SolarReviews, and their participating solar installers, dealers, and service providers at the phone number I typed into the form, even if that number is on a federal, state, or internal Do Not Call list. I understand that my information may be shared with EnergySage, SolarReviews, and licensed solar installers so they can contact me about solar quotes, financing, installation, batteries, and related home-electrification services. Consent is not a condition of purchase and is not required to receive solar estimates from other sources. Message frequency may vary. Message and data rates may apply. I can opt out of text messages at any time by replying STOP, and I can request no further calls by telling the caller or emailing contact@lifeofabit.com.

  • Implementation requirement: store the exact consent text shown at submit time.
  • Implementation requirement: store the user's typed phone number as part of the consent record.
  • Implementation requirement: store timestamp, IP or request metadata, page URL, and submit button label/version.
  • Implementation requirement: do not precheck the consent box if a checkbox is used in Phase 2.

Why This Copy Exists

Solar leads are often followed up by phone and SMS. That creates Telephone Consumer Protection Act (TCPA) risk if consent language is vague, buried, prechecked, missing network names, or disconnected from the actual button the user clicked. This draft is meant to make the expectations explicit. It identifies the partner networks by name, makes the marketing-contact nature of the consent plain, states that automated calls or texts may be used, includes an opt-out method for texts, and states that consent is not required to obtain estimates from other sources.

That last point matters. A user should be able to understand that they are choosing a convenience channel for quotes, not surrendering their only route to information. The copy is built to say that directly instead of hiding it in dense boilerplate.

Implementation Requirements for Phase 2

Important Note

This page is operational documentation and compliance-oriented publishing, not legal advice. Before launch, final form behavior and recordkeeping should be reviewed against the actual partner requirements, the specific form UX, and applicable law in the jurisdictions where the workflow will run.