How the RND Shields You From TCPA Liability

Calling a number that was reassigned to a new person can trigger TCPA liability even when you had real permission from the previous owner. The FCC built a safe harbor into the Reassigned Number Database for exactly this case. The deal is straightforward: if you had consent and you checked the Reassigned Number Database (RND) before calling, a single wrong call to a freshly reassigned number will not cost you. This matters most when you are dialing cell phones, where the Cellphone calling rule and Express written consent requirements make every wrong call expensive.

The three things you must prove

To be shielded from liability under the TCPA, a calling organization has to prove three things. First, that it obtained consent from the intended recipient. Second, that it or its authorized agent checked the database before calling to verify the number had not been permanently disconnected or reassigned after the date consent was obtained. Third, that the database returned a query response of no that turned out to be incorrect. In other words, the safe harbor only covers you when the RND itself was wrong, not when you skipped the check.

That third condition is the whole point. The protection is for a database miss, not for sloppy process. So the operational job is to make the check routine: log a consent date for every contact, scrub against the RND before each campaign, and keep the query results. This record-keeping habit mirrors the discipline behind DNC suppression we describe in filtering leads against the federal DNC, and it ties into the broader strategy in our VICIdial compliance overview. Treat your stored RND responses the way you treat a DNC list export: proof you can show later.

Does the safe harbor apply?

flowchart TD
  A[Wrong call to reassigned number] --> B{Had consent from intended recipient?}
  B -->|No| C[No safe harbor]
  B -->|Yes| D{Checked RND after consent date?}
  D -->|No| C
  D -->|Yes| E{RND said not reassigned?}
  E -->|No| C
  E -->|Yes| F[Safe harbor applies]

The diagram walks the three conditions in order. Miss any one of consent, a timely RND check, or a clean no answer from the database, and the safe harbor falls away. Hit all three and that one wrong call is protected. The shield covers a single miss per number, so it rewards a tight, repeatable process rather than a one-time scrub.

VICIfast ships compliant defaults so consent dates and scrub records are part of your normal workflow, not an afterthought. See our pricing to get protected.