In this article
Start the buying leads consent review with your contact plan, not a provider badge. Decide who will contact the homeowner, which business they will represent, what channel and technology they will use, and what the message will say. Then request evidence that matches those facts.
Disclosure and legal boundary: theBuildd publishes this guide and sells residential home-improvement leads. This is a procurement checklist, not legal advice or a conclusion about a particular lead, campaign, or provider. Federal and state requirements depend on facts this article cannot determine. Have qualified counsel review your planned outreach and the provider’s records.
Define the contact plan before judging the consent record
The same lead record can raise different questions under different contact plans. A manual call, manual text, call using an automatic telephone dialing system, artificial or prerecorded voice message, and email are not one interchangeable event. The message purpose, number type, relationship between the parties, claimed exemption, and applicable state law may also matter.
Write down the proposed contact plan before asking whether the evidence is adequate:
- the legal and trade name of the seller the person will hear from;
- the person or vendor that will place the call or send the message;
- the telephone number, email address, or other destination to be used;
- the channel, dialing or messaging technology, and any artificial or prerecorded voice;
- whether the message markets a service or serves another documented purpose;
- the script or message version, including how the sender identifies itself;
- the claimed permission, relationship, or exemption and the facts supporting it; and
- the federal and state rules counsel says apply to that exact plan.
Do not ask a provider to certify an undefined campaign. Give counsel the contact plan and the underlying evidence. The opt-in homeowner leads guide owns the broader question of what source and request context to inspect. This page focuses on the records needed to evaluate your planned use.
Ask for the exact page, disclosure, action, and timestamp
A cropped form image is a starting artifact, not a complete event record. It can omit the page version, surrounding language, preselected controls, button text, source URL, and what happened after submission. A generic source label has the same weakness: it names a category without showing the consumer’s experience.
Request a package that lets one provider record connect to one source event:
| Evidence to request | What it can help establish | What it does not prove by itself |
|---|---|---|
| Rendered page or call-flow version | The consumer-facing experience for a defined version | That this person saw that version |
| Exact disclosure and its placement | The words and presentation the provider says applied | That the person noticed, understood, or accepted them |
| Checkbox, button, verbal response, or other action | The action the system was designed to capture | Who acted or whether the record is accurate |
| Event timestamp and time zone | When the recorded action occurred | That later outreach remained appropriate |
| Source URL, publisher, campaign, and version ID | Where the event originated | Every later transfer or use |
| Supplied telephone number and relevant seller name | Values tied to the event | That the number still belongs to the person or authorizes every method |
| Immutable event or lead ID | A way to reconcile the event, delivery, and later request | That the underlying facts meet a legal standard |
| Retention and retrieval terms | Who stores the record and how it can be produced | That storage alone makes the outreach lawful |
Ask how the provider proves that the version shown is the version attached to the delivered record. If the form changes, the old disclosure and interaction data should not be overwritten by the new page. Use the sample contractor lead checklist to inspect the payload, field dictionary, and record linkage without confusing a polished example with proof.
Trace every party that collected, transferred, or used the lead
“Partner generated” does not identify the chain. Name each organization and its role before the lead reaches your office. A typical chain may include the publisher that displayed the form, the operator that captured the event, a lead generator, an aggregator, the provider that sold the record, the seller named to the consumer, and the contractor that will make contact.
For each party, record:
- its legal and consumer-facing name;
- what it displayed, collected, transferred, sold, or used;
- when it received and transferred the record;
- which seller or category it says the request covered;
- whether it can produce the source event and later preference records; and
- which contract allocates recordkeeping, suppression, and response duties.
This map does not determine whether consent transfers or whether a contact is permitted. It prevents an unnamed “source partner” from carrying every assumption. Put the roles, representations, and evidence-access terms into the lead generation contract checklist before purchase.
Match the record to the seller, number, purpose, and contact method
The evidence has to answer the question your outreach creates. It should not be labeled simply “approved” and applied to every future channel, seller, or message.
The current eCFR text for 47 CFR Part 64 defines prior express written consent in Section 64.1200(f)(9) as a signed written agreement that clearly authorizes the seller to deliver or cause delivery of advertising or telemarketing messages using an automatic telephone dialing system or artificial or prerecorded voice to the authorized number. That definition does not say every contractor call requires prior express written consent. Applicability depends on the actual facts and other provisions.
Give counsel a four-part match rather than a conclusion:
| Match | Question to resolve | Evidence to provide |
|---|---|---|
| Seller | Which business was identified and authorized? | Disclosure, seller name, party chain, transfer record |
| Number | Which telephone number did the person provide or authorize? | Submitted value, event ID, timestamp, later number changes |
| Purpose | What messages did the request cover? | Full disclosure, request context, script or message |
| Method | How will contact be initiated and delivered? | Dialing/messaging configuration, voice type, channel, vendor documentation |
A provider certificate may summarize its position, but it is not a substitute for inspectable facts. Ask counsel what the record supports, what remains unknown, and which facts would change the answer.
Review Do Not Call and suppression controls separately
Consent evidence does not replace suppression. National Do Not Call screening, company-specific requests, internal block lists, provider suppression, prior revocations, and state requirements can present separate questions. The reverse is also true: a screening result does not establish the source event or permission for a particular method.
Current FCC Part 64 rules contain company-specific Do Not Call procedures and a National Do Not Call safe-harbor process. Current FTC Telemarketing Sales Rule text contains its own Do Not Call provisions. Coverage, exemptions, relationships, and state overlays require fact-specific review.
Turn that review into operating questions:
- Who owns the master suppression list for your seller names and brands?
- Which National and state lists are checked, by whom, and at what point?
- What registry version, account, date, and campaign evidence is retained?
- How are company-specific requests from calls, texts, email, forms, and staff notes merged?
- Does the provider screen only before sale, or does your system screen again before contact?
- Which claimed exception is being used, and who approved the facts supporting it?
- How quickly do your CRM, dialer, messaging vendor, and provider receive a new block?
The goal is not to collect a “screened” field. It is to know which lists and seller identities were checked, when they were checked, what was excluded, and how a new request changes the contact decision.
Design revocation handling before the first call or text
Every channel that can receive a stop request needs a defined owner and path into suppression. Do not wait for the first complaint to decide whether a reply text, phone statement, voicemail, website request, or staff note counts as an actionable request.
Section 64.1200(a)(10) in the current FCC rule text recognizes multiple reasonable revocation methods. It includes common reply words such as “stop,” “quit,” “end,” “revoke,” “opt out,” “cancel,” and “unsubscribe,” and says covered requests must be honored within a reasonable time not exceeding ten business days. It also says a caller or sender cannot designate one exclusive method for covered requests.
Build the workflow around the request, not the deadline:
- Capture the original words, channel, seller, number, and timestamp.
- Stop new outreach through the receiving system promptly.
- Propagate the request to the CRM, dialer, messaging platform, provider, and other relevant vendors.
- Prevent a later import, duplicate, or new campaign from silently reactivating the record.
- Preserve the propagation log, including failures and corrections.
- Ask counsel how the request affects affiliated entities, unrelated message categories, and state obligations.
Ten business days is a federal outer limit for the covered rule described above, not a service-level target and not a complete statement of every applicable rule.
Contract for record access instead of accepting a certificate
Evidence is useful only if your team can retrieve it when a question arises. The contract should identify the system of record, responsible party, retrieval time, export format, retention period, access controls, and what survives cancellation.
For activity covered by the Telemarketing Sales Rule, 16 CFR 310.5 generally requires specified telemarketing records for five years. Where that rule requires consent, a complete consent record includes the person’s name and telephone number, the request for consent in the manner and format presented, the purpose, a copy of the consent, and the date it was given, plus other information for cited provisions.
That is not a universal declaration that every contractor must keep every lead record for five years. The rule’s coverage and exemptions need counsel review. It does show why a lead buyer should not accept a certificate with no underlying record.
Section 310.5 also allows a seller and telemarketer to allocate recordkeeping responsibility by written agreement. When the agreement assigns it to the telemarketer, the current text says the seller must implement practices and procedures to ensure compliance and retain access to records the telemarketer creates on its behalf.
Use a contract schedule that answers these questions:
| Record term | Written answer to require |
|---|---|
| Contents | Exact fields, page/disclosure version, event, consent, call, suppression, and revocation records retained |
| Custodian | Legal entity and system that hold the original record |
| Retrieval | Request route, response time, format, and named owner |
| Integrity | Versioning, timestamps, change log, and protection against overwriting |
| Retention | Period, start event, legal basis, deletion process, and litigation hold process |
| Access after exit | Export deadline and continued access for open questions or disputes |
| Vendor failure | Backup source and responsibility if a subcontractor closes or loses data |
Have counsel reconcile this schedule with the rules that apply to your business and campaign. A provider’s retention period should not decide your legal obligation by accident.
Remove the vacated one-to-one rule from stale checklists
Some consent checklists still present the FCC’s 2023 one-to-one restriction as current federal law. That description is stale.
In Insurance Marketing Coalition Limited v. FCC, filed January 24, 2025, the Eleventh Circuit vacated Part III.D of the FCC’s 2023 Order and remanded. The opinion describes the vacated provisions as requiring consent for one seller at a time and requiring resulting calls to be logically and topically associated with the interaction that produced consent.
The bounded takeaway is important:
- Remove those vacated Part III.D requirements from templates that present them as an effective federal rule.
- Do not turn the decision into a claim that any broad multi-seller disclosure is lawful.
- Continue reviewing seller identity, message purpose, technology, number, DNC controls, revocation, recordkeeping, and applicable state law.
- Recheck the current rule and legal developments immediately before a campaign launches.
A dated legal checklist is better than a confident one built around a rule that did not take effect as written.
Use this buying leads consent evidence table
Complete this table before approving a provider or contact workflow. “Available on request” is not complete until the owner, format, and retrieval time are named.
| Review item | Evidence requested | Owner and retrieval time | Counsel or operating decision | Stop sign |
|---|---|---|---|---|
| Contact plan | Seller, purpose, channel, technology, number type, script | __________ |
Which rules and review path apply? | The campaign is undefined |
| Source experience | Rendered page/call flow, URL, publisher, campaign, version | __________ |
What did the person encounter? | Only a cropped screenshot exists |
| Disclosure | Exact text, placement, controls, button or verbal prompt | __________ |
Which seller, purpose, and methods are described? | Text cannot be tied to the record |
| Consumer action | Checkbox, click, signature, verbal response, or other event | __________ |
What action was captured? | Provider supplies only a source label |
| Event record | Timestamp, time zone, number, lead ID, version ID | __________ |
Does the event reconcile with delivery? | Versions or timestamps are overwritten |
| Party chain | Publisher, generator, aggregator, provider, seller, buyer | __________ |
Who made and retained each record? | An unnamed partner controls the evidence |
| Method match | Dialer/message configuration and artificial or prerecorded voice use | __________ |
Does evidence match planned outreach? | One label is applied to every method |
| Suppression | National, company-specific, internal, vendor, and state process | __________ |
Which check occurs immediately before contact? | No owner or last-check evidence exists |
| Revocation | Intake channels, propagation map, timestamps, failure handling | __________ |
How does one request stop later outreach? | A vendor or duplicate import can reactivate it |
| Record access | Custodian, contents, export, retention, post-exit access | __________ |
Can the record be produced when needed? | Buyer receives only a certificate |
| Legal review | Named counsel, jurisdiction, review date, assumptions | __________ |
Proceed, change, or stop? | Generic assurance replaces fact review |
Keep qualification off this table. Source evidence and contact permission do not establish that the project fits your scope, that the homeowner can be reached, or that the job will close. Use the qualified lead definition for the separate call your team makes after contact is permitted.
Apply the same questions to theBuildd
theBuildd’s current public offer defines a commercial handoff, not a legal conclusion. It covers residential home-improvement leads in the United States for an agreed trade and ZIP scope. Delivery is by text and email within 10 minutes. There is one buyer per lead through theBuildd, while the homeowner may still seek other quotes independently. Your team contacts and qualifies the homeowner.
Those facts do not state which consent fields appear in a delivered record or prove that a planned campaign satisfies every federal or state requirement. This article does not invent that missing information. Ask theBuildd the same questions you would ask any provider:
- Which source and event records are available for a delivered lead?
- Which seller, disclosure, number, timestamp, and version can be tied to it?
- How can your team retrieve the record if the homeowner questions the contact?
- How are suppression and later preference changes communicated?
- Which contact methods does your counsel approve for your planned workflow?
Read the current plans and terms for the commercial offer. Then contact theBuildd about your trade, ZIP codes, evidence access, and handoff before buying. Results are not guaranteed, and a documented source does not replace your team’s qualification or legal review.
Buy only after the evidence and outreach plan can be reconciled
The go decision is not “the provider says its leads are compliant.” It is that your team and qualified counsel can connect a defined outreach plan to a source event, disclosure, seller, number, purpose, method, suppression process, revocation flow, and retrievable record.
Pause the purchase when a provider cannot name the source-page version, identify every party, tie the record to your seller and planned method, explain suppression ownership, route a stop request, or produce the underlying evidence after the sale. Resolve those gaps in writing before contact begins.
If the evidence package is available, use it to make a bounded decision for the actual campaign. If it is not, a generic certificate should not fill the gaps.