Product1 publisher3 min readPublished
FCC weighs letting AI-voiced political robocalls reach cellphones without consent before the midterms
FCC opens comment on a Club for Growth petition to let political robocalls, AI voices included, reach cellphones without consent at three calls per 30 days. The National Consumer Law Center says that cap means little when any number of political groups can each claim three calls before the midterms.
The Product Desk · Product desk
Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction
What happened
- The Telephone Consumer Protection Act now requires consent before automated calls to cellphones, and callers who skip it face private lawsuits or government enforcement.
- In place of consent, the petition would require a caller to stop within 10 days of being asked to stop.
- The National Consumer Law Center warns approval would bring more unwanted automated calls and could spread misinformation and deepfakes of recognizable voices before the midterms.
- The FCC is taking public comments on its comment website under proceeding number 02-278.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- cost Lawsuit risk is what makes skipping consent expensive for callers today. Approval would take that risk away from political callers who stay inside the cap, and the people receiving the calls would carry the cost in time and attention.
- exposure With no consent step, a voter's first contact with an AI-generated political voice is the call itself, and the only remedy left is a stop request the caller can delay.
- precedent An FCC approval would accept a per-caller volume cap in place of TCPA consent for one class of calls, giving other calling groups a template to cite in their own petitions.
A voter's cellphone rings in late October, and the voice on the line sounds like a candidate she recognizes. She says stop. Under the Club for Growth petition, that caller could still place two more calls before her request has to take effect [1].
The petition presents three calls per 30 days as the limit [3]. A limit set per caller is the number the sender sees. The person holding the phone sees the total from every caller. The National Consumer Law Center's objection rests on that gap. It calls the limit "meaningless due to the multitude of political action committees, campaigns, and non-profits that could make unsolicited, AI-voice robocalls" [5].
On the stop window, the group wrote: "Allowing calls to continue for 10 days after a stop request will let political callers of any party bombard voters in the run-up to the election." [6] Techdirt, which first reported the comment call, frames it as FCC head Brendan Carr making unwanted calls easier for big companies and Republicans, while Carr insists he is tough on robocalls [11]. The NCLC's wording is broader. The opening it describes would be open to political callers of any party [6].
These calls would arrive on a network already carrying heavy unwanted traffic. Techdirt cites the YouMail Robocall Index at 3.9 billion unwanted robocalls in August, or 5.2 million an hour [9]. Spread over August's 31 days, that comes to roughly 126 million a day [2]. Techdirt adds that summer numbers generally climb once fall arrives [10].
The petition is out for comment and the FCC has not ruled [1]. Techdirt's account does not give a comment deadline or a date for a Commission vote.
The proposal is built for callers who want to reach cellphones without collecting consent first [1]. The people whose phones ring pay for it, in time. In my view, the stop window is the hardest term to defend. Honoring a stop on the next call costs a caller only the calls it would have made to someone who already said no. The 10-day window lets a caller use two of its three monthly calls after hearing that no [1].
Anyone judging a messaging limit, in this docket or in their own product, can sort it with two questions. The first is whether the limit is counted per sender or per recipient. The second is whether a stop takes effect on the next call or after a delay. A per-recipient cap with an immediate stop leaves control of the volume with the person holding the phone. A per-sender cap with a delayed stop leaves it with the callers. The two mixed cases protect only partly: a per-recipient cap still lets calls through until a delayed stop kicks in, and an immediate stop still lets each new caller in once. Read the way the NCLC reads them, the Club for Growth terms fall in the per-sender, delayed-stop box, with three calls per caller per 30 days [3] and a 10-day stop window [4].
What to watch
- Whether the FCC sets a comment deadline or schedules a vote on the Club for Growth petition in proceeding 02-278 before the midterms.
- Whether any FCC action counts the three-call cap per caller or per recipient, and whether it shortens the 10-day stop window.
- Whether YouMail's fall robocall counts climb above August's 3.9 billion, as Techdirt says they generally do.