How do I screen a property-owner call list against Do Not Call and internal suppression lists?

Only businesses that subscribe can see the registry. The FTC's Q&A for telemarketers and sellers says access runs through telemarketing.donotcall.gov, and that every seller needs its own subscription account number, or SAN, separate from any calling vendor it hires. The SAN arrives by email after you register.

Entering that number turns on PropertyRadar's screening. The field sits under the profile icon, in Account Settings, then Telemarketing Settings. You type the SAN with its dashes and choose Update. It has to be on your individual account, because a SAN held at the company level isn't displayed there. PropertyRadar then scrubs every saved list against the registry, whether the list is dynamic, static or imported.

Two filters let you use the result while you're still building the list. Under Owner Details, then Owner Phone, set Primary Contact Phone DNC and Primary Contact Mobile Phone DNC to No. Do this before you buy contact data. PropertyRadar's pricing page charges 8 cents for each phone contact beyond the 250 phones and emails a Solo plan includes each month, so a registered number you filter out first is one you don't pay for.

Both filters read only the first phone number on the primary contact's record. The export has the same shape. It carries four status fields, one each for the first phone and first mobile of the primary and secondary contacts, and it includes only those first numbers. The flags don't establish coverage for an alternate number on the owner profile, a number from an outside skip trace or one the owner gave you directly.

PropertyRadar also doesn't publish the registry version date behind its flags. For calls the registry rules cover, the federal rules tie each call to registry data obtained no more than 31 days earlier, and the record of that access has to be your own. So use the flag to shape the list, and use your own download to date the screen.

Export the list from Connect, then Export to File, with the four phone status fields included. Add a row for every other number you hold on those owners, and note on each row where the number came from. Numbers from an outside skip trace belong here, and so do alternates you bought on the owner profile.

Clean the numbers before you compare them, because both comparisons depend on an exact match. This screen handles US numbers in the North American Numbering Plan. Strip punctuation, spaces and extensions. If a number has eleven digits and starts with 1, drop the 1. Store the result as ten digits of text so a spreadsheet can't reformat it. Anything that still isn't ten digits, an international number included, goes to a separate tab for a person to review.

Then collapse duplicates so each number appears once, and keep every property ID attached to it. An owner with four rentals shows up four times with the same phone. Without the other three IDs, a later stop request gets recorded on one property in PropertyRadar, and the same number can come back through a later export of the other three.

The registry comparison comes next, and it starts with counting area codes. They follow the owners' phones and not the county you searched, so an absentee list from one county includes area codes from wherever those owners live. The FTC's Q&A says data for up to five area codes is free, that files come as flat text or XML sorted by area code, and that you can download once in any 24-hour period. For a few late additions, the registry's Interactive Phone Number Search takes one area code and up to ten numbers at a time. Mark each row Registered or Not registered and write the download date beside it.

Your internal list has to be assembled, because the requests are scattered across the tools your callers use. Merge the numbers marked Do Not Call or Opted Out in PropertyRadar with the DNC list under WAVV Settings. WAVV is the dialer built into PropertyRadar. Add the opt-outs held in any other dialer, CRM or calling vendor, and keep the result as one master file. A request recorded in one system isn't automatically in the others, so a number an owner opted out in one dialer can stay callable in the next until the lists are merged.

Remove every row that matches either list and save what remains as the dial file. Don't make exceptions inside the batch. If you believe a registered number can still be called, on written consent for example, pull it out and have a named person review the seller, the number, the purpose of the call and the channel. That person documents the basis and releases the number in a separate file, so the batch never passes a suppressed number.

Load only the dial file into the dialer. PropertyRadar's phone marketing overview describes a prompt at the start of a WAVV calling session that offers to exclude DNC numbers, and accepting it gives you a second check. If you dial from another tool, import the master suppression file into that dialer before the first call.

You can also keep suppressed owners out of future lists inside PropertyRadar. Put their properties on a static list and add it as an Exclude List criterion on each new search. The criteria glossary says Exclude List accepts static lists and monitored dynamic lists. It works on properties, so the phone match in your file still has to catch an owner who reappears through a different property.

Passing both comparisons clears a number to dial. It doesn't confirm that the number reaches the owner, which is part of what to verify before contacting an off-market owner.

Suppose you export a list of 1,200 absentee owners with first numbers, and alternates from an outside trace bring the file to 2,050 rows. Thirty rows don't resolve to ten digits, and 80 repeat a number already in the file. Of the numbers left, 610 match the registry and 45 match your internal list. Twenty of those 45 are also registered.

The dial file ends up with 1,305 numbers. The 745 removed rows fall into four groups: 30 malformed, 80 duplicate, 610 registry matches and 25 that matched only the internal list. Keep both reasons on the 20 numbers that matched twice. If one of them later comes off the registry, the owner's request to you still stands.

Then count owners as well as numbers. Suppose 190 of the 1,200 have no number left in the dial file. Those owners move to mail, or to the steps for owners with no valid phone.

The FCC bars a "telephone solicitation" to a registered residential number, so coverage depends on what the call is for. 47 CFR 64.1200 defines a solicitation as a call encouraging the purchase or rental of, or investment in, property, goods or services. The FTC's rule defines telemarketing as a plan, program or campaign conducted to induce the purchase of goods or services.

Neither definition names a call that only offers to buy the owner's house. This workflow screens those campaigns anyway. The screen is a file comparison you already know how to run, and a script that adds a listing, a loan or another service changes what the call is for. Read the script before the list is loaded, and settle which rules apply to that campaign then.

Cell numbers get the same registry comparison as landlines, because paragraph (e) of the FCC rule applies the registry provisions to wireless numbers. Passing the screen doesn't settle consent for the calling method. Autodialed calls, prerecorded messages and texts have their own consent requirements in the same section, and a number that clears both comparisons hasn't been checked against them.

Calling hours follow the person who answers. Paragraph (c)(1) bars solicitation calls before 8 a.m. or after 9 p.m. local time at the called party's location. An absentee owner's area code and mailing address don't establish where they are today. Hold a number out of the queue until you've confirmed its time zone or your scheduling procedure has set a calling window for it.

The registry also covers calls made within a single state under the FCC's rules, according to the FTC's Q&A, and state officials enforce it alongside the two agencies. States have their own telemarketing rules as well. List the states your owners' numbers reach before the first session, and check each state's rules against the campaign.

Suppose an owner tells your caller on October 9, 2026 to stop calling. For calls the FCC's rule covers, paragraph (d)(3) requires the number, and the name if the person gave it, to go on your do-not-call list at the time of the request. In WAVV, the Call Outcome dropdown writes the outcome, the status and a note to the Activity panel on the property and owner profiles. That gives you a dated entry made during the call.

Two more changes in PropertyRadar keep the number from being dialed again. Set the phone's status to Do Not Call, and add the number to the DNC List under WAVV Settings. The overview says numbers on that list are excluded from future outbound calls and messages. It doesn't say a status alone blocks a dial, so do both.

Add the number to your master file the same day. Then pull it from every export already sitting in another dialer or with an outside calling team. The FCC rule holds the business the calls are made for liable when someone else keeps the list and fails to honor a request.

The owner's words set how far the request reaches. If they said to stop calling them, without limiting it to one number or one property, suppress their other numbers and properties too. Write the wording of the request in the log so the next person can see why.

The legal deadline is looser than the same day. Where the FCC's rule covers the call, a request has to be honored within a reasonable time that can't exceed ten business days, and paragraph (d)(6) keeps it in force for five years. For this owner that runs through October 9, 2031. Same-day suppression is a policy choice. It's easy when the request and the list live in the same file, and it removes the chance of a second call during those ten days.

16 CFR 310.5 lists the records the FTC's rule requires and sets a default retention of five years. Two of them come out of this process. The registry-access record names the entity that accessed the registry, the access date, the SAN used and the campaign it was for. The record of each do-not-call request holds the person's name, the phone numbers, the seller, the telemarketer that made the call, the request date and what the call was about.

Keep a screening log beside those two. It records the file name, who ran the screen, rows in and out, rows removed by reason, and the registry download date. Combined with call dates from the dialer, it shows that each call fell within 31 days of a download. Keep the review record for any number released by exception, and keep your written do-not-call procedure, which the FCC rule requires you to produce on demand.

A clean file doesn't establish the FTC's safe harbor alone. The Q&A lists registry access within 31 days, with records, as one condition among several. The others include written procedures, trained staff, monitoring and a company-specific do-not-call list. The screening log documents one of those conditions, so file it with the evidence for the rest.

The 31-day window also sets the schedule for repeating the work. If you downloaded registry data on October 5 and the campaign runs past November 5, download again and rerun both comparisons before the next session. Rerun the internal comparison on the morning of every session, because that list changes with each call.