The near-total cold-calling bans you should know about (CT, MS)

Why these two states stand apart

Most state telemarketing rules adjust the edges: different calling-hour windows, extra DNC registry requirements, disclosure language. Connecticut and Mississippi went further. Both enacted restrictions so broad that they effectively ban entire categories of outbound calling for many organizations.

New York and New Jersey have also added their own disclosure requirements — callers must meet specific identification obligations — but neither state went as far as an outright ban on cold outreach. CT and MS are in a different tier.

Connecticut 2023: near-total ban on consumer cold calling

Connecticut's 2023 law introduced what is widely described as a near-total ban on cold calling consumers in the state. Cold calling — reaching out to someone who has not given prior consent or has no prior business relationship — becomes heavily restricted. Organizations that previously relied on purchased Lead list data to dial Connecticut residents face a fundamentally changed operating environment.

The practical upshot for most outbound call centers: if your Connecticut-targeted campaign is built on cold prospect lists with no prior relationship, it is likely prohibited. Campaigns built on existing customers, warm leads who submitted their information, or contacts with documented Express written consent are in a different position and may still be permissible.

Mississippi 2024: Medicare cold-calling ban

Mississippi's 2024 law targets a specific vertical: Medicare. The law introduces a near-total ban on cold calling consumers specifically about Medicare. Insurance agencies, insurance marketing organizations, and lead generators focused on Medicare enrollment or plan switching are directly in scope.

This matters because Medicare marketing has been a significant outbound dialing vertical nationally, and Mississippi is not alone in scrutinizing it. The FCC and CMS have their own federal-level rules around Medicare calls. Mississippi's law adds a state-level layer on top.

How to adjust your VICIdial configuration

flowchart TD
  A[Lead Loaded into Hopper] --> B{State = CT or MS}
  B -- CT --> C{Prior relationship or consent documented?}
  C -- No --> D[Filter Out - Do Not Dial]
  C -- Yes --> E[Allow to Dial]
  B -- MS Medicare Campaign --> F{Prior relationship or consent documented?}
  F -- No --> D
  F -- Yes --> E
  B -- Other state --> E

The first step is identifying leads by state before they reach your Hopper. VICIdial's lead filtering tools let you create Lead filter rules that exclude records based on state code. For CT and MS campaigns, you can build a filter that flags records without a consent or relationship marker and routes them out before dialing begins.

For organizations running Medicare campaigns, the cleanest approach is to maintain separate campaigns for Mississippi leads and require that every record in those lists have a documented opt-in or prior relationship before loading. Do not mix warm and cold leads into the same Mississippi-targeted campaign — it creates audit risk.

NY and NJ: disclosure requirements still matter

New York and New Jersey have not gone the route of categorical bans, but they do require callers to identify themselves and disclose specific information during calls. Your Agent script should be reviewed for any NY/NJ dial-in campaigns to ensure the required disclosures appear early in the call flow.

State law changes frequently. The CT and MS restrictions are recent examples of a broader trend: states are increasingly comfortable drawing hard lines that federal law does not. Build a habit of reviewing State DNC list and regulatory changes at least once per quarter if you dial nationally.

Next steps

For a broader picture of US compliance requirements, start with the VICIdial compliance overview. Washington state's separate set of requirements — including the 10-second hang-up rule — is covered in why Washington makes you end a call within 10 seconds.

Need help structuring campaigns with proper state-level filtering built in? Review our plans to see what managed configuration support is available.