Regulatory & ComplianceCompliance

NDNC Registry Scrubbing

Build a layered suppression process for registry, internal, consent, and campaign eligibility checks.

10 min readUpdated 25 Sept 20264 guides in this section

Registry scrubbing is one layer of dialing eligibility. A production system also needs internal suppression, consent and contact-purpose rules, campaign controls, normalization, and an auditable decision for every attempted number.

Suppression layers

  1. Normalize the number to a stable dialing format.
  2. Reject invalid, unsupported, or incomplete destination numbers.
  3. Check the current applicable registry or provider suppression source.
  4. Check internal do-not-call and complaint lists.
  5. Confirm the contact relationship, consent, and approved purpose for the campaign.
  6. Apply schedule, concurrency, and campaign-level eligibility rules.
  7. Record the decision and source version used for the call attempt.

Dialing eligibility result

typescript
type DialDecision =
  | { allowed: true; reasons: string[]; sourceVersion: string }
  | { allowed: false; reason: string; sourceVersion: string };

function evaluateNumber(
  number: string,
  registryResult: RegistryResult,
  internalResult: SuppressionResult,
  campaign: Campaign
): DialDecision {
  if (!registryResult.eligible) {
    return { allowed: false, reason: 'registry', sourceVersion: registryResult.version };
  }

  if (!internalResult.eligible) {
    return { allowed: false, reason: 'internal', sourceVersion: internalResult.version };
  }

  if (!campaign.isWithinCallingWindow(new Date())) {
    return { allowed: false, reason: 'calling_window', sourceVersion: 'current' };
  }

  return {
    allowed: true,
    reasons: ['registry_clear', 'internal_clear', 'window_valid'],
    sourceVersion: registryResult.version
  };
}

Operational controls

ControlPurpose
Global emergency disableStop all affected outbound campaigns immediately
Campaign allowlistLimit a new deployment to approved test destinations
Negative cacheAvoid repeated attempts for known suppressed numbers until refresh
Registry freshness monitoringDetect stale or unavailable source data
Decision auditExplain why a number was allowed or blocked
Complaint escalationAdd a number and related records to internal suppression

Failure policy

If a required eligibility source is unavailable or stale beyond the approved threshold, default to not dialing and alert the compliance owner. Avoid silently treating unknown eligibility as permission.

Need implementation help?

Search the help center or talk with the OP26X telephony team.