CONTACT

The State-Level Call Center Rules That Are Already in Play

by King White, on Oct 23, 2026, 7:00:00 AM

Washington has drawn most of the attention on call center offshoring regulation. The Federal Communications Commission’s (FCC) proposed rules on foreign call centers remain in the rulemaking process, while the Keep Call Centers in America Act hasn’t moved past being introduced over a year ago. Both are worth watching. Neither is law yet.

However, several states have their own binding requirements on the books, and those sometimes get missed. Some of these state requirements are tied to any offshore relocation, while others are tied specifically to state contracts or particular industries. For a company planning where to place, consolidate, or relocate contact center operations, that state-level patchwork is a live consideration today, not a future one contingent on Congress or the FCC finishing their work.

The Federal Picture, Briefly

Two federal actions are in motion but not yet in effect. The FCC's Notice of Proposed Rulemaking on offshore call centers closed its reply comment period in June 2026 without a final rule following. If adopted as proposed, it would impose English-proficiency standards, location-disclosure requirements, and a possible cap on the share of customer interactions handled offshore, but only for the specific categories of providers the FCC regulates: telecommunications, wireless, VoIP, cable, and satellite broadcast services and their affiliates.

The Keep Call Centers in America Act, introduced in both the House and Senate in 2025, would go further for a broader set of employers, tying federal contract eligibility and grant access to whether a company has relocated call center work offshore. There’s no vote or markup recorded as of this writing, and bills that don't advance beyond committee within the two-year congressional session expire at the end of it. Neither proceeding changes anything for a company's operations today, but both are worth tracking for what they signal about direction.

Five States Already Have Their Own Rules

While the federal proposals work through their process, several states have already moved, each with its own trigger and enforcement mechanism:

1. New York: The state's Call Center Jobs Act requires covered employers to give advance notice, generally 90 days, to the state Department of Labor before relocating a call center or moving 30% or more of its call center employees offshore. Noncompliance carries civil penalties reported as high as $10,000 per day.

2. New Jersey: A closely mirrored statute imposes similar advance-notice and disclosure obligations on covered employers relocating call center work outside the state or country.

3. Connecticut: Rather than a notice requirement, Connecticut restricts state contract awards to companies operating offshore call centers, effectively excluding offshore-reliant vendors from state procurement.

4. Missouri: An executive order from the state's Office of Administration requires disclosure of offshore call center use for companies performing state-contract work.

5. Florida: Florida's rules take a narrower, industry-specific approach, restricting the offshore handling of medical information by covered healthcare entities rather than regulating call center location generally.

Each of these operates on its own trigger, threshold, and enforcement mechanism, and none are simply smaller versions of the federal proposals. A company's exposure depends heavily on its business model: A retailer relocating a general customer service line faces a different set of questions than a healthcare company handling protected medical information, or a government contractor bidding on state work.

Why This Belongs in Site Selection, Not Just Legal Review

It's tempting to treat this as a legal compliance question after a location decision is made rather than as part of the site selection process. That sequencing works less well than it used to. A company consolidating multiple regional contact centers into a single hub, for example, may trigger New York's or New Jersey's advance-notice requirement simply by exiting a location in one of those states, regardless of where the new hub is located. A company bidding on state government contracts in Connecticut or Missouri may find its existing offshore vendor relationship disqualifying, independent of cost or quality, in a way that only surfaces once the bid is already underway.

These aren't hypothetical edge cases; they're structural consequences of where a company already operates and the customers it serves. That makes state-level regulatory exposure a genuine site selection input, not a downstream legal formality, particularly for companies with a multistate footprint, government contract exposure, or regulated data in scope.

State implications of call center site selection are also a moving target: State legislatures have introduced call center and offshoring-related bills for years beyond these five states, tracked for over a decade by organizations that follow global sourcing policy. The number of states with active requirements has grown, not shrunk, over time.

The potential exposure compounds for companies operating simultaneously in more than one of these states. A financial services or insurance company with government contract work in Missouri, customer service operations touching New York and New Jersey, and health-adjacent data in Florida isn't dealing with one compliance question. It’s dealing with four separate ones, each triggered by a different part of the business, and each requiring its own review rather than a single blanket policy.

What This Looks Like in Practice

A multistate retailer consolidating three regional call centers into one national hub identified its preferred new location based on labor cost and infrastructure, standard site selection criteria, without mapping the states it was exiting against each state's notice requirements. Only after signing a new lease did the company learn that closing one of its existing locations, in a state with an advance-notice statute, required a filing it hadn't anticipated and a notice period that pushed its planned transition timeline back by several months. None of the underlying real estate or labor analysis was wrong. The regulatory footprint simply hadn't been evaluated alongside it.

A separate scenario shows up often in regulated industries. A healthcare-adjacent company evaluating an offshore customer service vendor for general inquiries assumed its Florida-specific medical-information restriction wouldn't apply, since the offshore team wasn't handling clinical data directly. A closer review found that some of the customer interactions in scope did touch protected health information incidentally, enough to bring the arrangement within the statute's reach. The fix was manageable, a narrower carve-out of which interaction types could be routed offshore, but only because it was caught during vendor selection rather than after the contract was signed.

Building State Requirements Into the Site Selection Process

A few practices reduce this exposure:

  • Map current and target contact center locations against known state-specific onshoring, disclosure, and industry-specific laws before finalizing any relocation or consolidation plan, not after.
  • Separate general relocation-notice laws (New York, New Jersey) from state-contract-specific restrictions (Connecticut, Missouri) and industry-specific rules (Florida), since applicability depends heavily on the company's business model and customer base.
  • Build this review into the same timeline as labor, cost, and incentive analysis, rather than treating it as a legal afterthought addressed after a site is chosen.
  • Revisit the list regularly. It's reasonable to expect more states to add requirements over the next several years, not fewer.
  • Involve qualified legal counsel early for company-specific applicability determinations. This overview is general information, not legal advice, and each statute's scope and enforcement mechanism should be confirmed against its current text.

Where Location Strategy Meets Regulatory Geography

This is exactly where location strategy and regulatory geography now intersect. A site that scores well on labor cost, infrastructure, and incentive potential can still create real exposure if the regulatory footprint of the departure and destination states aren’t mapped alongside it. We work alongside a company's own legal counsel rather than replacing it, so the recommendation reflects the full picture rather than the cost model alone.

If your company is evaluating a contact center consolidation or relocation across multiple states, particularly if government contracts or regulated data are part of the picture, it's worth mapping this exposure before a site is finalized, not after.

Topics:Contact Centers

Comments

More

Blog Posts →

Read

News →

View

Success Stories →