Link Leads Blog · September 9, 2026

TCPA calling hours: what time you can legally call or text aged insurance leads

The federal window is 8am to 9pm. The part that trips up multi-state campaigns is whose 8am it is — and it isn't yours. Here's how to work out the right clock, where states cut the window shorter, and why a text has to follow the same rule as a call.

The window is simple. Whose clock it runs on isn't.

The TCPA's calling-hours rule is easy to state: telemarketing calls and texts are restricted to between 8am and 9pm. The part that catches agents working a multi-state aged list is that the clock belongs to the person you're contacting, not the one dialing. A 7am call from an agent's desk in Eastern time can still be an 8:05am call to a lead in Central, and legal — but the same 7am call to a lead in Pacific is a 4am call by their clock, three hours outside the window, regardless of what time it reads on the agent's screen. The rule is about the recipient's local time, full stop.

Finding the right time zone from a data list

A clean aged list carries a state and a ZIP code on every record — that's what fixes the time zone, not the area code on the phone number. Area codes are assigned to where a number was first issued, and mobile numbers travel with their owner across moves and area-code splits; a person can carry a 212 number to Arizona and keep it for a decade. State and ZIP are the fields that actually describe where someone lives today, so build the time-zone lookup off those columns, not off the phone number's area code. States that split across zones — Texas, Florida's panhandle, Indiana, Michigan, Kansas, Idaho — need a ZIP-to-zone table rather than a single state-level assumption, since a state-level guess will misclassify part of the list either way.

State overlays that cut the window shorter than federal

Federal 8am–9pm is a floor, not a ceiling — several states run a narrower window for telemarketing calls, and a few extend it to texts explicitly where the TCPA's text coverage is inferred rather than spelled out. Florida is the sharpest example: the state's Telephone Solicitation Act layers its own restrictions on top of the federal window and adds a private right of action, which is covered in full in our FTSA post. The practical rule for a multi-state file: build your calling-hours logic off the tightest window that applies to any state in the batch, or — better — apply each record's own state-specific window rather than one blanket schedule for the whole list. A campaign compliant in 40 states and quietly out of window in four isn't a compliant campaign.

Texting runs under the same clock as calling

Agents sometimes treat SMS as a lighter-touch channel than a phone call, but the calling-hours restriction applies to text messages the same way it applies to voice calls — a text sent at 9:15pm recipient-local time is exactly as out of window as a call placed at 9:15pm. That matters more on a texting-heavy aged-lead workflow than on a manual dial list, because SMS platforms send in bulk and a scheduled blast doesn't know it's crossing four time zones unless you tell it to. If your follow-up cadence queues a day's send as one job, split it by time zone before it fires rather than sending the whole file at your own local 9am.

Building the window into the send, not just the plan

A calling-hours rule written into a compliance doc doesn't protect anyone if the dialer or SMS platform fires on the agent's clock. The fix is operational: tag every record with a computed time zone at list load, and gate the send — whether it's a dialer campaign or a 10DLC text blast — off that field rather than off a single start time for the whole batch. Most dialers and SMS platforms support a per-record or per-segment send window; the setup cost is one field and one filter, and it's cheaper than re-running a campaign that got flagged for a handful of out-of-window contacts buried in a file of ten thousand.

Consent and reassignment don't extend the window

A calling-hours violation is independent of everything else that has to be right before a call goes out — the number still has to clear a DNC scrub and a reassigned-numbers check regardless of what time it's placed. Getting those two right and still calling outside the window is still a violation, and getting the window right doesn't substitute for the scrub. Treat calling hours as one more gate in the pipeline, not the whole compliance picture.

Not legal advice

This is a practical framework for building calling-hours logic into a campaign, not legal advice. The TCPA, state telemarketing overlays, and how courts read text-message coverage change over time and vary by state. Confirm your specific calling and texting plan with counsel before you scale a multi-state campaign.

Build the list this schedule runs on

A calling window is only useful if the list underneath it has real state and ZIP data to key off of. Link Leads sells SMS lead lists at a flat $0.012 per lead, minimum order 5,000 leads ($60), filterable by state and age band, deduped and delivered as an instant CSV with a state and ZIP on every record. Build an order in the order builder, or pull a free 100-row sample to see the fields before you wire up a time-zone lookup around them.

These are aged data leads (not consented insurance-form leads) and are not DNC-scrubbed. Buyers are responsible for DNC scrubbing and dialing/texting compliance.