Your Internal Do Not Call List: What It Is and Why It's Required
The National Do Not Call Registry is a list of people who told the government they don't want telemarketing calls. Your internal do-not-call list is the list of people who told you. The second one is smaller, much easier to get wrong, and generates a surprising share of claims.
What it is
An internal do-not-call list — sometimes called a company-specific DNC list — is a record of everyone who has asked your business directly to stop calling them. Maintaining one isn't optional or a nice-to-have: it's a requirement for organisations engaged in telemarketing, and it applies independently of the federal registry.
Critically, someone can be absent from the national registry and still be on your internal list. The registry says nothing about a request made directly to you, and honouring that request is entirely your responsibility.
What it has to do
- Capture the request whenever and however it arrives. On a call, by email, through a web form, to a receptionist, to a salesperson in the field. There's no requirement that a consumer phrase it in a particular way or route it to a particular department.
- Take effect promptly. Rules allow a short processing window, not an open-ended one, and "we'll pick it up in the next data refresh" is not a defence if that refresh is monthly.
- Persist for years. Internal do-not-call requests must be honoured for a long period — in the region of five years — and in practice most businesses treat them as permanent, because there is rarely a good commercial reason to start calling someone again who asked you to stop.
- Cover the whole organisation. A request made to one division generally can't be ignored by another operating under the same brand.
- Be written down as a policy. You're expected to have a written procedure and to have trained people on it, not just a list that exists somewhere.
How it actually breaks
The failures are almost always operational rather than deliberate:
- The request goes into one system. An agent marks the contact in the CRM, but the dialer pulls from a separate export that doesn't inherit it.
- The number exists more than once. The same person appears as three records across two sources, and only one gets suppressed.
- A new list reintroduces them. A purchased list six months later contains the same number, nobody cross-checks against internal suppression, and the person who opted out gets called again — which is exactly the fact pattern that turns an annoyed consumer into a plaintiff.
- Nobody recognised it as a request. "Take me off your list," "stop calling me," and "I'm not interested, don't call back" are all opt-outs. Staff need to know that.
Getting it right
- Suppress on the number, not the record. Match every dial against the suppression list at dial time, so duplicate records can't route around it.
- Apply it to every new list before the campaign, the same way you'd apply a DNC scrub.
- Make it easy to add to. If logging an opt-out is slower than ignoring it, some will get ignored.
- Never delete entries. Ageing them out reintroduces exactly the people most likely to complain.
- Keep the dates. Being able to show when a request arrived and when suppression took effect is the evidence that matters later.
Where it fits with scrubbing
Think of it as three layers before a campaign runs: the federal registry, any applicable state registry, and your own internal list. The first two you can scrub against with a service. The third is yours alone, and no external provider can maintain it for you, because only you know who asked you to stop.
Carrier Fence covers the registry layers along with litigator and honeypot checks — 500 free coins to start. For the mechanics of handling opt-outs as they come in, see handling opt-out requests correctly.
General information, not legal advice. Specific requirements depend on your business and jurisdiction.