Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

Is This the End of the Pre-Recorded Telemarketing Call?

New FTC rules redefine consumers' privacy rights

The Federal Trade Commission today put telemarketers on notice: spamming consumers' phones won't be allowed anymore.

In an amendment to the Telemarketing Sales Rule, the FTC outlawed several automated practices that have become common in direct marketing, including the use of prerecorded sales messages without the written consent of the target customer.

"Just like the provisions of the Do Not Call Registry, these changes will protect consumers' privacy," said FTC Chairman William Kovacic. "The amendments now directly enable consumers to choose whether they want to receive prerecorded telemarketing calls."

The amendments will not affect calls that deliver purely "informational" prerecorded messages, such as notifying a consumer that their flight has been canceled or that they have a service appointment. Such purely "informational" calls are not covered by the TSR because they don't attempt to sell any goods or services. Charities will also be able to make prerecorded calls to members or previous donors.

According to the new rules, by December 2008, sellers and telemarketers must provide an automated keypress or voice-activated interactive opt-out mechanism at the outset of each call.

The prerecorded call amendment requires that any prerecorded telemarketing call must allow the telephone to ring for at least 15 seconds or four rings before an unanswered call is disconnected. It must begin the prerecorded message within two seconds of a completed greeting by the consumer who answers. And it must disclose at the outset of the call that the recipient may ask to be placed on the company's do-not-call list at any time during the message.

In addition, the new rules state that telemarketing calls must give the called party the option to be added to the telemarketer's do-not-call list, and then immediately end the call. If the call goes into a voice mailbox, the system must provide a toll-free number that allows the consumer to be added to the telemarketer's do-not-call list.

The new rules also regulate the use of "predictive dialers" in telemarketing. These automated systems send out calls on behalf of live salespeople, but a call will sometimes connect when no sales representative is available. The TSR now requires that at least 97 percent of a telemarketer's calls that are answered in person -- not by an answering machine -- be connected to a salesperson within two seconds after a consumer answers. This is designed to minimize the number of "dead air" and "hang-up" calls that result when no salesperson is available to take the call.

The amendment that requires permission from consumers to receive pre-recorded calls will become effective Sept. 1, 2009. The amendment regarding predictive dialers will become effective on Oct. 1 of this year.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15505
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1, and Sentry before 9.7.3 and 9.8.x before 9.8.1, allow remote attackers to execute arbitrary code via unspecified vectors.
CVE-2020-15506
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to bypass authentication mechanisms via unspecified vectors.
CVE-2020-15507
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to read files on the system via unspecified vectors.
CVE-2020-15096
PUBLISHED: 2020-07-07
In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. Apps using "contextIsolation" are affecte...
CVE-2020-4075
PUBLISHED: 2020-07-07
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened via window.open. As a workaround, ensure you are calling `event.preventDefault()` on all new-window events where the `url` or `options` is not ...