The bill directs the Federal Communications Commission to establish an interagency taskforce focused on unlawful robocalls—with particular attention to calls that originate outside the United States—and to produce a comprehensive report with recommendations for agencies and Congress. It sets deadlines for formation and reporting, prescribes who may sit on the taskforce (federal agency representatives plus seven private-sector designees), and requires the taskforce to analyze technical, enforcement, and international-cooperation options.
Separately, the measure authorizes the FCC to require providers to post bonds (up to $100,000) before filing certifications in the Robocall Mitigation Database, while directing the agency to define exemptions and limit burdens on bona fide providers. It amends the TRACED Act to change one required FCC notice frequency, and it adds statutory immunity for a registered private traceback consortium to receive, share, and publish detailed trace back information—alongside an express ability to publish lists of voice providers that refuse to participate or are found to originate many unlawful calls.
Together, these changes expand enforcement tools, reallocate information rights, and raise compliance costs and privacy/operational questions for service providers and policy teams.
At a Glance
What It Does
The bill requires the FCC—after consulting the FTC and Attorney General—to create a taskforce within 270 days and deliver a report within 360 days of the taskforce’s formation; the taskforce will analyze foreign-origin robocalls, call-authentication standards, international cooperation, and enforcement options. The FCC may adopt rules requiring certain providers to post a bond (capped at $100,000) before filing Robocall Mitigation Database certifications, with categorical exemptions for established providers. The statute adds immunity for a registered private traceback consortium to receive, share, and publish traceback data and allows publication of provider lists that decline to participate or are high-volume sources of unlawful calls.
Who It Affects
Telecom compliance and security teams at voice service providers and gateway operators; providers that file Robocall Mitigation Database certifications (including smaller VoIP entrants); members and potential members of the private traceback consortium; federal agencies involved in telecommunications enforcement (FCC, FTC, DOJ); and consumer-advocacy organizations and businesses that communicate by phone. It also has international implications for foreign carriers and regulators that originate or transit calls to the U.S.
Why It Matters
The bill couples technical-policy work (STIR/SHAKEN and traceback) with new administrative and private-sector powers (bonds, listings, and immunity) that could change how operators approach risk, disclosure, and international cooperation. Compliance costs and reputational risk may increase for providers outside established regulatory channels, while private traceback activity would gain statutory protection—shifting both incentives and operational practices in anti-robocall efforts.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Foreign Robocall Elimination Act tasks the FCC with assembling a focused interagency group to map the scale and sources of unlawful robocalls that come into the United States from abroad. The taskforce must include representatives from federal agencies selected by the FCC chair and seven named private-sector slots—ranging from voice carriers and technologists to a Consortium representative, a marketing business, a non-marketing communicator, and a consumer-advocate organization.
Private-sector appointees are to be jointly selected by the FCC Chair, the FTC Chair, and the Attorney General; if those officials cannot agree, the FCC Chair can appoint with a brief notice-and-vote safety valve for commissioners.
The taskforce’s deliverable is a single, time-bound report with concrete studies and recommendations. The bill lists a broad menu of subjects for analysis: estimating domestic versus foreign-origin unlawful call volumes, identifying high-volume foreign source countries, measuring financial loss and identity-theft impacts, assessing whether STIR/SHAKEN provides adequate authentication for foreign-origin calls, and exploring incentives and technical options to encourage foreign adoption of authentication standards.
The taskforce must evaluate whether additional DOJ resources or a dedicated DOJ office for robocall enforcement would be useful, whether criminal penalties indexed to call volume would deter abuse, and whether periodic public disclosure of certain traceback results would help or harm investigations and countermeasures.On the enforcement and operational side, the bill gives the FCC authority to require a bond—no greater than $100,000—before some providers may file a certification in the Robocall Mitigation Database, but it also instructs the agency to create exemption criteria. The statutory factors for exemption include whether a provider is registered with the FCC, contributes to universal service, holds state-level authority, is publicly listed, or otherwise shows indicia of bona fide operation.
The FCC must balance deterrence against creating needless burdens for established, regulated providers.Finally, the bill amends the TRACED Act to grant a registered private traceback consortium explicit immunity from civil suits for receiving, sharing, and publishing covered traceback information (defined to include call-detail records, provider identities, and some initiator contact information). It also permits the Commission or the consortium to publish lists of voice service providers that refuse to participate in traceback efforts or that are found to originate or transmit substantial volumes of unlawful robocalls; the FCC may use such information as a basis for enforcement.
The taskforce itself is temporary: it ends 90 days after submitting its required report to Congress.
The Five Things You Need to Know
Taskforce composition: federal agency representatives selected by the FCC chair plus seven private-sector slots—three technical/anti-robocall experts, one Consortium rep, one marketing-business rep, one regular non-marketing telephone communicator, and one consumer-advocacy rep.
Appointment mechanics: private-sector taskforce members are jointly appointed by the FCC Chair, FTC Chair, and Attorney General; if they deadlock, the FCC Chair may appoint after 48 hours’ notice unless a commissioner demands a Commission vote.
Bond rule: the FCC may require a provider to post a bond (not to exceed $100,000) before filing a Robocall Mitigation Database certification, but must create categorical exemptions—factors include FCC registration, state certificates, exchange listing, and other indicia of bona fide operation.
Traceback immunity and definition: the bill adds statutory immunity for a registered Consortium to receive, share, or publish ‘covered information’—explicitly including call detail records, identities of originating/transmitting voice providers, and initiator contact details—against civil suits.
Publication and enforcement power: the Commission or the registered Consortium may publish a list of voice providers that refuse to participate in private traceback efforts or are found to originate or transmit substantial unlawful robocall volumes, and the FCC may take enforcement action based on that information.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Names the statute the 'Foreign Robocall Elimination Act.' Practical effect: none beyond labeling, but useful for cross-references and administrative guidance and rulemaking citations.
Interagency taskforce: definitions, setup, membership, report, funds, termination
Defines key terms (Commission, Consortium, unlawful robocall) and requires the FCC—after consulting FTC and DOJ—to establish a taskforce within 270 days. Membership rules set a two-part roster: federal agency reps chosen by the FCC Chair (based on agency head recommendations) and seven private-sector slots with specified roles. The bill prescribes joint appointment authority for private members and creates a tie-breaker process that lets the FCC Chair appoint after brief notice unless Commissioners demand a formal vote. The taskforce must submit a report within 360 days of formation and terminates 90 days after report submission; funds from existing appropriations may be used for participation.
Comprehensive study on foreign-origin robocalls and recommended actions
The statute lists detailed study items the taskforce must address: relative volumes of domestic vs. foreign-origin unlawful calls, countries sending the highest volumes, financial and identity-theft impacts, options for encouraging foreign adoption of caller-authentication (including STIR/SHAKEN), traceback implementation issues, incentives for foreign cooperation, resource gaps at federal agencies, the potential utility of a DOJ office focused on robocall enforcement, criminal-penalty structures tied to call volume, and whether public disclosure of traceback results helps or harms mitigation and investigations. That level of specificity narrows the taskforce’s remit and signals congressional interest in both technical standards and enforcement resourcing.
TRACED Act amendment — FCC notice frequency change
Amends Section 13(d)(2) of the TRACED Act to change the required FCC notice frequency from annually to once every three years. That adjustment reduces the cadence of a statutorily required FCC notification and could affect how often the Commission collates or publishes certain updates tied to the TRACED Act.
Robocall Mitigation Database: bond requirement, exemptions, implementation guidance
Directs the FCC to issue rules permitting it to require a bond (up to $100,000) before a provider files a Robocall Mitigation Database certification, but only if the bond is necessary to preserve the Database’s integrity. The statute obliges the Commission to establish exemption criteria—considering FCC registration, state authority, exchange listing, and other bona fides—and to minimize burdens on compliant providers. The FCC must target bonds at providers that do not demonstrate legitimate operations, regulatory oversight, or ability to satisfy fines and forfeitures, and create categorical exemptions for identifiable classes of legitimate providers.
Registered Consortium immunity and publication authority
Adds an immunity provision to the TRACED Act for a registered private traceback Consortium: no civil cause of action may be maintained against the Consortium for receiving, sharing, or publishing 'covered information'—a term that includes call-detail records, identities of providers that originated/transmitted calls, and initiator contact data. The bill also allows the Commission or the Consortium to publish lists of voice providers that refuse to participate in private traceback efforts or that are found to originate/transmit substantial unlawful call volumes, and it explicitly authorizes the FCC to use such information as a basis for enforcement.
This bill is one of many.
Codify tracks hundreds of bills on Technology across all five countries.
Explore Technology in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Consumers and potential victims of phone fraud — the bill targets foreign-origin sources and funds studies that could lead to stronger international cooperation and technical fixes, which may reduce fraud exposure and identity theft from unlawful robocalls.
- Federal law enforcement (DOJ) and regulators (FCC, FTC) — the taskforce supplies a focused evidence base on volumes, foreign sources, and resource gaps and explicitly asks whether a dedicated DOJ office and adjusted penalties would help enforcement, strengthening decision-ready intelligence.
- Private traceback Consortium and participating providers — statutory immunity for receiving, sharing, and publishing trace back information lowers litigation risk and may encourage broader participation and more aggressive information-sharing among private actors.
- Compliant, established voice providers — the exemption criteria and direction to minimize burdens aim to shield incumbent, regulated carriers from unnecessary bonding and paperwork, preserving their ability to operate without disproportionate compliance costs.
- Consumer-advocacy organizations and businesses that rely on phone outreach — having a place on the taskforce ensures their concerns about overblocking, privacy, and legitimate communications are heard in formulating recommended practices.
Who Bears the Cost
- Smaller or unregistered VoIP and international gateway providers — the bond requirement and risk of being publicly listed could impose cashflow burdens, raise compliance costs, and deter market entry for providers without state licensing or FCC registration.
- Voice service providers flagged in published lists — being named as a non-participant or high-volume originator carries reputational harm and may trigger enforcement action, customer loss, or routing/peering restrictions from downstream providers.
- The registered Consortium itself — while granted immunity, the Consortium will face operational pressure to vet, curate, and publish traceback data responsibly and may need resources to defend against non-litigation consequences (e.g., reputational pushback, retaliation, or data-subpoena demands).
- Federal agencies with unfunded obligations — the taskforce may recommend additional DOJ, FCC, or FTC resources, but the bill permits use of existing appropriations; if Congress does not provide new funding, agencies could face unfunded mandates to increase international coordination and enforcement.
- Legitimate foreign carriers and regulators — pressure to adopt STIR/SHAKEN or participate in U.S.-led traceback efforts could create diplomatic friction and compliance costs for foreign operators not structured to meet U.S. regulatory expectations.
Key Issues
The Core Tension
The central dilemma is between increasing the information and enforcement tools needed to stop large-scale, foreign-origin robocall campaigns and protecting legitimate providers, investigative integrity, and individual privacy: stronger incentives for traceback and public naming can accelerate mitigation today but risk collateral damage—blocking lawful carriers, exposing investigative techniques, and reducing trust that undermines long-term international cooperation.
The bill stacks three distinct policy tools—research (taskforce/report), administrative conditioning (bonding for Robocall Mitigation Database filings), and legal immunity/publication authority for private tracebacks—into a single push against foreign-origin unlawful robocalls. That mix raises implementation questions.
First, calibrating the bond regime is delicate: a bond large enough to deter fraud-enabling shell providers could also block legitimate small providers and new entrants, while a too-modest bond may be ineffective. The statutory factors for exemption help, but applying them consistently across diverse provider types (domestic incumbent, small VoIP reseller, foreign gateway) will require detailed rulemaking and verification infrastructure.
Second, the immunity for the registered Consortium increases private-sector willingness to share trace back material, but it also reduces avenues for injured parties to challenge inaccurate or defamatory publications. The statute contemplates publishing provider lists and some traceback data; doing so risks chilling cooperation, exposing investigative methods, revealing proprietary routing relationships, and prompting retaliatory behavior by bad actors who adapt to avoid detection.
The bill asks the taskforce to study whether disclosure would improve or undermine mitigation, but Congress has already created an immunity shield that could be difficult to roll back if harmful effects appear.
Third, the bill targets foreign-origin calls but offers no direct mechanism for compelling foreign carriers or regulators to act; it instead leans on incentives, publication, and technical persuasion (e.g., encouraging STIR/SHAKEN adoption abroad). That approach risks diplomatic and practical limits: carriers in some source countries may lack the regulatory framework or motivation to implement authentication, and aggressive U.S. publication or enforcement could complicate international cooperation.
Finally, the proposal raises privacy and data-governance questions—call-detail records and initiator contact information are sensitive; the bill does not prescribe safeguards around retention, access controls, or minimization for published or shared data, leaving those details to agency rulemaking or Consortium practice.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.