Keep Call Centers in America Act: 2025 Status and Summary

Keep Call Centers in America Act: 2025 Status and Summary

ON THIS PAGE

Written by: Matt Beucler, CEO, Plura AI

Key Takeaways

  • The Keep Call Centers in America Act (S.2495 / H.R.4954) remains stalled at the Introduced stage with no committee movement through June 2026.
  • Both bills would require public disclosure of offshoring, restrict certain federal funding, mandate 120-day advance notice, and require consumer disclosure when AI or offshore agents are used.
  • Parallel FCC and state rules already create enforceable limits on offshore handling of sensitive data and call-center operations.
  • Contact-center operators are already reviewing 100% U.S.-infrastructure AI platforms to match the onshoring direction reflected in the legislation.
  • Plura AI delivers an FCC-licensed, 100% U.S.-infrastructure platform that supports compliance with TCPA, HIPAA, SOC 2, and state rules.1 Start a conversation with Plura today.

Current Legislative Status

Bill Introduced Committee Referral Current Stage
S.2495 July 29, 2025 Senate Committee on Commerce, Science, and Transportation Introduced, no further action recorded
H.R.4954 August 12, 2025 House Committees on Energy and Commerce; Education and Workforce; Oversight and Government Reform; Armed Services Introduced, no further action recorded

All data points in the table above come from the Congress.gov bill pages for S.2495 and H.R.4954.

Core Requirements in S.2495 and H.R.4954

Both S.2495 and H.R.4954 share the same basic structure.2 The provisions below reflect the bill text as summarized by Integrity Staffing and the Congress.gov bill pages.

  • Public disclosure list. The U.S. Department of Labor (DOL) would publish and maintain a public list of companies that relocate call-center jobs offshore, modeled on the existing Worker Adjustment and Retraining Notification (WARN) database.
  • Federal funding restrictions. Companies that offshore call-center work could lose eligibility for specified federal grants and loans, including some Small Business Administration (SBA) programs.
  • Federal contract requirement. Call-center work tied to federal contracts would need to occur inside the United States.
  • Advance notice. Companies planning to move call-center operations offshore would need to provide at least 120 days of notice to the DOL.
  • Consumer disclosure. Companies would disclose to customers when they are speaking with an offshore agent or interacting with AI in customer conversations.

Industries identified as most affected include healthcare, insurance, financial services, e-commerce and retail, logistics, technology, and government contractors. Understanding when these bills were introduced and how far they have moved helps leaders gauge near-term operational risk.

Review Plura pricing tiers and platform capabilities

Legislative Timeline and Activity

S.2495 was introduced in the Senate by Sen. Ruben Gallego (D-AZ) on July 29, 2025. The bill was read twice and referred to the Senate Committee on Commerce, Science, and Transportation on the same date. No markup, amendment, or vote has been recorded since that referral.

H.R.4954 was introduced in the House by Rep. Kristen McDonald Rivet (D-MI-8) on August 12, 2025. The bill was referred to four House committees on the date of introduction. No markup, amendment, or vote has been recorded since that referral.

As of June 2026, both bills remain at the Introduced stage within the 119th Congress (2025-2026), with no legislative movement beyond initial committee referral.

Cosponsors and Committee Movement

Cosponsor data for S.2495 and H.R.4954 appears on the respective Senate and House bill pages on Congress.gov. Readers can use those pages for current cosponsor counts and party distribution, which Congress.gov updates in real time.

Neither the Senate Committee on Commerce, Science, and Transportation nor any of the four House committees of referral has recorded a hearing, markup session, or vote on either bill through June 2026.

Likelihood of Passage in the 119th Congress

Both S.2495 and H.R.4954 hold Introduced status with no recorded committee movement through June 2026. Bills that do not advance beyond committee referral within a two-year congressional session expire at the end of that session without becoming law. The 119th Congress runs through January 2027, and no markup, hearing, or floor vote has been scheduled for either bill as of the date of this update.

Operators and compliance teams tracking these bills should consult qualified legal counsel for guidance on how the current legislative posture relates to their specific contractual and operational obligations. This article describes the legislative record and related measures; it does not provide legal advice.

Related Federal and State Onshoring Measures

S.2495 and H.R.4954 sit within a broader federal and state environment that already creates enforceable obligations for covered operators.

FCC NPRM CG Docket No. 26-52. The Federal Communications Commission (FCC) issued a Notice of Proposed Rulemaking (NPRM) under CG Docket No. 26-52. The proposal would cap offshore customer-service calls at 30% and prohibit offshore handling of sensitive consumer data, including passwords, multi-factor authentication credentials, Social Security numbers, and banking and card data. The NPRM is a proposed rule, not a final rule, and its provisions move through the formal rulemaking process.

State measures. Several states have enacted or proposed laws that restrict offshore handling of consumer, medical, or financial data.

  • New York – The Call Center Jobs Act requires companies to notify the DOL before relocating call-center operations and authorizes penalties up to $10,000 per day for non-compliance.
  • New Jersey – A mirror statute creates similar advance-notice and disclosure requirements for covered employers.
  • Connecticut – The Connecticut General Assembly has adopted state-contract restrictions on offshore call-center arrangements.
  • Missouri – An executive order from the Missouri Office of Administration requires offshore disclosure for state-contract work.
  • Florida – Florida statutes limit offshore handling of medical information for covered entities.

Secondary coverage of these state measures appears in publications from Littler, JD Supra, and Polsinelli.4 Operators can work with qualified counsel to assess how these state measures relate to their specific operations.

See how Plura plans align with your compliance requirements

Operational Impact for Contact-Center Leaders

Even at the Introduced stage, S.2495 and H.R.4954 influence procurement decisions. Contact Center Leaders, Chief Compliance Officers (CCOs), and CX executives at healthcare plans, insurers, financial services firms, and franchise networks are already reviewing whether their current vendor infrastructure aligns with the onshoring direction these bills signal, especially alongside the FCC NPRM and active state laws.

Analysis from Everise notes that passage of the Keep Call Centers in America Act would likely accelerate adoption of agentic AI and automation as operators work to reduce cost per call and allow fewer domestic agents to handle growing volumes.4 That pattern matches McKinsey research on contact-center modernization. U.S. contact centers already see 35% to 45% annual agent turnover, and onshoring mandates would intensify that labor pressure.3

Plura AI is an FCC-licensed platform of AI agents that runs voice, SMS (Short Message Service), RCS (Rich Communication Services), and webchat conversations on 100% U.S. infrastructure. This domestic architecture extends across every layer of the stack, so voice origination, model hosting, data storage, and call recording all sit on U.S.-based infrastructure. The platform architecture goes further by removing third-party routing dependencies, since Plura owns its own FCC-licensed audio bridging carrier rather than routing through a Communications Platform as a Service (CPaaS) provider. Branded caller ID is issued at the carrier level, and compliance support is enforced at origination rather than added later in the flow.

Screenshot of Plura’s fully compliant AI communications platform showing business registration and phone number provisioning workflows for AI Voice, SMS, RCS, and Webchat communication automation.
Plura’s FCC-licensed AI communications platform simplifies compliant business registration and phone number provisioning for AI Voice, SMS, RCS, and Webchat workflows.

Plura supports compliance with TCPA (Telephone Consumer Protection Act, 47 U.S.C. § 227), DNC (Do Not Call) registry requirements, HIPAA (Health Insurance Portability and Accountability Act, 45 CFR Parts 160, 162, and 164), SOC 2 (System and Organization Controls 2, per AICPA Trust Services Criteria), and 50+ state rule sets.1 Real-time DNC scrubbing checks every outbound contact before dial. Consent records are timestamped and immutable. Quiet-hours rules apply automatically through time-zone detection. Customers remain responsible for their own regulatory obligations and certifications, and Plura provides the infrastructure layer that supports those obligations.

Plura Security & Compliance dashboard highlighting SOC 2, ISO, and GDPR standards with secure trust verification management.
Plura Security & Compliance supports SOC 2, ISO, and GDPR standards with trust registration, verification management, and secure AI communications.

Healthcare, insurance, and financial services operators are asking whether their current AI or BPO (Business Process Outsourcing) vendor can demonstrate 100% U.S. infrastructure by architecture instead of by contractual language alone. Plura’s architecture answers that question at the carrier level for teams that need clear evidence for compliance, security, and procurement review.

Conclusion for CX and Compliance Teams

As of June 2026, the Keep Call Centers in America Act (S.2495 / H.R.4954) remains stalled at the Introduced stage in the 119th Congress, as detailed above. The surrounding regulatory environment, including the FCC NPRM under CG Docket No. 26-52 and active state laws in New York, New Jersey, Connecticut, Missouri, and Florida, already creates concrete compliance considerations for covered operators.

Compliance officers and CX executives tracking S.2495 and H.R.4954 can bookmark the Congress.gov bill pages for S.2495 and H.R.4954 for real-time updates, and can consult qualified legal counsel on how the current landscape relates to their operations.

Operators evaluating 100% U.S.-infrastructure platforms that align with the onshoring direction these bills represent can review Plura capabilities and pricing tiers directly.

Explore Plura’s U.S.-infrastructure platform options

Frequently Asked Questions

What is the current status of the Keep Call Centers in America Act as of June 2026?

Both S.2495 (Senate) and H.R.4954 (House) remain at the Introduced stage in the 119th Congress. S.2495 was introduced on July 29, 2025, and referred to the Senate Committee on Commerce, Science, and Transportation. H.R.4954 was introduced on August 12, 2025, and referred to four House committees: Energy and Commerce; Education and Workforce; Oversight and Government Reform; and Armed Services. Neither bill has recorded a hearing, markup, amendment, or vote through June 2026. Bills that do not advance beyond committee referral within the two-year congressional session expire at the end of that session. Operators can consult qualified legal counsel for guidance on how this legislative posture relates to their specific obligations.

What would the Keep Call Centers in America Act require if it became law?

The bills would direct the Department of Labor to publish a public list of companies that relocate call-center jobs offshore. Companies that offshore call-center work could lose eligibility for certain federal grants and loans, including SBA programs. Call-center work tied to federal contracts would need to be performed inside the United States. Companies planning to move operations offshore would need to provide at least 120 days of advance notice to the DOL. The bills also include consumer disclosure requirements for offshore agent interactions and AI use in customer conversations. These provisions remain proposed, not enacted, as of June 2026.

How does the FCC NPRM CG Docket No. 26-52 relate to S.2495 and H.R.4954?

The FCC NPRM under CG Docket No. 26-52 is a separate federal regulatory action that proposes capping offshore customer-service calls at 30% and prohibiting offshore handling of sensitive consumer data such as passwords, Social Security numbers, and banking information. S.2495 and H.R.4954 are congressional bills that would move through both chambers and require presidential signature. The NPRM follows the Administrative Procedure Act rulemaking process. Both the legislative bills and the NPRM reflect a policy direction toward onshoring call-center operations, but they proceed through different legal mechanisms and timelines. Operators can monitor both tracks and work with qualified counsel on their specific exposure.

Which industries face the most direct exposure to the Keep Call Centers in America Act?

Industries most directly affected by the bill provisions include healthcare, insurance, financial services, e-commerce and retail, logistics, technology and consumer products, and government contractors. Healthcare plans that receive a significant share of revenue from Medicare and Medicaid face particular exposure to the federal funding restriction provisions. Financial services and insurance operators that handle sensitive consumer data face overlapping exposure from both the proposed legislation and the FCC NPRM sensitive-data proposals. Government contractors with offshore call-center arrangements would see the most immediate operational impact from the federal contract performance requirement.

What infrastructure attributes are operators reviewing in response to the onshoring direction of these bills?

Compliance officers and CX executives are reviewing whether their current AI or BPO vendor infrastructure can demonstrate 100% U.S.-based voice origination, model hosting, data storage, and call recording by architecture rather than by contractual promise alone. Key attributes include whether the vendor holds its own FCC carrier license rather than routing through a third-party CPaaS, whether branded caller ID is issued at the carrier level, whether DNC scrubbing and TCPA consent logging are enforced at the platform layer, and whether the vendor’s compliance posture supports HIPAA, SOC 2, and the 50+ state rule sets that already create enforceable obligations independent of S.2495 and H.R.4954. Plura runs on 100% U.S. infrastructure by architecture and operates as its own FCC-licensed audio bridging carrier, supporting operators who need to demonstrate domestic infrastructure posture to their compliance teams, counsel, and procurement reviewers.


1 Plura AI maintains SOC 2, HIPAA, ISO, and GDPR posture as part of its platform infrastructure. References to compliance frameworks in this article describe Plura’s platform capabilities and do not constitute a guarantee that any customer using Plura will themselves be compliant with applicable laws or standards. Customers remain solely responsible for their own regulatory obligations, certifications, consent management, recordkeeping, and the claims they make to their own end users. Consult qualified legal counsel for guidance specific to your use case.

2 This article describes regulatory frameworks at a general level and does not constitute legal advice. Laws and regulations vary by jurisdiction, change over time, and apply differently depending on facts and circumstances. Readers should consult qualified legal counsel before making compliance decisions.

3 Performance figures, customer outcomes, and industry statistics referenced in this article are drawn from cited third-party sources or Plura customer case studies. Individual results vary based on implementation, use case, industry, audience, and execution. Past or aggregate performance is not a guarantee of future results.

4 References to third-party products, services, companies, or research are made for informational and comparative purposes only. Plura AI is not affiliated with, endorsed by, or sponsored by any third party named in this article unless explicitly stated. Trademarks and product names referenced remain the property of their respective owners.

This article is provided for informational purposes only and reflects Plura AI’s understanding at the time of publication. Product capabilities, integrations, and specifications are subject to change. For the most current information, visit plura.ai.

This article was produced with the assistance of AI tools and reviewed by Plura AI prior to publication.

See how Plura AI transforms AI voice agents