Every outbound solar floor eventually learns the same thing: the expensive compliance failures are not exotic. They are a list that got scrubbed before the phones were appended, a rep dialing a 9:30pm homeowner because the area code said otherwise, or a number that came back on a fresh purchase three months after someone asked to be left alone. All three are workflow problems, and all three are fixable.
This page describes operational practice, not legal advice. Rules change and state law varies — put your specific dialing setup in front of compliance counsel and treat their answer as authoritative over anything here.
The four lists every floor keeps
Compliance on an outbound floor is not one list, it is four, and they fail in different ways.
- The National Do Not Call Registry. Federal, run by the FTC, and the one everybody knows about. Access is by area code through your registered organization.
- State registries. Several states run their own and some impose stricter calling rules than the federal baseline. If you dial nationally you inherit the strictest rule that applies to each call, not the average.
- Your internal do-not-call list. Everyone who has ever asked your company to stop. This obligation is yours alone and it does not reset when you change data vendors.
- Known-litigator and complaint lists. Commercial products, not a legal requirement. Floors that dial at volume use them because a small population of serial plaintiffs generates a disproportionate share of demand letters.
The scrub happens after the append, not before
This is the single most common ordering mistake. A team buys a list of addresses, scrubs it, then sends it out for phone append — and dials numbers that were never checked against anything, because the numbers did not exist yet when the scrub ran.
The list you scrub has to be the list you dial. Append first, scrub second, dial third, and re-scrub anything that has been sitting. If you are running bulk skip tracing on any cadence, build the scrub into the delivery step rather than leaving it as something a manager remembers to do.
Calling windows run on the homeowner’s clock
The federal baseline restricts telemarketing calls to between 8am and 9pm in the called party’s local time, and several states narrow that further. The operational trap is how floors determine local time: they use the area code.
Area codes stopped being a location signal when numbers became portable. A mobile with a 917 prefix can belong to someone who moved to Phoenix six years ago, and the phone kept the number. If you are calling homeowners about their house, you already know where the house is — derive the calling window from the property address, not from the prefix. Floors that get this wrong tend to discover it in the evening block, which is exactly the block they least want to lose.
Consent and the established business relationship
Registry listing is not absolute. The Telemarketing Sales Rule recognizes an established business relationship — broadly, a window following a purchase or payment, and a shorter one following the consumer’s own inquiry or application — and separately recognizes express written consent. Both are real and both are narrower than sales teams assume.
Two practical consequences. First, an EBR belongs to your company, not to a list you bought: a lead who filled out a form on someone else’s site did not inquire with you. Second, consent has to be documented in a way you can produce later, which means capturing what the person saw and agreed to, not just a checkbox state in a CRM.
The internal list is the one that gets you
Federal scrubbing is a solved, purchasable problem. Internal suppression is where floors actually fail, because it is the only list nobody else maintains for you. The failure looks like this: a homeowner asks a rep to stop calling in March, the rep marks it, and in June the team buys a fresh list for the same county that contains the same household — and nothing in the new file knows about March.
The fix is to treat suppression as a permanent property of your organization rather than a property of a list. Every inbound file gets filtered against your cumulative internal list before it reaches a dialer, and that list only ever grows. If you dedupe against prior deliveries anyway — and you should, for cost reasons alone — the suppression pass belongs in the same step.
What to log
Whatever your process is, the part that matters under scrutiny is whether you can show it ran. At minimum, keep the date each list was scrubbed and against what, the internal suppression list with the date and source of every entry, the consent record where you are relying on consent, and enough dialer history to reconstruct when a specific number was called and by whom. Retention periods are set by rule — the TSR’s five-year record requirement is the usual floor — so confirm the applicable ones rather than picking a duration that feels safe.
Where the list itself is a compliance question
There is a quieter failure mode upstream of all of this. If the phone on a record does not actually belong to the homeowner, you are not making a marginally less efficient call — you are cold-calling a stranger who has no relationship with you at all, and who is far more likely to complain about it.
That makes match quality a compliance input, not just a performance one. A list appended to “whoever last lived at this address” behaves very differently from one matched to the name on title, particularly across rentals, recent sales, and homes held in trusts. Our accuracy guide covers why advertised match rates do not tell you which of the two you bought, and the skip tracing software comparison covers who does which.
Disclosure: Scout Data sells homeowner contact data, so treat this section as a maker’s pitch. Our Atlas product matches phones to the owner on title by name, scrubs against do-not-call registries before a list is delivered rather than after, and replaces numbers that stop working. The same workflow is described from the sourcing side in our skip tracing guide for solar and roofing teams. None of that removes your own obligations — an internal suppression list, consent records, and calling windows stay yours no matter who supplies the data.
Frequently asked questions
How often do you have to scrub against the National Do Not Call Registry?
The FTC’s Telemarketing Sales Rule ties its safe harbor to having accessed the registry within 31 days of the call. Most floors treat that as a ceiling rather than a target and scrub far more often — monthly is the rule, but a list that sat in a queue for three weeks before anyone dialed it gets scrubbed again on the way out. Confirm the current requirement and how it applies to your setup with counsel.
Does a Do Not Call scrub cover cell phones?
Registry scrubbing and wireless rules are two different problems that people routinely collapse into one. A number can be absent from the registry and still be a mobile that the TCPA restricts you from reaching with an autodialer or a prerecorded message absent the required consent. Know which of your numbers are wireless before you decide how they get dialed.
Do we still need an internal do-not-call list if we scrub the federal registry?
Yes. They are independent obligations. Someone who asks your company to stop calling has to be recorded and honored by you even if they never registered federally, and the Telemarketing Sales Rule requires those records be kept for five years. In practice the internal list is the one that causes trouble, because a freshly purchased list will happily reintroduce a number you were already asked to stop dialing.