The mechanics of do-not-call scrubbing do not change by trade. The federal registry, state registries, your internal list and the calling window work the same way for a roofing floor as for a solar one, and they are covered in full in DNC compliance for outbound solar. Read that first; this page does not repeat it.
What is different is the shape of the work. Roofing and HVAC teams assemble lists under time pressure that solar teams rarely face, and they sit on a customer service history that solar teams mostly do not have. Those two facts break a perfectly ordinary compliance routine in two perfectly specific places.
This page describes operational practice, not legal advice. Storm solicitation, contractor registration and consumer-protection rules vary sharply by state and change after major events. Put your dialling and canvassing programme in front of counsel and treat their answer as authoritative over anything here.
The storm week is where routines fail
A hail event lands on a Sunday. By Tuesday there is a list, by Wednesday there are six extra callers, and by Friday somebody is asking why the dialer is calling a number that was on the internal do-not-call list since March. Nothing unusual happened. The routine simply did not survive being run at four times the speed by people who joined this week.
Four things break, reliably, in that order:
- The scrub gets stale before the list gets worked. A storm list is bought at once and dialled for weeks. The federal safe harbour is tied to having accessed the registry recently, and a list scrubbed on day one and dialled on day thirty may no longer satisfy it. Re-scrub on load, not on purchase.
- The scrub runs before the numbers exist. Storm lists are bought as addresses and appended afterwards, which puts the scrub in exactly the wrong place. Append first, scrub second, dial third.
- Surge staff dial outside the pipeline. Temporary callers get a spreadsheet and a cell phone because setting them up properly takes a day nobody has. Everything on this page is enforced by the pipeline; a spreadsheet is not in the pipeline.
- The list gets reused. A storm file is a snapshot of a moment. Six months later it is a stale list whose suppression state, ownership and phone data have all moved, and it is exactly the file somebody rediscovers in a slow month.
The fix is unglamorous: make the storm response a rehearsed procedure rather than an improvisation. Pre-agree the vendor, pre-agree the pipeline, pre-provision the surge seats, and write down that no list gets dialled that did not come through it. Storm restoration leads covers the sourcing half of the same week.
State rules that only exist after a disaster
This is the part with no solar equivalent. A number of states impose additional obligations specifically on contractors soliciting work after a declared disaster or severe weather event: registration requirements, restrictions on when and how a homeowner may be approached, mandatory contract-cancellation language, and limits on discussing insurance proceeds. Several apply to canvassers as well as callers.
These are consumer-protection and contractor-licensing rules rather than telemarketing rules, which means they live in a different statute, are enforced by a different agency, and will not appear in any compliance product you buy for do-not-call scrubbing. A floor that is fully compliant on the telemarketing side can be entirely offside here.
Because these vary by state and are amended after major events, the only durable practice is to check the specific jurisdiction each time a campaign opens in a new one, rather than to learn the rule once. If you work insurance restoration, roofing insurance supplement basics covers where the claim process intersects with what a rep is allowed to say.
Your service history is a list, and it is the good one
The second structural difference works in your favour. A roofing or HVAC company that has been trading for a decade owns something a solar start-up does not: thousands of households that hired it, paid it, and gave it their phone number in the course of the job.
That is first-party data, it is the highest-yielding list in the building, and the established business relationship exception exists precisely for it. Three qualifications on how far it goes:
- It belongs to the entity that did the work. Buying a competitor’s customer list, or acquiring the competitor, does not obviously transfer their relationship to you. This is a question for counsel before the first dial, not after.
- It is time-bounded. The exception runs from the transaction, and a job from many years ago has aged out of it even though the household still remembers you fondly.
- It never overrides an internal do-not-call request. A past customer who asked to stop being called is suppressed, full stop, and the relationship makes no difference.
The service-versus-sales line is worth drawing explicitly in your scripts. A call that schedules a maintenance visit under an agreement the customer signed is servicing that agreement. A call that opens with maintenance and closes on a system replacement is a sales call that began with a pretext, and the pretext is not a defence. Script them separately, staff them separately if you can, and log which one happened.
The seam between the door and the phone
Roofing and HVAC teams run canvassers and callers against the same neighbourhoods, frequently in the same week. That creates a suppression seam solar floors with a phone-only motion never encounter: a homeowner tells a knocker never to come back, the rep records it in a field app, and the dialer — which has never read that app — calls them on Thursday.
From the homeowner’s point of view they told your company to stop and your company ignored them. From a compliance point of view that is exactly what happened, and the fact that two systems were involved is not interesting to anybody. Both channels have to write into the same file, same day. Building a suppression list covers the schema that makes that possible, including keying on the property so a door refusal and a phone refusal land on the same household.
A short pre-campaign check
| Before the first dial | What you are confirming |
|---|---|
| Numbers exist, then the scrub ran | The file you scrubbed is the file you are dialling, not the address list it came from |
| Internal suppression applied, including field refusals | Both channels are writing to one list and the load read it |
| Calling window derived from the property, not the area code | Ported mobiles do not tell you where the homeowner is |
| State-specific post-disaster rules checked for this county | The obligations that no telemarketing product covers |
| Surge staff on the same dialer as everyone else | Nobody is working a spreadsheet outside the pipeline |
| Line type present on every number | Wireless numbers and automated dialling are governed differently |
The list quality argument, briefly
One upstream point, because it matters more in these trades than in solar. Roofing and HVAC lists are frequently built from storm footprints over address files, which means a large share of the households have never had their ownership checked. Call a rental and you are pitching a roof to a tenant; call a recently sold home on an old file and you are pitching to the seller. Neither is a marginally worse call — both are cold calls to a stranger with no connection to you, and strangers complain.
That makes match quality a compliance input. Skip tracing accuracy covers why advertised match rates do not tell you which kind of list you bought, and how to get roofing leads covers the sourcing decision behind it.
Disclosure: Scout Data is our product and we sell the data these calls run on. Our List Builder matches phones to the owner on title and applies federal do-not-call scrubbing before a list is delivered rather than after — which removes one step from the storm-week scramble and none of your own obligations. The internal list, the state rules and the calling windows stay yours no matter who supplies the records.
Frequently asked questions
Can we call storm-damaged homes without scrubbing, because it is urgent?
Urgency is not an exception. The obligations that apply to a Tuesday in February apply to the week after a hailstorm, and the compressed timeline is the reason storm weeks produce a disproportionate share of compliance failures rather than a reason they are excused. If anything, a list assembled in forty-eight hours deserves more scrutiny than one assembled over a month.
Does our service history give us an established business relationship?
For customers of your own company, within the relevant window, generally yes — that is what the exception is for. Two things narrow it more than contractors expect. It attaches to the legal entity that did the work, so a customer list acquired with another company is a genuinely open question that needs a lawyer rather than an assumption. And it is time-bounded from the transaction, so a decade-old install is not a current relationship.
Is a maintenance reminder call telemarketing?
It depends entirely on what the call does, not on what it is called internally. Scheduling a visit the customer already contracted for is servicing an agreement. The same call that turns into a replacement pitch has become something else partway through, and the fact that it started as service does not travel with it. Teams that script these together should expect them to be treated together.