TL;DR: The do not call safe harbor is not one defense. It is two federal defenses with different condition lists, plus a third that only covers abandoned calls. The FTC’s Telemarketing Sales Rule safe harbor runs six conditions: written procedures, training for your own personnel and any entity assisting in your compliance, a maintained internal do-not-call list, a prevention process built on a registry file obtained no more than 31 days before the call with records documenting that process, monitoring and enforcement of those procedures, and proof the call was an error rather than a failure to capture an opt-out. The FCC version at 47 CFR 64.1200(c)(2)(i) runs five lettered standards, and they are not the same five. It carries no monitoring condition at all, and it adds a purchasing standard that bars any arrangement splitting registry access costs among a telemarketer’s client sellers. The FTC bans that cost-sharing too, but in its registry fee section instead of inside the safe harbor, so failing it costs you something different. Build your program to one list and you can still lose the other. Under 47 CFR 64.1200(d)(3) an internal opt-out is recorded at the time it is made and honored within 10 business days, and when a vendor holds that list you stay liable for any failure to honor it. Under (d)(6) the request binds you for 5 years. Registry access is $85 per area code per year, capped at $23,425, with the first five area codes free, as of November 19, 2026.
Somebody says the list is clean. The registry file came down three weeks ago, the scrub ran, nobody has complained. So you are covered.
Maybe. The scrub is one condition out of six, or one out of five, depending on which regulator is asking. That is the part most compliance write-ups skip. They treat the do not call safe harbor as a single thing you either have or do not have, usually a binder somebody wrote in 2019. It is not a binder and it is not single. Two federal agencies each publish their own safe harbor for registry violations, the condition lists overlap but do not match, and the conditions that go unmet are rarely the scrub.
This is general information about how the provisions are written, not legal advice. Have counsel review your actual program.
What the Do Not Call Safe Harbor Actually Covers
Start with scope, because this is where the word “safe” does the most damage. A safe harbor is not immunity. It is a defense to a specific violation, and each one names the violation it answers.
The FTC safe harbor answers two things: calling a person who already told you not to call, and calling a number on the National Do Not Call Registry. That is it. It does not answer a calling-hours violation. It does not answer a caller ID transmission failure, a misrepresentation, or an unlawful prerecorded message. Those live in different paragraphs of the same rule and carry no equivalent defense.
The FCC safe harbor rule is narrower still. It sits inside the registry paragraph at 47 CFR 64.1200(c)(2) and answers a telephone solicitation to a residential subscriber whose number is on the national registry. Nothing else in that section inherits it.
So what is left uncovered? Consent. If the problem with a call is that you never had the consent the rules required for an automated dial or a prerecorded voice, no registry safe harbor repairs it. You were not wrong about the list. You were wrong about the legal basis for the call, and that is a different argument with no error defense attached. If you are working out which basis applies to a given campaign, start with how the National Do Not Call Registry works and what it does and does not reach.
The FTC Do Not Call Safe Harbor Has Six Conditions
The Telemarketing Sales Rule says a seller or telemarketer will not be liable if it can demonstrate that, as part of its routine business practice, all of the following are true. Read them as a list of six things a regulator can ask you to produce.

- It has established and implemented written procedures to comply with the do-not-call requirements. Note both verbs. Written and implemented.
- It has trained its personnel, and any entity assisting in its compliance, in those procedures.
- It has maintained and recorded a list of telephone numbers it may not contact. This is the internal list, separate from the national registry.
- It uses a process to prevent telemarketing to any number on that internal list or the registry, “employing a version of the ‘do-not-call’ registry obtained from the Commission no more than thirty-one (31) days prior to the date any call is made,” and maintains records documenting the process.
- It monitors and enforces compliance with those written procedures.
- The call was the result of error “and not of failure to obtain any information necessary to comply with a request” not to receive further calls.
Condition four is the one everybody knows, and it is the one every vendor sells against. The 31 day clock has been written about to death, including by us, in detail, in the three separate clocks a DNC scrub actually runs on. Fine. Now look at five and six, which almost nobody writes about.
Condition five asks whether anyone checks. Not whether you wrote a procedure, whether you monitor and enforce the one you wrote. A procedure nobody audits is a document, and the rule distinguishes between the two on purpose. What would you produce if asked? An exception report with names on it, dates, and what happened to the rep who bypassed the suppression step. If the honest answer is that nothing is monitored because nothing has gone wrong yet, the condition is unmet right now, today, with a clean call history.
Condition six is sharper, and it quietly rules out the most common real-world failure. The call has to be an error. It cannot be the downstream consequence of never capturing the opt-out in the first place. A rep hears “take me off your list,” says sure, and moves to the next call without logging anything. Three weeks later the number gets dialed again. Was that an error? The dial was. The cause was a failure to obtain the information needed to honor the request, which condition six names and excludes. You do not get to call it a glitch.
The FCC Safe Harbor Has Five Standards, and They Are Not the Same Five
Here is the finding that changes how you should read your own compliance program, and it is checkable in about four minutes against the two provisions.
The FCC’s version at 47 CFR 64.1200(c)(2)(i) requires that you demonstrate the violation was the result of error and that, as part of routine business practice, you meet five lettered standards: (A) written procedures, (B) training of personnel, (C) recording a list of numbers the seller may not contact, (D) accessing the national database with a registry version obtained no more than 31 days before the call, and (E) purchasing the national database.
Four of those map cleanly onto FTC conditions one through four. Then the lists part ways, in both directions.
The FCC has no monitoring standard. The phrase “monitors and enforces” appears in the FTC safe harbor rule and appears nowhere in the FCC’s section. Its five standards stop at purchasing.
The FCC adds a purchasing standard the FTC safe harbor does not contain. Standard (E) requires that you purchase registry access from the administrator and that you do “not participate in any arrangement to share the cost of accessing the national database, including any arrangement with telemarketers who may not divide the costs to access the national database among various client sellers.”
Read that twice if you use an outside calling vendor, because it describes a normal-sounding commercial arrangement and makes it fatal to the defense.
Does the FTC permit cost-sharing, then? No. It bans it just as plainly, in the section that sets registry access fees: no person may participate in any arrangement to share the cost of accessing the registry, including any arrangement with a telemarketer or service provider that divides costs among that provider’s various clients. Same prohibition, different address, and the address is the point. Under the FCC rule the ban is a condition of the safe harbor, so breaking it takes the defense with it. Under the FTC rule it is a standalone prohibition sitting outside the six conditions, so breaking it is its own violation rather than a forfeiture of the harbor.
One behavior. Two different consequences. That is what you lose by treating the two safe harbors as one rule stated twice.
The practical version: six plus five does not mean eleven things to do. It means a combined list where two items are agency-specific, and a program built to satisfy only the overlap satisfies neither completely. Write the superset. Monitoring and enforcement because the FTC asks for it. Purchasing and no cost-sharing because the FCC conditions its harbor on it, and the FTC prohibits it anyway.
The Safe Harbor Conditions Most Teams Fail Are About Vendor Records
Go back through both lists and mark every clause that reaches past your own payroll. There are more than you would expect.
FTC condition two does not say train your employees. It says train your personnel and any entity assisting in your compliance. Your screening provider assists in your compliance. So does the agency running the dials. Can you produce their training records? Most teams cannot, because they never asked for them, because the contract was signed as a purchase rather than as a compliance dependency.
FTC condition three contemplates the internal list being maintained by “a telemarketer or another person acting on behalf of the seller.” Allowed. Then the FCC closes the loop on what that delegation does to liability, in the internal do-not-call procedures at 47 CFR 64.1200(d)(3): if the requests are recorded or maintained by a party other than the entity on whose behalf the call is made, “the person or entity on whose behalf the call is made will be liable for any failures to honor the do-not-call request.”
You can outsource the list. You cannot outsource the liability. The rule says so in one sentence.
That same paragraph sets the clock everyone gets wrong in the other direction. An internal opt-out must be recorded at the time the request is made, and honored within a reasonable time not exceeding 10 business days. Teams hear “ten business days” and build a ten-day process. Read it again. The recording happens immediately; ten business days is the outer limit on honoring, not a grace period for writing it down. And since the whole thing happens inside systems you control, a fourteen-day sync window between a CRM and a dialer is not a reasonable time, it is a self-inflicted violation with a calendar behind it.
Under 47 CFR 64.1200(d)(6) that request has to be honored for 5 years. Five years is longer than most CRM migrations, most vendor contracts, and most of the people who will be on your team when it matters.
So the vendor questions are not procurement questions. Who holds the internal list? Can they produce a training record? How do they access the registry, and does any part of that access get cost-shared across their book of clients? What does their suppression evidence look like five years out? Ask before the campaign, because every one of those answers is a condition of a defense you are planning to rely on.
The Abandoned Call Safe Harbor Rule Is a Third, Separate Defense
There is a second safe harbor inside the FTC rule, one paragraph below the registry one, and it protects something completely different. It covers abandoned calls, and its conditions are mechanical rather than procedural.

- Abandonment of no more than 3 percent of calls answered by a person, measured over a single calling campaign if it runs under 30 days, or separately over each successive 30-day period.
- Ring for at least 15 seconds or four rings before disconnecting an unanswered call.
- Whenever a sales representative is not available within 2 seconds of the person’s completed greeting, promptly play a recorded message naming the seller and a telephone number.
- Retain records establishing compliance.
Why does this matter in an article about the registry safe harbor rule? Because the two get merged in conversation and they have nothing in common. Writing procedures and training your team earns you nothing here. Your pacing algorithm either kept abandonment under 3 percent across the measuring window or it did not, and the measuring window is per campaign or per 30 days, not an annual average that smooths a brutal week in March.
Which means a team can satisfy the registry safe harbor rule and fail the abandonment one in the same campaign, with the same dialer, on the same afternoon.
What a Do Not Call Safe Harbor Looks Like Inside the Dialer
Be clear about what tooling can and cannot do here, because the vendor claims in this category get loose. No platform grants anybody a safe harbor. There is no setting for it. Of the six FTC conditions, three are organizational: writing the procedures, training the people, and monitoring and enforcing what you wrote. Software does not do those. A person does, and then another person checks.
What the calling system decides is whether the other three conditions produce evidence or just intentions.
Condition three is the internal list. The question is not whether the list exists, it is whether the list the dialer reads at dial time is the same list the rep wrote to at the end of the last call. One list, read at the moment of the dial. If the suppression lives in a CRM field and the dials come off an exported spreadsheet, there are two lists, and the older one is doing the dialing.
Condition four has two halves and teams usually build the first. Prevent the call, and maintain records documenting the process. A screening step that blocks a dial and leaves nothing behind satisfies half of a condition, and the half it skips is the half a regulator reads. The record needs the timestamp, the source of the suppression, and the registry file version it ran against.
Condition six is a capture problem, and it is the one that gets solved on the call itself. The opt-out has to be recorded when the buyer says it, not when somebody gets around to CRM hygiene on Friday. That means a one-action disposition at the end of the call that writes to the suppression list directly.
Kixie’s National DNC integration checks calling lists against the National Do Not Call Registry and applies suppression workflows, and PowerDialer sessions log call outcomes into the CRM automatically rather than depending on a rep to remember. Customers stay responsible for their own calling practices and should get legal guidance for their specific programs. The point of putting suppression and logging in the same system is narrow and worth stating plainly: it makes the evidence a byproduct of the work instead of a separate project nobody staffs.
Then there are the lists the federal registry never touches. Several states run their own, and a national scrub does not reach them, which is its own operational problem covered in the state do not call lists a national scrub misses. Industry rules can bite too, as they do for agents working property owners, where the registry exemptions are unusually specific. We walked that through in the DNC and TCPA rules that decide whether real estate outbound calling is legal.
Do Not Call Safe Harbor FAQs
Is the do not call safe harbor the same under FTC and FCC rules?
No. The FTC safe harbor rule lists six conditions and the FCC version at 47 CFR 64.1200(c)(2)(i) lists five lettered standards. Four overlap. The FTC adds monitoring and enforcement plus an error-not-failure-to-capture requirement. The FCC adds a purchasing standard barring cost-sharing arrangements for registry access. They are commonly described as identical because the subparagraph everyone quotes, the 31 day registry file, genuinely is.
Does the safe harbor protect me if I called someone without consent?
No. Both registry safe harbor rules answer registry and internal-list violations. A consent problem is a different violation with no error defense attached, so a call that needed prior express written consent and did not have it is not rescued by a clean scrub.
How fresh does the registry file have to be?
Both provisions name 31 days before the call is made. That is an outer limit for the defense rather than a recommended cadence, so a campaign running longer than a month needs a refresh schedule rather than a single screening at intake.
If a vendor keeps my internal do not call list, am I still liable?
Yes. Under 47 CFR 64.1200(d)(3), when opt-out requests are recorded or maintained by a party other than the entity on whose behalf the call is made, that entity is liable for any failure to honor the request.
What does registry access cost?
As of November 19, 2026 the annual fee is $85 for each area code of data, up to a maximum of $23,425, and the first five area codes are free. Access runs through the telemarketer portal, which is restricted to organizations complying with the federal telemarketing rules.
How long does an internal do not call request last?
Five years under 47 CFR 64.1200(d)(6), recorded at the time it is made and honored within a reasonable time not exceeding 10 business days under (d)(3).
Start With the Two Conditions Nobody Audits
Do not start by rewriting the policy. The policy is almost certainly fine and almost certainly unread.
Pull your last 90 days of dials and answer two questions with records rather than recollection. First, for every number suppressed in that window, can you show when the suppression was captured, where it came from, and which registry file version the preventing scrub ran against? That is FTC condition four’s second half and FCC standard (D). Second, what did you do the last time a rep dialed a suppressed number? If the answer is that it has not come up, you have no monitoring and enforcement record, which is condition five, and you have it missing on a quiet month rather than a bad one.
Then ask your calling vendor one question in writing: do you participate in any arrangement that shares or divides registry access costs across your clients? Get the answer in a document. Under the FCC rule that single sentence is a condition of the defense.
Three artifacts, none of them a binder. If you cannot produce all three this week, the safe harbor you are counting on is a plan, not a defense.
Sources
- Electronic Code of Federal Regulations, 16 CFR 310.4, Abusive telemarketing acts or practices, including the do-not-call safe harbor conditions at (b)(3) and the abandoned-call safe harbor at (b)(4). https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-310/section-310.4. Reviewed November 19, 2026.
- Electronic Code of Federal Regulations, 16 CFR 310.8, Fee for access to the National Do Not Call Registry, including the $85 per area code fee, the $23,425 maximum, the first five area codes at no charge, and the prohibition on cost-sharing arrangements. https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-310/section-310.8. Reviewed November 19, 2026.
- Electronic Code of Federal Regulations, 47 CFR 64.1200, Delivery restrictions, including the national registry safe harbor standards at (c)(2)(i)(A) through (E), the internal do-not-call procedures and ten business day limit at (d)(3), and the five year honoring period at (d)(6). https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200. Reviewed November 19, 2026.
- Electronic Code of Federal Regulations, 16 CFR 310.5, Recordkeeping requirements for telemarketing, including the five year retention period. https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-310/section-310.5. Reviewed November 19, 2026.
- National Do Not Call Registry telemarketer access portal, operated for the Federal Trade Commission, covering organizational eligibility and registry file downloads. https://telemarketing.donotcall.gov/. Reviewed November 19, 2026.
Sources verified and content reviewed by the Kixie Research Team on November 19, 2026.
Ready to close more deals with Kixie?
See how Kixie's AI-powered tools can transform your sales and support operations.
Start Free Trial