Key Dimensions and Scopes of DND
Do Not Disturb (DND) service — the telecommunications feature that silences or diverts incoming calls and notifications — operates across a surprisingly layered set of rules, boundaries, and jurisdictional considerations. What looks like a simple on/off toggle carries real regulatory weight, varies meaningfully by geography and context, and sits at the center of some of the more contested disputes in consumer telecommunications. This page maps those dimensions in detail.
- Geographic and Jurisdictional Dimensions
- Scale and Operational Range
- Regulatory Dimensions
- Dimensions That Vary by Context
- Service Delivery Boundaries
- How Scope Is Determined
- Common Scope Disputes
- Scope of Coverage
Geographic and jurisdictional dimensions
The National Do Not Call Registry, administered by the Federal Trade Commission, covers solicitation calls to U.S. telephone numbers — landlines and mobile phones alike. Registration is permanent (the FTC eliminated the previous 5-year expiration rule in 2008), but the registry's reach stops at the U.S. border. Canadian consumers operate under a separate framework: the National Do Not Call List managed by the Canadian Radio-television and Telecommunications Commission (CRTC), with a 31-day processing window before registrations take effect (CRTC National DNCL).
Within the United States, state-level DND regimes add a second jurisdictional layer. States including Florida, Indiana, and Wyoming maintain independent do-not-call lists that apply to intrastate solicitation calls — calls originating and terminating within the same state. A business that scrubs its call list against the FTC registry may still be in violation if it hasn't also checked a state-specific registry that covers intrastate traffic. The FTC's federal framework does not preempt stricter state rules; it sets a floor, not a ceiling (FTC Telemarketing Sales Rule, 16 CFR Part 310).
Scale and operational range
The FTC's National Do Not Call Registry contains more than 249 million registered phone numbers (FTC Do Not Call Registry Data Book). That scale makes it one of the largest consumer preference registries in the world, and it also illustrates the operational problem for telemarketers: list management at that volume is not a casual undertaking. Callers are required to scrub their call lists against the registry every 31 days — not once, not annually, but on a rolling monthly cycle.
The operational range of DND also extends into device-level and platform-level implementations. Smartphone DND modes, hospital quiet-hours protocols, hotel do-not-disturb signage, and workplace notification suppression systems each represent a distinct scope of application. The telecommunications regulatory framework governs the first category; the remaining three are governed by internal policy, hospitality standards, or employer communications rules — entirely separate systems sharing only a name.
Regulatory dimensions
The Telemarketing Sales Rule (TSR), codified at 16 CFR Part 310, is the federal instrument that gives the National Do Not Call Registry its enforcement teeth. Violations carry civil penalties up to $51,744 per call as adjusted for inflation (FTC TSR Penalty Adjustments). The FTC shares enforcement jurisdiction with the Federal Communications Commission, which administers the Telephone Consumer Protection Act (TCPA), codified at 47 U.S.C. § 227. The TCPA's private right of action — $500 per violation, trebled to $1,500 for willful violations — is a separate legal avenue from FTC enforcement.
These two regulatory frameworks interact without perfectly overlapping. The TCPA focuses heavily on the technology used to make calls (automatic telephone dialing systems, prerecorded messages), while the TSR focuses more broadly on the commercial relationship and the consumer's expressed preference. A caller can violate one without violating the other, which is a structural feature that generates considerable litigation.
Dimensions that vary by context
| Context | Governing Framework | Who Administers | Key Scope Limit |
|---|---|---|---|
| National telemarketing calls | FTC/TSR, 16 CFR Part 310 | Federal Trade Commission | U.S. numbers only |
| Intrastate telemarketing | State DNC lists | State AG offices | Varies by state |
| Wireless autodialing | TCPA, 47 U.S.C. § 227 | FCC + private plaintiffs | Consent-based |
| Hotel/hospitality DND | Property policy | Hotel management | Property boundary |
| Device-level DND | OS/platform policy | Apple, Google, Samsung | Device settings |
| Workplace notifications | Employer policy | HR/IT governance | Employment agreement |
| Healthcare quiet hours | CMS guidelines, JCAHO standards | Hospital administration | Patient room boundary |
The healthcare context deserves particular attention. The Joint Commission on Accreditation of Healthcare Organizations (JCAHO) maintains standards around patient rest and noise management that function as a form of institutionalized DND. These standards are not telecommunications regulations — they're patient safety protocols — but they produce the same functional outcome: a boundary around who may interrupt and when.
Service delivery boundaries
DND as a telecommunications service has hard delivery boundaries that are often misunderstood. Registration on the National Do Not Call Registry does not block all calls. The statute and rule exempt calls from political organizations, charities, telephone surveyors, and companies with an "established business relationship" (EBR) — defined as a relationship created by a transaction within the preceding 18 months or an inquiry within the preceding 3 months (FTC DND FAQ).
The EBR exemption is where most consumer frustration concentrates. A person may register their number, stop receiving cold calls from strangers, and still receive calls from a bank, insurance company, or retailer with whom they've done business — because the EBR exemption legally permits those calls. That isn't a registry failure; it's a statutory design choice embedded in the original legislation.
The DND home page provides an orientation to the full landscape of DND types, which helps clarify which of these boundary conditions applies in a given situation.
How scope is determined
The scope of DND coverage in the telecommunications context flows from four sequential determinations:
- Number type — Is the number residential, mobile, or business? Business-to-business calls are generally exempt from the registry.
- Call type — Is the call a solicitation, survey, political message, charity appeal, or EBR follow-up? Each category carries different exemption status.
- Technology used — Does the call use an automatic telephone dialing system (ATDS) or prerecorded message? TCPA consent requirements apply.
- State overlay — Does the call originate and terminate within a state that maintains its own DNC list?
These four determinations happen in sequence. A call that clears the federal registry requirement may still be barred by state law; a call that clears both may still require prior express written consent under the TCPA if it uses ATDS technology. Scope, in this context, is a nested set of conditions — not a single yes/no.
Common scope disputes
The three most litigated scope disputes in DND and TCPA enforcement center on definitional ambiguities rather than clear-cut violations.
What constitutes an ATDS? The Supreme Court addressed this in Facebook, Inc. v. Duguid, 592 U.S. 395 (2021), holding that an ATDS must have the capacity to produce telephone numbers using a random or sequential number generator — not merely store and dial numbers from a list. That ruling narrowed the TCPA's reach considerably and remains the controlling standard.
What qualifies as an EBR? The 18-month window runs from the last transaction, but "transaction" is not exhaustively defined. Whether a website visit, a quote request, or a free trial constitutes a transaction for EBR purposes has been contested in both FTC guidance and private litigation.
Who bears responsibility for third-party callers? When a business hires a telemarketing vendor that violates DND rules, liability can flow back to the business under agency principles — but only if the FTC or a court determines the business had sufficient control over or knowledge of the vendor's methods. This question of vicarious liability is actively litigated.
Scope of coverage
The clearest way to map what DND covers and doesn't cover is to distinguish between preference-based coverage (what the consumer's registration protects against) and consent-based coverage (what the consumer's prior agreement unlocks).
Preference-based coverage under the National Do Not Call Registry protects registered numbers from unsolicited commercial solicitation by for-profit entities with no prior relationship. That's the core protection — specific, but not unlimited.
Consent-based frameworks under the TCPA operate in the opposite direction: they determine when a caller may contact a number that might otherwise be protected, provided the consumer has given prior express consent (for informational calls) or prior express written consent (for marketing calls using ATDS or prerecorded messages). The FCC has issued guidance clarifying that consent must be given to a specific entity — not broadly to a category of callers — a position affirmed in its 2024 one-to-one consent rule amendments (FCC TCPA Consent Rules).
The two frameworks — preference and consent — create a coverage map that is neither a complete shield nor a complete permission slip. It's a negotiated boundary between consumer preference and commercial access, enforced imperfectly but with real financial consequences when enforcement does occur.