Do Not Contact List (DNC)

A Do Not Contact (DNC) list records people, addresses, phone numbers or accounts your team must exclude from specified outreach. Each restriction should state its reason and channel scope. A company-wide contact restriction is different from an email unsubscribe, an invalid address or a national Do Not Call registry check.

Use the record to answer a practical question before a rep calls or a campaign sends: Is this particular outreach allowed under our policy and the applicable rules? A restriction should remain effective when a contact moves between campaigns, an agency receives a list or a duplicate record is imported. Do not assume that storing a flag in the CRM enforces it in every connected tool.

Do Not Contact, Do Not Call and unsubscribe are not interchangeable

• Do Not Contact: an internal restriction whose scope you must define. It may cover a person, a specific address or number, or an entire account. A request to stop all outreach should not be reduced to a single-channel unsubscribe.
• Do Not Call: a phone-specific restriction. Distinguish a direct request to your company from a registry-screening result. See the separate Do Not Call List entry.
• Email unsubscribe: a request to stop marketing email, potentially covering all marketing messages from the sender rather than just one campaign. Do not restart email through a different rep, list or sending tool.
• Data-quality suppression: a decision not to use an address or number because it is invalid or otherwise unsuitable. An invalid email address does not tell you what the person requested about phone calls.

The FTC describes the National Do Not Call Registry as a list for personal phone numbers, not business phone or fax lines. It is not a universal list of people who cannot receive any type of contact. A work title alone does not tell you whether a particular number is personal. Keep registry screening and your own contact restrictions distinct; neither replaces a review of the rules applicable to the campaign.

What to record in a suppression list

Recommended operating fields, not a universal legal retention specification:

An operational example: the same person enters another campaign

Illustrative scenario, not a client result: A prospect replies, “Please stop emailing me.” The rep records the request and applies an email restriction under the company's policy. The team removes the person from queued marketing email and checks that other senders and campaigns honor the restriction. When a newly purchased or imported list includes the same address, matching against the suppression record blocks re-enrollment.

If the prospect instead says, “Do not contact me again,” use the broader request when setting scope. Do not switch to a phone call or social message to work around it. If the wording or identity match is unclear, pause the affected outreach and ask the responsible operations or compliance owner to resolve it. A data refresh or job change is not, by itself, a reason to clear an opt-out.

How to enforce DNC across outreach campaigns

1. Capture the request where it arrives. Include replies, unsubscribe actions, call dispositions and manual reports. Preserve the source and scope, not just a tag.
2. Apply the restriction and cancel queued activity. Check active campaigns, scheduled follow-ups and any agency working on your behalf.
3. Check imports and duplicates. Keep restrictions from being overwritten by a blank field, a different campaign or a new data source.
4. Recheck at the action point. As an operating safeguard, check current suppression status before a send or dial, not only when building the list.
5. Handle failures explicitly. If a sync fails or a tool cannot enforce the required scope, pause the affected activity until the gap is resolved.
6. Keep a reviewable history. Record what changed, why it changed and who authorized any later correction. Limit access to suppression data to the people and systems that need it.

What CAN-SPAM requires, and what your workflow should do

The FTC's CAN-SPAM guide says the law covers B2B commercial email and requires honoring opt-out requests within 10 business days. It also says hiring another company to send email does not remove your responsibility. Treat that deadline as a legal limit, not a reason to keep sending while you wait. Our operational recommendation is to suppress affected outreach when the request is received and verify enforcement.

Do not turn an email opt-out rule into a blanket statement about calls, texts, other countries or every kind of message. The FTC's telemarketing guidance also points to FCC rules and state laws. Have the responsible adviser assess the audience, location, channel and method before launch. This entry explains operating practice, not individualized legal advice.

Review enforcement without erasing the restriction

Use test records to check a new import, a duplicate merge, a queued email and an agency handoff. Review missed requests, failed syncs and attempted restricted outreach. Do not describe a clean audit as proof of legal compliance or more booked meetings. For retention and deletion requests, follow an approved privacy policy that addresses what information may be retained to honor restrictions; simply removing an active contact record is not an enforcement design.

For a managed program, bring your existing suppression rules, excluded accounts and tool handoffs to a SalesHive strategy call. Agree on the operating scope before expanding outreach.