The short answer

DNC is the suppression check that must pass before an outbound call is placed. It is not one list but several: the national registry, state registries, and the organisation’s own internal list of people who asked it directly to stop. The internal list is the one that generates most liability, because it is entirely within the caller’s control.

In detail

The layers operate independently. The US national registry covers consumers who have opted out of telemarketing generally. Some states maintain their own registries with different scope. Internal do-not-call lists record people who asked a specific organisation to stop calling, and that request must be honoured regardless of any other consent on file. Litigation-focused lists of known serial plaintiffs are a commercial risk-management addition rather than a legal requirement.

Timing and freshness matter as much as the check itself. Registry data changes, cached results go stale, and a number scrubbed weeks ago may have been added since. A suppression architecture needs a defined maximum age for cached results and a defined behaviour when the scrubbing vendor is unavailable — because the alternative to a decision made in advance is a decision made accidentally at dispatch time.

Reassignment is the failure case teams overlook. Disconnected mobile numbers are reissued to new subscribers, so consent captured from one person can lead to calls to someone who never gave it. Checking a number against reassignment data before calling is the standard defence, and it is separate from the do-not-call check even though both run in the same gate.

The operationally important property is that suppression is checked immediately before dispatch, not when the list was loaded. A campaign built yesterday and run today must re-check, because an opt-out received in between has to take effect.

How Rexa handles it

Rexa runs a pre-dispatch DNC gate that checks the destination against cached results and falls back to a live scrub through DNCScrub when the cache is stale or missing, with a separate reassigned-number check on the same path and number-validity verification through Numverify. Behaviour on vendor error is not left to chance: each workspace sets a dnc_fail_mode that decides whether an unavailable vendor blocks or permits the call.

Compliance reference

Back to the glossary

All 53 glossary terms