Skip to content

Your Dormant NJ Database Is Not One List — It Is Three: How to Sort Contactable Records from Off-Limits Ones Before a Single Outreach Goes Out

August 17, 2026 written by Fello

Your Dormant NJ Database Is Not One List — It Is Three: How to Sort Contactable Records from Off-Limits Ones Before a Single Outreach Goes Out

Your Dormant NJ Database Is Not One List — It Is Three: How to Sort Contactable Records from Off-Limits Ones Before a Single Outreach Goes Out

TL;DR

  • A dormant New Jersey database is three distinct buckets with completely different outreach rules, not one list you work or avoid.
  • Treating un-consented records the same as consented ones exposes your team to TCPA fines up to $1,500 per text and Do-Not-Call penalties exceeding $50,000.
  • New Jersey law ties your outreach permissions to documented prior express written consent and existing customer status, not just intent.
  • Teams that complete this triage before outreach begins are seeing approximately 4 to 6 additional listing conversations per month from contacts they already owned.

Introduction

Your database has deals in it. But nothing happens because no one can answer the one question that stops everything: which of these contacts can we actually reach?

The real issue is rarely the contacts themselves. One large team generated 188 listing appointments from an existing 200,000-contact database without buying a single new lead. For New Jersey teams, there is also a compliance layer on top of that operational problem. NJ has its own telemarketing statute stacked on top of federal TCPA rules, and when no one knows which records carry valid consent, the safe move feels like touching nothing. That is not safety. It is revenue loss on a schedule.


Why a Single Flat List Is the Most Dangerous Thing in Your CRM

Most dormant databases were never built with segmentation in mind. Contacts from open houses, web forms, purchased lists, referrals, and past closings all landed in the same folder with no consent tagging and no suppression scrubbing. This is the Lead Trap: treating a solvable database problem as a lead supply problem. The financial stakes justify getting this right: per-text TCPA violations can run $500 to $1,500 per message, with Do-Not-Call fines exceeding $50,000 for a single campaign.


New Jersey's telemarketing statute at N.J.S.A. 56:8-120 carves out two categories that get different treatment: contacts who made an express written request for communication, and existing customers who have opted in. Everything outside those two categories is an unsolicited prospect. NAR reinforces this from a real estate perspective: prior express written consent is the gold standard, and scrubbing against the National Do-Not-Call Registry is a standard of care for any outreach.


These are the records your team can work right now, but "documented" means more than most CRMs enforce by default. N.J.A.C. 13:45D-4.2 requires consent to be clear, conspicuous, and affirmative. Pre-checked boxes and passive list enrollment do not count.

A Bucket One record needs a consent date and timestamp, the method consent was captured, a source URL or form name, the specific phone number consented to, and no subsequent opt-out on record. All five fields must be present. If they are, this contact is ready to work immediately.


These contacts are off-limits until you fix the documentation. This is where most dormant databases are heaviest: real relationships, genuine opportunities, but no consent record to act on. Run a re-consent sequence through channels that do not require prior consent, typically email or direct mail. Reference the prior relationship, explain what they are opting into, and require an explicit affirmative action. When a contact responds, document the timestamp, method, and specific phone number, and they move to Bucket One. Until then, no phone or text outreach goes out.


Bucket Three: DNC-Flagged and State Suppression Records

These contacts are off-limits for telemarketing. Bucket Three includes anyone on the National Do-Not-Call Registry, the New Jersey state suppression list, your internal do-not-contact list, or anyone who previously requested removal. Database records must be re-scrubbed against DNC lists every 31 days to stay compliant. A record that was clean at import may have registered on the DNC list before your campaign launches.


What "Contactable Now" Looks Like in Practice

A Bucket One contact with a validated phone number, clean DNC status, and documented consent on file is what "contactable now" actually means. It is a status earned through a defined verification process, not assumed from import.

This is where Felix becomes relevant. Felix is Fello's AI teammate who runs 1:1 follow-up across text, calls, and email around the clock, never dropping a conversation. Felix only works contacts that have cleared the gates: DNC scrubbing passed, phone validated, consent documented. As Fello puts it: "Without clean data, AI just automates bad data." The sort is the prerequisite, not an optional configuration step.


Maintaining the Three Buckets Over Time

This triage is not a one-time project. New contacts enter your database continuously, existing contacts change phone numbers, and consent can lapse. Monthly DNC re-scrubs every 31 days are the minimum standard. Fello's Living Database runs continuous enrichment, DNC scrubbing, phone validation, and address confirmation as an ongoing condition for every contact.


Frequently Asked Questions

Can I assume consent exists for contacts from a few years ago? No. Under N.J.A.C. 13:45D-4.2, consent must be affirmative and specific. If your CRM does not have a timestamp, consent method, and source URL on file, that record belongs in Bucket Two until re-consent is documented.

Does past client status cover them for all outreach? Existing customer status can support outreach eligibility under N.J.S.A. 56:8-120, but the contact must not be on the DNC list, the relationship must be active or recent, and the outreach must be topically related to that relationship. Document the basis and run the DNC check regardless.

Can Felix reach Bucket Two contacts while re-consent is in progress? No. Felix runs on Active contacts only, which requires DNC scrubbing and phone validation to have cleared. A Bucket Two contact is not eligible for Felix outreach until re-consent is documented and the record is fully validated.


Bottom Line

Sort your dormant NJ database before a single outreach goes out. Bucket One contacts are ready to work now. Bucket Two contacts need a re-consent sequence before any phone or text outreach. Bucket Three is off-limits for telemarketing. Complete the sort, then let Felix run follow-up on every cleared contact. The next deal is already in your database. The sort is what makes it visible.