Reassigned Numbers Database Checks: How to Screen Aged Leads Before Calling

Before reactivating an older lead, verify the evidence connecting that person to the phone number and review whether the planned contact is permitted. A Reassigned Numbers Database check can help identify a permanent disconnection after a relevant reference date. It belongs within a broader review of contact information, consent records, and suppression requirements.

The practical starting point is simple: locate the number, establish a defensible reference date, query the appropriate database, and keep the result attached to the campaign record. Do not interpret a clean result as permission to call.

Why an old lead needs a fresh review

A CRM can preserve a phone number long after the relationship behind it has changed. A record may still contain a person's name, an old inquiry, and a number that now belongs to someone else. Contacting that number can reach an unintended recipient.

The FCC established the Reassigned Numbers Database, or RND, to address unwanted calls associated with reassigned numbers. It also created a limited safe harbor for qualifying callers who rely on erroneous database information. This protection has conditions; it is not general immunity for a campaign. FCC Reassigned Numbers Order

For an operations team, the useful goal is a repeatable review that prevents stale associations from passing through unnoticed. Start with the oldest records and any segment showing wrong-person outcomes, while applying the same documented eligibility standards to every campaign.

Understand what the RND answers

An RND query uses a telephone number and a reference date. The administrator calls this the date of consent, but its guidance also permits a past date on which the caller could reasonably be certain the intended consumer remained reachable at that number, such as a documented conversation. Using a recent date without supporting evidence would defeat the purpose of the check. Official RND FAQ

The response concerns permanent-disconnection information relative to that date. It does not supply the current subscriber's name or independently establish the scope of consent.

The three response categories require different treatment:

• Yes: The database identifies a permanent disconnection on or after the submitted date.
• No: The result indicates no permanent disconnection in the relevant interval under the database's rules.
• No Data: The database cannot provide the relevant determination. It is not an affirmative clearance.

The FCC explains that Yes and No Data do not qualify for the described safe harbor. A No response may support eligibility when the other conditions are met. FCC guidance on RND responses

Build a review process before the upload

The following is a recommended operating framework, not a legal determination for any particular campaign.

1. Inventory the evidence

Keep separate fields for the original acquisition date, consent evidence, last verified contact, and proposed RND reference date. They may differ. Document why the selected date is appropriate rather than silently substituting the most recent CRM edit.

Identify missing evidence before buying more screening. An upload containing phone numbers alone may not support the query your team actually needs.

2. Preserve the original record

Store original source values and record identifiers. Normalize numbers in a separate processing field, flag malformed input, and identify duplicates without erasing their histories.

Two records can share a number while carrying different reference dates or client relationships. Establish which record is being evaluated and why. Do not allow deduplication to discard evidence needed for the decision.

3. Confirm the service and responsibilities

Ask whether a provider queries the official RND on your behalf or returns a different commercial signal. Request sample results, error definitions, evidence exports, and the terms governing its role.

The FCC clarifies that a duly authorized agent can query for a caller. The caller remains responsible for proving the relevant database query and authorization if relying on the safe harbor. Build those records into the agreement and implementation. FCC guidance on authorized agents

4. Route results to explicit decisions

As a conservative operating recommendation, hold Yes results from the proposed campaign pending review of the person-number association and contact basis. Place No Data, missing dates, and processing errors in a review queue rather than treating them as passing results.

For No results, continue through the remaining checks. Record the decision, reviewer or rule version, and time of release. Use descriptive statuses such as “RND check returned No” rather than an unsupported label such as “fully compliant.”

5. Reconcile before dialing

Compare the final campaign file with the reviewed records. Check that suppressions, holds, and late-arriving opt-outs were carried forward. A sound screening decision has little value if an earlier export is the file that reaches the dialer.

Keep DNC and consent controls separate

RND screening addresses a particular uncertainty about an existing number relationship. National and company-specific Do Not Call requirements, permission for the proposed contact, and other applicable rules require separate evaluation. FTC guidance also notes that its Telemarketing Sales Rule does not preempt state law. FTC compliance guidance

Optional litigator screening should likewise remain a distinct risk signal. It cannot establish consent or replace required suppression and compliance controls. Have counsel determine the requirements for the audience, jurisdiction, technology, and purpose of the campaign.

Keep an evidence package your team can retrieve

A practical internal record should include the submitted number, selected reference date and its basis, query timestamp, returned result, relevant provider identifiers, and the eventual campaign decision. Preserve supporting authorization when an agent performs the query.

Set access and retention rules with your privacy and legal teams. Store identifiable evidence securely; a public research article does not need individual phone numbers, names, or consent documents.

For quality reporting, aggregate results by a clearly defined lead-age band. State the sample size and distinguish disconnect responses, unknowns, and processing failures. Do not describe the Yes-response percentage as a confirmed current-reassignment rate or extrapolate it to the entire market.

Aged lead screening checklist

• Establish the intended campaign and applicable eligibility rules.
• Locate the original contact and consent evidence.
• Document the reference date and its basis.
• Confirm whether the official RND is being queried.
• Preserve query results and agent authorization where relevant.
• Hold unresolved results for review.
• Apply other permission and suppression controls.
• Verify that the dialer receives the final reviewed file.

Frequently asked questions

Is using the RND mandatory?

The official administrator states that RND use is voluntary. Its usefulness and potential safe harbor do not remove other calling obligations. Official RND FAQ

Does No mean the person consented?

No. Evaluate consent evidence separately. The response addresses the database query, not every requirement governing the intended call.

Can I use today's date for every old record?

Do not invent a recent reference date to obtain a favorable response. Select a date supported by the relevant contact evidence and the database's guidance.

How often should I check?

Design the workflow around campaign timing and current database information. If relying on the safe harbor, review its most-recent-update requirement with counsel rather than assuming one historical query covers all future calls. FCC agent guidance

Make the review reproducible

The strongest aged-lead process lets another reviewer reconstruct the decision. Preserve what you knew, when you checked it, and how the result affected the campaign. That discipline makes screening operationally useful and makes weak assumptions easier to catch before dialing.

This article provides general operational information, not legal advice.