How to clean a cold calling list before reps dial it
A seven-step routine to clean a cold calling list: duplicates, do-not-call requests, switchboards, time zones and reassigned numbers, with a worked example.
By the DialSavvy team5 min read
On this page
A rep opens Monday’s list at 09:00, dials the first 40 rows, and reaches two switchboards, a duplicate of someone she called on Friday, and a man who asks, for the second time, not to be called again. None of that is a dialing problem. It is a list problem, and it takes about one pass to fix.
Here is the order we would clean a cold calling list in, with a worked example and a disposition list to copy.
Why the order matters
Each step shrinks the list for the next one. Removing duplicates first means you never pay to check the same number twice. Applying your do-not-call list before anything else that touches a person keeps the one step with legal weight from being skipped when the afternoon gets busy.
The seven steps
1. Keep one record per person
Merge rows that share a phone number or an email address. Keep the record with the most recent activity, and carry over any notes. A person who appears three times on a list is a person who may get three calls in a day.
2. Apply your do-not-call list
Remove every number and person on your internal do-not-call list, every time. For telemarketing calls to residential subscribers, the FCC’s rule in 47 CFR 64.1200(d) requires:
- a written policy for keeping the list, and training for the people who call;
- recording a request at the time it is made, and honoring it within 10 business days;
- honoring it for 5 years.
Section 64.1200(e) extends those rules to wireless numbers. Many B2B teams apply the same discipline to every request, including from office lines, because one rule is easier to run than two. Check the scope for your calls with your counsel.
3. Tag each number by type
Label every number as one of: direct line, mobile, switchboard, or unknown. Do not delete switchboards. Put them in a separate, short block whose goal is a direct line or a name, and update the record when you get one.
4. Add the contact’s time zone
Set a time zone on every record from the person’s location, not the area code alone, since mobiles travel with their owners. Calling hours are set in the called person’s local time. Our guides to calling prospects in different time zones and state telemarketing calling hours cover the windows.
5. Rest recent no-answers
Pull anyone called in the last few days with no answer and no reason to try again. Repeated calls to the same person in a short window rarely help the conversation, and they use up each number’s daily calls. Our guide to calls per day per phone number covers the limits.
6. Check numbers that may have been reassigned
Phone numbers get disconnected and handed to new people. The FCC’s Reassigned Numbers Database lets a caller check whether a number may have been reassigned since a date, such as the date you got consent. Facts from the FCC’s page:
| Fact | Detail |
|---|---|
| Live since | 1 Nov 2021, for paid subscribers |
| Size | Over 305.9 million geographic and toll-free numbers, as of 17 Feb 2023 |
| Subscriptions | Six tiers, by query volume, for 1, 3 or 6 months |
| Unused queries | Roll over when you buy a new subscription before the term ends (from 5 Feb 2025) |
| Pricing | Interim usage charges; the most recent revision the FCC lists took effect on 28 Apr 2025 |
The database also carries a safe harbor. Under 64.1200(m), a caller is not liable for a call that needed prior express consent if it queried the database, got a “no” (not disconnected since the consent date), and the answer was wrong. That matters most for consented calls, such as follow-ups to inbound leads. For cold lists, the database is still a quick way to find stale mobile numbers before a rep does.
7. Count what is left
Write down the count after each step. The numbers tell you where your data source is weak, and they help you set a realistic target for the block.
A worked example
This is an example with round numbers, not data from a real list. A team imports 1,000 rows:
| Step | Rows removed or moved | Rows left to dial |
|---|---|---|
| 1. Duplicates merged | 60 removed | 940 |
| 2. Do-not-call list applied | 15 removed | 925 |
| 3. Switchboards tagged | 180 moved to a separate block | 745 |
| 4. Time zones added | 0 removed; 745 now have a zone | 745 |
| 5. Recent no-answers rested | 40 moved to next week | 705 |
| 6. Reassigned-number check on mobiles | 10 removed | 695 |
The rep starts the day with 695 numbers that each reach the right person in their calling hours, plus 180 switchboards with a different goal. The 60 duplicates also say something: the list source needs a fix before next month’s import.
A disposition list to copy
Clean lists stay clean only when reps log what they learn on the call. These outcomes feed straight back into the steps above:
- Do not call: add to the do-not-call list at once (step 2).
- Wrong number: remove the number from the record.
- Not at this company: close the record, and note where the person went if they say.
- Switchboard only: keep the tag, and add the direct line if you got one (step 3).
- Call back at a time: set a task in the person’s time zone (step 4).
- No answer: let the attempt count drive step 5.
Our Salesforce call disposition guide covers how to set these up as picklist values.
How DialSavvy handles this
DialSavvy runs compliance checks before every call: calling hours in the contact’s time zone, and your do-not-call list. Each rep gets a brief before every dial, and AI answer detection labels each answer as a person, voicemail, a phone menu or a call screener, so outcomes are logged without extra clicks. National do-not-call registry checks are coming. The dialer page and the compliance page describe what runs today.
If you want to see this on your own data, book a demo and bring a sample list: we will walk through the checks each row would go through before the first ring.
Sources
- 47 CFR 64.1200, Delivery restrictions, eCFR (ecfr.gov)
- Reassigned Numbers Database, Federal Communications Commission (fcc.gov)
Checked against these sources by the DialSavvy team. How we write. Spotted an error? Email hello@dialsavvy.com.