A callable record needs more than a phone number.

Identify the campaign purpose, responsible business and person authorized to release the list. Keep the source, relevant permission evidence, suppression review and calling-window decision accessible to that person. A list supplier's label or a completed CSV import is not the release decision.

Give operators a clear hold-and-escalate path. They should not have to decide during a live session whether an unknown time zone, conflicting status or missing permission record can be ignored. Resolve those cases before the record becomes available for calling.

The federal calling-time provision in 16 CFR 310.4(c) addresses 8 a.m. to 9 p.m. at the called person's location, absent prior consent. That provision is not a complete answer for every state, industry or campaign. Have the responsible reviewer establish the applicable window.

As a time-conversion example, 7:45 p.m. Eastern is ordinarily 4:45 p.m. Pacific. It is not 10:45 p.m. Pacific. The arithmetic does not establish where a person currently is or whether the call is eligible. A phone's area code alone may be insufficient location evidence.

Use the approved location information and configuration. When location is unresolved, hold the record for review instead of assuming that the office's local time or the number's area code makes the attempt acceptable.

The customer's federal-registry scrub and any additional applicable review occur as part of list eligibility. Internal DNC records what the business knows about a person's stop request. Neither replaces the other.

When the person asks not to be called, acknowledge the request and use the supported Do Not Call outcome on the correct record. Do not store an explicit stop only as an ordinary callback note. The business must also coordinate that decision across other systems or campaigns it operates; this guide does not promise an automatic cross-CRM synchronization.

Read the internal DNC policy when designing imports and handoffs. Reimporting a duplicate must not be used to disregard a known suppression decision.

1. Confirm the source and the campaign to which the records belong.
2. Review the required eligibility and registry evidence under the approved policy.
3. Reconcile known stop requests, duplicates and changed contact information.
4. Check the location information and supported quiet-hours configuration.
5. Set the approved attempt cap. A cap is a maximum, not a target or permission to call.
6. Use permitted test records to inspect an eligible case and a blocked case, then preserve the result.
7. Have the responsible owner release the reviewed list and record unresolved exceptions as holds.

A test that blocks every record does not establish that the eligibility logic is correct. Pair a blocked test with an authorized eligible test so a general calling failure is not mistaken for a working safeguard.

Unknown location: hold the record until the approved process resolves it. Wrong number: record the mismatch and prevent the affected contact from continuing under an incorrect identity while the data is reviewed. New stop request: update the supported suppression record and notify the responsible owner of other affected workflows.

A callback task outside the current policy: do not treat the task as an override. Reconcile it with the person's actual request and present eligibility. Conflicting duplicates: do not choose the more permissive version simply because it can be dialed.

The released list should have an owner, an identifiable source, a documented policy decision and no unresolved records silently mixed into the calling queue. The operator should know how to stop, record an outcome and escalate a conflict.

Retain the permitted test references and observed behavior. If an ineligible contact reaches the calling workflow, pause the affected work and report the record and configuration. Do not repeatedly contact a real person to reproduce a failure.

The official rule link above was checked September 26, 2026. Review current requirements when making campaign decisions. Product configuration is an operational control, not a substitute for that review.