For a U.S. business, a useful Do Not Call process connects campaign approval, current suppression data, direct stop requests, vendor execution, and retrievable records. Build those connections before releasing a calling list. This guide provides an operational framework for review; campaign-specific legal advice requires the applicable facts and qualified counsel.
Classify the campaign before choosing a rule
Record the seller, purpose, intended recipients, states involved, calling method, lead source, and vendors. Distinguish a live sales conversation from informational calls, prerecorded or artificial-voice calls, texts, and charitable solicitations. If the purpose or technology changes, review the classification again.
Review both the FTC's Telemarketing Sales Rule and the FCC's TCPA implementing rules, plus applicable state requirements. 16 CFR 310.4 covers the TSR's Do Not Call restrictions and related practices. 47 CFR 64.1200 contains additional delivery and solicitation restrictions, including consent provisions that depend on the call and technology. An exception under one provision should be evaluated against the rest of the applicable framework.
Assign a named reviewer to document the permitted scope, conditions, evidence, and review date. Hold records with unresolved permission, identity, or jurisdiction questions outside the releasable list. A purchased lead or a vendor's “compliant” label still needs supporting evidence.
Make suppression a repeatable process
For covered calling, use authorized National Registry access and apply the seller's own Do Not Call list alongside other applicable restrictions. The TSR's safe-harbor process includes a registry version obtained no more than 31 days before a call, written procedures, training, and monitoring. These are conditions of that provision, not a promise that list matching alone satisfies every obligation. A direct request to stop calling has its own effect under the rule’s entity-specific restriction.
The following is a proposed operating sequence. Configure the exact release rules and deadlines with your reviewer, then test the implementation.
Scroll sideways for all columns. Keyboard users can focus the table and use the arrow keys.
| Stage | Record | Check before release |
|---|---|---|
| Intake | Lead source, seller, campaign, normalized number, evidence reference. | Missing or ambiguous records are held. |
| Suppression | Applicable lists, versions, query time, direct stop requests. | Known excluded test records stay excluded. |
| Decision | Rule version, reviewer, reason, and disposition. | Every released row has a traceable decision. |
| Vendor handoff | Export version, recipient, receipt, replacement/cancellation status. | The vendor uses the intended current list. |
| After calling | Outcomes, new requests, complaints, and investigation notes. | Changes reach every affected calling queue. |
Use restricted access for phone numbers and permission evidence. Preserve a reliable identity mapping so formatting changes do not let an excluded number reappear as a different row. Registry information belongs in its authorized compliance use, not a prospecting dataset.
Trace a stop request across every vendor
Give agents a clear way to accept a stop request and record its scope, time, seller, and number. Establish a process for removing affected records from scheduled lists and queued jobs, distributing the change, and receiving acknowledgments. A request should survive an app restart, a fresh lead import, and a handoff to another calling vendor.
Investigate any failure at its boundary: intake, storage, synchronization, export, vendor import, or dialing queue. Assign an owner and verify the correction through the full path. Configure prompt handling under the applicable legal deadlines rather than treating an internal batch schedule as permission to delay.
Keep records with the correct retention trigger
The current 16 CFR 310.5 recordkeeping rule generally requires covered records for five years from production unless otherwise specified. Certain materials, including scripts and provider contracts, have different retention-start triggers. The rule also specifies call-detail fields, consent and stop-request evidence, registry-access records, and formats, including UTC for covered time records. Apply the complete rule and its exceptions to your activity.
The FTC's 2024 recordkeeping update explains the change. Use the current regulation when older summaries differ. Where responsibilities are allocated by written agreement, verify both the allocation and the seller's required oversight and access; outsourcing should leave the records retrievable.
Create a retention schedule by record class, trigger, owner, location, and access procedure. Test retrieval of one campaign's source evidence, list versions, stop requests, and call results. Resolve missing fields before scaling the campaign. Counsel should address any additional state rules, litigation holds, or other retention duties.
The campaign-review worksheet supports that discussion; it is an original planning aid, not an exhaustive compliance form. For the broader enforcement context, see Do Not Call enforcement. For inbound routing, see business call routing.